> Some Reddit users on the same thread also pointed out that while the system is already doing plenty in the background, even small updates like this might prev

> Some Reddit users on the same thread also pointed out that while the system is already doing plenty in the background, even small updates like this might prevent deeper power-saving states. This is undoubtedly the answer, and I suspect that if any actual effort were made by Microsoft, the problem might be eliminated entirely. Maybe. Most likely, the update is implemented calling a standard stack of system calls that are completely benign in a normal application, which is already limiting power savings in various ways. But when run by itself, the call stack is triggering a bunch of stuff that ends up using a bit more power. The big question is: Can this actually be optimized with some dedicated programming time? Or is the display/task bar/scheduling such a convoluted mess in Windows that updating the time every second without causing a bunch of other stuff to wake up is impossible without a complete rewrite.