Server 2016 can't run SFC or DISM or update .NET 4.7.0

S

Semsoid

Member
Joined
Nov 27, 2022
Posts
12
I don't know what has happened fully to this server, but it won't run updates, manual updating .NET 4.7.0 to 4.8 fails.

SFC and DISM won't work either:

sfc /scannow

Windows Resource Protection could not start the repair service.

Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169


Error: 1812

An initialization error occurred.
For more information, review the log file.

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

I believe someone tried to copy WINSXS from a working PC, complicating things further. Any help is appreciated.
 

Attachments

Hi and welcome to Sysnative,

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Hi,

Step 1. Download
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.
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 following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Here are the logs after going your procedure. Thanks ahead for all the help

C:\Windows\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.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 Configure a Windows Repair Source.

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

Attachments

Hi,

Do you have a similar server (or clone) with the same patch level?
 
I have another 2016 server, but that one had no issues. So, patches have been applied After this one had issues. Os versions are same level.
 
Okay, please run the following command on the problematic server, and use the other server as source: (replace ServerName).
Rich (BB code): 
DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess
 
Last edited:
DISM /Online /Cleanup-Image /RestoreHealth /Source:\\server\C$\Windows\WinSxS\ /LimitAccess is the correct line I believe, running it now
 
C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth /Source:\\server\C$\Windows\WinSxS\ /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.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 Configure a Windows Repair Source.

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

Attachments

Hi,

A lot of files are fixed, please perform the following steps to replace some files which has not been fixed.

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.
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 following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess
 

Attachments

It rotated the logs few minutes after I sent you a copy, so in case you see something in them, here is an updated CBS log files
 

Attachments

I should be able to find it. If I do, what's next? Copy the Winsxs folder from it back?
 
Hi,

No I wouldn't do that, I suggest to use the back-up for a complete restore and then take a look at the remaining issues.
 
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