Last month, I encountered several workstations that couldn't install the latest Cumulative Updates. I tried various solutions, including running the Windows Update Troubleshooter, manually downloading the MSU file, and using all the SFC and DISM commands (pointing to the WIM), but nothing worked. I even attempted to rename the SoftwareUpdates and catroot2 folders, which also failed. In the end, I downloaded an ISO from the Microsoft 365 Admin Center, mounted it, and initiated the setup, only to have it hang during the rollback process. I had to reimage the system.
Now, I'm facing the same issue with a 2019 Server that won't take the March Cumulative Update. I've tried everything I did for the workstations, plus I extracted the SSU from the MSU file since I heard that was causing issues. After several reboots, the update still fails. Has anyone else experienced this recently? Is there any actual fix that works? I've attached snippets from the CBS log for reference.
3 Answers
We're seeing similar issues lately—there doesn't seem to be a clear reason for the updates failing.
Have you run your log through an AI tool? I did and it highlighted some issues. Here's what I found:
- Main error code: 0x800f0922, which usually indicates issues with connecting to Windows Update servers, a small system reserved partition, or .NET servicing corruption.
- It also flagged 0x80070002, meaning certain files couldn’t be found, hinting at a corrupt update cache or missing components.
- Lastly, 0x800f0826, which means a dependent update failed, causing others to abort. The problem seems to be with the Servicing Stack Update, which is crucial for installing other updates.
I've tried multiple AIs, as I mentioned in my post, but so far, their suggestions haven't resolved anything. I doubt it's an issue with the reserved partition or Windows Update itself, and I don't think it's a .NET issue either. I unpacked the CU and installed the SSU separately.
Is this a new server or have you done an in-place upgrade? Windows Update uses the system reserve partition to stage updates, and you might need to clean that out.
The 2019 server has been the original OS for several years. This is the first time I’ve seen it fail with monthly updates.
Yeah, there's definitely no pattern here either. I'm working on gathering data to see how widespread this is among our computers and servers. Microsoft hasn’t acknowledged any issues so far.