Server 2016 - SFC Errors unable to fix corrupt files

B

borito78

Member
Joined
Apr 29, 2020
Posts
10
Hi,

I have noticed today on a machine running Server 2016, in the Server Manager shows message:

Role and feature refresh failed with the following error: The request to list features available on the specified server failed. A DISM session could not be opened %1 is not a valid Win32 application. Error: 0x800700c1
Click to expand...


If I run sfc /scannow I get message:

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Windows\system32>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.
Click to expand...


Running DISM /Online /Cleanup-Image /CheckHealth I get following output:

Deployment Image Servicing and Management tool
Version: 10.0.14393.3241


Error: 193

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
Click to expand...


Not sure what to do to fix this, anyone have any ideas?
I've attached the CBS.log file from the sfc scan

Thanks!
 

Attachments

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-04-30 10:07:30.033
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\********\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 copied file C:\Users\********\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\********\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\********\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\********\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\********\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\********\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\********\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\********\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\********\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 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
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2020-04-30 10:07:33.408
Script hash: 8ThLOTwS1f6O7EMg/3Zw8mFupY7gKoIDKOKMDkxB+/Q=
----------------------EOF-----------------------
 
Last edited:
If I run sfc /scannow now I get message:
Windows Resource Protection did not find any integrity violations.
Click to expand...

However running DISM /Online /Cleanup-Image /CheckHealth still shows above error 193
 
Ran DISM /Online /Cleanup-Image /RestoreHealth

Still got Error 193.


CBS.log file too large to attach, please find it here CBS.log
 
Created a local admin account.

Ran DISM /Online /Cleanup-Image /RestoreHealth from an elevated command prompt.

Still returned with this almost instantly:


Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.3241


Error: 193

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
Click to expand...
 
Please see files attached.

Thanks
 

Attachments

  • Downlevel1.png
    Downlevel1.png
    160.8 KB · Views: 5
  • Downlevel2.png
    Downlevel2.png
    170.1 KB · Views: 5
  • Downlevel3.png
    Downlevel3.png
    140.9 KB · Views: 5
Update from today

Logged onto the server and all appears to be ok

Server Manager reporting no problems.

Ran the CheckHealth parameter:

Code: 
PS C:\Windows\system32> DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.3241

Image Version: 10.0.14393.3241

No component store corruption detected.
The operation completed successfully.


Thanks for your help!!
 

Attachments

  • 1588578854099.png
    1588578854099.png
    128.8 KB · Views: 2
Is it vital that I run RestoreHealth even though the HealthCheck reported back with no problems and Server Manager is also reporting no problems?
 
Ran DISM /Online /Cleanup-Image /RestoreHealth

Got:
Code: 
[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.
 
I resolved the SFC issues by running the SFCFix tool.

Why after leaving it for the weekend, do you think it has resolved the DISM issue?
 
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