[SOLVED] Server 2016 - DISM / SFC Not Completing

P

PC23

Active member
Joined
Mar 18, 2022
Posts
28
Hi,

Thanks to anyone who might read this and help me out.

I have a Server 2016 Standard (with GUI) machine which has started to experience some serious issues, vital services not starting.

I've run a full repair chkdsk on C:, which did not help, and then went on to run sfc. SFC said some files had issues but it could not fix them. Both SFC and DISM do not complete, and the problems remain.

Ran DISM online with both /RestoreHealth and /ComponentCleanUp, both fail. Sorry I've run both DISM and SFC quite a few times (among trying various other things) so I can't remember right now exactly what errors were produced with all switches I've tried but /ComponentCleanUp fails with error 2 (system cannot find the file specified). I have not, so far, been pointing DISM at source files but have done in the past, but it was a nightmare to find the right image for it to accept (although that may have been with Server2012, don't know if its as much of a pain with 2016 with less releases).

I then tried to run SFCFix.exe (no script) but this too failed to complete (stage 1 failed immediately, then it stopped completely during a later stage) stating a catastrophic error had occurred.

Hoping I might get some advice on using SFCFix again but with a script?

Server info is:
Server 2016 - 1607
Build 14393.4946
All updates as of now are installed. My particular issue is not with updates, updates actually seem to install fine, although very slowly, standard situation with Server 2016. Having said this, this whole issue may have started after I rolled back the Jan 2022 problematic updates and then waited for Feb to resume monthly updates.

Server was originally installed from iso: SW_DVD9_Win_Server_STD_CORE_2016_64Bit_English_-4_DC_STD_MLF_X21-70526

Thank you.
 
Just running through sfc, DISM and SFCFix again in order requested for this forum.

Will upload logs once available.
 
So SFC ends with:
'Windows Resource Protection found corrupt files but was unable to fix some of them...'

Then SFCFix crashes with log:
'SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-03-19 04:56:54.225
Microsoft Windows Server 10 Build 14393 - amd64
Not using a script file.

SFCFix version 3.0.2.1 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2022-03-19 04:57:09.573
----------------------EOF-----------------------'

CBS logs attached.

Thanks!
 

Attachments

SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Thanks very much for your reply.
Please see log:
Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-03-21 22:38:28.593
Microsoft Windows Server 10 Build 14393 - amd64
Using .zip script file at C:\Users\Administrator\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\Administrator\AppData\Local\niemiro\Archive\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\Administrator\AppData\Local\niemiro\Archive\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\Administrator\AppData\Local\niemiro\Archive\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\Administrator\AppData\Local\niemiro\Archive\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\Administrator\AppData\Local\niemiro\Archive\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\Administrator\AppData\Local\niemiro\Archive\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\Administrator\AppData\Local\niemiro\Archive\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\Administrator\AppData\Local\niemiro\Archive\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\Administrator\AppData\Local\niemiro\Archive\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: 2022-03-21 22:38:33.640
Script hash: SOEKhMgBZqNrqZsYuxB6+1cidOQC/pQU8XjDWQW4S9M=
----------------------EOF-----------------------
 
Could you please run SFC or DISM again? If either complete successfully, then please try and install any updates which may be available to you.
 
Thanks. I ran sfc again, this time it did not find any integrity violations.

Restarted the server, however, my 2 services which are not starting still won't start (as mentioned earlier, I never had a problem actually installing updates)

Anything else you think might be worth doing at this stage to try to help these services to start? They are both services related to 3rd party software. If there's nothing else I should run first, I may now try to install them over the top and see if they start to work again.
 
Tried to reinstall one of the problem bits of software (I had previously uninstalled it completely before posting here, previously the service would not start).

It installs, installs the service and the software, but same as before, the service won't start. When manually trying to start the service I get:

'Error 1064: An exception occurred in the service when handling the control request'
 
Hmm, eventvwr mmc also crashing when I try to expand any windows logs
 
Ran sfc again, still completing with no integrity violations.

Will await further instruction. Thank you.
 
This issue appears to be specific to those two third-party services you mentioned. I would recommend that you create a new thread in the Windows 10 forum (Server 2016 is the same build) for now.

PC23 said:
'Error 1064: An exception occurred in the service when handling the control request'
Click to expand...
It would seem that there is an issue with the driver associated with that service. Is there any updates for the software?
 
Thanks for your reply and all your help.

One of the pieces of software where the service doesn't start is Veeam Agent for Windows. There was an update available. Installed that, but it still can't start the service at the end of the installation process. Errors out with '..setup application has encountered a critical error and will be closed'

Will start new thread in W10 forum as suggested, thanks.
 
Welcome and just noticed that you managed to resolve your other problem too. I'm glad everything appears to be working okay now.
 
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