Forum Discussion
2025-10 Cumulative Update for Windows Server 2019 (KB5066586) Undoes Update on Reboot
We have a Windows Server 2019 Standard which will not install the 2025-10 Cumulative Update for Windows Server 2019 (KB5066586) update. The installation part goes fine, but when the server is rebooted to finalize the update, it goes into "Undoing changes". Then it reboots again, and I am back where I started.
The error code is 0x8007000d.
I have done the following to debug this:
- Ran System File Checker sfc /scannow. No errors found.
- DISM /Online /Cleanup-Image /ScanHealth. No errors found.
- Ran Windows Update Troubleshooter. No errors found.
- Shut down Windows Update services. Renamed SoftwareDistribution and Catroot2 folders. Restarted services. No change.
- Ran ScanDisk. No errors found.
- Disabled antivirus. No change.
- Ran Disk Cleanup and manually deleted additional temp files. No change.
- Checked Event Viewer. Only error is Event 20 which is a failure of the Windows Update Agent.
I am out of ideas. If anyone has some, I would much appreciate the help.
I am out of ideas.
9 Replies
- Michael2000Brass Contributor
Anyone got any further ideas?
- PedroLucasCopper Contributor
Hello Michael2000.
Your action plan covers most of the possible causes so if still the same, I do not think there's much you can do (maybe, some package that became corrupt leading to the actual scenario).
Only thing left is to double-check if following scenario applies: https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/windows-devices-fail-boot-after-installing-kb4041676-kb4041691
- Michael2000Brass Contributor
Thank you for your response. Unfortunately, the article does not apply to what I am experiencing. The system is not having trouble rebooting. It reverses the installation of the Cumulative Update on reboot.
- LCazesCopper Contributor
Hello,
Start by stopping non-Microsoft services with MSCONFIG.
Stop and disable SQL Server-type services.
Check if you have any unknown profiles in "Advanced system settings" -> User Profiles -> Settings.
If you have any, delete them.
Reboot your server.
Try installing your updates again.
That's it.- Michael2000Brass Contributor
I performed these step.
- No SQL Server, so did not need to stop those services.
- I didn't have any unknown profiles, but I did find a bunch of profiles in there, as if people were logging into the server, even though they weren't. I deleted them all.
- MSCONFIG not running. All of the other services looked normal.
Unfortunately, the update did not install. By the way, it is now trying to install 2025-11 Cumulative Update for Windows Server 2919. This is what happens on the reboot.
- Michael2000Brass Contributor
Sorry for the slow respones. I was on a work trip.
I appreciate these tips. These are some good ideas. I'll give them a try this coming Saturday. I have to wait until the weekend, because this is a production server. I'll report back on Monday, Nov. 17.
- PedroLucasCopper Contributor
As the "0x8007000d (ERROR_INVALID_DATA)" error message indicates a possible system corruption, please try below steps to repair the image, if machine is connected to the internet (DISM works best when it can connect to Microsoft Update to grab any missing or corrupted files):
- Open an elevated command prompt.
- Type the following command, and then press Enter. It may take several minutes for the command operation to be completed: DISM.exe /Online /Cleanup-Image /RestoreHealth
- Reboot machine and check if same error.
Otherwise, if your computer can't connect to Windows Update, you can alternatively use a working Windows installation as the repair source.
If still same issue, as a last resort, you could try identifying the invalid data and attempt to restore the files from similar Windows image in a healthy state, following guidelines in https://learn.microsoft.com/en-us/troubleshoot/windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates
But, keep in mind that this process may be time-consuming and you might end up needing to rebuild the image after all (as described in article resolution).