SFCfix cannot repair several corrupted item including CMD.exe

foxcrew66 · Apr 20, 2019

Hi there. This is my first time posting. I need some help with my windows server 2012. Recently i noticed some of the service would not work including computer browser and the sql service keep stopping. When i try opening the CMD, this message pop up:

I tried running the "sfc /scannow" command using the powershell. Following message show up: "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."

After that I tried using the SFCfix to try and recover those corruped file. Report generated shows many SFC verification failure and the CMD.exe still cannot be opened. Is there any way to fix this?

I have attached the SFCfix and CBS log. Thank you

Sysnative Windows Update · Apr 24, 2019

Hi!

Do you still need assistance?

foxcrew66 · Apr 25, 2019

Hi,

yes i still need the assistance.

Not so urgent however. Thank you very much

Sysnative Windows Update · Apr 29, 2019

Hi!

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
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.

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

foxcrew66 · May 1, 2019

Hi,
Thanks for the help.
After running the sfc /scannow it looks like there is still some corrupted file.

The following is the report copied from SCFfix.txt. The Cbs log is attached.

Code:

SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-05-01 23:31:17.398
Microsoft Windows Server 2012 R2 Update 3 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\wow64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_866c6bf6227abe66\cmd.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-utilman_31bf3856ad364e35_6.3.9600.17415_none_f3b4aad604fac1ce\Utilman.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-sethc_31bf3856ad364e35_6.3.9600.17415_none_53cb39e048d8c14d\sethc.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-osk_31bf3856ad364e35_6.3.9600.17415_none_9bc7ce532dac247d\osk.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-narrator_31bf3856ad364e35_6.3.9600.17415_none_af28d3d777766b35\Narrator.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-magnify_31bf3856ad364e35_6.3.9600.17415_none_5f38d2536c6d52bf\Magnify.exe
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_7c17c1a3ee19fc6b\cmd.exe

Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\wow64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_866c6bf6227abe66\cmd.exe to C:\Windows\WinSxS\wow64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_866c6bf6227abe66\cmd.exe.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-utilman_31bf3856ad364e35_6.3.9600.17415_none_f3b4aad604fac1ce\Utilman.exe to C:\Windows\WinSxS\amd64_microsoft-windows-utilman_31bf3856ad364e35_6.3.9600.17415_none_f3b4aad604fac1ce\Utilman.exe.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-sethc_31bf3856ad364e35_6.3.9600.17415_none_53cb39e048d8c14d\sethc.exe to C:\Windows\WinSxS\amd64_microsoft-windows-sethc_31bf3856ad364e35_6.3.9600.17415_none_53cb39e048d8c14d\sethc.exe.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-osk_31bf3856ad364e35_6.3.9600.17415_none_9bc7ce532dac247d\osk.exe to C:\Windows\WinSxS\amd64_microsoft-windows-osk_31bf3856ad364e35_6.3.9600.17415_none_9bc7ce532dac247d\osk.exe.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-narrator_31bf3856ad364e35_6.3.9600.17415_none_af28d3d777766b35\Narrator.exe to C:\Windows\WinSxS\amd64_microsoft-windows-narrator_31bf3856ad364e35_6.3.9600.17415_none_af28d3d777766b35\Narrator.exe.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-magnify_31bf3856ad364e35_6.3.9600.17415_none_5f38d2536c6d52bf\Magnify.exe to C:\Windows\WinSxS\amd64_microsoft-windows-magnify_31bf3856ad364e35_6.3.9600.17415_none_5f38d2536c6d52bf\Magnify.exe.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_7c17c1a3ee19fc6b\cmd.exe to C:\Windows\WinSxS\amd64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_7c17c1a3ee19fc6b\cmd.exe.

