sign up log in tour help stack overflow careers

Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ×

How to disable Visual Studio debugger?

Not to bore you, I'm gonna make long story short. Two machines, identical systems on them, identical programs (mostly). One has Visual
Studio installed, one has ... uhmm, something else.

Sometimes when I try to install applications from let's say a CD, Visual Studio's Just-In-Time Debugger pops up, reports an "unhandled
win32 exception in ..." and asks whether I want to debug using "New instance of Microsoft VIsual Studio 2010". If I choose Yes, it runs VS, if
I choose No it closes the thing, and I'm back in Windows Explorer.

Which would be ok, except I know the application is perfectly all right, and this way I cannot install it (in this latest cast it was the client from
my bank for internet banking and paying bills and such).

So, how do I get rid of that thing (just-in-time debugger)?

I don't want to uninstall VS since I'm using it daily, of course.

Edit 1 :: I tried disabling Just-In-Time debugging in VS's Tools/Options/Debugging/Just-In-Time, then unchecking all three checkmarks, but
that just gave another error when trying to run the executable installation program.

An unhandled win32 exception occurred in autorun.exe [some number]. Just-In-Time debugging this exception failed with the following error:
No installed debugger has Just-In-Time debugging enabled. In Visual Studio, Just-In-Time debugging can be enabled from ...

Check the documentation index for 'Just-in-time debugging, errors' for more information.

Very informative :/

Edit 2 :: The application runs fine on the other machine that doesn't have VS installed. To a large extent software on both machines is the
same, with just some minor differences (systems installed from image). Minor differences: notepad2, ++, git, ... some small stuff that is left
to dev's own choosing.

I don't want this to sound as rant against VS, since I realize it's taking that tone, but I extremelly dislike software that is not self contained
and messes other software up. And I had the same problem before with other applications as well. So for now, I'm blaming VS.

If necessary, I'm willing to disable all kinds of debugging for this thing to work permanently (mostly use print statements anyways), if that will
help. And if it possible.

visual-studio-2010

edited Apr 14 '11 at 20:15 asked Apr 14 '11 at 19:04

Rook
27.7k 27 109 179

4 Umm... the debugger should only come up if the application was going to crash anyway... the alternative is
usually something like dr watson that creates the equivalent of a core file – forsvarir Apr 14 '11 at 19:09

1 @forsvarir - I've also encountered the same behaviour with other applications, but this is the first time it
really bothers me since I need(!) to run this (gotta pay the bills). The application I'm trying to run is, I assure
you, perfectly allright. I don't think the bank would give out CD's with applications that aren't working. –
Rook Apr 14 '11 at 19:12

3 @unknown close voter - Questions relating to Visual Studio are offtopic here? I believe they fit quite nicely
into the "software tools commonly used by programmers" category. – Rook Apr 14 '11 at 19:13

8 Answers

I just had this problem today with Visual Studio 2013. This MSDN article: Just-In-Time
Debugging in Visual Studio works for me. In my case, I just rename Debugger to
Debugger_del and DbgManagedDebugger to DbgManagedDebugger_del.

To disable Just-In-Time debugging by editing the registry

1. On the Start menu, search for and run regedit.exe

 1. On the Start menu, search for and run regedit.exe

2. In the Registry Editor window, locate and delete the follow registry keys:

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

3. If your computer is running a 64-bit operating system, also delete the following registry
keys:

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

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDeb
ugger

4. Take care not to accidentally delete or change any other registry keys.
5. Close the Registy Editor window.

edited Jan 9 at 2:19 answered Feb 24 '14 at 6:34

Afriza N Arief
2,787 19 48

+1 Thank you, this helped me! – Shaul Behr May 26 '14 at 11:30

+1 Thank you from me, too. The other answer with the VS Options did not change the values in the
Wow6432Node folder. Only after deleting the debugger keys in there, VS2010 went quiet. – Yamakuzure
Sep 25 '14 at 10:06

Enabling or disabling Just-In-Time debugging

You can enable or disable Just-In-Time debugging from the Options dialog box. To enable or
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

edited Sep 22 '12 at 17:51 answered Sep 21 '12 at 5:42

j0k Jitender kumar Gautam
16k 11 43 58 111 1 2

the question is rather old, but to who might still looking in here for an answer I found the following
Microsoft MSDN page that helped me to disable the just-in-time debugger:

http://msdn.microsoft.com/en-us/library/k8kf6y2a(v=vs.80).aspx http://msdn.microsoft.com/en-
us/library/5hs4b7a6.aspx

it worked for me in 2010 Shell Edition.

