title: WinDbg: Version mismatch of dbghelp.dll when trying to attach to a process
body: <p>Over a year ago I already used WinDbg and DebugDiag to find a memory leak in a JNI native DLL that we use from within Java. Now I am searching for a thread handle leak. 
  I created a memory dump using Process Explorer and tried to analyze it in DebugDiag, but all I get are script errors:
  <img src="https://i.stack.imgur.com/u0HgU.png" alt="Memory dump analysis fails with script errors"></p>
  
  <p>I also tried WinDbg, but it is not able to attach to a process anymore. I always get the error message "dbghelp.dll has a version mismatch with the debugger":
  <img src="https://i.stack.imgur.com/Qcbi4.png" alt="WinDbg 6.12.0002.633 X86 fails with &quot;Could not attach to process xxx 0x80004005&quot;">
  <em>("Unbekannter Fehler" means "Unknown error")</em></p>
  
  <p>I uninstalled DebugDiag and the Windows SDK, then downloaded the newest versions and installed Windows SDK 8 and DebugDiag 1.2 (x86). The problem stays the same. Even after replacing the Windows SDK with Version 7.1 (the latest SDK for Windows 7) nothing changes.</p>
  
  <p>I'm using a machine with Windows 7 (32 Bit).</p>
  
  <p>I assume that the problems in DebugDiag have the same cause as the problems in WinDbg. But I don't understand what version mismatch is meant (and googling didn't help either):</p>
  
  <ul>
  <li>WinDbg: 6.12.0002.633</li>
  <li>dbgeng: 6.12.0002.633</li>
  <li>dbghelp: 6.12.0002.633</li>
  </ul>
  
  <p>How can I make WinDbg (and hopefully DebugDiag) work again?</p>