More on diagnosing ‘The debugger is not properly installed’


It seems that you can no longer make comments on my post — Diagnosing ‘The debugger is not properly installed’. Feal free to leave new comments here.


Comments (3)

  1. David Davies (Goldname Sachs) says:

    I seem to be having the same general problem.

    Have tried all the suggestions above but to no avail.

    What is most weird is the debugging was working 3 days ago and I cant identify any thing that has changed since which would be a likely cause.

    Also I can see a problem in the Debugger Diagnostics

    C:Program FilesDebuggerDiagnostics>debuggerdiagnostics

    Begin ‘CheckMDMImage()’

    mdm.exe: version 7.10.3077.0 with unexpected hash {B19F8401-D870EC1C-3FFE4390-2320C75A-F21AAB00}.

    Result of ‘CheckMDMImage()’ is ‘00000000’

    Begin ‘CheckMSDBG2Image()’

    msdbg2.dll: version 7.10.3077.0 with unexpected hash {3F51C5FC-9F1ECA65-3A1A636C-7CEF0B90-FDD23491}.

    Result of ‘CheckMSDBG2Image()’ is ‘00000000’

    Begin ‘CheckCSMImage()’

    csm.dll: version 7.10.3077.0 with unexpected hash {B6C94B03-0869D9A5-0254B23C-EF2E09D5-F2163A1B}.

    Result of ‘CheckCSMImage()’ is ‘00000000’

    Begin ‘CheckPDMImage()’

    pdm.dll: version 7.10.3077.0 with unexpected hash {4B7C4F86-125CC871-B394D2F7-F0E6018B-CC0600A8}.

    Result of ‘CheckPDMImage()’ is ‘00000000’

    Begin ‘CheckColoaderImage()’

    coloader.dll: version 7.10.3077.0 with unexpected hash {1A9E74B5-4CDC7112-CC1027B6-A9BA59E1-AED6120F}.

    coloader.tlb: hash {CF0AEEDA-C0BC2E64-877D923E-9660E04F-ED949C15}.

    Result of ‘CheckColoaderImage()’ is ‘00000000’

    Begin ‘CoInitialize(NULL)’

    Result of ‘CoInitialize(NULL)’ is ‘00000000’

    Begin ‘InitializeCOMSecurity()’

    Result of ‘InitializeCOMSecurity()’ is ‘00000000’

    Begin ‘CoCreateCoLoaderApt(&spLoaderApt)’

    Result of ‘CoCreateCoLoaderApt(&spLoaderApt)’ is ‘00000000’

    Begin ‘CoCreateCoLoaderFree(&spLoaderFree)’

    Result of ‘CoCreateCoLoaderFree(&spLoaderFree)’ is ‘00000000’

    Begin ‘UseCoLoader(spLoaderFree)’

    .NET: SoftwareMicrosoftVisualStudio7.0 – not registered

    .NET: SoftwareMicrosoftVisualStudio7.1 – engine created

    .NET: SoftwareMicrosoftVisualStudio8.0 – not registered

    .NET: SoftwareMicrosoftRascal8.0 – not registered

    Native: SoftwareMicrosoftVisualStudio7.0 – not registered

    Native: SoftwareMicrosoftVisualStudio7.1 – engine created

    Native: SoftwareMicrosoftVisualStudio8.0 – not registered

    Native: SoftwareMicrosoftRascal8.0 – not registered

    Result of ‘UseCoLoader(spLoaderFree)’ is ‘00000000’

    Begin ‘CoCreateIIS(&spIIS)’

    Result of ‘CoCreateIIS(&spIIS)’ is ‘00000000’

    Begin ‘CoCreateMachineDebugManager(&spMachine)’

    Result of ‘CoCreateMachineDebugManager(&spMachine)’ is ‘00000000’

    Begin ‘GetCausalityProvider(spMachine, &spProvider)’

    Result of ‘GetCausalityProvider(spMachine, &spProvider)’ is ‘00000000’

    Begin ‘GetSessionString(&sbstrSessionString)’

    Session string = ‘version=7.0;autoattachclsid={70F65411-FE8C-4248-BCFF-701C8B2F4529};machine="

    FWITTKW126304";session={2DF949F7-F438-4A62-8F35-F866443DE701}’

    Result of ‘GetSessionString(&sbstrSessionString)’ is ‘00000000’

    Begin ‘AddToSessionMap(sbstrSessionString, spProvider)’

    MDM Called IDebugSession2::IsAlive(void)

    Result of ‘AddToSessionMap(sbstrSessionString, spProvider)’ is ‘00000000’

    Begin ‘UseOleAut32(spMachine)’

    Result of ‘UseOleAut32(spMachine)’ is ‘00000000’

    Any new ideas would be gratefully received.

  2. Gregg Miskelly says:

    Everything looks clean from the debugger diagnostics run. What is your scenario — (1) Managed or native? (2) Web or client? (3) Do you get the error when you open the processes dialog?

    If it is managed, my guess is that you have a corupt installation of the .NET Framework.