Windows 10: Windows 11 Windows Defender scheduled scan returns 0x2 error

When the Windows Defender scheduled scan runs from Task Scheduler it does not complete and returns error code 0x2. This happens even if I run it manually from scheduler. This happens on all three of my Windows 11 machines and so is not machine specific. I am currently up to date on all three machines. Windows Defender will run to completion if I run it from Windows Security under Virus and Threat Protection. I know this has been a lingering issue, dating back to at least Windows 10. Is there a known solution?Thank you.

:)

 

Windows Defender Scheduled Scan returns result 0x2

Hey bru,
I'm curious what command you're using for your wd task (i.e. Action Tab). I'm just doing a daily signature update and quick scan.

 

Windows Defender Scheduled Scan returns result 0x2

Hi Mcd73165. This is an old issue that dates way back to the Windows 10 Anniversary Update. Some folks got the problem immediately. Others get it at a later time. In my case, it started in April after a cumulative update. Microsoft forums are loaded with this issue and a slew of suggestions. Some work -- most don't. The common fix is to do what you did -- create your own scheduled scan. In my case, the problem was solved by another cumulative update, which, from everything I've read, usually does not fix the issue.

Take a look at this thread I started in April. Windows Defender Errors Solved - Windows 10 Forums

 

Windows Defender Scheduled Scan returns result 0x2

Hi. There are 4 Windows Defender Scheduled Tasks. All but the periodic scan task result in successful completions (0x0). The Scheduled Periodic scan task results return 0x2. This holds true even if I run the task on demand. I've found that by disabling Real Time Protection then rebooting the machine causes the task to run successfully 1 or 2 times after which the problem occurs again. This holds true on 2 computers (1 laptop and 1 desktop). Some time ago I created my own Windows Defender scheduled scan to run once a week which runs flawlessly. The built in task starts a program in C:\ProgramData\Microsoft\Windows Defender\platform\4.16.17656.18052-0\MpCmdRun.exe Scan - ScheduleJob - ScanTrigger 55. The task I created starts a program in "C:\ProgramFiles\Windows Defender\MpCmdRun.exe" -Scan - Scan Type 1. When my task runs a Command Prompt window shows while scanning while the built in scan runs in the background. Has anyone else noticed a problem with the built in Periodic scan task? Again as mentioned earlier, the other 3 built in Defender Scheduled tasks run without any problem.
Thanks.