Solved Why does MS not categorize MSE definition updates as important??

[TBoyd]

With the recent MSE V4 version update, the folder for MpCmdRun.exe has changed.
The BAT file in POST #15 needs to be changed to work with MSE V4.
I'm looking at a Win7 x64 install, but i expect Win7 32 bit is the same...

The old folder was "c:\Program Files\Microsoft Security Client\Antimalware"
The new folder is "c:\Program Files\Microsoft Security Client"

The new BAT file for V4 is:

-- --------------------------------------------------------
:: MSEUpdate.bat

@echo off
cd "c:\Program files\Microsoft Security Client"
MpCmdRun.exe -SignatureUpdate
:: pause
-- ---------------------------------------------------------

Note:
If you have any issues you can remove the "::" in the pause statement.
This will uncomment the pause, and the CMD window will stay open so you can check for any errors.
Just hit enter in the CMD window to close it...

Thanks, David. This update should be valuable for anyone else using this method!

It now works for MSE V4.

BTW - Tried to give you another rep, but it wouldn't let me!

 

[DavidE]

@TBoyd,
You're welcome and thank you for testing this.
don't worry about the rep - thought appreciated.
As we discussed, here is how i have the task setup so there is no CMD window.
Let me know if there are any questions/issues.


I have my Scheduled MSE definition update setup to NOT use a BAT file.
Task Scheduler runs MpCmdRun.exe directly, rather than via a BAT file.

The difference is this way you won't see the CMD window every time the Task runs.
Some people prefer seeing the BAT CMD window, I don't.
It's a personal choice...

Either way you can check if the update process works by looking in Windows Update History.

For anyone that does not want to see the BAT file CMD window, here is how I have Task Scheduler setup for MSE V4.

I set up the task running Task Scheduler with my ADMIN account (run as administrator).
I use the PC logged in with my STANDARD account.

Task summary/highlights:

Task properties (General tab):

Author: <my ADMIN> account
"Run whether user is logged on or not" is selected
"Run with highest privileges" is checked
​

Trigger:

On a schedule
Daily
Recur every 1 days
Repeat task every 4 hours for a duration of 1 day (4 hours is my personal choice...)
​

Action:

Program/Script: "C:\Program Files\Microsoft Security Client\MpCmdRun.exe"
Add Arguments (optional): -SignatureUpdate
​

View attachment 210695

View attachment 210696

View attachment 210697

 

[TBoyd]

Hey David

I meant to post sooner, but I have noticed that the task is not working. I eliminated using the .bat file method & am using the Task Scheduler method. I have noticed that a cmd window pops up for a fraction of a second at the time of the scheduled task, but the update does not occur.

I may try going back to the .bat file method with the corrected location of the .exe file & see what happens.

The only difference I noted when following your instructions for the Task Scheduler method is that when I checked "Run whether user is logged on or not" & "OK", I get a message stating that it cannot be set up with blank password accounts - or something to that effect. The task is accepted if I check "Run only when user is logged on". I don't know if this has anything to do with the problem.

NOTE:

I just tried changing to "Run only when user is logged on", and then checked the "Do not store password" box just below. This time the task was accepted.

I will have to wait & see if this will work now on the next scheduled time. This may or may not be an exception to the instructions - i.e. - when the user does not use a password. I'll report back on this.

 

[DavidE]

Hi TBoyd,

Yea, using an Admin account without a PW could make a difference.
I have a PW on all my ADMIN accounts, and I normally log in with a STANDARD account.

The way you saved your task setup with "Run only when user is logged on" and "Do not store password" may work...
If it doesn't let me know, there are some things we can try for trouble shooting.

 

[TBoyd]

Sorry I took so long to report back on this. A few days ago, I deleted the task via the task scheduler & entered the new command via the elevated command prompt. It appeared to work OK, but then it stopped working. I found that my entry via the command prompt also shows in the task scheduler, and when I reviewed the various tabs in the properties menu of the task, some options & conditions didn't seem correct. I have corrected them to suit my requirements & will see if this runs like it used to.

--Probably a "cockpit" problem!

 

[DavidE]

You can look at at C:\Windows\Temp\MpCmdRun.log
See if you have an entry in there for when the scheduled task should have run.

If there is an entry for the task, and it has error(s) post that back.
If there is no entry for that task run time, let me know.

Next step would be to "Enable all tasks history" in Task Scheduler, run it, and see what is logged there.

 

[TBoyd]

You can look at at C:\Windows\Temp\MpCmdRun.log
See if you have an entry in there for when the scheduled task should have run.

If there is an entry for the task, and it has error(s) post that back.
If there is no entry for that task run time, let me know.

Next step would be to "Enable all tasks history" in Task Scheduler, run it, and see what is logged there.

It apparently is running now, but the scheduled times for it to run are not in the log file. The "Last Run Time" in Task Scheduler shows it ran at the appointed time, and the result was successful - so it must be OK now. Previously - before changing some settings for the task - the last run time was not showing anything.

BTW - I haven't chosen "Enable all tasks history".

It is obvious now that - without enabling the tasks history - scheduled tasks are not recorded in the log file, but manually-run tasks are recorded. If I want to verify a scheduled task run, it can be viewed only in the Task Scheduler under the "Last Run Time" column. Enabling all tasks history would enable me to check them in the log file, but I choose not to have a ever-growing log file of all tasks.

Thanks, David!

 

[DavidE]

OK, let me know...

When I test/troubleshoot a scheduled task I temporarily Enable History:

Enable All tasks History

Manually run the task with Rt-click > Run
Check what is in the History TAB for errors/success (for the task)

If needed, set up a timer for 1-2 minutes from now
Wait for it to run, and check the History TAB for errors/success

Disable All tasks history
​

If you still have issues, you are using an ADMIN account without a PW as your "normal everyday" logon, right?

If needed, I can set up an account like yours and do some testing...just want to be sure i understand correctly.

 

[TBoyd]

It's working OK now, David. I must have had some settings checked incorrectly in the beginning. I now check it from the Task Scheduler & it is running successfully & on schedule.

Thanks much!

 

[o770]

Task Scheduler runs MpCmdRun.exe directly, rather than via a BAT file. The difference is this way you won't see the CMD window every time the Task runs.

Hello. How have you got to hide the command prompt window? I get mine popping up everytime just like TBoyd. Thanks!

 

[DavidE]

Try changing the User to SYSTEM in the Task.

Step 3 in this link should help you make that change.

How To Fix Microsoft Security Essentials Virus Definitions Updates | groovyPost

 

[o770]

Wonderful, thanks!

 

[DavidE]

You're welcome!