[SOLVED] Server 2016 Cumulative update failure

asandberg

Member
Joined
May 13, 2025
Posts
8
Hello,
I'm struggling/failing to get one of my 2016 servers to take cumulative updates the last few months.
Error 0x80073701. Restore health command produces error 0x800f081f. sfc scannnow produces "Windows Resource Protection found corrupt files but was unable to fix some of them." I've attached what you request and appreciate any help.
 

Attachments

Hi @asandberg,

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
 
Hello and welcome,

Follow the instructions below please.

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
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment 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.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

Hi Peter. Thanks,Adam

SFCFix version 3.0.2.1 by niemiro.
Start time: 2025-06-07 19:43:03.848
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\adamadmin\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
Successfully took permissions for file or folder C:\Windows\servicing\packages

Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1 to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml to C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\packages\package_4158_for_kb5022838~31bf3856ad364e35~amd64~~10.0.1.13.cat to C:\Windows\servicing\packages\package_4158_for_kb5022838~31bf3856ad364e35~amd64~~10.0.1.13.cat.
Successfully copied file C:\Users\adamadmin\AppData\Local\niemiro\Archive\packages\package_4158_for_kb5022838~31bf3856ad364e35~amd64~~10.0.1.13.mum to C:\Windows\servicing\packages\package_4158_for_kb5022838~31bf3856ad364e35~amd64~~10.0.1.13.mum.

Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
Successfully restored ownership for C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
Successfully restored permissions on C:\Windows\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
Successfully restored ownership for C:\Windows\servicing\packages
Successfully restored permissions on C:\Windows\servicing\packages
PowerCopy:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2025-06-07 19:50:58.245
Script hash: i80nwUtZ9X0fO+D0BBH9FNjlNy8KZhT/r+n5y8HTrjQ=
----------------------EOF-----------------------
 
The log looks good.

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.
 
Here are the results:

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.
 
Great.
Check Windows Update again and report the result.
 
Remove Update Manually
  1. Right-Click the Start button and click Command Prompt (Admin) on the list.
  2. When command prompt opens, copy and paste the following command into it, then press enter.
    wusa /uninstall /KB:5046612
  3. Let me know if it says it was successful or if there are any errors.
 
Hi Peter. Failed - attached error.
 

Attachments

  • Screenshot 2025-06-09 201151.webp
    Screenshot 2025-06-09 201151.webp
    15.8 KB · Views: 2
FRST Registry Search
  1. Click the Start button and in the search box, type CMD
  2. When you see cmd.exe on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, press enter afterwards.
    Code:
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

    Note: This loads your components hive which is what we want. Please keep the command prompt window open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  4. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  5. Right-click on the file FRST64.exe and choose Run as administrator.
  6. Copy and paste KB5046612 into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt 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.
 

Attachments

sfc scannow successful

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

Windows Resource Protection did not find any integrity violations.
 

Attachments

Great.
Check Windows Update again and report the result.
 
Peter. My server installed the CU update successfully! I will request a donation from management and if denied, I'll donate myself. You've been a lifesaver. Thank you so much!
Adam
 
Great and your welcome. Thanks ahead for the donation.

Follow the instructions below to cleanup the tools and logfiles used in this thread.
Rename the file FRST64.exe to uninstall.exe and run it. This will remove all files and folders created by FRST and the tool itself.
Reboot the machine to complete.
You may remove all other tools and log files.

Take care.
 

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

Back
Top