Windows 10: Security alerts found doing a full systems scans using Windows Defender

The Windows Defender Security alerts were found during full scan on Sunday 10-20-24. I moved them into Quarantined, then ran Microsoft Defender Offline, Full scan late last night and early this morning. The last Full scans didn't any new threats. I was kind of shocked they were contained in Dell Support directory and files.I review the Event View logs for them. This is the event view log information:Microsoft Defender Antivirus has detected malware or other potentially unwanted software. For more information please s

:)

 

Defender not Running Regular Scan


I've never understood the need some people feel to set up a scheduled task to run a Defender scan. For the past year the automatic maintenance has run Defender scans for me.

That is, until the Anniversary Upgrade - it broke something and Defender never ran another scan. It finally alerted me that a scan was long overdue. I followed the suggestion on another thread...
Windows Defender No Longer Performs AutoScan
...and the automatic maintenance scans are back to running regularly again.

 

defender scans

Hi Ian,

Thanks for posting your query on Microsoft Community.

This issue might occur if you have set any task scheduler for Windows Defender.

I suggest you to delete the task for Windows defender and check if it helps.

Follow the below steps:

• 
  Search and open Schedule tasks.
  
• 
  In the left-hand menu, open the Task Scheduler Library, then select
  Microsoft >Windows >Windows Defender.
  
• 
  Double-click Windows Defender Scheduled Scan.
  
• 
  Select the Triggers panel, then select Delete.
  

Hope it helps, reply to us with the status of your issue. We will be happy to assist you.

 

New Defender Platform 4.18.2003.4-0 - Items skipped during scan Alert

@Farvatten -- Just got updated to platform version 4.18.2003.8 via Windows Update. Defender scan ran and there was no notification of any item(s) being skipped. I did not run the PowerShell command so, for at least now, it appears maybe Microsoft actually fixed the problem?????