Microsoft has released an update to fix that behavior, see Update KB4052623: Microsoft fixes Defender ScanSkip Bug. See also the marked answer.
Windows Defender, "Items Skipped During Scan"
I keep getting this notification after quick scans, "Windows Defender skipped an item due to exclusions or network protection settings."
To make this clear: I don't have ANY exclusions, and as far as I'm aware, I haven't changed my network protection settings in the past.
What's going on? Is this malware, or a bug with the new update? How do I fix this? I want to be reassured that I'm safe, this isn't very reassuring.
EDIT: Thank you to Techradar for bringing this issue to light. If any employees read this, could you perhaps re-title it in a way which doesn't make users feel so endangered by the bug? All of us have come to the conlusion that (especially with MBAM) we should be clear.
Windows for home | Windows 10 | Security and privacy
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
69 additional answers
Sort by: Most helpful
-
Anonymous
2020-03-22T20:56:34+00:00 I getting the same message/problem and I'm also worried too. :(
I filed the problem through Feedback Hub, but don't how to find my report?
Hopefully Microsoft will fix it sometime soon?
EDIT: I also keep getting this notification after all defender scans, "Windows Defender skipped an item due to exclusions or network protection settings."
To make this clear: I don't have ANY exclusions, as far as I'm aware, I also have'nt changed my network protection settings in the past either.
-
Anonymous
2020-03-21T17:55:11+00:00 I update and quick scan frequently. Today was the first time " WDA scan skipped an item due to exclusion or network scanning settings".
I proceeded to run a full scan with same message displayed. I have made no changes, done nothing to cause this message. Just updates.
-
Anonymous
2020-03-21T17:14:17+00:00 I run a scan everyday. Just got the error message today
-
Anonymous
2020-03-21T02:47:16+00:00 Having same problem on 2 of 3 computers. The one not having this problem hasn't gotten the March Culmlitave update yet