Friday, October 19, 2007

disabling VS just-in-time debugging

do you have Visual Studio installed on a machine that you use for every day tasks? are you tired of canceling the just-in-time debugging when you know that you're never going to use it on the apps that are triggering it? well, here's your post... turn it off.

from: http://msdn2.microsoft.com/en-us/library/k8kf6y2a.aspx

To enable/disable Just-In-Time debugging
- On the Tools menu, click Options.
- In the Options dialog box, select the Debugging folder.
- In the Debugging folder, select the Just-In-Time page.
- In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types: Managed, Native, or Script.
- To disable Just-In-Time debugging, once it has been enabled, you must be running with Administrator privileges. Enabling Just-In-Time debugging sets a registry key, and Administrator privileges are required to change that key.
- Click OK.

13 comments:

VB Student Failure said...

What if you uninstalled VS but winXP keeps trying to run the just-in-time debugging when an application crashes? Now I get this: "an unhandled win32 exception occurred in *program name* Just-in-time debugging this exception failed with the following error: no installed debugger has just-in-time debugging enabled" The error then tells me to disable it through the VS options but VS is uninstalled!

How can I disable this message if there is no more VS?

Stephen Cawood said...

VB student... I'm not sure what you're after. the behaviour you're seeing is what I wanted.

you need to see exceptions so that you know which program caused the error.

Charlie Arehart said...

Stephen, I'm with the VB student, and I wonder if you've misunderstood him in your reply. Like him, I'm getting the error that Windows is trying launch the JIT debugger, but I no longer have VS installed. You say, "you need to see exceptions so that you know which program caused the error." That's true, but we just don't want to be prompted to launch the debugger when we don't have it installed.

The steps you (and the technote) offered also presume we have VS installed, right? That's where you wanted us to use the Tools>Options feature? Again, if we don't have it, we can't use it.

Granted, you may not know the answer, but the VB student was asking a legit question, and one I'm seeking the answer to, which led me here. :-)

ghz said...

if it is neccessary you can switch back to the Dr. Watson thing by running "drwtsn32 -i"

source: Debugging Tools for Windows Help

Stephen Cawood said...

Charlie, you're right. These steps are for machines with VS installed. I haven't run into the issue without VS installed, so I'm afraid I can't help.

keenox said...

this happens to me too. it's very annoying. i uninstalled vs hoping that the annoying JIT message will dissapear, but this wasn't the case. fxxk microsoft!

Joseph said...

Here's hoping the drwtsn32 -i works. I get the JIT error message when I'm not even running code, just random iexplore.exe exceptions. Thought it was even funnier to keep on getting error messages when I disabled the JIT debugging. It's like saying you're not going to get the other JIT selection screen because you have disabled JIT debugging. Please click ok.

ldeffenb said...

Even worse, I've got VS 2008 whose evaluation timer just expired. I still get the popup, but if I say "Debug", it prompts me to elevate privileges, then it informs me that my evaluation period is over.

Now, how can I get this all to STOP without actually purchasing VS2008 just to get into the environment to disable the JIT debugger?

Pavn Andhukuri said...

Delete the following keys in the registry editor to completely disable Just-in-time Debugging (Even if Visual Studio is uninstalled)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

Anonymous said...

WAIT... DON'T remove your registry keys. Your programs/explorer will crash and you won't be able to access them at all. I've been trying to access a simple folder and it kept crashing. I removed the reg keys and it still crashes, it just doesn't give me a prompt this time.

Stephen Cawood said...

Anon raises a good point. You should think hard (and back it up) before you mess with your registry.

Anonymous said...

ghz' drwtsn32 -i just fixed it for me.

barryda said...

hi, so I no hardly anything at all about computers. I was talking a course at school for visual studios. I uninstalled it. Now whenever I go into this one folder on my computer get that message that say no installed debugger has just-in-time debugging enabled...blah blah blah. I ran the Dr. Watson for Windows now I can't access anything in that folder. When I try opening something the folder says not responding, or if i
leave it open for a few seconds it will crash closing itself and all other folders open. What do I need to do to stop this happening