[SOLVED] Problems after installing KB4524104 on Windows Server 2012 R2

/ScanHealth shown 1 CSI Metadata / Payload corrupt, while /RestoreHealth failed with error 0x800f081f "The source files could not be found."
Log attached.
 

Attachments

Thank you. Please do the following:

Step#1 - FRST Fix
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

Done
--------

Fix result of Farbar Recovery Scan Tool (x64) Version: 12-10-2019 02
Ran by <censored> (15-10-2019 01:06:22) Run:10
Running from C:\Users\<censored>\Desktop
Loaded Profiles: <censored> & MediaAdmin$ & <censored> (Available Profiles: <censored> & MediaAdmin$ & <censored> & Administrator)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-xmllite_31bf3856ad364e35_0.0.0.0_none_09340fc3a3d63ba3]
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-s..configurationengine_31bf3856ad364e35_0.0.0.0_none_391d74e4892257bd|Package_732_for_KB4343898~31bf3856ad364e35~amd64~~6.3.1.9.4343898-1147_neutral_GDR
StartRegedit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-xmllite_31bf3856ad364e35_0.0.0.0_none_09340fc3a3d63ba3]
"Package_1050_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-3062_neutral_GDR"="6.3.9600.17415@4"
"Package_854_for_KB4512488~31bf3856ad364e35~amd64~~6.3.1.5.4512488-1339_neutral_GDR"="6.3.9600.19416@4"
"Package_857_for_KB4520005~31bf3856ad364e35~amd64~~6.3.1.11.4520005-1345_neutral_GDR"="6.3.9600.19416@4"
EndRegedit:
*****************

Error: (0) Failed to create a restore point.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-xmllite_31bf3856ad364e35_0.0.0.0_none_09340fc3a3d63ba3 => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-s..configurationengine_31bf3856ad364e35_0.0.0.0_none_391d74e4892257bd\\Package_732_for_KB4343898~31bf3856ad364e35~amd64~~6.3.1.9.4343898-1147_neutral_GDR" => removed successfully
Registry ====> The operation completed successfully.


==== End of Fixlog 01:06:22 ====
 
Thanks.

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. 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.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste 11.0.9600.19503 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
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 file below, 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. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, run DISM again and attach CBS.log.
 

Attachments

Done.

SFCFix version 3.0.2.1 by niemiro. Start time: 2019-10-15 08:58:24.345 Microsoft Windows Server 2012 R2 Update 3 - amd64 Using .zip script file at C:\Users\<censored>\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-ie-timeline_31bf3856ad364e35_11.0.9600.19503_none_5077d5aa4ce1c1bb\timeline.dll Successfully copied file C:\Users\<censored>\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-ie-timeline_31bf3856ad364e35_11.0.9600.19503_none_5077d5aa4ce1c1bb\timeline.dll to C:\Windows\WinSxS\amd64_microsoft-windows-ie-timeline_31bf3856ad364e35_11.0.9600.19503_none_5077d5aa4ce1c1bb\timeline.dll. Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-ie-timeline_31bf3856ad364e35_11.0.9600.19503_none_5077d5aa4ce1c1bb\timeline.dll Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-ie-timeline_31bf3856ad364e35_11.0.9600.19503_none_5077d5aa4ce1c1bb\timeline.dll PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 3 datablocks. Finish time: 2019-10-15 08:58:24.631 Script hash: /lZHsCCWxzZABrQLLrXItlEghlPoUd910rIDHdI32z4= ----------------------EOF-----------------------
 
Appears to be resolved, will try to install missing updates for dotnet 3.5 and rerun to see if something else pops up.
 

Attachments

Rerun DISM and everything looks correct. Donation also sent, thanks very much for the help. 👍
 
Hello I'm resurrecting the thread as I noticed yet another corruption during the scheduled idle scavenge of components which fails while checking the applicability for Package_1050_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8. Running SFC right after shows no corruption, but running DISM /online /cleanup-image /scanhealth shows 1 meta data corruption.

Unfortunately this seems to be an endless circle because every time I make a change in either roles or features, install certain updates, or WU runs the scheduled scavenge of outdated components everything messes up. But the culprit seems to be KB3000850, also rebuilding this won't help because it seems the OEM images supplied with the server all have these problems and WSS can only be installed as an OEM.

Attached are the logs.

Thanks in advance, for the help.
 

Attachments

No not replaced recently, memory diagnostics been run recently and were all okay.
Did also run a test on the OS SSD, upon your suggestion too by the way sometime ago, but it was also okay.
 
Also even just running: dism /online /cleanup-image /analyzecomponentstore
Fails with component store corrupt exception while SFC /scannow and dism /scanhealth and /restorehealth show no corruption atm (after correcting the faulty registry key manually), and Always at the same bit being:

Being evaluating package applicability for Package_1050_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8 and enumerating component deployment for amd64_microsoft-windows-xmllite_31bf3856ad364e35_6.3.9600.19416_none_7a474c33770b4dcc

CBS log attached.
 

Attachments

Please do the following:

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.
 
I'm reporting more errors, because apparently the error is thrown also on update checks in CBS.log but it's not fatal, it also doesn't trigger corruption exception on DISM or SFC.
Problem still seems to be amd64_microsoft-windows-xmllite_31bf3856ad364e35_6.3.9600.19416_none_7a474c33770b4dcc

Log attached.
 

Attachments

Step#1 - FRST Fix
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

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

Back
Top