Microsoft acknowledges SFC scan problem in Windows 10 builds


Ivan Jenic
by Ivan Jenic
Author
Loading Comments

The exclusive semaphore is owned by another process

It’s completely normal that every Windows 10 build introduces its own various issues. At the end of the day, the purpose of Windows 10’s Insider Program is to gather feedback about these issues so that Microsoft can address them in future releases.

Still, there are some problems that take quite some time to be acknowledged by Microsoft, let alone fixed. One of these issues is a long-standing problem with the sfc/scannow command in the Command Prompt, something that has been broken for a couple of builds now.

Users have reported this issue in every Windows 10 build since the very day it appeared with Microsoft ignoring it ignored it. Well, until now, is: In the freshest Windows 10 build 14936, Microsoft finally acknowledged the problem with the SFC scan command:

“Running sfc /scannow in an elevated command prompt will fail at 20% with the error “could not perform the requested operation.”

The company warned Insiders about this problem even though the majority of users already knew about it and others having already encountered it. Microsoft didn’t mention when the fix would be released but even acknowledgement is a solid start, so we should expect to see in future builds.

This problem indeed needs to be solved as soon as possible because the SFC scan command is one of the most widely-used Command Prompt commands. If the SFC scan command itself is broken, many other issues can’t be fixed.

Have you noticed the same problem with the SFC scan in recent Windows 10 builds? Tell us in the comment section below.

RELATED STORIES YOU NEED TO CHECK OUT: