Back in April of last year I blogged about solving some of the reasons why people run into 'debugger is not properly installed' errors. Today, I would like to add some addendums.

First, make sure you go through all the original steps first. This blog will focus on fixing some of the most common failures that DebuggerDiagnostics.exe reports.

If the 'CoCreateCoLoaderFree' step fails, then try re-registering coloader.dll (regsvr32 "%CommonProgramFiles%\Microsoft Shared\VS7Debug\coloader.dll")

 

If the 'CoCreateIIS' step hangs, this is because CLSID {9E69610-B80D-11D0-B9B9-00A0C922E750}, is registered, but does not work. You can try:

  1. Reinstalling IIS (which is what owns that CLSID)
    -or-
  2. Deleting HKEY_CLASSES_ROOT\CLSID\{9E69610-B80D-11D0-B9B9-00A0C922E750}

 

If the CoCreateMachineDebugManager fails with '80080005', then check if you can start the 'mdm' service by doing 'net start mdm'. If you can, then you probably have corrupt registry permissions for HKEY_CLASSES_ROOT\CLSID\{73B25FFD-F501-437B-8B11-7F0DE383964F}. Open up regedit.exe, and make sure that 'Users' are allowed to read this key.