SxS Corruption on WSSE2012R2

valistral

valistral

Contributor
Joined
Mar 26, 2019
Posts
52
SFC finds corrupted files (hash mismatches) while DISM just doesn't, WU works for now, but certain DISM commands like /startupcleanup will just fail saying some updates sxs assemblies are missing throwing STATUS_SXS_ASSEMBLY_NOT_FOUND.

I tried to troubleshoot the issue myself, but I wasn't able to restore those files even using the OEM deployment OS wim image.
Attached are the log files (CBS and SFCFix).
 

Attachments

Also running chkdsk with /f (there's only some unallocated space in the MFT and some offset of the USN journal not matching to correct) option causes the system to throw STOP 0xc000021a on the next boot and the only way to correct is doing restoring the system from a bare metal backup.
 
Hello and welcome!

Then start by performing HDD check.


GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:


  • Download GSmartControl and save it on your Desktop;
  • Execute gsmartcontrol.exe; Let the install complete and launch the programme.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
    info_failing.png
 
Hello performed the test on the OS SSD, and everything white, no errors detected from the extended self test.
 
softwaremaniac said:
What updates if any are listed as needed to be installed?
Click to expand...

None just two rollup previews that I now firmly refuse to install considering the several incidents I happened to have with 'em, since apparently involved WU MSFT engineers are often able to break stuff just by leaving stupid typos into registry keys or worse that then I have to manually rectify.
 
That's a good idea. Previews are essentially beta updates that test things out and as such more often than not, cause severe issues sooner or later.

Can you please do the following again?

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Okay this is new, it finished with Errore: 0x800f0906 because it couldn't find a replacement for some file, but that was probably because of connectivity issues trying to re run now.
 

Attachments

I think I found some of the culprit of /startcomponentcleanup, /restorehealth switches failing in DISM being:
  • KB2987107
  • KB3037924
  • KB3087041
  • KB4487000
For all but the last one removing the package manually via DISM fixed the corruption bit partially, for the last one running WUSA /uninstall /kb:4487000 even if it said "it wasn't installed" apparently cleaned the left over assembly corruption that prevented from running /startcomponentcleanup, somehow...

Attempting a SFC /scannow now.
 
Same result on sfc /scannow it still finds the same other .NET related assemblies file being corrupted but I have no clue on how to recover those, cbs log attached.
 

Attachments

Do the following:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. 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. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Here the log, but I think that part of the corruption was fixed by uninstalling KB2987107 and fixing the store enough to do /startcomponentcleanup, now DISM doesn't complain but SFC still does.
 

Attachments

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 and just provide the link here.
 
Do the following to get an updated list of corrupt files:

SFC Scan


  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 commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Still the same 12 files, log attached. And DISM says there's no corruption still.
 

Attachments

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