News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Blog Archives

  • Microsoft: Mumble mumble just ignore Windows Defender mumble mumble

    Posted on July 16th, 2019 at 15:00 woody Comment on the AskWoody Lounge

    Remember the sfc /scannow stupidity – where scanning a perfectly good Windows installation triggered errors such as, “Windows Resource Protection found corrupt files…” ? Susan wrote about it a week ago.

    @EP just posted a link to an official Microsoft explanation, KB 4513240, that sounds similar:

    The System File Checker (SFC) tool flags files in %windir%\System32\WindowsPowerShell\v1.0\Modules\Defender as corrupted or damaged. You see error messages such as the following:

    Hashes for file member do not match.

    This is a known issue in Windows 10, version 1607 and later versions, and Windows Defender version 4.18.1906.3 and later versions…. Future releases of Windows will use the updated files in the Windows image. After that, SFC will no longer flag the files.

    At least, I think it’s the same problem.

    So if you run sfc /scannow with any version of Win10 prior to 1909, you just need to know — by osmosis, no doubt — that you should ignore the error message.

    Meshuggeneh.

  • Microsoft confirms patch KB 3022345 breaks SFC /scannow

    Posted on May 26th, 2015 at 10:18 woody Comment on the AskWoody Lounge

    Even though SFC /scannow reports corrupt system files, in fact, the files aren’t corrupt at all. It’s just that Microsoft’s file scanner gets confused by Microsoft’s files.

    Oy.

    InfoWorld Tech Watch