Build 14931 sfc not working

Running Insider Preview on a 64 bit Pro machine. Couldn't get Store to open so ran sfc /scannow with the following result:

Microsoft Windows [Version 10.0.14931]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>sfc /scannow
Beginning system scan.  This process will take some time.
Beginning verification phase of system scan.
Verification 20% complete.
Windows Resource Protection could not perform the requested operation.
C:\WINDOWS\system32>

Any ideas?

I didn't try to open Store (no Internet connection), but always check sfc with new Builds to see if it's working. My 64-bit Win 10 Pro Build 14931 had EXACTLY the same result above. It's a BUG in System File Checker. Ran it before and after restart - failed at 20% both times. My CPU is AMD.

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.

This is a bug and has been reported many times which you can find other postings by searching this forum also in the feedback Hub just use sfc /scannow as the search title in the Feedback Hub and you can upvote the many postings.
I'm a unpaid independent Advisor/volunteer

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.

It's not just sfc that isn't working properly either:

Microsoft Windows [Version 10.0.14931]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>
C:\WINDOWS\system32>dism /online /cleanup-image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.14931.1000
Image Version: 10.0.14931.1000
[==                         4.5%                           ]
Error: 1726
The remote procedure call failed.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
C:\WINDOWS\system32>

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.

 
 

Question Info


Last updated February 2, 2021 Views 97 Applies to: