Windows defender auto update schedule

Snodon · 28 Nov 2021

Nothing works
Created cmd file in Windows dir:-

cmd
"%ProgramFiles%\Windows Defender\MpCmdRun.exe" –signatureupdate
or
"C:\Program Files\Windows Defender\MpCmdRun.exe" –signatureupdate

window opens but nothing runs
tried changing it to a .bat file - nothing runs
tried changing to a .ps1 file - it tries to run but I get the same old parameter invalid message
running from task manager with admin priv - same result

If I run either command direct in a cmd window they run ok

Years ago when I worked in IT support I always thanked god for microsoft as I made a fortune sorting out their crap. Now I just get angry. come back DOS all is forgiven.

MaloK · 28 Nov 2021

Do you have a value named "AutoRun" at:

[HKCU\Software\Microsoft\Command Processor]
or:
[HKLM\Software\Microsoft\Command Processor]

Snodon · 29 Nov 2021

Do you have a value named "AutoRun" at:

[HKCU\Software\Microsoft\Command Processor] - this key does not exist
or:
[HKLM\Software\Microsoft\Command Processor] - this key exists but no value

MaloK · 29 Nov 2021

Snodon said:

Do you have a value named "AutoRun" at:

[HKCU\Software\Microsoft\Command Processor] - this key does not exist
or:
[HKLM\Software\Microsoft\Command Processor] - this key exists but no value

Hi Snodon,

I just did a couple of test and even only a "space" in the AutoRun value is enough to make the command fail.

Remove completely the AutoRun Value and try your cmd again.

Try3 · 29 Nov 2021

Please would you post the task definition
Task scheduler,
[select your WD update task],
right-click, Export.

Then zip the file [or just add .txt to the end of its filename] just to ease posting it,
click on the Insert image/file icon

in the TenForums post editing toolbar,
select the zipped / renamed file and post.

I'll then be able to run a comparison test using exactly the same task definition as you.

Do you have any other strange symptoms at the moment [in TS or elsewhere]?

Why does your local time show as 0644 instead of the 1244 I would have expected?

Denis

You do no need to bother with this additional step as I'll do I for you but you could do it before posting if you wanted to.

Before attempting to use anybody else's task definition .xml file, you have to open it in a text editor [such as Notepad] and delete the entire that starts and ends <UserId>...</UserId>
<UserId>UserAccountsSID</UserId>

If this line was left in, Task scheduler would object.
Deleting this line allows Task scheduler to import the task [and assign the current user to it].

Snodon · 29 Nov 2021

MaloK said:

Hi Snodon,
I just did a couple of test and even only a "space" in the AutoRun value is enough to make the command fail.
Remove completely the AutoRun Value and try your cmd again.

Sorry, I was not specific enough.

The key - [HKCU\Software\Microsoft\Command Processor] does not exist at all

The key - [HKLM\Software\Microsoft\Command Processor] does exist but there is no "AutoRun" within it

MaloK · 29 Nov 2021

I don't understand why your cmd processor is not working, and also as Denis mentioned, do you have any other kind of strange behaviours occurring in your machine ?

Snodon · 29 Nov 2021

No, machine working ok.
This is a new install of win10, about a month, as my Intel SSD failed after 4 years. The Intel SSD in the other machine is now about to fail as well, only 2 years old - not happy. Replacing with Samsung ones.

MaloK · 29 Nov 2021

Ok, near new installation... but still something looks wrong.

can you do what I call the Dumb test, create a cmd file containing

DumbTest.cmd:

Code:

@echo off
echo this is a dumb test
pause

Double-click on it, You should receive:

Code:

this is a dumb test
Press any key to continue . . .

And the windows should remain open. Any other comportment would be suspicious.

Snodon · 29 Nov 2021

Yes, that works ok