Need help with something like batch files trying to shut down M$ Security Essentials

[chrisJumbo]

Clint, I just put the two kill commands that you had above into a batch file, ran it and it killed both processes. Now the first time both stopped and then MsMpEng.exe restarted. I manually killed it after that. Then I re-started it and ran my kill.bat again. This time both stopped. So I'm not sure what allowed it to restart itself, but obviously it has some self-protection thing somewhere.

kill.bat

C:\WINDOWS\system32\taskkill.exe /f /im MsMpEng.exe
C:\WINDOWS\system32\taskkill.exe /f /im msseces.exe
Pause

Secondly, I don't think Steve was trying to be a pain with his first response, but as a moderator, I think he believes he needs to warn others who may be attempting things that they shouldn't. Anyway, I hate to see it when posts get nasty. I hope the above helps you.

BTW, I also restarted it again, but will probably re-boot. Also, there are programs that I will manually stop for similar reasons to Clint. I can't add anymore memory and it saves me enough to get through the day without getting the running out of virtual memory error and things do run smoother. I wouldn't suggest this for the uninitiated. :O)

[deepsand]

Looking through your list of tasks with which you feel MSE interferes, there is but one that stands out as being perhaps affected by MSE, that of A/V creation and/or editing. Is the problem there one regarding MSE's usage of CPU or RAM?

[Clint1]

Looking through your list of tasks with which you feel MSE interferes, there is but one that stands out as being perhaps affected by MSE, that of A/V creation and/or editing. Is the problem there one regarding MSE's usage of CPU or RAM?

(Also defrag'ing et al). To a point.....I don't have a dual, quad or 8-core CPU, it's just a HyperThreaded CPU. So even though it's 3.4ghz (2.4ghz 200/800mhz FSB o'clocked to 282/1100mhz+ bus), (plus the max dual-channel RAM & 10,000rpm VelociRaptor), it's not as good at multitasking as a little slower multi-core CPU. I do ~a dozen or more things at a time, with gobs of files and apps open, therefore the fewer Services or background apps/programs that don't need to be running at the time, the better.

[Clint1]

Clint, I just put the two kill commands that you had above into a batch file, ran it and it killed both processes. Now the first time both stopped and then MsMpEng.exe restarted. I manually killed it after that. Then I re-started it and ran my kill.bat again. This time both stopped. So I'm not sure what allowed it to restart itself, but obviously it has some self-protection thing somewhere.

Nice, green coming your way.

If you look under Services > Microsoft Antimalware Service > Properties > Recovery, those drop-downs need to be set to "Take no action". If they are set to Restart, I believe that's what's causing it to restart after the stop command.

C:\WINDOWS\system32\taskkill.exe /f /im MsMpEng.exe
C:\WINDOWS\system32\taskkill.exe /f /im msseces.exe
Pause

Works great, thanks a bunch. But how do you get the command window to automatically close once the tasks are completed? I believe there's a line that can be added at the end, but I don't know what that is.

Secondly, I don't think Steve was trying to be a pain with his first response, but as a moderator, I think he believes he needs to warn others who may be attempting things that they shouldn't.

It may appear that way to an "outsider" ( ), but that has been going on with me for many years. So there is much more to the entire context of the story than just one post. The post could have been prefaced with any appropriate warnings (for newbies), which is totally fine, but then followed by the assistance sought (then it just got worse from there in subsequent posts). You are the first person, to actually help (and I appreciate that).

Anyway, I hate to see it when posts get nasty. I hope the above helps you.

Couldn't agree more, that's why I leave here for months on end. And; indeed it does, thanks again.

BTW, I also restarted it again, but will probably re-boot. Also, there are programs that I will manually stop for similar reasons to Clint. I can't add anymore memory and it saves me enough to get through the day without getting the running out of virtual memory error and things do run smoother. I wouldn't suggest this for the uninitiated. :O)

That's another reason why I do this (described in ^ prior post above), PageFile usage. The lower that "Commit charge" is kept (PF usage) shown in XP's Task Manager, the more stable the PC. (You may want to try changing the size of your PF/virtual memory).

[Clint1]

Works great, thanks a bunch. But how do you get the command window to automatically close once the tasks are completed? I believe there's a line that can be added at the end, but I don't know what that is.

Ok I found out by just removing the "Pause" line at the end, I can click it, MSE totally shuts down, and the cmd window automatically closes. So it's working fine now.

But the problem still remains on how to get the START batch file's window to automatically close. This still works to start MSE again, but the cmd window remains open:

@title MSE Manager
@echo Running MsMpSvc... Wait until it's done.
net start MsMpSvc
"C:\Program Files\Microsoft Security Client\msseces.exe"

[Clint1]

Contrary to what is said here, the simple "Exit" line doesn't work!

Exits out of the DOS window if the batch file is running from Windows.
Additional information and the syntax of this command in each version of Windows and MS-DOS can be found on our EXIT command page.
And there's nothing on this "EXIT command page" other than "Exit"!

[Clint1]

Contrary to what is said here, the simple "Exit" line doesn't work!

Exits out of the DOS window if the batch file is running from Windows.
Additional information and the syntax of this command in each version of Windows and MS-DOS can be found on our EXIT command page.
And there's nothing on this "EXIT command page" other than "Exit"!

(Sorry again about all the dupe posts, couldn't help it. There really should be a way for us to delete our own posts).

I got this fixed. To start all of MSE, in one-click, and to have the cmd window automatically close, the batch file is:

@echo off
net start MsMpSvc
start "" "C:\Program Files\Microsoft Security Client\msseces.exe"
EXIT

I'm not sure the "EXIT" at the end does anything, but the key was the start "" area. I'm at a lost as to why that's not needed in any of my other batch files!

To stop all of MSE (thanks to Chris), and *to have the cmd window automatically close, the batch file is:

C:\WINDOWS\system32\taskkill.exe /f /im MsMpEng.exe
C:\WINDOWS\system32\taskkill.exe /f /im msseces.exe

*Had to remove the "Pause" at the end.

[chrisJumbo]

In general, I have found that once a batch file is done it exits and goes away on its own. I had the "pause" statement so that I could see the results of each line as it was running. I'm glad we found a solution. Happy editing.

BTW, I do some simple movie making using my wife's Windows 7 PC and just use Windows movie maker. When I tried to use my Windows XP PC the program would crash all of the time. Since moving to my wife's, I haven't had any problems.

And blessings back to you. :O)

[Clint1]

BTW, I do some simple movie making using my wife's Windows 7 PC and just use Windows movie maker. When I tried to use my Windows XP PC the program would crash all of the time. Since moving to my wife's, I haven't had any problems.

Maybe a thread on WMM, it's most buggy. I've found that the older version 2.1.4026.0 is better, more stable. With XP's SP's, I don't remember if it's SP2 or SP3, the moviemk.exe file changes to v2.1.4027.0 . You should be able to find the 4026 version in one of those $SPuninstall folders. You don't need to change any of the .dll files or the others, but I saved those too in case I might. Rename the 4027 version of moviemk.exe and keep them both in the same folder, because .mswmm files are not cross-compatible between versions. So if you edited a clip with 4027 and saved the .mswmm file, it will not open in 4026, but you can simply drag the v4027 .mswmm file to the renamed v4027 moviemk.exe file and it will open, you don't even have to rename it back.

[chrisJumbo]

Thanks for the tip. I will have to check that out. :O)