Visual Studio JIT Debugger loads extremely slowly, 30 seconds

When I run the .Net program that executes

System.Diagnostics.Debugger.Launch()

which should call the JIT debugger. Here's what happens on my machine:

A warning appears called "Machine Debug Manager" explaining its command line options. So this is mdm.exe, but could it not be silent?

The real problem is now: exactly 30 seconds later, the Visual Studio JIT Debugger selection dialog box appears.

Since procmon does not show registry or file system activity during these 30 seconds, I assume some timeout will occur (due to the 30 second length). Procmon also shows that vsjitdebugger.exe fires at the very beginning, so 30 seconds seems to cause vsjitdebugger, not mdm.

Does anyone have an idea how I can get rid of the delay?

+4
source share
1 answer

It is decided:

deleted "C: \ Program Files (x86) \ Common Files \ Microsoft Shared \ VS7DEBUG \ mdm.exe"

which is apparently something old. regsvr32 / u mdm.exe failed, so you can manually clean the COM registry.

JIT starts right away.

+2
source

All Articles