Server 2016 can't update SFC just hangs

Addagro

Member
Joined
Jan 2, 2024
Posts
21
Hello,

I have a server that seems to be corrupted, updates wont install and any troubleshooting steps just seem to hang or do nothing.

I found this forum while searching online and found the thread below.

[SOLVED] - Windows Server 2016: sfc /scannow fails and Updates are not installing

I'm having almost the exact same issue but worse.

SFC crashes at 47% while running, it says: Windows Resource Protection could not perform the requested operation.
DISM hangs at 68.8% while running, it says: The file or directory is corrupted and unreadable.

I have attached the CBS logs and DISM logs (if needed)

I have also attached the Component Scanner TXT

Let me know if you need anything else.

Thanks so much!
 

Attachments

Hi and welcome to Sysnative,

Here's the first fix.

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

I ran the SFCFix you have sent over and have attached the TXT file.

I ran the SFC scan and it failed at 47 % I have attached the log as well.

Let me know if you need anything else.

Best regards,
 

Attachments

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Hi,

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • 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.
  • 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.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Reboot the server and run the System File Checker again and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the System File Checker again. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the System File Checker again. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Rich (BB code):
2024-01-19 15:59:48, Info                  CSI    00005a0a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_10.0.14393.0_es-es_30c27eaea92a0588\System.Data.Resources.dll do not match actual file [l:25]'System.Data.Resources.dll' :
  Found: {l:32 LmscYlhJsZWopR8+MKXP0sBA+4ghZxOcDcxt/DUiwmY=} Expected: {l:32 go4y0MZ9MI8clusFdKt4v1NQ4zgzQZY7z5cvoHIY8os=}

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Hi,

The attached CBS logs are the same as uploaded in post #13, please attach the most recent logs.
 
i apologize, not sure why it uploaded the wrong file. here's it the CBS log again.
 

Attachments

Rich (BB code):
2024-01-26 09:46:43, Info                  CSI    00005a84 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_10.0.14393.0_es-es_30c27eaea92a0588\System.xml.Resources.dll do not match actual file [l:24]'System.xml.Resources.dll' :
  Found: {l:32 VSurcaTPMqbsY2VsVnfMW8+uzPT6bUxdh/isZUwchI4=} Expected: {l:32 lcOC3e/STQvezfM74gnsi0AdOYgnFlMlTE/UZVmTe08=}
2024-01-26 09:46:44, Info                  CSI    00005a86 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_10.0.14393.0_es-es_30c27eaea92a0588\System.Security.Resources.dll do not match actual file [l:29]'System.Security.Resources.dll' :
  Found: {l:32 +VJcm8YZAMDFCBe7gbV+7OUrmIUj/poeGqbrhPMRAy0=} Expected: {l:32 ppkD3IVtZuTkjtAiLhxIwXV6I4pOSLIHzIm5Yuw5amc=}
2024-01-26 09:46:44, Info                  CSI    00005a88 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_10.0.14393.0_es-es_30c27eaea92a0588\System.Web.Services.Resources.dll do not match actual file [l:33]'System.Web.Services.Resources.dll' :
  Found: {l:32 zdrV0+UfqLRzduGzqLLBdd+WeSlWmfayGoouvjwOU7I=} Expected: {l:32 BYcy7wwgMD8adwuP1MHqUXRZ+tjVVzGS3+9eaXO3WDQ=}

Hi,

Here's the next fix.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Success!

Well kind of.

Got the message below

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.

The system file repair changes will take effect after the next reboot.

Uploading the CBS log. let me know if there's anything else i should do. I can't reboot right now since it's the middle of the day. But I will tonight.

Thanks so much once again.

Best regards,
 

Attachments

Hi,

Great, I would suggest to reboot the server first, and then run the following DISM command.

Run DISM in an elevated command prompt and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

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

Back
Top