Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Operating Systems
Windows 10
OS Archive
Windows 10 SFC /scannow Can't Fix Corrupted Files After WD Definition Update
Message
<blockquote data-quote="Gandalf_The_Grey" data-source="post: 823881" data-attributes="member: 52096"><p>Starting today, Windows 10 users are finding that the /sfc scannow feature is no longer working and that it states it found, but could not fix, corrupted Windows Defender PowerShell files.</p><p></p><p>The Windows System File Checker tool, commonly known as SFC, has a /scannow argument that will check the integrity of all protected Winodws system files and repair any issues that are found.</p><p></p><p>As of this morning, users in a <a href="https://www.wilderssecurity.com/threads/system-file-check-defender-and-windows-10-1903.418588/" target="_blank">wildersecurity.com thread</a> have started reporting that when they run <em>sfc /scannow</em>, the program is stating that "Windows Resource Protection found corrupt files but was unable to fix some of them." I too was able to reproduce this issue on a virtual machine with Windows Defender configured as the main antivirus program.</p><p></p><p><img src="https://www.bleepstatic.com/images/news/Microsoft/Windows-10/s/sfc/scannow-broken/sfc-scannow.jpg" alt="sfc /scannow error" class="fr-fic fr-dii fr-draggable " style="" /></p><p><em>sfc /scannow error </em></p><p></p><p>The full text of what users are seeing when they run this command can be read below:</p><p style="margin-left: 20px">Beginning system scan. This process will take some time.</p> <p style="margin-left: 20px"></p> <p style="margin-left: 20px">Beginning verification phase of system scan.</p> <p style="margin-left: 20px">Verification 100% complete.</p> <p style="margin-left: 20px"></p> <p style="margin-left: 20px">Windows Resource Protection found corrupt files but was unable to fix some of them.</p> <p style="margin-left: 20px">For online repairs, details are included in the CBS log file located at</p> <p style="margin-left: 20px">windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline</p> <p style="margin-left: 20px">repairs, details are included in the log file provided by the /OFFLOGFILE flag.</p><p></p><p>According to the CBS.log file, SFC is stating that the hashes for the Windows Defender PowerShell components located in the C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender are not matching their corresponding files in the WinSxS folder.</p><p></p><p><img src="https://www.bleepstatic.com/images/news/Microsoft/Windows-10/s/sfc/scannow-broken/cbs-log.jpg" alt="CBS Log" class="fr-fic fr-dii fr-draggable " style="" /></p><p><em>CBS Log</em></p><p></p><p>The strange thing, though, is that when checking with the fsutil hardlink list command, it is reporting that these files are properly linked, so the hashes should be the same.</p><p></p><p>While yesterday was the <a href="https://www.bleepingcomputer.com/news/microsoft/windows-10-july-2019-cumulative-updates-released-with-fixes/" target="_blank">July 2019 Patch Tuesday updates</a>, this does not appear to be related to the latest Windows 10 1903 KB4507453 cumulative update or the Windows 10 KB4507469 update as I do not have those installed.</p><p></p><p>Instead, it appears to be related to the latest definition updates for Windows Defender, which were released this morning and are version 1.297.823.0.</p><p></p><p><img src="https://www.bleepstatic.com/images/news/Microsoft/Windows-10/s/sfc/scannow-broken/defender-definitions.jpg" alt="Current Windows Defender Definitions" class="fr-fic fr-dii fr-draggable " style="" /></p><p><em>Current Windows Defender Definitions</em></p><p></p><p>Some users have reported being able to fix the error by running the following DISM commands:</p><p>[CODE]DISM /Online /Cleanup-Image /CheckHealth</p><p>DISM /Online /Cleanup-Image /ScanHealth</p><p>DISM /Online /Cleanup-Image /RestoreHealth[/CODE]</p><p></p><p>For those who do not wish to use these commands, you can wait for Microsoft ro resolve the issue.</p><p></p><p>[URL unfurl="true"]https://www.bleepingcomputer.com/news/microsoft/windows-10-sfc-scannow-cant-fix-corrupted-files-after-update/[/URL]</p></blockquote><p></p>
[QUOTE="Gandalf_The_Grey, post: 823881, member: 52096"] Starting today, Windows 10 users are finding that the /sfc scannow feature is no longer working and that it states it found, but could not fix, corrupted Windows Defender PowerShell files. The Windows System File Checker tool, commonly known as SFC, has a /scannow argument that will check the integrity of all protected Winodws system files and repair any issues that are found. As of this morning, users in a [URL='https://www.wilderssecurity.com/threads/system-file-check-defender-and-windows-10-1903.418588/']wildersecurity.com thread[/URL] have started reporting that when they run [I]sfc /scannow[/I], the program is stating that "Windows Resource Protection found corrupt files but was unable to fix some of them." I too was able to reproduce this issue on a virtual machine with Windows Defender configured as the main antivirus program. [IMG alt="sfc /scannow error"]https://www.bleepstatic.com/images/news/Microsoft/Windows-10/s/sfc/scannow-broken/sfc-scannow.jpg[/IMG] [I]sfc /scannow error [/I] The full text of what users are seeing when they run this command can be read below: [INDENT]Beginning system scan. This process will take some time.[/INDENT] [INDENT][/INDENT] [INDENT]Beginning verification phase of system scan.[/INDENT] [INDENT]Verification 100% complete.[/INDENT] [INDENT][/INDENT] [INDENT]Windows Resource Protection found corrupt files but was unable to fix some of them.[/INDENT] [INDENT]For online repairs, details are included in the CBS log file located at[/INDENT] [INDENT]windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline[/INDENT] [INDENT]repairs, details are included in the log file provided by the /OFFLOGFILE flag.[/INDENT] According to the CBS.log file, SFC is stating that the hashes for the Windows Defender PowerShell components located in the C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Defender are not matching their corresponding files in the WinSxS folder. [IMG alt="CBS Log"]https://www.bleepstatic.com/images/news/Microsoft/Windows-10/s/sfc/scannow-broken/cbs-log.jpg[/IMG] [I]CBS Log[/I] The strange thing, though, is that when checking with the fsutil hardlink list command, it is reporting that these files are properly linked, so the hashes should be the same. While yesterday was the [URL='https://www.bleepingcomputer.com/news/microsoft/windows-10-july-2019-cumulative-updates-released-with-fixes/']July 2019 Patch Tuesday updates[/URL], this does not appear to be related to the latest Windows 10 1903 KB4507453 cumulative update or the Windows 10 KB4507469 update as I do not have those installed. Instead, it appears to be related to the latest definition updates for Windows Defender, which were released this morning and are version 1.297.823.0. [IMG alt="Current Windows Defender Definitions"]https://www.bleepstatic.com/images/news/Microsoft/Windows-10/s/sfc/scannow-broken/defender-definitions.jpg[/IMG] [I]Current Windows Defender Definitions[/I] Some users have reported being able to fix the error by running the following DISM commands: [CODE]DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth[/CODE] For those who do not wish to use these commands, you can wait for Microsoft ro resolve the issue. [URL unfurl="true"]https://www.bleepingcomputer.com/news/microsoft/windows-10-sfc-scannow-cant-fix-corrupted-files-after-update/[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top
