{"id":2921,"date":"2026-04-10T06:47:59","date_gmt":"2026-04-10T05:47:59","guid":{"rendered":"https:\/\/innovatenews.site\/index.php\/2026\/04\/10\/microsoft-says-windows-secure-lock-screen-clock-deliberately-runs-up-to-30\/"},"modified":"2026-04-10T06:48:01","modified_gmt":"2026-04-10T05:48:01","slug":"microsoft-says-windows-secure-lock-screen-clock-deliberately-runs-up-to-30","status":"publish","type":"post","link":"https:\/\/innovatenews.site\/index.php\/2026\/04\/10\/microsoft-says-windows-secure-lock-screen-clock-deliberately-runs-up-to-30\/","title":{"rendered":"Microsoft says Windows' Secure Lock screen clock deliberately runs up to 30\u2026"},"content":{"rendered":"
\n

The topic Microsoft says Windows’ Secure Lock screen clock deliberately runs up to 30\u2026<\/strong> is currently the subject of lively discussion \u2014 readers and analysts are keeping a close eye on developments.<\/p>\n

This is taking place in a dynamic environment: companies\u2019 decisions and competitors\u2019 reactions can quickly change the picture.<\/p>\n

Windows can be a weird beast. Sometimes it’ll have a bug that stops people from using Windows in the strangest ways, and sometimes it’ll have bugs that feel more like features. However, sometimes people will report a bug in Windows, only for Microsoft to look at it and say, “Oh, no, that’s how that’s meant to work. No bugs here.”<\/p>\n

\"\"<\/figure>\n

Such is the case of a bug that causes the clock on the Secure Lock screen to run up to 30 seconds behind. People brought it to Microsoft’s attention, and the software giant simply replied that the clock is meant to do that. It may sound weird in practice, but Microsoft does explain why this bug is actually a deliberate Windows feature.<\/p>\n

If you’ve used Windows 11 for any length of time, you’ll understand.<\/p>\n

As spotted by Neowin, Microsoft has published a document titled “Secure Lock Screen clock may appear up to 30 seconds behind.” In it, the company describes the issue people have been reporting: when the real-world time advances a minute, the clock on Secure Lock will sometimes take up to 30 seconds to catch up. Everything else that uses the clock, such as the system time, event logs, and authentication, reports the time as normal.<\/p>\n

So, when is Microsoft fixing this issue? Well, that’s the neat part, it won’t:<\/p>\n

The Secure Lock screen runs on the Winlogon secure desktop under the system account and refreshes the clock every 30 seconds. Because this polling interval is not aligned to minute boundaries, the displayed time can update up to 30 seconds after the actual minute change.<\/p>\n

Microsoft notes that this odd behavior only happens on the Secure Lock screen. If you perform a user lock, Windows uses a dynamic timer that can flip the minute over “almost immediately” when the time changes. It’s just the weirdness with the Secure Lock screen’s dependency on the system account that causes this issue, and Microsoft doesn’t plan to fix it.<\/p>\n