Forum Discussion
Windows 11 updates failed for Cumulative Update 24H2. Any fix available?
If you have failed to update your Windows 11 system, you may want to try the free command line tool Reset Windows Update Agent, a utility that comes with your system. It is built into the system and does not require a download, so you just need to locate and open a command line window on your computer and type in a specific command to All you have to do is find and open a command line window on your computer and enter a specific command to reset Windows Update components. However, it is important to make sure that the commands are entered correctly in order for it to work as a troubleshooter for updates.
Below is a set of commands to help you fix Updates failed for installing Windows 11 Cumulative Update:
#stop Windows Update service
net stop wuauserv
#stop encryption service
net stop cryptSvc
#stop background Intelligent Transfer Service
net stop bits
stop MSI installation service
net stop msiserver ()
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver After reboot, open Settings, tap Windows Update > Check for Updates to install Windows 11 24H2 Cumulative Update.
I tried this process, but it rejected the 'rename' commands, with an error "Access is denied", even though I was running as administrator.
What AV are you running and have you tried uninstalling it?
im having the same issues with no other AV besides windows defender. A youtube video suggested creating a batch file that didnt yield me the access denied and still fails to fix the issue.
Only running Microsoft Defender AV, which was enabled, but there were other updates held up by this Cumulative Update 24H2 hanging at 81%, including some Windows Security and Microsoft Defender Definition Updates, and a .NET Framework Quality Update.
After going through the above steps from UriahZane, despite the 'rename' errors, I finally got the Update to restart, which installed the security and .NET updates that were pending, and then successfully completed the 2025-04 Version 24H2 installation. So things appear to be resolved and working now.
