Every new Windows 10 Preview build brings its own dose of issues to Insiders who install it. At the end of the day, Windows Insider Program’s main purpose is for users to identify and report that issues, so Microsoft can fix them. However, there are some issues that are quite annoying, and last for a couple of builds.
One of those issues is the problem with the sfc/scannow command in the Command Prompt. Users have been reporting the crashing problems with this command for a couple of builds, and Microsoft finally decided to address it.
In the previous Windows 10 Preview build, Microsoft publicly acknowledged the problem, and promised the solution in some of the future builds. And in build 14942, the solution finally arrived, as Microsoft announced that the issues with sfc/scannow has been finally addressed.
“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.””
It looks like the problem is indeed solved, since we haven’t notice any complaint about this on the Community forums. So, Windows Insiders now can normally use this command to address other issues in the latest build, that are still present.
Maybe it took too long for Microsoft to resolve this problem, since it was one of the most frequently reported problems lately. But, since the issues doesn’t exist anymore, it really doesn’t matter now.
Have you tried to run sfc/scannow in an elevated Command Prompt? Is the command working for you now? Tell us in the comments.
RELATED STORIES YOU NEED TO CHECK OUT:
- Windows 10 Build 14942 causes Edge crashes, installation problems, and more
- Windows 10 build 14942 increases number of processes in Task Manager
- Windows 10 build 14942 lets you hide app list in Start Menu
- Download Windows 10 update KB3197356 manually to fix installation issues