answered Jul 2 '12 at 11:12

dev0
391 2 2

I am adding this response even though this is an old topic because I have just spent most of the
day on this very issue and finally solved it. Every solution I found focused on disabling or turning
off JIT debugging in Visual Studio, deleting keys from the registry or changing IE script debugging
settings. But if you don't have a registered copy of VS, you have a problem. Of course, many of
the solutions work in different ways but then you are left with the error above "no installed
debugger has just-in-time debugging enabled" which no-one seems to have an answer for.
However, the answer is not to disable JIT but rather stop server side debugging in your
application. Unless you actually want to do server side debugging it is not necessary for it to be
on.

It makes complete sense to me now because I had server side debugging turned on in ASP.
Before installing VS, it made no difference because no debugger was assigned to handle the
bugs so they were sent to the browser. Once I installed VS, JIT took over and did what tit was
supposed to do.

So the quick answer, open IIS, click on default sites or your sites and in your application settings,
ASP in my case, turn off server side debugging!!

It may not be everyone's answer, or even the solution to the above problem, but hope it provides
more insight to this problem and help someone else.

answered Jul 3 '13 at 9:49

ws8
42 6

regarding the key in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\AeDebug and SOFTWARE\WOW3264Node\Microsoft, I could only change
the Auto value from 1 to 0 and it worked.:

REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug" /v Auto /d 0

REG ADD "HKLM\SOFTWARE\WOW3264Node\Microsoft\Windows NT\CurrentVersion\AeDebug" /v
Auto /d 0

answered Jan 8 at 14:30

Alex
109 1 3

If you're running the same software on two machines and it's crashing on one(which is what's
happening if the debugger is starting) then you probably have something else going wrong on your
machine. It could be that you've got driver incompatibility issues, or that some of the other
software you have installed on the machine has incompatible versions of dll's...

You need to try to eliminate as many of the differeces as you can (easier said than done, I
know)... If you copy the contents of the CD onto a local disk, does that help? If you shutdown your
virus checker while you install the software does that help? Does it help if you turn the network
off? You've said that both machines have 'mostly' the same, software, what happens if you
uninstall some of the differences? Have both machines been patched to the same level?

As Visual studio is trying to start up when you have issues, have a look at the call stack and see
what dlls are loaded, print it out... run some of the other software that crashes on that machine
and do the same thing... look for any common libraries and do a comparison between the
machines to see if they have the same version of the libraries...
Of course it could also be that it's a hardware issue (I've had intermittent failures before now
because one of my drives was getting ready to fail and others because my graphics chip was
running too hot)...

As I said, not really an answer, but some things to consider...

If all else fails... you're probably stuck doing your bills on the other computer (although another
experiment might be to create a VPC on the broken pc to see if it worked then)...

answered Apr 14 '11 at 19:51

forsvarir
7,326 6 23 44

No, copying to disk doesn't help. Virus checker (and all others of the kind) stutted down - same thing
occurs. Both machines are with the same software (base installed from the same image) except some of the
small (notepad2 and the like) and developer stuff (in this case, only VS). – Rook Apr 14 '11 at 20:05

Why is this a problem just now? My coleague is changing workplace and he has to return "the other
computer" to his old firm. I on the other hand would like to avoid buying another one just to pay my bills :(
Apart from that - not helping, but yes, your comments stand. – Rook Apr 14 '11 at 20:06

you may get a more useful response somewhere like the superuser forum, since I'd still put my money on
software compability issues. depending on your base OS, VS will probably have upgraded a bunch of stuff
for you when it was installed, which ?may? not have been done on the other machine. path differences/install
orders can make a difference. corrupt registry entries can... you might want to try doing a repair install
 orders can make a difference. corrupt registry entries can... you might want to try doing a repair install
against VS (if that is really the only difference) to see if it changes anything. All I can really do is off
sympathy. we've all be somewhere like that in the past and it sucks – forsvarir Apr 14 '11 at 20:18

Right click on Project--Properties. Select the 'Web' tab. Under Debuggers, check 'Silverlight'
(beside ASP.NET that is already checked).

Now visual studio won't debug your javascript because fortunately it can't debug Silverlight and
javascript at the same time. You can now attach your javascript to the browser debugger.

edited Apr 26 '13 at 14:42 answered Apr 26 '13 at 2:43

yazanpro
1,087 1 15 34

This problem was appearing when I started pdf viewer. I reinstalled this program in other folder
(another disc in comp) and in my case it worked.

answered May 1 at 18:05

user4855054
1

Could you please add a little more details about the solution you provide? – abarisone May 1 at 18:23