[SOLVED] Component Corruption Windows Server 2019

[FamousSime]

Hello,
I got this infamous component corruption error. SFC /scannow is not working, also DISM is not working (error 1009). Also got ERROR_BADDB errors in CBS logs.

CBS logs and ComponentsScanner file are attached. Can somebody help me? I have no idea, how I can find out, which components are missing/corrupted. Despite finding a solution.

Do you need some other logs? Thanks a lot!

 

[Maxstar]

Hi and welcome to Sysnative,

Please run

ComponentsScanner again and perform the following repair option.

• Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
• Follow the on-screen instructions.
• When the following message appears: "ComponentsScanner has detected the following issues that it is able to repair automatically."
• Press Y to perform the repair.
  
  
  
  
  
• Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
• Post the logfile ComponentsScanner.txt as attachment into your next reply.

 

[FamousSime]

Hi, thanks for the help.

I ran it again, but it gave me no option to run repairs, it just finishes.
But DISM and SFC is working fine right now. But Windows Update still says "We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet."

I do not know, if the ERROR-BADDB is fixed, but has nothing to do with the windows update error.

 

[Maxstar]

Hi,

Please attach a new copy of the CBS logs and the WindowsUpdate.log.

Export the Windows Update log

• Right-click on the Start button and click Windows PowerShell (Admin).
• Copy and paste the following command into it, press enter afterwards

Get-WindowsUpdateLog

• Wait for the message "WindowsUpdate.log written to C:\Users\<username>\Desktop\WindowsUpdate.log".
• Attach the logfile WindowsUpdate.log to your next reply.

 

[FamousSime]

Here are the logs, thanks!

 

[Maxstar]

Open an elevated command prompt, run the following command and attach services.txt to your next post.

wmic service get name,displayname,pathname,startmode,exitcode > "%userprofile%\desktop\services.txt"

 

[FamousSime]

Here it is!
Thanks again!

 

[Maxstar]

Please run this command as well:

WMIC SERVICE GET caption, name, startmode, state > "%userprofile%\desktop\services.txt"

 

[FamousSime]

I get Error "Invalid GET Expression."

 

[Maxstar]

Strange, it works on an VM with Server 2019 here. What is the result of the following command:

wmic service get name,displayname,startmode,state > "%userprofile%\desktop\services.txt"

 

[FamousSime]

I just ran this command, it worked. I guess the issue was the space after ",". I just copy and pasted the command.

wmic service get caption,name,displayname,startmode,state > "C:\temp\services.txt"

 

[Maxstar]

Let's check some other things. Error 80072f8f usually indicates a problem with the SSL certificate validation.

1. Please check the system date and time settings.
2. Is this server running third-party antivirus software or firewall?
3. Is there a proxy server configured on this system?

 

[FamousSime]

Yes I read about that error, but could not find anything. No wrong date and time, antivirus not blocking anything (we get notified if it does) and no proxy server. We had the same problem with another VM, it happens suddenly without any changes to the machine itself. We could not solve the issue, as it was easy to reinstall windows as a whole, we did this. But reinstalling windows on this machine is not an easy task.
At least now the BADDB error is gone and DISM is working again.

 

[Maxstar]

Which antivirus software is installed, and have you tried to disable / uninstall it before attempting to update?

 

[FamousSime]

We use Crowdstrike with all our VMs, and most of them are updating fine. We did not really consider it blocking the update, as we would see some detections in the Crowdstrike console. But there are not any at all.

 

[Maxstar]

Could you please try to update again with Process Monitor running.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.

 

[FamousSime]

Sorry for late reply! I was in a hurry because of other important tasks. But I have seen, that 2 of our servers are detecting our domain network as public network, both of them are having the exact same problem with error above. I already tried a few things Google told me, but did not work as of now. I guess this is another matter and does not fit here. Still, I can install update packages and use DISM or SFC, so thanks a lot for your help!

 

[Maxstar]

Hi,

This is definitely a network problem or SSL validation issues because the domein is detected as public network. For this issue you could start a new thread in the networking section.