[10v1709b16299.248 x64] Windows Resource Protection could not start the repair servic

Z

zzz

Member
Joined
Mar 4, 2018
Posts
12
I get the error message in the title whenever I try to run the command "sfc /scannow". This has been happening for quite a while. I have tried the popular solution of running the command "sc config trustedinstaller start=demand"(and different variants for the "start" command argument) followed by the command "net start trustedinstaller". While these commands worked, they did nothing to fix the problem.

I suspect that this problem is related to the problem that one of my apps (Fitbit) has a blank icon when pinned to the taskbar, and none of the standard fixes for this problem work.

I have followed the instructions to run SFCFix, and I have attached the resulting CBS file. Thanks in advance for your help!
 

Attachments

OK, please do the following.

Step#1 - DISM /RestoreHealth Scan
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. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes (even if you get an error), copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Good. Now please do the following.

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run sfc /scannow just like you have in the past.
3. Stop Process Monitor sfc fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.
 
It doesn't appear you did it corectly. Please ensure that Process Monitor is running prior to opening up the command prompt and then go ahead and run sfc /scannow and then stop it after it fails. Please provide both logs again. Thanks.
 
BrianDrab said:
It doesn't appear you did it corectly. Please ensure that Process Monitor is running prior to opening up the command prompt and then go ahead and run sfc /scannow and then stop it after it fails. Please provide both logs again. Thanks.
Click to expand...

Yes, I had started procmon immediately before executing the sfc command. This time, I executed procmon right before opening the command prompt window. The resulting log file is now huge - many times more than the previous time - and so I have put it on my Google drive, with the link sysnative.zip.
 
You did it correctly this time however it looks like you used the 32-bit command-prompt window and not the 64-bit.

When you opened cmd.exe you opened it from C:\Windows\SysWOW64

I need you to open it up from c:\windows\system32 and then do the steps again.

Thanks.
 
BrianDrab said:
You did it correctly this time however it looks like you used the 32-bit command-prompt window and not the 64-bit.

When you opened cmd.exe you opened it from C:\Windows\SysWOW64
Click to expand...

I was using a keyboard shortcut program (HotkeyP) that opened the command prompt at c:\windows\system32. However, as HotkeyP is a 32-bit program, Windows in its infinite wisdom redirected it over to C:\Windows\SysWOW64, where it got the 32-bit version of the command prompt.
I need you to open it up from c:\windows\system32 and then do the steps again.

Thanks.
Click to expand...

Having run into similar versions of this problem before, I had actually created a junction point named C:\Windows\system64 that always pointed to c:\windows\system32. So I changed my command prompt entries in HotkeyP to run C:\Windows\system64\cmd.exe. This worked, and I now get the 64-bit version of the command prompt when I invoke it via hotkey.

The results of running sfc /scannnow are completely different when I use the 64-bit version of the command prompt. In fact, sfc now runs perfectly, with no errors, and no corrupted files detected. So my sfc problem can be considered fixed. Thanks!

This still leaves the problem that when I create a shortcut for my Windows 10 app (Fitbit) in the taskbar, the shortcut's icon is invisible, and none of the standard fixes for repairing this work. Interestingly, this started right after I restored my system from backup; the icon had been displaying fine for months before this. Everything else on my system works fine after the restore from backup. Is this something you could look into, or is there somewhere else on this forum that I should be asking about this?

Thanks again for all your help!
 
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