Hi all, I've just done a clean install of Win7 Ultimate 32-bit, and also, amongst other programs, Office 2003. Previously I had installed this on Win XP and even with 'visual basic for applications' selected in the Office installation options, managed not to awaken the sleeping dragon that is MDM.exe, Microsoft's Machine Debugging Manager. But now on my new system I see that MDM is back. Needless to say, Microsoft's advice about turning off the service doesn't make one jot of difference to its presence. Nor does reconfiguring the Office installer to remove (as far as I can see) all references to scripting, including visual basic for applications. Sure, I can manually stop the MDM service, but would rather it wasn't there at all. I also suspect it may be resurrected by an Office update sometime. Of course, it doesn't use much memory, but it's irritating on principle. If, as Microsoft claims (in the kb link above), it is "you can safely turn off the Machine Debug Manager [...] If you do not use your computer for debugging purposes", then why the heck isn't there just a big fat control panel button that says "MACHINE DEBUG MANAGER ON / OFF"?? I can remember battling the MDM zombie back in the days of Office 2000! I can't believe this is still an issue, even in the days of Vista/7 UAC. Can anyone advise on how to behead it for good in 2010?