You can confirm this yourself by right clicking on your Crystaldiskmark folder and selecting "Scan with Microsoft Defender". So I find it highly questionable that the temp files are infected. Those temp files are only created on the fly when you start a benchmark run, then they are deleted afterward. And note that Defender is only flagging the *temporary* benchmark files as infected, not the actual Crystaldiskmark executables. I've been using this Crystaldiskmark for a long time with no issues before now. I have Windows 10, and it just started doing this on my machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |