Wednesday, November 08, 2017
Odd Windows DST bug
Computer was being balky so I did a System Restore. Today is 11/8, after change from DST to standard. The restore point was 11/4, before the change, still in DST.
Before restore, the computer's clock agreed with other clocks, all standard time. After restore, the computer is now ONE HOUR EARLIER than other clocks. If Win was trying to make everything agree with the restore, the computer clock should have moved forward, not backward.
I wonder if the oddness happened because I made the restore during the 1AM to 2AM hour? In any case a restore shouldn't cause a clock adjustment at all. The clock should simply use today's date to set DST mode.
Later: The balkiness seems to be AVG's Resident Shield Service, which previously stayed inert most of the time. Now it's always active and sometimes hyperactive, consuming all of the CPU. This problem is mentioned in several online forums but I don't see a solution yet.
¶ 2:15 AM 
