Windows 10: sfc scannow not working and windows module installer stopped immediately again and again...

Few days back I saw that windows update is not happening . then searched internet and got suggestion to enable windows module installer but after starting it everytime it stopped after few minutes. then try to use sfc scannow but it is also not working and saying that windows resourde protection couldn't start repair service and dism command says no such interface. tried with all possible tricks but everytime same error "windows resource protection couldnot start repair service". My question is is there any corruption in recovery image so if I try to reset pc will be a problem there? Pls help me with solution. Thanks.

:)

 

SFC scannow not working but verify only is working

there is no problem in chkdsk I've checked When I select command prompt and sfc scannow from f8 and repair.. it shows that a reboot is required for pending repair and pending renames folder in winsxs is full of files.. what should I do??

 

sfc /scannow "Windows Resource Protection could not start the repair service"

Hi,

Windows Resource Protection could not start the repair service is an error which may occur if you are trying to run the System File Checker tool (SFC /SCANNOW) to scan and repair Windows system files. To resolve this error, we suggest that you follow the
steps below:

• Press the Windows + R keys to open run command box.
• In the run command box, type services.msc, and press
  Enter.
• In the list of services, double click the Windows Modules Installer service.
• Set the startup type to Auto, and click OK.
• Restart your computer.
• After the restart, you'll be able to run the sfc /scannow command without any problems.

We would appreciate it if you could get back to us and provide us your feedback.

 

SFC /SCANNOW Errors After Update

I've just updated a Windows 8.1 Pro PC to Windows 10 using the Techbench ISO which updated without any problems. However, I've just run sfc /scannow and it found errors it could not repair. I have managed to get sfc /scannow to run without errors - see what I did below:

1. Ran sfc /scannow which showed error "Windows Resource Protection found corrupt files but was unable to fix some of them."
2. Ran Dism /Online /Cleanup-Image /ScanHealth which reported "The component store is repairable."
3. Ran Dism /Online /Cleanup-Image /RestoreHealth which failed with Error: 0x800f081f "The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature."
4. Mounted the W10 Techbench ISO and ran Dism /Online /Cleanup-Image /RestoreHealth /source:wim:G:\sources\install.wim:1 /limitaccess which reported successfully "The restore operation completed successfully."
5. Ran sfc /scannow wich completed successfully with report "Windows Resource Protection found corrupt files and successfully repaired them."

Please advise:

1. Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
2. Why did I have to use install.wim from the Techbench ISO at step 4 above for Dism /Online /Cleanup-Image /RestoreHealth to work and will I have to use install.wim from the Techbench ISO every time I need to run this Dism command?
3. How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?