Successfully restored ownership for C:\Windows\WinSxS\wow64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_866c6bf6227abe66\cmd.exe
Successfully restored permissions on C:\Windows\WinSxS\wow64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_866c6bf6227abe66\cmd.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-utilman_31bf3856ad364e35_6.3.9600.17415_none_f3b4aad604fac1ce\Utilman.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-utilman_31bf3856ad364e35_6.3.9600.17415_none_f3b4aad604fac1ce\Utilman.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-sethc_31bf3856ad364e35_6.3.9600.17415_none_53cb39e048d8c14d\sethc.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-sethc_31bf3856ad364e35_6.3.9600.17415_none_53cb39e048d8c14d\sethc.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-osk_31bf3856ad364e35_6.3.9600.17415_none_9bc7ce532dac247d\osk.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-osk_31bf3856ad364e35_6.3.9600.17415_none_9bc7ce532dac247d\osk.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-narrator_31bf3856ad364e35_6.3.9600.17415_none_af28d3d777766b35\Narrator.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-narrator_31bf3856ad364e35_6.3.9600.17415_none_af28d3d777766b35\Narrator.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-magnify_31bf3856ad364e35_6.3.9600.17415_none_5f38d2536c6d52bf\Magnify.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-magnify_31bf3856ad364e35_6.3.9600.17415_none_5f38d2536c6d52bf\Magnify.exe
Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_7c17c1a3ee19fc6b\cmd.exe
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-commandprompt_31bf3856ad364e35_6.3.9600.17415_none_7c17c1a3ee19fc6b\cmd.exe
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 7 datablocks.
Finish time: 2019-05-01 23:31:19.148
Script hash: DZ/MnlmL/P6Ah+ebzzhqQRXo5+cqiufnCJIkw6lcrgA=
----------------------EOF-----------------------

Sysnative Windows Update · May 1, 2019

Run SFC Scan again.

foxcrew66 · May 1, 2019

I already run the sfc scan. please check the attachment for the cbs logs. thank you

Sysnative Windows Update · May 1, 2019

I know you did, but I wanted to check if the repair SFC allegedly made was successful.

Please do the following:

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:

Download the portable version of GSmartControl and save it on your Desktop;
Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
Please note: If the SMART Status reads: Unsupported, stop and let me know.

foxcrew66 · May 1, 2019

Oh I see. The SMART status on my hard drive is unsupported. what should I do?

Sysnative Windows Update · May 1, 2019

Are you using an NVME SSD?

If so, please use your vendor's official tool.

foxcrew66 · May 1, 2019

I am using PERC H730 Adp. Finding the suitable software right now.

foxcrew66 · May 3, 2019

Right now I unable to find a software to check the drive health. Is it ok if I skip this step?

Sysnative Windows Update · May 3, 2019

That is your RAID Controller. There is no software for it. You need to test the actual drives.

No, we cannot skip this, because I am almost certain that this is causing your errors due to the specificity of the error message.

foxcrew66 · May 5, 2019

I see. how do I test the drive? is there any method?

Sysnative Windows Update · May 5, 2019

GSmart works, but the problem is the fact they are in RAID. You need access to separate drives (unRAIDed, so to speak) to test them.

In some cases, even looking at the Event Viewer logs may give clues.

foxcrew66 · May 5, 2019

will give it a try

Tekno Venus · May 7, 2019

Diskovery can read the health information of each drive within a RAID array, although I'm not sure if PERC controllers are fully supported yet: Diskovery | The data storage inspection tool

foxcrew66 · May 12, 2019

thank you Tekno Venus. i already tried the Diskovery software. posting the log here. I hope the data needed is inside the log

Sysnative Windows Update · Jun 25, 2019

Hi!

Is this still an issue?

SFCfix cannot repair several corrupted item including CMD.exe

Member

Attachments

Inactive

Member

Inactive

Attachments

Member

Attachments

Inactive

Member

Attachments

Inactive

Member

Inactive

Member

Member

Inactive

Member

Inactive

Member

Senior Administrator, Developer

Member

Attachments

Inactive