+- Geeks for your information (https://www.geeks.fyi)
+-- Forum: Windows (https://www.geeks.fyi/forumdisplay.php?fid=12)
+--- Forum: Tips and tricks (https://www.geeks.fyi/forumdisplay.php?fid=23)
+--- Thread: Some Windows 10 Clocks Didn’t “Fall Back,” Here’s How to Fix It (/showthread.php?tid=4397)
Some Windows 10 Clocks Didn’t “Fall Back,” Here’s How to Fix It - harlan4096 - 05 November 18
![[Image: img_5bdf4ecf1feb0.png]](https://www.howtogeek.com/wp-content/uploads/2018/11/img_5bdf4ecf1feb0.png)
Quote:Daylight Savings Time ended at 2 a.m., but at least one of our Windows 10 PCs didn’t notice. Windows 10 is set to automatically update the time, but didn’t. We’ve seen a few similar reports online, too.Full reading: https://www.howtogeek.com/fyi/some-windows-10-clocks-didn%e2%80%99t-%e2%80%9cfall-back%e2%80%9d-here%e2%80%99s-how-to-fix-it/
Yes, It’s Yet Another Windows 10 Bug
We noticed this problem on a PC that was powered off when the time changed. When we turned it on later in the morning, it never bothered updating the time. In other words, that PC is reporting a time one hour ahead of the real time. The PC had several hours to update the clock after we turned it on, but it never bothered doing so.
This particular PC is running Windows 10’s buggy October 2018 Update, so maybe this is yet another problem with that update. On the other hand, another PC running the October 2018 Update updated the time just fine.
We don’t know how many people experienced this problem, but we can already see we’re not alone. Make sure to check the clocks on your Windows 10 PCs, just in case.