[SOLVED] Windows Server 2012 - CBS Catalog Missing

[tahhan]

Yes it was successfully uninstalled and asked for a restart.

 

[PeterJ]

Ok. Allow the machine to restart to complete the uninstall.
Next, run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, attach the file cbs.log to your next reply.

Next, run the command dism /online /cleanup-image /restorehealth in an elevated commandprompt and report the result.
If it fails, attach the file dism.log to your next reply.

 

[tahhan]

After the restart, I ran sfc /scannow, the result:

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Then the command dism /online /cleanup-image /restorehealth, the result:

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.2.9200.22807

Image Version: 6.2.9200.22807

[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

I attached both CBS & DISM logs.

 

[PeterJ]

Remove Update Manually

1. Click on the Start button and in the search box, type Command Prompt.
2. When you see Command Prompt on the list, right-click on it and select Run as administrator.
3. When command prompt opens, copy and paste the following command into it, then press enter.
   wusa /uninstall /KB:5020610
4. Let me know if it says it was successful or if there are any errors.

 

[tahhan]

Uninstalled successfully without any issue.

 

[PeterJ]

Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, attach the file cbs.log to your next reply.

 

[tahhan]

Actually I started the command dism /online /cleanup-image /restorehealth so after it get finished I will follow what you have asked.

 

[PeterJ]

Why do you want to run the dism command /Restorehealth if SFC reports no issues and updates ae installing fine ?

 

[tahhan]

No specific reason, it is actually a routine procedure with all Windows servers, where I regularly perform chkdsk/sfc/dism commands to check the healthiness of these Windows.

 

[PeterJ]

I suggest to use /CheckHealth and/or /ScanHealth first before using /RestoreHealth. It looks like /RestoreHealth detects an issue somewhere but the location/reason is not logged.

 

[tahhan]

Ok, I will do that, /CheckHealth, /ScanHealth, and /RestoreHealth. Then I will send you the logs so you may detect where is the issue. If no issue logged after all of that, I will just ignore that error.

 

[PeterJ]

Ok.

 

[tahhan]

I ran all the options /CheckHealth, /ScanHealth, and /RestoreHealth sequentially..

Attached are the CBS & DISM logs

 

[PeterJ]

Check Windows Updates.
Provide a screenshot of the available important updates if there are any.

 

[tahhan]

There is one important update which has appeared yesterday, check the attachments.

 

[PeterJ]

Try to install the update and report the result.

 

[tahhan]

I ran the update, and it was successfully deployed. Then I used "Check online for updates from Microsoft Update", I found around 67 updates, so I deployed them all. I'll update you once it's finished.

 

[PeterJ]

Okay. Fingers crossed.

 

[tahhan]

I updated the Server with all the required updates, it didn't report any issue with whatsoever. But still I'm getting the same error when I ran DISM with RestoreHealth option. If you think, it is not an issue since I'm able to perform all the updates very smoothly, then I will ignore it. What do you think?

 

[PeterJ]

Great all updates installed successful.
Please attach the files c:\windows\logs\cbs\cbs.log and c:\windows\logs\dism\dism.log.