Despite an update ‘mitigating’ the problem, some Windows 11 users seemingly still can’t change the date and time in settings—although there is a workaround

For those who find themselves in the habitual cycle of postponing Windows updates, the recent developments surrounding Windows update 24H2 may resonate. This latest iteration of the operating system has addressed numerous issues, yet it has not been without its quirks. A particularly peculiar bug has emerged, preventing users from adjusting the date and time settings on their devices.

Ongoing Challenges with Date & Time Settings

According to the “known issues and notifications” section of the current build, a recent update highlighted an ongoing problem: “Date & Time in Windows Settings might not permit users to change time zone.” While Microsoft has made strides to mitigate this issue with a recent fix, it remains a point of frustration for many users.

In addition to this time-related glitch, users have reported other significant challenges, including:

  • Malfunctioning mouse and keyboard functionality
  • Users becoming trapped in boot loops
  • Unmanageable update caches, with some reaching a staggering 8.63 GB that are difficult to delete

Microsoft has acknowledged these concerns and is actively investigating the matter, promising a resolution in an upcoming Windows update. This proactive approach reflects the company’s commitment to enhancing user experience, even amidst the occasional hiccup.

While smaller updates are a common occurrence, major updates like 24H2 typically arrive once a year. Interestingly, this particular bug has not yet been reported on Windows 10, which may serve as a point of contention for those hesitant to upgrade. However, with Windows 10 set to lose official support next year, the choice between enduring minor bugs or exposing oneself to security vulnerabilities becomes increasingly clear.

Winsage
Despite an update 'mitigating' the problem, some Windows 11 users seemingly still can't change the date and time in settings—although there is a workaround