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

I have created another fix for you.

Step 1:
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 file adamjw.zip, and save this to your Desktop. Ensure that this file is named adamjw.zip - 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 adamjw.zip.
  5. Drag the file adamjw.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to check please.

Step 2:
After this has completed you can run SFC /scannow and then follow this with another DISM restorehealth as you did before to see what remaining files still need to be repaired.
 
It looks like the files I have been providing were in their compressed format and so they have been rejected based on their file hashes. I will need to create new expanded versions of the files to replace them. I will work on this over the next few days. Thank you for your patience.
 
Thank you very much. If there's anything I can do on my end, please let me know.
 
I just re-read your earlier post and realized that after I did the last SFCFix, I did not do an SFC /scannow - I just did a DISM restorehealth. Would this have changed the approach at all or does it not matter?
 
Yes, the SFC /scannow makes sure the changes get incorporated and cascaded through the various file locations in the Windows System. There is no harm in running it and repeating the DISM and then providing a new CBS.zip
 
I have created a new fix which should provide the correct expanded versions of the files where I was able to find them and also make some registry changes for those files which I have not been able to expand.

Step 1:
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 file SFCFix.zip and save this to your Desktop. Ensure that this file is named SFCFix.zip - 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 SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to check please.

Step 2:
After this has completed you can run SFC /scannow and then follow this with another DISM restorehealth as you did before to see what remaining files still need to be repaired.
 
Well we seem to be making progress. SFC /scannow appears to have been successful:

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.

DISM still failed with error 0x80240021.

See attached CBS.
 

Attachments

Can you please provide the SFCFix.txt file that I asked for (item 8 from Step 1). I want to check that all the corrections were correctly made.

Thanks!
 
Many thanks!

There is one more corruption in the CBS.log and this fix will put that right.

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 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 file should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to check please.

Step 2:
After this has completed run another DISM restorehealth as I want to see if it will complete without failures. Please post the latest CBS.log after this has run.
 

Attachments

Well, it didn't work, but it does seem to have resolved the prior issue as it is a new error:

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================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

Here is the CBS
 

Attachments

One of the updates that appears to be required by CBS is update KB3000850. Let's see if we can force it to install.

Code: 
2021-08-26 09:17:08, Info                  CBS    REPR: WU scans package Package_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8 that is required by CBS


Install Update with DISM
  1. Download this update and save to your desktop. The file name will be Windows8.1-KB3000850-x64.cab.
  2. Click on the Start button and in the search box, type Command Prompt
  3. When you see Command Prompt on the list, right-click on it and select Run as administrator. Go ahead and allow if you receive the UAC prompt.
  4. Copy and paste the following command into the command prompt window and press enter.

    dism /online /add-package /packagepath:%userprofile%\desktop\Windows8.1-KB3000850-x64.cab
  5. You should receive the message:
    The operation completed successfully.
    Restart Windows to complete this operation. <---You may not get this line.
    Do you want to restart the computer now (Y/N)? <---You may not get this line.
 
Last edited:
C:\Windows\system32>dism /online /add-package /packagepath:%userprofile%\desktop
\Windows8.1-KB3000850-x64.cab

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

Processing 1 of 1 - Adding package Package_for_KB3000850~31bf3856ad364e35~amd64~
~6.3.1.8
[==========================100.0%==========================]
An error occurred - Package_for_KB3000850 Error: 0x8007371b

Error: 14107

One or more required members of the transaction are not present.

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

Attachments

Hello adamjw

The log shows that there were some manifest files missing.

Code: 
2021-08-27 09:21:37, Info                  CSI    0000004e Changelist winner missing its manifest - Microsoft.Management.Infrastructure.Native.Unmanaged, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2021-08-27 09:21:37, Info                  CSI    0000004f Changelist winner missing its manifest - Microsoft.Windows.PowerShell.Common, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2021-08-27 09:21:37, Info                  CSI    00000050 Changelist winner missing its manifest - Microsoft-Windows-PowerShell-Exe, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2021-08-27 09:21:37, Info                  CSI    00000051 Changelist winner missing its manifest - Microsoft-Windows-PowerShell-SIP, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2021-08-27 09:21:37, Info                  CSI    00000052 Changelist winner missing its manifest - Microsoft-Windows-PowerShell-Events, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2021-08-27 09:21:37, Info                  CSI    00000053 Changelist winner missing its manifest - Microsoft-Windows-PowerShell-WSMan-Plugin, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2021-08-27 09:21:37, Info                  CSI    00000054 Changelist winner missing its manifest - Microsoft-Windows-MSF-Core, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2021-08-27 09:21:37, Info                  CSI    00000055 Changelist winner missing its manifest - Microsoft.Windows.PowerShell.V3.Common, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2021-08-27 09:21:37, Error                 CSI    00000056@2021/8/27:16:21:37.330 (F) base\wcp\componentstore\csd_winners.cpp(1211): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)
[gle=0x80004005]

However, from the error I am unable to be sure if it is the actual files that are missing or the registry entries that are corrupt or both.

Please do the following scan to show whether the manifest files are on your system or not. The fix also includes a registry repair for one of the previously detected corruptions.

  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 file into your next post for me to check please.
 

Attachments

Thanks for the log - this confirms that you do have the files on your system but the registry is missing some of the entries. The following fix will provide the registry keys that you need. It is a new SFCFixScript.txt file (make sure you delete the previous ones so that you do not use them by mistake).

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. 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 file into your next post for me to check please.

After this has completed please try to install the KB3000850 update again as instructed in post #36
 

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