Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows Resource Protection could not start the repair service.


  • Please log in to reply
12 replies to this topic

#1 clayto

clayto

  • Members
  • 476 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:54 PM

Posted 26 May 2017 - 09:54 AM

​For several weeks I have not been able to use sfc/scannow (or DISM). Every time it starts it reports "Windows Resource Protection could not start the repair service."  How do I get it working again?



BC AdBot (Login to Remove)

 


#2 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:08:54 PM

Posted 27 May 2017 - 03:09 AM

Reset Windows services to there default startup settings with the batch script i have created download url link is below.

 

 

Restore Windows Services To Default Startup Settings

Posted Image


#3 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,757 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:09:54 AM

Posted 27 May 2017 - 10:41 AM

Press the windows keywindowskey_zps092d5c75.png  and the X key to open the Windows Mobility Center menu.

 

When the menu opens select Command Prompt (Admin)

 

Type the following command in the Command Prompt, then press Enter.

 

net start trusted installer

 

You should  see the following messages:

 

Windows Modules Installer service is starting

 

Windows Modules Installer service was started successfully


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#4 clayto

clayto
  • Topic Starter

  • Members
  • 476 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:54 PM

Posted 27 May 2017 - 12:23 PM

Thanks for the suggestions, however neither work. The first leaves the same 'could not repair message', the second produces the message 'name invalid'.



#5 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,757 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:09:54 AM

Posted 27 May 2017 - 12:30 PM

I'm a little confused  here since I only made the one suggestion.  Open the command prompt and run the command net start trustedinstaller.  Does this mean you could not open the menu by pressing the Windows button and the X key thus not being able to run the command?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#6 clayto

clayto
  • Topic Starter

  • Members
  • 476 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:54 PM

Posted 27 May 2017 - 01:34 PM

Odd that you say that, there are two suggestions: Free Booter's and yours.

 

I don't have a problem with using Command Prompt --- when I enter  the Cmd "net start ......" the response is name invalid.

 

Mobility Centre on my PC has nothing to do with Command Prompt which is (among other ways) accessed from what is referred to as Secret or Start Menu ie. right click Start icon.



#7 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:08:54 PM

Posted 27 May 2017 - 03:36 PM

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.
 

Sfc  /Scannow   /OFFBOOTDIR=D:\   /OFFWINDIR=D:\Windows


Please replace partition letter D: with Windows installed partition letter.  When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.


Edited by FreeBooter, 27 May 2017 - 03:40 PM.

Posted Image


#8 clayto

clayto
  • Topic Starter

  • Members
  • 476 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:54 PM

Posted 28 May 2017 - 08:02 AM

After many, varied attempts I get:      "The arguments passed to sfc are invalid.  The offline windows directory specified points to the online system."

 

This is what I entered    sfc /SCANFILE=C:\windows\system32\kernel32.dll /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows

 

Does Windows Recovery Media refer to the USB Recovery Drive which I produced with EASUSTOD when I first had the PC., and which I did use (it does not boot into Recovery Environment but I opened that and clicked 'continue with Windows 10.'. )



#9 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:08:54 PM

Posted 28 May 2017 - 10:04 AM

Please create yourself a Windows 10 bootable media with Windows 10 Media Creation Tool.


Posted Image


#10 clayto

clayto
  • Topic Starter

  • Members
  • 476 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:54 PM

Posted 03 June 2017 - 02:33 AM

Both sfc and DISM are working OK now --- because I have installed Creators update. I had hoped it might clear away some issues and it has done so, although I have a few problems, some old and some new. The update so far has been fairly trouble free.



#11 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:08:54 PM

Posted 03 June 2017 - 02:59 AM

I am glad to hear your issue has been resolved!


Posted Image


#12 Innyve89

Innyve89

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:54 PM

Posted 22 June 2017 - 01:42 PM

I have encountered the same problem and tried dc3's solution but it didn't work. I read somewhere that you may need to check logs, I'm not sure how to do that or what I should do next.

#13 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,757 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:09:54 AM

Posted 23 June 2017 - 12:32 PM

@Innyve89

 

You should start your own topic.  There is insufficient information in your post regarding your issue, otherwise I would request to have your post split to create a new topic for you.  You may believe that you are experiencing the same problem as the OP, but there usually are enough differences that your issue could require a different approach to resolving your problem.  You will get a greater number of members reading a new topic.  This topic has eleven post which is enough to make others believe that this issue has been adequately addressed and will not see your post.

 

In your new topic please post a full description of the problem you are experiencing and any error messages you are receiving.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users