[SOLVED] Server 2022 - Component store corruption

mikesmolens

New member
Joined
Mar 16, 2025
Posts
4
Hello,

This is my first post w/ Sysnative. My GoogleFU has led me to here.

I need some help with a production server 2022 box. Long store short is the problem started with not being able to run win updates successfully. The server is a VM that is hosting in a datacenter, while I don't have physical access to the VM. I can have the hosting company help me with certain things. I am also able to take snaps before I attempt any fixes. I reset all the Windows Updates components and when I attempt to run a sfc /scannow the scan gets all the way to 100% but then fails with Windows Resource Protection could not perform the requested operation. I have run DISMs scans with no issue while booted into the server and in the RE environment. I have also discovered during my troubleshooting that I can't install any updated drivers manually as well b/c the hosting company has tried to reinstall the VMWare tools and these tools will fail to update any drivers, even if I attempt to install the driver manually. I am really trying to avoid having to build a new box and do a migration of all data/services. Any help with repairing this would be appreciated.

-Mike
 
Hi @mikesmolens,

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
 
I can run the ComponentsScanner and I attached the log but when I attempt to zip up the logs it gives me the message about creating it on the desktop but once I click on yes I am getting the error File not found or no read permissions.
 

Attachments

I was able to run the SequenceNumberChecker against the DRIVER component file and it seems to have repaired that file. I am now able to run updates and install drivers as well.
 

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

Back
Top