

Looking at the WindowsUpdate.log, you can see three distinct error codes:ģ 22:09:22.3989998 9200 8576 Handler * START * Command Line Install Updates to install = 1ģ 22:09:27.7566112 9200 8576 Handler Command line install completed. the latest cumulative update, servicing stack, etc.). The same error occurs even after all other updates have successfully installed (e.g. When doing this as part of an MDT image creation task sequence, that failure ends up happening over and over again, as MDT detects the failure, reboots the computer, and then tries it again, only for it to fail again.

Users can manually update the Windows Defender definitions by going to Windows Security > Virus & threat protection and then clicking on the ' Check for updates' link.I have been building Windows 10 images based on the Windows 10 20H2 media and seeing repeated failures on the “Security Intelligence Update for Microsoft Defender Antivirus – KB2267602” installation. Windows 10 users can check what version of Windows Defender is being used by checking this guide. Microsoft has just released new Antivirus/Antispyware definition whose version is 1.313.1687.0 that fixes the issue. Our Quick Scan was not affected because it did not go deep enough into the file system to encounter a file with two dots in it. This also meant that the bug affected both Quick and Full scans. Once you find the offending file, you can remove the extra dot, start the Windows Defender Antivirus Server, and the next scan will be able to continue and not crash. xmlĪfter Windows Defender crashes, you may be able to see the offending file by opening Event Viewer and going to Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational and examining the errors. Two dots in file name causes a crashĪ user on Reddit has discovered that these crashes are being caused by files that have two periods in the file name.įor example, when Windows Defender scans the following files it would crash because of the two dots. While two of us at BleepingComputer verified the crashes using the above version, another person was able to complete a Full Scan without an issue.
