[SOLVED] Win Server 2012 R2 Windows Update / Component Store Corruption

It looks like you will need to carry out the registry search as asked for in post #76.
 
Ok, thanks! I'll check it out tomorrow.
 
This will now delete those registry entries.

NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Thanks - all seems OK. Over to you to check if Windows Update is functioning and for any further errors that need attention.
 
Thanks. Windows Update says no updates available. Will try a DISM RestoreHealth and see what the result is.
 
So it completed with the following result:

Deployment Image Servicing and Management tool
Version: 6.3.9600.19408

Image Version: 6.3.9600.19397

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was repaired.
The operation completed successfully.


That seems like it would be positive, however, when I look at the CBS, it says it did find corruption but ignored it since it was not repairable.
 

Attachments

These are not flagged as errors because they relate to old versions of the component that have been superseded (and may not even be available to download). All looks good to me :-).
 
That's great to hear!

I have a couple more questions - I had tried an SFC /scannow - why would it still be trying to reproject that same TabTip32.exe file when we had removed the related KB from the registry?

And then is any of this stuff of concern:

2021-09-09 12:05:10, Info CBS Session: 30909869_2624404881 initialized by client WindowsUpdateAgent.
2021-09-09 12:05:10, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2021-09-09 12:05:10, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2021-09-09 12:05:10, Info CBS Session: 30909869_2624404882 initialized by client WindowsUpdateAgent.
2021-09-09 12:05:10, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2021-09-09 12:05:10, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2021-09-09 12:05:10, Info CBS Session: 30909869_2624404883 initialized by client WindowsUpdateAgent.
2021-09-09 12:05:10, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2021-09-09 12:05:10, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2021-09-09 12:05:10, Info CBS Session: 30909869_2624561084 initialized by client WindowsUpdateAgent.
2021-09-09 12:05:10, Info CBS Session: 30909869_2626123646 initialized by client WindowsUpdateAgent.
2021-09-09 12:05:10, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2021-09-09 12:05:10, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2021-09-09 12:05:10, Info CBS Session: 30909869_2626123647 initialized by client WindowsUpdateAgent.
2021-09-09 12:05:10, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2021-09-09 12:05:10, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2021-09-09 12:05:10, Info CBS Session: 30909869_2626123648 initialized by client WindowsUpdateAgent.
2021-09-09 12:05:10, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2021-09-09 12:05:10, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2021-09-09 12:05:10, Info CBS Session: 30909869_2626123649 initialized by client WindowsUpdateAgent.
2021-09-09 12:05:10, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2021-09-09 12:05:10, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]

Attached is the latest CBS.
 

Attachments

If you got the message "Windows Resource Protection did not find any integrity violations" then you have no system file issues.

The log goes into a lot of detail but generally if there is no "Error" and it is only "Info" you do not need to worry.
 
Sorry, I should have stated that I did not get the no integrity violations message. I got a corrupt files message:

Beginning system scan. This process will take some time.

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

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios.
 
I am now suspicious that the recent Windows update that attempted to reinstall KB3102429 did not do so correctly (see post#74) even though it was reported as successful. This should have sorted out the TabTip32.exe problem. I need to see your latest registry hives so that I can check what happened.

Step#1 - Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.

Step#2 - Export SideBySide
  1. Click on the Start button and type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (.)
  6. Name this file SxS (with no file extension) and save it to your Desktop.
  7. Once done please upload this file via Dropbox or OneDrive or SendSpace.
 
Many thanks!

It looks as if there are missing registry entries. The following fix will add the same keys as I have on a VM I installed to match your system.

  1. If needed, download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attach this log into your next post for me to check the results.
After this has completed you can run SFC /scannow and post a new CBS.log
 

Attachments

Beginning system scan. This process will take some time.

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

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
 

Attachments

The logs confirmed the TabTip32.exe file plus a few others were successfully repaired.

You should be OK now.
 
You must log in or register to reply here.

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

Back
Top