![\"Windows](\"https:\/\/www.newsbeep.com\/au\/wp-content\/uploads\/2026\/01\/1768997531_597_0x0.jpg\")
<\/p>\n<\/p>\n
Beware of January’s update.<\/p>\n
NurPhoto via Getty Images<\/p>\n
January has become a nightmare for millions of Windows users, as Microsoft\u2019s latest January update creates a surprising raft of issues. We have seen multiple emergency updates<\/a>. But serious problems remain. And there\u2019s no firm timeline on fixes.<\/p>\n Forbes\u2018Hitting Targets\u2019\u2014Iran\u2019s Hackers Use Starlink To Attack IsraelBy Zak Doffman<\/a><\/p>\n \u201cThis year\u2019s first mandatory Windows 11 update is a mess,\u201d Windows Latest<\/a> warns. Users keep reaching out \u201cto share their nightmare experience,.\u201d For those unaware, “this update is a mandatory security patch, so it\u2019s going to attempt installation whether you like it or not.\u201d And that makes failures unavoidable.<\/p>\n Three of the issues have been acknowledged by Microsoft. The Classic Outlook freezing<\/a> bug, the Remote Desktop<\/a> Bug, and the failure to shutdown<\/a> bug. \u201cBut it doesn\u2019t look like there were only three issues that needed Microsoft\u2019s attention.\u201d<\/p>\n Windows sleep deprivation issue.<\/p>\n Windows Latest<\/p>\n Microsoft is looking into an issue with desktop.ini that likely means it will be fixed soon. But there\u2019s also a new sleep state issue that is garnering increasing user complaints. This preserves battery and power, but the issue is PCs are not falling asleep as planned.<\/p>\n Windows Latest says \u201cthere\u2019s a regression bug in Windows 11 25H2 on the desktop S3 sleep path. Even with hybrid sleep and wake timers disabled, the system-level Maintenance Activator (SystemEventsBroker) does not properly clear the maintenance wake context after the first wake, causing the second sleep to wake immediately.\u201d<\/p>\n