SFC and DISM Not Working on Server 2012 R2

Step 1:
Next fix.

Step 2:
Remove Update Manually
  1. Click on the Start button and in the search box, type Command Prompt.
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator.
  3. When command prompt opens, copy and paste the following command into it, then press enter.
    wusa /uninstall /KB:5005627
  4. Let me know if it says it was successful or if there are any errors.
 

Attachments

FRST Registry Search
  1. Click the Start button and choose Control Panel.
  2. In the upper right corner ensure the View by: is set to Category.
  3. Select the Programs group.
  4. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog.
    Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  5. Right-click on the file FRST64.exe and choose Run as administrator.
    Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  6. Copy and paste KB5005627 into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Perform the instructions in message #47 again. You can skip step 1, 2 and the first 2 command's at step 5.
 

Attachments

I made a small error in the fix causing one registry fix to fail. Attached a new fix.
 

Attachments

Back
Top