Yep, I had the same problem some days ago while I was debugging a 32-bit
target, and I couldn’t figure out how to cope with it. I was to fully
reinstall the WinDbg package. I think the problem is related to windows
workspace settings, because before WinDbg dramatically failed to start
the next time, I opened many different child windows, docked and not.
Anyways, any useful information and suggestions how to deal with this
oddity will be highly appreciated.
Konstantin Manurin
System Programmer
Again, in case anywone gets bitten…
I am getting this with increasing frequency using windbg 6.6.0007.5 (64
bit). The symtoms are that you start windbg and all you get is a dialog bix
with that text in it and an OK button. Clicking the button dismisses the
dialog and windbg exits.This is a hard error, and the only ways I have found to fix this is either
to do a complete deinstall reinstall or to rename away the directory\Program Files\Debugging Tools for Windows 64-bit\riched20.dll