Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Virtualization Community Blog

Office 2003 and Machine Debug Manager Error

Created: 16 Jul 2008 • Updated: 29 Jul 2010 • 1 comment
Tony 1776's picture
0 0 Votes
Login to vote

I have been working to get Office 2003 virtualized and deployed in a testing environment. When I deployed my SVS package I keep getting a hardware install screen popping up when I restarted. It didn't need to find any drivers because under admin it goes away after a minute or two. But under a limited account it produces errors.

If I clicked fast enough under a admin account I could see what the "device" was and it said Machine Debug Manager.

At first I thought some driver just wasn't installed correctly but when the same problem popped up right after I put my SVS package on the computer I thought something must be up with my package. I haven't found the exact cause of the problem but I have found a fix.

The first fix is the one that ended up working for me.

Open run and enter: (note quotation marks are needed)

"%CommonProgramFiles%\Microsoft Shared\VS7Debug\mdm.exe" /unregserver

Click Ok then enter the following:

"%CommonProgramFiles%\Microsoft Shared\VS7Debug\mdm.exe" /regserver

Click Ok then reboot the computer.

Or try this:

  1. Start->Run regedit.exe
  2. Go to HKEY_CLASSES_ROOT\AppId\{9209B1A6-964A-11D0-9372-00A0C9034910}
  3. Delete 'AccessPermission' and 'LaunchPermission'
  4. Start->Run cmd.exe
  5. "%CommonProgramFiles%\Microsoft Shared\VS7Debug\mdm.exe" /regserver
  6. net stop mdm
  7. net start mdm

Hopefully this will be helpful to someone as it took me quite some time to figure out.

Comments 1 CommentJump to latest comment

bhawver's picture

Thanks for the info above. After a ton of searching, I actually found that this is typically caused by the way the VSA file was packaged.

People that get the New Hardware Found message after packaging Office or other applications most likely packaged the VSA using "global settings". This is improper and should be avoided.

I found in my scenario the best way to handle packaging something like Office (where we wanted the updates to be installed into the SVS layer) was to do it as an application and choose "c:\windows\system32\cmd.exe" as the application we were installing. This allowed us to install the hotfixes, service packs for Office and other items (office related) into one layer.

The other way of doing this would be to use the SVS Admin panel and update the layer one at a time with each hotfix/service pack for the application.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

Login to vote