Windows 10: Windows 10 build 14931 SFC scan cannot perform the requested operation

I was just finally able to update to Windows 10 build 14931 after working on it for about a week on and off. By all appearances the update looks successful and my machine seems to work just fine after the update however when I do my regular checks after such an update and in running a SFC scan in an elevated command prompt it fails at 19% with the message "Windows resource protection could not perform the requested operation". I did a search on this build and this error and it looks like others are having the same issue and a resolution but cannot find one. SO I am wondering if others are having this problem and if anyone has and has been able to resolve. Thanks!

PS Microsoft.....FYI.....I am really getting tired of jacking around with your substandard update roll-outs and thinking the insider program is not worth the hassle it causes. *Mad

:)

 

Error message "Windows Resource Protection could not perform the requested operations" when running SFC /Scannow

Reran SFC scan and at 23% returned message: Windows Resource Protection could not perform the requested operation. If I reboot and rerun, it will perform scan correctly.

 

Can't exit from Advanced Startup Option

When i type sfc /scannow, i started to scanning. After it scanned, it says windows resource protection couldn't perform the requested operation

 

(This isn't a MS forum... please feel free to make your feelings known to MS by phone, letter, carrier pigeon or the feedback app, or their technet forum for example. We're users, like you, often with our own frustrations).

 

Trust me, I am oh so aware of this. By the way....I did make my feelings known by all the avenues you outlined. I even sent my best carrier pigeon, but like everything else pertaining to Microsoft, it was probably sent to India so I am assuming at this point that the poor thing drowned.

 

Too far for the best trained carrier pigeon...

So, have you tried:
From an admin command prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Make sure the result is clear or fixed- else do not proceed.
Post back the result, which you can get after a restart as follows:
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!

Then run SFC /SCANNOW in Safe Mode - or at boot (see Option 1 here:
SFC Command - Run in Windows 10 - Windows 10 Forums
)

(If still no luck you can then try DISM commands - and after that, an in-place upgrade repair install).

 

@ToddB

If you can get yourself updated to at least build 14942, this issue has been resolved. Current Insider build is 14946. This excerpt is from the Feedback Hub release notes for build 14942.


We fixed an issue where running sfc /scannow in an elevated command prompt would fail at 20% with the error “could not perform the requested operation.”


You can read the entire release notes post in the Feedback Hub.

 

Thank you guys for this. Sorry for late reply. Say F14tomcat you mentioned "getting myself updated to build 14942". I am currently at build 14931 as a participant in the insider program. My machine indicates that it is currently up to date when I check for updates. Can you please advise how I can update to build 14942? Will I have to do a manual download? Thanks!

 

@ToddB ... I believe 14931 is the current latest build for Insiders in the Slow Ring. It is also the latest ISO available for Insider downloads.

Windows 10 Insider Preview ISO Advanced

Check your settings in Settings>Update and security>Windows Insider Program. If you are set to the SLOW ring, there are no more updates at the moment. You can change that to FAST if you wish. There will be a delay of anywhere from 1 to 3 days before you will get an update to a higher build. When you get it, it will be build 14951, the current FAST ring build. If you do change it, I recommend you restart your system.

Do A backup first before changing anything!


Here is the screen to check and change.





TC

 

Microsoft indicated that the preview builds could have bugs. This was known from the beginning. The whole purpose of being an Insider is to help find them.
Knowing this, I really can't understand your statement.

 

I am well aware of this. I am a software developer and although I don't implement or "release" on the magnitude and complexity that Microsoft does it is fair to say that if I implemented software to my users with as much trouble as I have had with the insider builds I would likely find myself flippin burgers (Nothing against burger flippers I love hamburgers). It is just my contention that with the resources that Microsoft has and the quality control requirements that should be in place these releases should not cause so much trouble (for me anyway) each time they are released. Like everything the price (although I don't pay for the releases directly) is going up and the quality is going down. You have a point however and I am no longer an"insider" due to the time I spend on each release trying to get it to upgrade/update completely/successfully. I guess I have realized I can not have such an unstable OS given other things that I do. So your point is noted thank you.

 

