![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 79%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGN%3C/text%3E%3C/svg%3E)
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"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
Answer accepted by question author
69 additional answers
Sort by: Newest
-
Anonymous
2020-03-25T00:16:17+00:00 have the same problem, await ms fix
-
Anonymous
2020-03-24T23:46:57+00:00 So are you saying that Microsoft is going to fix this issue? I just started getting this a couple days ago. Is Microsoft going to send an update fix? You said that the issue was fixed and it's not. I'm still getting this message every time defender runs.
His workaround fixed my issue but as he explained to me, the workaround is not recommended. So I undid the changes. We are all waiting on Microsoft for a fix.
-
Anonymous
2020-03-24T23:07:35+00:00 So are you saying that Microsoft is going to fix this issue? I just started getting this a couple days ago. Is Microsoft going to send an update fix? You said that the issue was fixed and it's not. I'm still getting this message every time defender runs.
-
Anonymous
2020-03-24T17:04:27+00:00 Wow, that worked for me (Fix #1) on my Windows 10 VM. I am going to try it elsewhere (may try Fix #3 instead). Thanks!
But please read my article twice. The 1st edition was a quick shot deeply this night (here in Germany) to uncover the reason for this behavior. In the morning, after some sleep, I updated the article with further details. Scanning network shares is causing additional and senseless traffic, that could lead to trouble in bigger network environments. That's probably the reason, why Microsoft's developers has changed the behavior. Details and explanations may be found within my blog post.
Yes, thanks, that makes sense. I will undo the change and wait for something official from Microsoft. Fix #3 did not work anyway (there was no parameter given, and I tried "1" and that did not work, either). Hopefully, this is just a bug.