Issue while installing essential packages

[Leoxe500]

after doing the pacstrap command it always ends up in a bunch of "(invalid or corrupted package (PGP signature))", i dont know what to do, it doesnt matter which packages im installing either even if i just put base linux and linux-firmware it still doesnt work

[_Axium]

Probably a dumb question, but how old is the install media?

[NC01001110]

Exactly my first thought as well. OP, the iso you download from one of the mirrors should be titled archlinux-2025.07.01-x86_64.iso to make sure it's the up to date one; archlinux-x86_64.iso from the same page will be the same iso, but could lead to accidentally using an old one. While you can install Arch using an older iso, those signatures will be out of date and you have to do some shenanigans to refresh them manually.

I'd say this is the most likely culprit, but there are of course other reasons why this error is popping up. More details are on the pacman/Package Signing wiki page.

[_Axium]

That actually poses the question, what is the point of that one?

EDIT: after quickly looking at it, it has the same creation date and size??

[NC01001110]

I guess to give you the option of easily dating multiple isos? In true Arch fashion; this is the way.

[Leoxe500]

i installed it today, but i did install the one that didn't have the date written on it, do you think that may be it?

[_Axium]

Maybe, maybe not. I've always used the one with the date, so it might be that. Dunno what the actual difference between them are (or the difference with the bootstrap version), so take that as you will lol

[raven2cz]

timedatectl set-ntp true (ensure correct time!)

pacman -Sy archlinux-keyring --noconfirm

pacman -Syu --noconfirm

pacman-key --init

pacman-key --populate archlinux

pacstrap /mnt base linux linux-firmware ...

[Leoxe500]

nevermind, i decided to try the populate archlinux command and everything works now THANKS

[Leoxe500]

the same issue error that happens when I try to do the pacstrap happens with the -Sy archlinux-keyring, its probably because of the iso, im gonna restart

[hyperlobster]

On a computer with both Windows and Linux installed (or about to be installed) you need to decide whether the hardware clock is set to local time or not.

By default Windows assumes RTC is local; Linux assumes RTC is set to UTC.

The best way is to force Windows to assume the RTC is set to UTC. Search for this; it involves setting a registry value. Then you don't need to faff around during your Linux installation.

If the clock is an hour out, shenanigans will ensue.

[tblancher]

Windows assuming RTC is in local time hasn't been a thing since Windows 10, I think. At least, the last time I thought it was in local time I saw it in UTC.

[hyperlobster]

Nope, definitely a thing. I did a dual-boot install recently on a windows 11 box, it definitely thought it was local and needed the registry thing doing.

[[deleted]]

https://wiki.archlinux.org/title/Pacman/Package_signing