Thank you for this F14Tomcat. I thought of this very thing after I posted a reply to your previous post and made the necessary insider changes and tried to update to the latest build once available. Tried it twice, messed around with it for a little over a day and could not get it to update successfully. So I reverted to my previous build and removed myself from the insider ring. Can you please tell me one thing. The current release (slow ring current) that I am running still has an issue with the system files from what I can ascertain however my OS seems to work just fine and is stable. So with that being said would you suggest that I let things be as it is and if so how would you suggest I fix down the road when a fix becomes available (if that makes sense)? Thank you again!

 

@ToddB ... It (14931) has an expiration date, believe 5/17/17. You can check in WINVER command. You're not going to get any more updates to it. If you reverted to a previous build and dropped out of Insider, I am a little confused what build you are on right now. 14393.321 AU? 14926? (the Insider before 931) I was under the impression that if you completely dropped out of Insider, cut the cord with the MS program, they made you reinstall 14393. I've never been down that road, so I'm not really sure. Maybe someone reading this can say yeah or nay.

I, personally, would not keep running a version (14931) that refuses to update. I would either clean install it, go back to RTM AU, or somehow get my hands on an install.esd from the 14951 WU and make an ISO an do an in-place upgrade.

 

Again F14Tomcat thank you for the information above that you have provided me. I really appreciate your help. I am sorry to mislead you on my last post but I have not actually quit participating in the insider ring. I was going to do this but firstit prompts me if I want to suspend my participation for X amount of days. When one goes to permanently exit the insider ring it takes you to a site that advises that you should only exit on a build that is production. So I stopped my exit at that point and put alot of thought of the options you laid out above. I finally decided to try to update to 14951. So I found an ISO update of 14951 to download, burned and tried to update that way. In doing so it failed again, backed out installation update and restored my current version of windows. On re-boot I got the follow MS message:





So my question is: Do you know what course of action I should take to resolve the following error when trying to update to 14951? If that appears that it may involve a clean install I am hoping to go back to a stable production of Windows 10. Would that be the RTM you mentioned above and if so could you please advise how I would get to a stable version. I would like to get this OS stable as I am going to be using this laptop in a class that I will be starting tomorrow and I need a stable OS till April 17' which is how long my class is. I am going to be writing alot of code on this machine and I really don't want to spend my time and take the risk of messing around with OS problems. I cant lose my work on this machine. Again your suggestions and advise is greatly appreciated!
So

 

@ToddB - Good morning! The error you see above indicates the system could not put back your personal data and programs. It most likely did not get past about 75%, when it started to roll-back. This is a known problem. MS issued a warning concerning this. If you have any 3rd party Antivirus installed (which you do), chances are high the install will fail. This is from the official blog:

If you have a 3rd party antivirus product installed on your PC – your PC might not be able to complete the update to this build and roll-back to the previous build.

Announcing Windows 10 Insider Preview Build 14951 for Mobile and PC | Windows Experience Blog

And Shawn's announcement here on TF:

Insider Announcing Windows 10 Insider Preview Build 14951 for PC and Mobile - Windows 10 Forums

-----------------------------------------------------------------------------------------------------------------------------------------

Based on what you stated above regarding how you will be using the laptop, it would be ill-advised to use a Beta System. Using your machine for important school work and code writing demands the most stable environment you can get. With minimal extra 3rd party software. You have some apps installed you probably don't need or should not have. But that's a different topic.

The best advice I can give you, under your stated conditions, is to make a good system image backup, have all your personal files and program installers and product keys saved somewhere off-line. Do a complete, from scratch, Clean Install of the public RTM 14393. All the instructions and links you will need are in this tutorial:

Windows 10 - Clean Install - Windows 10 Forums[2]=Installation%20and%20Setup

If you have a class starting tomorrow (10/25/16), you really cannot afford to try to fix a test Insider system. Go back to stable RTM AU.

Hope this helps, TC.