Windows Server 2019 Standard, Failed KB5040430 update, no SFC or DISM functionality

Miterin

New member
Joined
Dec 10, 2024
Posts
1
Hello All,

I've been working in IT for a few years now and I've finally run head first into a wall and hit a problem that I'm quite lost in. I was searching on the internet and found this thread, which I felt was somewhat similar to my own issue.


I'm working on a server running 2019 standard with two virtuals, an RDS server and a DC. The virtual servers are totally fine and updating without any issues but the physical server has been failing to update since the July update, KB5040430. I've attempted to run SFC, which results in the error, "Windows Resource Protection could not start the repair service". I then attempted to run DISM /online /cleanup-image /restorehealth, which results in the error "1006, "The volume for a file has been externally altered so that the opened file is no longer valid"". I've also tried scanhealth with the same results. Next I tried to manually install the missing update from the Catalog but it says it's not the correct update for the system. I tried using DISM to extract and add-package the update, it failed too. I then ran a system state restore process to before the update was available but it failed with an error "Access Denied". I attempted the same thing but using the local Administrator account instead of the Domain Admin account but it failed with the same error. In the CBS log I can see the same error, repeated over and over again "Failed to create CBS worker - waiting for a second and trying again [HRESULT = 0x800703ee]", so I'm guessing that's related to my issue?


Right now the server is running but it has issues and can hang on a reboot often due to the trustedinstaller service. I'd really like to avoid having to reinstall the OS on the physical server but if that's what needs to happen, so be it. Any help would be appreciated.

SFC > Failed
DISM > Failed
Manual Update Installation (KB5040430) > Failed
SFCFix > Failed
System State Restore > Failed
 

Attachments

Hi @Miterin,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top