Comments on: Disable script debugging, mdm.exe, or Machine Debug Manager

By: Chris Hope

Chris Hope — Sun, 24 Oct 2010 10:22:00 +0000

Looks like u have a browser hijacker. Antiviruses won’t do much good at removing them. Best fix for the future is to use a firewall (I’m using Comodo) to monitor any executables, batches, or VB scripts that u run. If the firewall detects that an exe etc. is trying to mod a protected COM interface or a critical area eg, common files, system32, your AV or FW directory then u can get a heads up whether malicious activity is underway.

P.S. There are a few browser Cache scrubbing utilities around, i’ve never used one. GOOD LUCK!

By: kocmohabt33

kocmohabt33 — Thu, 14 Oct 2010 16:40:00 +0000

I have a question what if my MDM.exe doesn’t appear in my Services tab in Administrative Tools, and on top of that, I have 2 instances of the file none of which are in C:Program FilesCommon FilesMicrosoft SharedVS7Debug, but in c:WINDOWSSystem32 and c:I386. I’ve noticed that this and another process called “mshta.exe” start at random and do so when I’m not paying attention to my Task Manager. I have no need of this process and would very much like to disable it… Any help is much appreciated.

By: Anonymous

Anonymous — Sun, 28 Mar 2010 13:39:00 +0000

Thanks for all the help… Especially Habeeb. I had the service turned off but knowing where it was hiding was great.

DAEMON Tools will not run (computer won’t even boot in normal mode) if this service is running; at least the one with the STPD.sys file version 1.6 or higher..

Thanks again.

By: Habeeb

Habeeb — Sat, 21 Nov 2009 09:29:00 +0000

The process responsible to be enabled/disabled as per the above step is situated at system32 folder of your OS. What I would like to add is that, after you perform the above steps, if you still find it appearing, then it is firing up from the following path.

C:Program FilesCommon FilesMicrosoft SharedVS7Debug

Just rename it to something like MDM1.exe and it will go.

Thats it.

By: trish

trish — Tue, 03 Nov 2009 06:04:00 +0000

worked 4 me, as well. thx!

By: still works

still works — Thu, 02 Jul 2009 02:10:00 +0000

Still works today on my XP – thanks!