4 ms·
I multiboot Windows 10 Pro and a variety of Unixen. Been doing it for decades and it's been getting harder lately because Microsoft's updates have been acting m
by __MatrixMan__ 6y ago
I multiboot Windows 10 Pro and a variety of Unixen. Been doing it for decades and it's been getting harder lately because Microsoft's updates have been acting more and more like they own the place.
The most recent nag-you-to-use-edge update didn't just forget to restore the defaultness of my Arch EFI entry--a mistake I could forgive--it deleted it. Luckily I could boot into Debian and restore the entry because the asshats at Microsoft didn't expect there to be a second Linux lying around.
Also, it somehow discovered that I'm not I'm Greenwich, and changed my hardware clock to local time (thereby confusing the other OS'es).
Not sure what telemetry mattnewton was talking about, but I can confirm that in general, Microsoft updates are not to be trusted.
I just booted Windows for the first time this month earlier this evening. Saw it installing updates when I shut it down. God knows what messes I'll be cleaning up in the morning.
- GoblinSlayer 6y agoMaybe you have a setting in EFI that the clock is in local time, but just shifted it to show UTC?
- __MatrixMan__ 6y agoSo far as I know, Windows always expects the hardware clock to be in local time. I found some registry hack that fixes this, and I think that the update broke the hack which later triggered a network time sync. Admittedly the situation was a bit janky in the first place, so I might share some blame in that case.