Have you encountered with Windows Resource Protection error? Windows operating system is no stranger to errors and corruption to the files. However, a simple change in the settings can cause plenty of problems. The Windows Resource Protection error is not a big deal, and anyone can solve it with minimum CMD knowledge.However, technical & command knowledge should not pose a problem. But you’ve to learn what caused the “Windows Resource Protection could not start the repair service” error. Many Windows users do not read the error causes, and they end up finding the making the same again. We do not want you to make the same mistake again, so allow us to tell you the reasons behind “Windows Resource Protection could not start the repair service” error.What Triggers This Error?There is a service called “ Windows Modules Installer (TrustedInstaller),” and it has full-control over registry keys and Windows Resource Protection (WRP).
- Windows Resource Protection could not start the repair service is an error you can receive when trying to start SFC /scannow. We help you solve this.
- Jun 08, 2016 WIndows resource protection has found some corrupt files. No Fix in Performance & Maintenance Hello, I have tried to run sfc/ scannow and it gives me the notification that: WIndows resource protection has found some corrupt files but is unable to fix some of them.
The 'windows resource protection could not start the repair service' error is one of the weirdest error people encounter.
The Microsoft added System File Checker (SFC) on your copy so that you can identify & fix the corrupted files.The (SFC) System File Checker interrupted because the Windows Modules Installer is disabled. If the WMS is disabled, then it causes the Windows Resource Protection could not start the repair service. In short, you have to enable the Windows Modules Installer, and the problem gets fixed. How to Fix Window Resource Protection Error: 1. It Works On 64-Bit Windows PCBy following simple steps, you can fix the problem in a few clicks without any issues.
Over the past few weeks I have experienced several interesting problems between my two computers. Of particular note was an issue I discovered when the Event Viewer on my Windows 7 Ultimate 32-bit machine failed. After some troubleshooting I decided to attemptSFC /scannow. I got the error message 'Windows Resource Protection could not perform the requested operation.' This worried me.
So I attempted to boot into WinRE from my Win 7 installation disk. The result in WinRE was the same. No good.I scrounged forum after forum looking for an answer, but nothing worked. It seemed like everyone just gave up and reinstalled their OS, but I would not do that.
So I kept exploring. CBS.log showed nothing of interest as sfc never made it past 'Beginningverification phase of system scan.' Finally I found this article: which, while interesting and comprehensive, did not directly solve my issue. It did, however, point me to the registry key:HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSourcePathThis registry entry does not appear to exist in Win 7, but another entry in it's vicinity caught my attention:HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionProgramFilesDirI had recently moved my program files dir to a different hard drive and placed a junction point in it's place. In the process I had altered HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionProgramFilesDir to point to 'D:Program Files', thenback to 'C:Program Files' when the junction point was in place.' C:Program Files' is incorrect!the trailing backslash is incorrect, and must be removed!with the ProgramFilesDir value set to 'C:Program Files' I ran sfc /scannow and it scanned properly, finding several corrupt files (some of which required checking cbs.log to repair).I can imagine that some virus maker somewhere will use this to break SFC in the future, but here's your solution!So to review: HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionProgramFilesDir cannot have a trailing backslash!Tell your friends!:)Cheers,Crosmanrond. Hi UnclevaraI realise this might be too late, but the error tells you that you have to specify the correct drive letters.'
Offbootdir' is the system reserved patition (usually about 100MB in size).' Winbootdir' is the windows directory on the drive you would like to fix.You can view the different drives (volumes) by using the DISKPART utility. In elevated command prompt (or PowerShell), typediskpartto enter the Disk Partitioning Console, then typelist volumeto view your machine's volume detailsThank you to Crosmanrond!!! There was a power failure on my Windows 2008 R2 system while it was doing an update to Service Pack 1, and I have been struggling for a week to get sfc to run.
Windows Resource Protection Could Not Repair Corrupt Files
While installing Java earlier, I received and error telling me Javacould not find the%CommonProgramFiles(x64)% directory.The SFC scans also only got to 15% and would then give me the same error 'Windows Resource Protection could not perform the requested operation.' I did what you suggested - changed all the HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionProgramFilesDir keys from e.g. '%ProgramFiles%' to 'C:Program Files' and the scan completed successfully.Thanks a million!
Cbs.log
I know this is a bit old, but I was having the same issue and this is still the second result via Google.None of the above solutions helped me but the suggestion of using /offbootdir and /offwindir gave me the error that the drive isn't offline (makes sense since I was booted to the OS on that drive).I pulled the drive and hooked it up via eSATA to another computer and was able to run sfc /scannow /offbootdir=f: /offwindir=f:windows (F: being the drive letter when I hooked it up).The scan worked but didn't return any errors. I'm not looking for help, just posting to help others that might find this. Odd thing I noticed that my System Volume has no letter.
Apr 29, 2016 - I want to expand the opportunities of rebellion with this mod, improve the. STAR WARS™ Rebellion General Discussions Topic Details.
Is this normal?Microsoft DiskPart version 6.1.7601Copyright (C) 1999-2008 Microsoft Corporation.On computer: LARRY-PCDISKPART list volumeVolume ### Ltr Label Fs Type Size Status Info-Volume 0 F DVD-ROM 0 B No MediaVolume 1 System Rese NTFS Partition 100 MB Healthy SystemVolume 2 C NTFS Partition 931 GB Healthy BootVolume 3 D Backup B NTFS Partition 232 GB HealthyVolume 4 E Removable 0 B No MediaDISKPART. My system reserved partition doesn't even show up:DISKPART list volumeVolume ### Ltr Label Fs Type Size Status Info-Volume 0 D DVD-ROM 0 B No MediaVolume 1 Recovery NTFS Partition 14 GB Healthy SysteVolume 2 C OS NTFS Partition 283 GB Healthy BootNot to mention the Recovery Volume has not drive letter.I'm trying to fix a PC for a client that got a nasty trojan on here. I've removed the malware, but cannot create a restore point nor do a sfc/ scannow command process beyond 10% which gets me the error everyone has flocked here for. I also tried the latercommand left here and got the error message others have gotten because of it. I'm guessing without specifying the correct partition letter in the command I will be unable to execute it.