Windows Defender Default Scheduled Task - Looking For Information

I'm looking for some information.
If your on 1703, using Windows Defender and it's Default Scheduled Scan.
The Last Run Results always shows 0x2 (Failed) ... no matter how the action is run (automatic or manual)
Could you check your Windows Credentials / Generic Credentials and see if your PCNAME\USERNAME is listed ?

I've got two pcs Desktop & Laptop (1703 - 15063.332)
Desktop
Windows Defender / Default Scheduled Scan always shows Last Run Results of 0x2 (Failed) ... no matter how the action is run (automatic or manual)
Windows Credentials / Generic Credentials - PCNAME\USERNAME - NOT LISTED.
Note: I added the PCNAME\USERNAME and now the Last Run Results is showing 0x0 (Successful)
Note: I couldn't even open Command Prompt as Admin and run the command without if failing, now I can.
"C:\Program Files\Windows Defender\MpCmdRun.exe" Scan -ScheduleJob -ScanTrigger 55

Laptop
Windows Defender / Default Scheduled Scan always shows Last Run Results of 0x0 (Successful) ... no matter how the action is run (automatic or manual)
Windows Credentials / Generic Credentials - PCNAME\USERNAME - LISTED.

Task Scheduler Library / Microsoft / Windows / Windows Defender
Windows Defender Schedules Scan / Actions - C:\Program Files\Windows Defender\MpCmdRun.exe Scan -ScheduleJob -ScanTrigger 55

I have Ver 1607 on a desktop.
The scheduled Defender scan does not run. It has never run since I have had Ver 1607. It always shows as 0x2 error. The user account is 'System'.

I posted here as well but there was never a solution.

My workaround was to create a Scheduled Task. This works fine.

Currently I have windows defender available to view and can see whether it has or has not performed a scan. The action center may display that it ran 6 or 9 scan but it has not. When you view the task scheduler you will then see the error codes. The action center is counting the scans but these scans never occurred with the windows defender. They are failed events with the task scheduler.

Jeddie,
Yes, the Defender Default Scheduled Scan runs under the System Account.
Yes, you can create your own Scheduled Scan, which is run under your User Account.

I've read that if you change the Default Scheduled Scan to run under your User Account, it will complete successfully. I was just curious, if adding your User Account (PCNAME/USERNAME) to Windows Credentials / Generic Credentials accomplished the same thing.

Eagle51 said:

I've read that if you change the Default Scheduled Scan to run under your User Account, it will complete successfully. I was just curious, if adding your User Account (PCNAME/USERNAME) to Windows Credentials / Generic Credentials accomplished the same thing.

Yes @Eagle51 I am aware of this possible solution. I haven't tried it yet. I was hoping for a solution from Microsoft in next version 1703.

But based on OP it seems it has not been fixed?

Jeddie,
As far as I know it has not been fixed. As I mentioned, on my Laptop the Default Scheduled Scan runs successfully and I didn't add my User Account (PCNAME\USERNAME) to Windows Credentials / Generic Credentials and no clue want did ... lol
Since I added my User Account (PCNAME\USERNAME) to Windows Credentials / Generic Credentials on my Desktop, the Default Scheduled Scan runs successfully. So maybe that is the fix, your guess is a good as mine :)

Note: I've tried changing the from the System Account to User Account which does work.

@Eagle51
I was updated to Ver 1703 with the hope of a fix from Microsoft. Well Windows defender continues to not run. It shows the 0x2 error as it did under ver 1607. The other 3 auto maintenance tasks run correctly.

Next step is the change the User Account in the task to my User name.

How MS can offer an AV that does not perform regular scans as promised is beyond me. This is a major bug in my opinion.