So 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 t

So 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.