Windows Defender, "Items Skipped During Scan"

That "items skipped" message doesn't bother me. All else looks good running the manual scan.

But I haven't seen a notification that Defender has run automatically in quite a while. That worries me. All the settings for it look good, & Defender still says "no action needed", though...

Defender definitely doesn't always run automatically, the schedule ranges from unpredictable to insane.

Manual scanning is no issue for me.

Thanks for the comforting words. I can't say I've seen the automatic one run every day, that's right. But I don't think I've seen it since March 15, the date I first posted into this this thread. I'll wait a day or two more before panicking. Thanks again.

I use Windows 10 Home 1909 and I have the same problem with Windows Defender since the beginning of March.

I have this notification that appears after a manual scan or when I want to scan files on a network drive.

I'm talking about it here :

https://answers.microsoft.com/fr-fr/protect/forum/all/el%c3%a9ments-ignor%c3%a9s-pendant-lanalyse/1fd44d4d-5df8-46a8-bd92-45bda9a7303e

The issue was not resolved. Any other suggestions

Not a problem ChipmunkLover, I understood your focus and was only wanting to be certain you didn't believe I was trying to tell you what to do.

I fully understand the frustration, but also realize the complications for Microsoft in their attempts to use Windows 10 to try to move quickly to a more secure platform, which though I think you might at least have a glimmer of an idea, I'm sure most consumers don't.

When Microsoft began their push with Windows 10 in 2015 I had expected to see many issues like this one, since the rapid development environment it's really intended to be is like nothing they, nor anyone else for that matter has ever attempted.  Though to most Windows 10 simply appears to be another Windows version with major updates similar to the older service packs twice each year, in truth it's actually more like a new set of well tested beta releases on that same cycle.

Unfortunately, this inevitably leads to some of the very issues you describe.  However, I must point out that due to certain design criteria inherent in the 32-bit Windows environment, that platform is likely to die a much quicker death than even its 64-bit sibling, since some of these security issues don't have a solution on the older 32-bit platform.

That may not have anything to do with why this particular notification message occurs on that system, but it's another reason I'd be advising clients or customers to try and leave it behind if at all possible.

I've forgotten which of the specific directions we've already discussed in this thread, but as for myself, I'm trying to transition quickly to first the Surface Go running Windows 10 S mode and eventually likely something based on Windows Core, hoping to leave the legacy desktop completely behind with my most recent systems and most of the malware and security issues along with it.

I know not everyone has that choice, but I feel it's likely to end up being the only way to survive the cyber attacks I expect we'll be experiencing over the next decade.  Attacks against our government health services websites during such a critical period are just a small hint at what's to come.

Stealing money from befuddled grandmothers and small businesses was just the beginning.

Rob