- Windows resource protection could not start repair service how to#
- Windows resource protection could not start repair service install#
- Windows resource protection could not start repair service driver#
- Windows resource protection could not start repair service Patch#
- Windows resource protection could not start repair service windows 10#
Windows resource protection could not start repair service install#
Therefore, disabling this service might fail to install the windows updates for the PC. The installer service of Windows enables installation, modification, and removal of Windows components. Therefore, try the simple and effective methods that are given below: Method 1: Start The Windows Installer Service
Windows resource protection could not start repair service how to#
It is quite normal that you might not be aware of how to resolve windows resource protection could not start the repair service. Smart Solutions To Fix Windows Resource Protection Could Not Start The Repair Service Here, we are going to discuss all the possible solutions and methods that will give you fruitful results. Therefore, if you are looking for ways to fix windows resource protection could not start the repair service, go through this article thoroughly. Hence, it is essential to find the exact cause of the error and then rectify it with the most perfect solutions. Various factors are responsible for this error to occur. One of the major problems that users are encountering is that the windows resource protection could not start the repair service. But at times, this operating system also generates a number of errors that are quite hard to resolve. Thank you for reading and any thoughts are appreciated.Being one of the most popular operating systems, Windows offers various features that provide a better user experience. I will be seeing if you can put it on a thumb drive and have 2008 recognize it. There were no restore points at this time but I will be changing that as soon as I have it back up with all needed software reinstalled. If you boot to the dvd to do a repair it gives you the option to restore to an earlier point. I noticed one feature in 2008 that would have saved me time if I had investigated further during the install. I still would like to hear any thoughts on this problem and if anyone else has come across it. I am currently wiping the system and will be reinstalling the os this afternoon. Nothing like walking into a room of people wanting to know why the server is down and trying to report what has happened after a virus and running the fixes and Windows updates. What was there was recoverable via an external drive. I was lucky enough to have this be a fairly new system so the group it belonged to hadn't stored too much data on it yet.
Windows resource protection could not start repair service driver#
The main cause seems to stem from driver updates and system configuration changes. For Vista there is a couple fixes you can try posted on various sites as it is more known. From what I've learned talking to other technicians if this happens and you can not run a repair or restore it to a month or more previously there is no known fix for 2008. It occurs more often on Vista and is known as the KSOD (blacK Screen Of Death). Apparently it is not too common in 2008 but is known to happen. I have since been researching this issue. I could really use some help here in bringing this server back up. I then tried a command I found from another site: SFC.EXE /scannow /offbootdir:c:\ /offwindir=c:\windows which just gave me the list of commands for SFC. I entered sfc /scannow and recieved this message: Windows Resource Protection could not start the repair service. I decided to try a repair inserted the dvd booted to it and went to the Command Prompt. I tried to boot into Safe Mode and met with the same results. Nothing but the mouse cursor and a black screen. But after the Windows loading bar finished the screen went black and after about 10-15 seconds the mouse cursor appeared. I plugged the network connection back in restarted the system and it appeared to boot normally. I then ran the latest version of Malicious Software Removal Tool which turned up nothing and then scanned the system with Trend which also reported no problems.
Windows resource protection could not start repair service Patch#
The patch KB958644-x86 was applied and reported itself non applicable to the system.
We removed the network connections and stopped the Server service. I have a server that was reported to be infected with the conficker worm.