Why are computer fleet updates failing to install?
Updates are failing after completely installing and restarting, leaving administrators with persistent error codes across multiple servers and machines. Short of fully reimaging the systems, standard recovery methods are failing to resolve the issue.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1trying DISM with source iso's
- 2resetting update cache
- 3trying an IPU
- 4growing the EFI partition
- 5installing the .NET update manually
- 6deleting the contents of the SoftwareDistribution folder
- 7clearing out the CCMCache
- 8running SFC
In their words
Unedited, most upvoted first, each linked to the thread it came from.
“My entire fleet of computers is failing to take the September update.”source ↗
“Short of reimagine, I’m not really sure what else to try.”source ↗
“I’m noticing that the Windows Server patch updates are failing after completely installing and restarting to apply the patches.”source ↗
“We use WSUS, and are seeing similar issues with 4 of my 40 servers.”source ↗
Where this came up
People with this problem also raised
- 2Intel extension update stuck in a reboot loop
- 2Why won't my store data update through the API?
- 2Furnace won't turn on after new AC installation
- 4Why do wireless access point firmware updates keep breaking deployments?
- 2Can you install Windows 10 ESU updates without a subscription?
- 3How to stop software updates from breaking your production website