Windows Server 2016 error 0x80073712 with KB5052006

[syntax]

SFC

C:\>sfc /scannow

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.

DISM

C:\>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[===========================80.0%==============            ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

ComponentsScanner

Loading registry hive from C:\Windows\System32\config\COMPONENTS
Parsing loaded hive, please wait...
Hive parsed successfully - found 1,415,779 keys and 2,338,896 values
Starting corruption scan
Performing regedit load test
Scanning CanonicalData\Catalog for corruptions
Scanning CanonicalData\Deployments for corruptions
Scanning DerivedData\Components for corruptions
Scanning VersionedIndex\...\ComponentFamilies for corruptions
Checking WinSxS catalogs against CanonicalData\Catalogs
Checking f! marks
Checking manifests
Found 7 inconsistencies between WinSxS and COMPONENTS hive
Checking for malformed Deployment keys
Checking CatalogThumbprints & c! marks
7 warnings detected
Generating report


The corruption scan completed after 11766.99 seconds.
No corruptions were detected, but 7 warnings were found in the COMPONENTS hive.

If you are not experiencing issues with Windows Update, these warnings can likely be ignored.

A report has been saved to C:\Users\administrator.TEPA\Desktop\ComponentsScanner.txt. Please review this report for more information.

If you require assistance repairing these warnings, seek advice from sysnative.com or your favourite support forum.

---------------------------

Would you be willing to upload a copy of your COMPONENTS hive and details of your Windows Update configuration
to Sysnative in order to improve this tool and support further research and development?

The uploaded data is completely anonymous and no personal or identifying data will be uploaded.

This is completely optional. If you do not wish to continue with the upload the tool will exit.

Do you agree to upload your hive to Sysnative? Press "Y" for yes or "N" for no.

You have chosen not to upload this hive

The program will now exit. Press any key to continue. . .

Sorry, it seems to have skipped over the option to upload to Sysnative.

 

[Windows Update Bot]

Hi @syntax,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[PeterJ]

Hello and welcome,

Follow the instructions below please.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the file SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the
  
  SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[syntax]

Hi PeterJ,

Thanks for chiming in.

Stage 1 of 6 failed on server
Stage 2 - 100%
Stage 3 - 100%
Stage 4 - 100%
Stage 5[a,b,c,d,e,f,g,h] - 100%
Stage 6 - Failed to create zip file with errno 2
This last error repeated 4x and I had to CTRL-C to break out of it. There failed to create the SFCfix.txt file, likely due to the error.

Reboot successful

SFC

C:\>sfc /scannow

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.

C:\>

 

[PeterJ]

Restart the machine ones again.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[syntax]

Reboot complete.

C:\>sfc /ScanNow

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.

C:\>

 

[PeterJ]

Extract the zip file you already downloaded in message #3 manually.
Provide the full path of the 5 folders and 1 file that are extracted.

 

[syntax]

My initial execution was as you instructed - both files saved to desktop and I dragged/dropped the .zip to the .exe.

To keep things tidy, I extracted it to C:\Temp\SFCfix

C:\temp\SFCFix>tree
Folder PATH listing
Volume serial number is 0000007B DAE1:4D0E
C:.
├───amd64_windows-defender-am-sigs_31bf3856ad364e35_10.0.14393.0_none_e9f929873253e3cd
├───manifests
├───wow64_microsoft-windows-migrationengine_31bf3856ad364e35_10.0.14393.5006_none_d8c3ace46a2d3c2b
├───wow64_microsoft-windows-statemanager.resources_31bf3856ad364e35_10.0.14393.0_en-us_b8a9ada3d79b6c71
└───x86_netfx4-system_ni_b03f5f7f11d50a3a_4.0.14305.0_none_3f7dfb0ca6ab2808

C:\temp\SFCFix>dir /s
 Volume in drive C has no label.
 Volume Serial Number is DAE1-4D0E

 Directory of C:\temp\SFCFix

03/08/2025  06:53 PM    <DIR>          .
03/08/2025  06:53 PM    <DIR>          ..
03/08/2025  06:53 PM    <DIR>          amd64_windows-defender-am-sigs_31bf3856ad364e35_10.0.14393.0_none_e9f929873253e3cd
03/08/2025  06:53 PM    <DIR>          manifests
03/07/2025  09:43 PM                41 SFCFix.txt
03/08/2025  06:53 PM    <DIR>          wow64_microsoft-windows-migrationengine_31bf3856ad364e35_10.0.14393.5006_none_d8c3ace46a2d3c2b
03/08/2025  06:53 PM    <DIR>          wow64_microsoft-windows-statemanager.resources_31bf3856ad364e35_10.0.14393.0_en-us_b8a9ada3d79b6c71
03/08/2025  06:53 PM    <DIR>          x86_netfx4-system_ni_b03f5f7f11d50a3a_4.0.14305.0_none_3f7dfb0ca6ab2808
               1 File(s)             41 bytes

 Directory of C:\temp\SFCFix\amd64_windows-defender-am-sigs_31bf3856ad364e35_10.0.14393.0_none_e9f929873253e3cd

03/08/2025  06:53 PM    <DIR>          .
03/08/2025  06:53 PM    <DIR>          ..
07/16/2016  02:19 PM        37,967,128 MpAsBase.vdm
07/16/2016  02:19 PM        75,071,248 MpAvBase.vdm
               2 File(s)    113,038,376 bytes

 Directory of C:\temp\SFCFix\manifests

03/08/2025  06:53 PM    <DIR>          .
03/08/2025  06:53 PM    <DIR>          ..
08/07/2020  01:24 AM             3,636 msil_microsoft.identitys..anagement.resources_31bf3856ad364e35_10.0.14393.3866_en-us_8cfb952fa71426f3.manifest
               1 File(s)          3,636 bytes

 Directory of C:\temp\SFCFix\wow64_microsoft-windows-migrationengine_31bf3856ad364e35_10.0.14393.5006_none_d8c3ace46a2d3c2b

03/08/2025  06:53 PM    <DIR>          .
03/08/2025  06:53 PM    <DIR>          ..
05/25/2016  07:26 PM         5,590,872 sflistrs1.dat
               1 File(s)      5,590,872 bytes

 Directory of C:\temp\SFCFix\wow64_microsoft-windows-statemanager.resources_31bf3856ad364e35_10.0.14393.0_en-us_b8a9ada3d79b6c71

03/08/2025  06:53 PM    <DIR>          .
03/08/2025  06:53 PM    <DIR>          ..
02/03/2018  11:29 PM             8,192 Windows.Storage.ApplicationData.dll.mui
               1 File(s)          8,192 bytes

 Directory of C:\temp\SFCFix\x86_netfx4-system_ni_b03f5f7f11d50a3a_4.0.14305.0_none_3f7dfb0ca6ab2808

03/08/2025  06:53 PM    <DIR>          .
03/08/2025  06:53 PM    <DIR>          ..
07/16/2016  02:20 PM        10,281,640 system.ni.dll
               1 File(s)     10,281,640 bytes

     Total Files Listed:
               7 File(s)    128,922,757 bytes
              17 Dir(s)   8,993,447,936 bytes free

C:\temp\SFCFix>

Also, I see SFCFix (the program) created C:\SFCfix with data in it. Do you want me to zip that up for you?

C:\SFCFix>dir /ah /as /s
 Volume in drive C has no label.
 Volume Serial Number is DAE1-4D0E
File Not Found

C:\SFCFix>attrib /s
A            C:\SFCFix\CrashDumps\SFCFixCrashReport\SFCFixCrashDump.dmp
A            C:\SFCFix\CrashDumps\SFCFixCrashDump1.dmp

C:\SFCFix>

 

[PeterJ]

Okay, perform the instructions below only.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

 

[syntax]

It ran and didn't take long to complete. "Failed" something or other flashed on the screen before the CMD window disappeared on its own and SFCfix.txt opened. It's probably the same failed line shown in SFCfix.txt

 

[syntax]

One thing to note is this server encountered two unexpected reboots since we last worked on it. There is no minidump folder under C:\Windows, so whatever is causing this is a hard crash, and there's no indication in the System event log as to why. I'm not sure if this server was exhibiting this behavior before we began our troubleshooting. I'm not trying to throw blame - I'm just keeping you aware of what's happening.

 

[PeterJ]

It ran and didn't take long to complete. "Failed" something or other flashed on the screen before the CMD window disappeared on its own and SFCfix.txt opened.

Great. At least we got a result now.
The result shows I made a small mistake in 1 of 6 copies. The other 5 files are copied successful.

New fix.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download the attachment SFCFixScript.txt and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

 

[syntax]

Looks good this time around.

 

[PeterJ]

Great. Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[syntax]

C:\>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.

C:\>

Since my inital report also had problems with DISM, and it takes a while to run, I've started "Dism /Online /Cleanup-Image /RestoreHealth". I'll report the result.