Windows Update - 2026-01 Security Update (KB5074109) causes shutdowns instead of sleep

I successfully installed this update over 2 weeks ago. Since installing I find that the system will not sleep. Instead it hangs on shutdown (eventually it will shut down after many minutes) usually I have to do a hard reset in order to get back to work but that entails all the usual boot stuff (+work has crashed) so very unwelcome.
There are many users worldwide that have reported the same annoying feature.
I believe that I have traced this to my hardware not supporting S0 but only S3. I have uninstalled the update and everything is good again.

So it seems that either:
(i) MS issue a fix that addresses this .. but there is nothing that I can see on MS official that suggests that they are interested in fixing this issue; there are many other issues with the update (BSOD, failure to install etc.) that they are working on but no mention of the S0/S3 problem.
(ii) or I change my hardware, which is frankly ridiculous; especially as the perceived wisdom is that S0 is designed with laptops in mind (to make them behave more like smartphones), but desktop PCs are far better served by retaining S3. I have a desktop (see my spec list).
(iii) or I abandon windows and go to Linux, which I am very reluctant to do for all the usual reasons.

Does anyone know whether MS will address this issue in "the big fix", when/if it arrives?

Thanks anyone
Phil

Have you checked for file corruptions? If not then run the following three commands in CMD or Powershell window. They can take some while so be patient.: -

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth

I'll try that now thanks

I think there were no corrupted files? (see image)

There are problems with Windows 11 Component Store but the repair failed with error code 0x800f0915.
Here is an AI generated response to query on 0x800f0915: -

Error 0x800f0915 occurs when DISM (Deployment Image Servicing and Management) cannot find the necessary repair files to fix system image corruption, typically during Windows updates or system repairs.
Primary Solutions

Use Windows Update as the repair source
Instead of relying on a local ISO, let DISM fetch files directly from Microsoft’s servers:
DISM /Online /Cleanup-Image /RestoreHealth /Source:WindowsUpdate

Enable .NET Framework 3.5
This often resolves underlying service issues:
Go to Control Panel > Programs > Turn Windows features on or off, and enable .NET Framework 3.5 (includes .NET 2.0 and 3.0).

Clean up the Windows component store
Run these commands in an elevated Command Prompt:

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth


Reboot after completion.

Reset Windows Update components
Stop services, clear caches, and restart:

net stop bits
net stop wuauserv
net stop cryptsvc
ren "%ALLUSERSPROFILE%\Microsoft\Network\Downloader\qmgr*.dat" qmgr.dat.bak
ren "%SystemRoot%\SoftwareDistribution\DataStore" DataStore.bak
ren "%SystemRoot%\SoftwareDistribution\Download" Download.bak
ren "%SystemRoot%\System32\catroot2" catroot2.bak
net start bits
net start wuauserv
net start cryptsvc


Temporarily disable third-party antivirus
Security software can interfere with update processes.

Perform an in-place upgrade (Repair Install)
If all else fails, mount the latest Windows 11 24H2 ISO from Microsoft’s website, run setup.exe, and choose "Keep personal files and apps" to repair the system without data loss.

Note: The error is common in Windows 11 24H2 and may stem from corrupted update caches, missing system components, or interference from security software. Always check the DISM log at C:\Windows\Logs\DISM\dism.log for detailed diagnostics.

thank you but the problem lies in the update not my computer. Many other users have reported the same symptom and MS have acknowledged that this problem, exactly as described above, is in the update not the user's machine. They say they are working to fix it. This was not the case when I originally posted here so I guess MS have answered the question for me .. I just have to be patient!
Nevertheless I will look into possible component corruption, as you suggest, so thank you again for pointing me to this process.

Philomacc11 said:

thank you but the problem lies in the update not my computer. Many other users have reported the same symptom and MS have acknowledged that this problem, exactly as described above, is in the update not the user's machine. They say they are working to fix it. This was not the case when I originally posted here so I guess MS have answered the question for me .. I just have to be patient!
Nevertheless I will look into possible component corruption, as you suggest, so thank you again for pointing me to this process.

Click to expand...

Update ... so, hoping that MS has fixed this problem with S3 that it admits to know about, and having waited over a month, I went ahead and installed the latest update (KB5077181) (26200.7840) today .... and yes it produces exactly the same problem namely sleep mode hangs and requires hard reset to recover. Obviously MS have not fixed this issue so I will uninstall the update and resume my now, looking more certain, migration to Linux.

I'm sure linux will solve the problems. Good luck.