Help! I'm Stuck on Cumulative Patch Error 0x80073701 for SQL Server
Asked by
CuriousCoder72
I'm having a tough time getting cumulative patches installed on my SQL server, and I'm hitting a wall with error code 0x80073701. This issue pops up after I try to install these patches, and I've tried quite a few troubleshooting steps:
- Rebooting the server and restarting services.
- Deleting or renaming the C:\Windows\SoftwareDistribution folder.
- Running 'sfc /scannow' and various DISM commands, including checkhealth, StartComponentCleanup, and RestoreHealth.
I've checked the logs and found repeated references to errors indicating invalid packages and extraction failures. I'm at my wits' end, and since this server is critical, I really need help from anyone who's faced a similar issue! What solutions did you find effective?
Answers
I had a similar problem when trying to install updates via Ivanti. I attempted to repair using a source in DISM, but nothing worked. Eventually, I had to do an in-place repair/reinstall of the OS. It got the system up to date, but just be warned that it can mess with other applications. Good luck!
Reply to this answer
I can relate! For my SQL server, I faced the same struggle with cumulative updates failing unless I stopped all SQL services first. The error logs hinted at missing parts of the updates, and trying to reinstall individually didn’t help. Stopping the services was the only workaround that worked in the end. Hang in there!
PatchWizard: We've had to patch several SQL servers, and thankfully most went smoothly, but one definitely gave us a hard time like yours.
Reply to this answer
If this is a critical server, I’d suggest considering migrating and rebuilding. Typically, it’s best practice to have at least three servers so that maintenance on one won’t affect service for your clients. But if you're already running standalone SQL, focus on getting that problematic server out and rebuilt, then sync it back up once it's fixed.
JustSQLThings: Unfortunately, this is not a clustered SQL setup. It's just a standalone for manufacturing, with daily Veeam backups.
Reply to this answer
Add your answer
Answers are reviewed before publication.
FixItFrank: Yeah, I feel you. I'm trying to avoid a full rebuild of the VM as well. Hopefully, someone has a solution that doesn't involve that.