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: 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:
Disable hotkeys in Windows 10 with Simple Disable Key Windows 10 build 14393.222 (KB3194496) available for Release Preview and Slow Ring Microsoft investigates Surface Pro 2 battery issues Windows 10 now runs on 400 millions devices Microsoft acknowledges Windows phone error 8500201D preventing email syncing
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
