Okay, so I got smart an realized that this whole time I'd assumed that the fault was with Arch, simply because it detected the error.

False.

Windows was set to the wrong time zone, so when I booted into it, it set the to that time zone time, and a subsequent reboot by Arch was then seen as the last boot having been in future time.

Sorry for the noise.

-- Chris

Reply via email to