sfc /scannow, DISM and Windows 11 Installation not working after KB5058502 failure

Anonymous
2025-06-07T00:01:24+00:00

I'm running Windows 11 and today the update KB5058502 attempted to install. However, an error occurred during the update which let to the system get stuck on "Undoing changes made to your computer", which would never actually complete. Through the use of Windows 11 install media on a USB stick, I was able to change the boot from "Windows Rollback" back to "Windows 11". The system mostly functions (Windows Explorer seems to behave normally and most applications seem to work fine), with a few exceptions:

  • Some applications fail to open with the error "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail."
  • Steam fails to open with the error "The code execution cannot proceed because C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controIs_6595b64144ccf1df_6.0.22621.5262_none_6ebff4ba87ff320e\COMCTL32.dll was not found. Reinstalling the program may fix this problem."
  • sfc /scannow fails with the message "Windows Resource Protection could not start the repair service." (I checked and trustedInstaller is running)
  • DISM /Online fails with the message "Error: 193 An error occurred while attempting to start the servicing process for the image located at C:. For more information, review the log file."
  • Windows 11 Installation Assistant (trying to repair the Windows install) errors with "Installation failed", followed by "Something went wrong | Select Try again, and if that doesn't work, contact Microsoft support for help. Error code 0x800700c1"
  • Installing the KB5058502 update with the standalone installer fails with the message "This update is not applicable to your computer".

I'm assuming this is all because of corrupted files due to the update failing to install (apart from maybe the Windows 11 installation assistant failing, surely that shouldn't even be using installed files...?) Checking the CBS log, I've found that the following error is repeated over and over: "Failed to create CBS worker - waiting for a second and trying again".

OS Version 10.0.22631 Build 22631

Thanks!

Ben

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Ramesh Srinivasan 88,100 Reputation points Independent Advisor
2025-06-09T02:42:19+00:00

Hi,

The new errors are related to Store apps, and DISM can't fix them.

  1. Download Windows 11 Media Creation Tool (MCT) from this link:

https://go.microsoft.com/fwlink/?linkid=2156295

  1. Run MCT and download the ISO it recommends for your system. Do *not* uncheck "Use the recommended options for this PC".
  2. Right-click on the downloaded ISO and choose "Mount." This assigns the ISO a drive letter.
  3. Run setup.exe from the ISO drive. This starts the 24H2 in-place upgrade.

(Your files, settings and applications will be preserved if you use the ISO recommended for your system by the Media Creation Tool.)

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

48 additional answers

Sort by: Newest
  1. Ramesh Srinivasan 88,100 Reputation points Independent Advisor
    2025-06-08T15:45:16+00:00

    Update:

    Upon inspecting the latest CBS logs, DISM was able to fix 90% of the component store corruption.

    Please run "SFC /Scannow" again.

    Share the latest CBS logs.

    Was this answer helpful?

    0 comments No comments
  2. Ramesh Srinivasan 88,100 Reputation points Independent Advisor
    2025-06-08T15:29:02+00:00

    Hi,

    Thanks for the detailed information. We've eliminated some really old drivers and also successfully fixed the system file corruption.

    1. Press Win + R, type "ncpa.cpl" and click OK.

    Right-click on the Ethernet adapter and click Properties.

    Post a screenshot of the Properties dialog.

    1. Share the latest CBS logs. To collect the logs, open admin PowerShell and run: GCI -Path 'c:\windows\logs\cbs', 'c:\windows\logs\dism\dism.log', 'C:$WINDOWS.~BT\Sources\Panther\setupact.log' | Compress-Archive -destination (join-path ([environment]::GetFolderPath('Desktop')) \CBS.zip)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-06-08T15:19:25+00:00

    Thanks Ramesh,

    here's the second Fixlog. I noticed after this that Windows booted considerably faster than it has been doing since the failed update; it had been on a "please wait..." screen for a minute or two before starting Windows, this now doesn't happen.

    SFC can now get a little further; it now says

    Beginning system scan.  This process will take some time. 
    
    Beginning verification phase of system scan. 
    
    Verification 6% complete. 
    
    Windows Resource Protection could not perform the requested operation.
    

    DISM can also get further; it says

    Deployment Image Servicing and Management tool 
    
    Version: 10.0.22621.2792 
    
    Image Version: 10.0.22631.5335 
    
    [===========================62.3%====                      ]    
    

    This doesn't seem to get any further after leaving it for a while.

    Certain applications still fail with the COMCTL32.dll error or the Side-by-side configuration error.

    Just to clarify something I mentioned in the original post, in order to boot into Windows, I had to change the Boot option in msconfig from "Windows Rollback (\windows)" to "Windows 11 (C:\WINDOWS)". (I feel like the way I mentioned this originally was a bit ambiguous and it could have some relevance.)

    In case it helps (now that I was able to run SFC and DISM somewhat), here's updated CBS logs: CBS 20250608 15.43.zip

    Thanks

    Was this answer helpful?

    0 comments No comments
  4. Ramesh Srinivasan 88,100 Reputation points Independent Advisor
    2025-06-08T14:25:04+00:00

    Hi,

    The CrossDevice error is unrelated, and we can fix that later.

    Several system files are corrupt. Please run the 2nd fixlist.txt, which removes outdated drivers and repairs some system files, sourcing them from my GitHub.

    https://www.winhelponline.com/fixlist/Pogman999...

    Post the latest fixlog.txt.

    Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to provide accurate, safe information.

    Was this answer helpful?

    0 comments No comments