Ask a new question

build 14279, sfc scan not able to run. win 10 Pro

I make it a point to run sfc /scannow with each new build. The last ~5 builds > no problems. With build 14279 get "Windows Resource Protection could not start the repair service."

Anything to worry about ?

3 people found this helpful

Was this discussion helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this discussion?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this discussion?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

In build 14279 the command SFC /scannow is broken (most likely it will be fixed in the next release)

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Darkz2012 discovered the real reason sfc /scannow does not work in build 14279,
wrpint.dll is missing from the required folders for both x64 & x86(32bit) systems.
If you copy the file wrpint.dll back to the right locations sfc /scannow works.

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_repair/14279-windows-10-resource-protection-couldnt-start/80b8f073-c56d-41ef-9c3f-0e93bd453123?page=2#LastReply

Darkz2012 replied on

just upgraded to insider 14279 went quite smoothly no real issues but  every time i try sfc /scannow now i get a message  "resource protection couldnt start repair service "

tried net start trustinstaller but still get the same error

I found the reason why it cant start (Well for me anyways) :-P

For some reason the wrpint.dll was missing from my "%SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d" 

I found a copy in 

"%SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14279.1000_none_5a92ee0dd788e433"

Now it's more than likely that the names are different but I am pretty sure the names would be pretty close depending on machine architecture that is, for X86 going off a hunch here but I would look in.

"%SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_c982bd78c7285567"

To see if its there, if not take a wander over to..

"%SystemRoot%\winsxs\x86_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14279.1000_none_fe74528a1f2b72fd"

Copy the wrpint.dll  And wack it in the appropriate folder. Also you will need to grant ownership from System to Administrators to copy the file to the correct directory.

If unsure of the correct locations just delete or move CBS.LOG from Windows\Logs\CBS run SFC /SCANNOW and open the log file and it will tell you the right location, or the location its trying to find the file in.

I will also state the the X64 Version of the file is about 65.5Kb & the X86 Version is about 55Kb

I will post a SS to show that I'm not telling ya porky pies.

Hope this helps Good Day :-)


Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks Darkz2012 for finding the solution for Build 14279 only:

Some commands below to help anyone with changing permissions and copying the missing wrpint.dll

Build 14279 only

Right-click start, Command prompt (admin)

For x64 bit systems - copy & paste these commands in one go & press enter (repeat for x32 bit commands)

takeown /F %SystemRoot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d\* /R /A
icacls %SystemRoot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d\*.* /T /grant administrators:F
xcopy /C /R /O /Y %SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14279.1000_none_5a92ee0dd788e433\wrpint.dll %SystemRoot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_25a158fc7f85c69d

Build 14279 only

Right-click start, Command prompt (admin)

For x32 bit systems - copy & paste these commands in one go & press enter

takeown /F %SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_c982bd78c7285567\* /R /A
icacls %SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_c982bd78c7285567\*.* /T /grant administrators:F
xcopy /C /R /O /Y %SystemRoot%\winsxs\x86_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14279.1000_none_fe74528a1f2b72fd\wrpint.dll %SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14279.1000_none_c982bd78c7285567

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I would just like to know why Microsoft would prevent insiders from running sfc scan ? 
Don't believe everything you think

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I would just like to know why Microsoft would prevent insiders from running sfc scan ? 

Someone at Microsoft more than likely was having a bad hair day, OR something was changed and it wasn't picked up :-)

Windows 11, The Guessing OS.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

WHY SHOULD WE INSIDERS HAVE TO FIX SOMETHING THEY CREATED?

THEY CREATED THE PROBLEM.

I ALSO LOST MY ABILITY TO DOWNLOAD UPDATES FOR OTHER SOFTWARE PROGRAMS & MY ABILITY TO USE MY MCAFEE SECURITY & THEIR PROGRAMS.

REGARDS, THOMAS ANDERSEN, PREVIEW BUILD INSIDER.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

You don't have to do anything. You can always leave the Windows Insider program and go back to using software that has been thoroughly tested. 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

Thanks for the reports. We've done some investigation and we are working to get a solution out asap.

Rohit S

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Build 14291

A workaround, based on the above instructions for Build 14279, but with different folder name(s) until Microsoft fixes the problem is to copy

wrpint.dll

from

C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14291.1001_none_b11fef854a76db2a

to

C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14291.1001_none_7c2e5a73f273bd94


to copy that file it is necessary to take ownership of both those folders, and to set permissions to allow "Full control."

Suggest it is wise to revert ownership to "TrustedInstaller" after copying. However "TrustedInstaller" is not "found" as a "User or Group" when selecting an object type.

An internet search (A?KVG) showed that it is necessary to enter the object name as "NT Service\TrustedInstaller"

Also wise to revert permissions for the "Name" used during copying to "Read & execute", "List folder contents", and "Read" only.

 sfc /scannow ran to completion after making these changes, and found no errors!

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Build 14291 - sfc /scannow is not working also with same error
Windows resource Protection could not start the repair service.

Updated commands for build 14291 only
to help anyone with changing permissions and copying the missing wrpint.dll

Build 14291 only
Right-click start, Command prompt (admin)
For x64 bit systems - copy & paste these commands in one go & press enter (repeat for x32 bit commands)

takeown /F %SystemRoot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14291.1001_none_7c2e5a73f273bd94\* /R /A
icacls %SystemRoot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14291.1001_none_7c2e5a73f273bd94\*.* /T /grant administrators:F
xcopy /C /R /O /Y %SystemRoot%\winsxs\amd64_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14291.1001_none_b11fef854a76db2a\wrpint.dll %SystemRoot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14291.1001_none_7c2e5a73f273bd94

Build 14291 only
Right-click start, Command prompt (admin)
For x32 bit systems - copy & paste these commands in one go & press enter

takeown /F %SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14291.1001_none_200fbef03a164c5e\* /R /A
icacls %SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14291.1001_none_200fbef03a164c5e\*.* /T /grant administrators:F
xcopy /C /R /O /Y %SystemRoot%\winsxs\x86_microsoft-windows-servicingstack-onecore_31bf3856ad364e35_10.0.14291.1001_none_55015401921969f4\wrpint.dll %SystemRoot%\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14291.1001_none_200fbef03a164c5e

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Discussion Info

Last updated February 2, 2021 Views 800 Applies to: