- Remove From My Forums
-
Question
-
Hello all.
I
installed Visual Studio, and had no problems. Except one. The
Just-In-Time debugger. It seems to come up all the time now, and it
has broken Winamp AND Cakewalk SONAR 5. I tried disabling it in Visual
Studio’s options, but that doesn’t stop the pop up and the subsequent
shut down of the program (which did NOT happen before). Any ideas?
Answers
-
Although anything is possible I suppose, it seems unlikely that installing the Just-In-Time debugger caused these applications to start crashing. But I guess if you really want to know if that is the problem, you can try removing HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionAeDebugDebugger.
If it was me, I would take a look at where the app was crashing, and send a bug report to the product support team that own’s your crashing app.
Тебе надо побороть собственную нетерпеливость.
Извини, но рано тебе еще программировать. На курсы, дружок, на курсы. Пусть тебя там прежде всего научат аккуратности. А то ставишь небось все, что попадает в поле зрения и лишь потом решаешь, нужно ли. 
Снеси “студию”. Если не поможет, то все остальные инструментальные среды, имеющие в составе отладчики сборок, подобные JIT. Если и это не поможет, переставь систему, и.. .
1) Читай побольше об альтернативных средах разработки, прежде чем выбрать и поставить, для начала одну и тлько одну из них! Освой как следует ее управляющие и конфигурирующие средства, прежде чем пробовать что-то еще.
2) Не ленись сносить имеющуюся версию (редакцию) какого-либо продукта уровня “студии”, прежде чем поставить другую.
Не совмещай несколько версий и тем более редакций, отлдичающихся локализацией, конфигурацией и/или происхождением. Проблемы могут быть даже с совмещением или установкой поверх – для обеих оригинальных редакций, что же говорить о “левых”! Такое совмещение – занятие для очень терпеливых людей, не ленящихся потратить много времени на поиски по форумам на предмет возможных подводных камней у запланированного совмещения.
Our buildserver (TeamCity, much recommended), runs our a whole bunch of testsuites on our finished c++ program.
Once in a whole, a test causes our program to crash, often bringing up a VisualStudio dialog offering me to JustInTime debug the crash. The dialog stops the buildserver from progressing. Instead of the build marked as failed, it just hangs. I’ve turned off the Just In Time debugging feature in VisualStudio, but when it’s turned off, you still get a message “Couldn’t JustinTime Debug this, you can turn it on in the options”.
Does anybody know of a way to ensure that any unhandled exception in a program does not result in any modal dialog?
skaffman
397k96 gold badges815 silver badges768 bronze badges
asked Dec 12, 2009 at 14:20
Lucas MeijerLucas Meijer
4,3846 gold badges35 silver badges53 bronze badges
1
This MSDN article explains how to disable Just-In-Time debugging on a Windows server. I’ve included the relevant portion of the article below:
After Visual Studio is installed on a server, the default behavior when an unhandled
exception occurs is to show an Exception dialog that requires user intervention to
either start Just-In-Time debugging or ignore the exception. This may be undesirable for
unattended operation. To configure the server to no longer show a dialog when an
unhandled exception occurs (the default behavior prior to installing Visual Studio), use
the registry editor to delete the following registry keys:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionAeDebugDebugger
HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkDbgManagedDebuggerOn a 64-bit operating system also delete the following registry keys:
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindows NTCurrentVersionAeDebugDebugger
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkDbgManagedDebugger
answered Dec 12, 2009 at 14:37
Emerick RogulEmerick Rogul
6,6663 gold badges32 silver badges39 bronze badges
2
Delete (or rename) c:windowssystem32vsjitdebugger.exe.
I tried deleting the registry keys, and I tried unchecking all the boxes in the Visual Studio options, but neither worked.
To be clear, my situation wasn’t a C++ one. I was using Micro Focus COBOL for Visual Studio 2010, and by using the registry and VS options suggestions I managed to get rid of the “Want to debug?” dialog, but that resulted in a different dialog to hold up my automated process:
Visual Studio Just-In-Time Debugger
An unhandled exception (‘COBOL runtime: Fault detected’) occurred in CASDBC.exe [3564]. 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 Tools/Options/Debugging/Just-In-Time.Check the documentation index for ‘Just-in-time debugging, errors’ for
more information.OK
answered Apr 21, 2014 at 18:58
1
I would not recommend to edit/remove regs. Usually the registry is a mess to play with.
The solution that helps me is a quite simple. I`ve just added JIT debugger to my Visual Studio. Steps are:
-
Open
Windows Control panel -
Programs -
Programs and Features -
Find
Visual Studio 2017 - Click
Change. On a new opened window navigate to theIndividual Componentstab - Check
Just-In-Time debuggercheckbox - Click
modify
After VS reload the error should be fixed.
Suraj Kumar
5,5398 gold badges20 silver badges41 bronze badges
answered Jan 31, 2019 at 9:25
neberaaneberaa
1,3962 gold badges10 silver badges9 bronze badges
In my case , on win2012 server, I tried:
- removing registry keys
- deleting the exe for the jit debugger from c:windowssystem32
and it still came up!
I rebooted, etc.
Was making my web site in IIS stall until dialog was acknowledged!
Final solution, which did work: In control panel, in Programs: Uninstalled “Microsoft Visual Studion 2010 Shell (Isolated)” Uninstalled that, and problem solved.
(Whether SQL Management Studio still works…. I do not know!)
answered Jul 24, 2014 at 20:19
2
In the Window for the question
Do you want to Debug using the selected debugger?
Click YES (new window opens) > OPTIONS (top row menu) > DEBUG
Then in the New window remove the TICK which shows ENABLE JUST IN TIME DEBUGGER.
After disabling the JUST IN TIME debugger close the window or click OK
Your problem will be solved. I’ve tried this and got rid of the JUST IN TIME POP UP messages.
Uwe Keim
39.2k56 gold badges174 silver badges291 bronze badges
answered Dec 7, 2012 at 18:54
Best Solution for this problem is so simple
2 steps to make it done
open cmd prompt
type : regedit
go to path–>HKEY_LOCAL_MACHINE–>SOFTWARE–>Microsoft–>Windows NT–>CurrentVersion–>AeDebug
You can find now the file : Debugger
right click , Modify
copy and paste this text inside it:
drwtsn32 -p %ld -e %ld -g
click ok and voila 🙂
answered Apr 3, 2014 at 23:34
I haven’t Just-In-Time in Options:
I found to solve this with options of Internet :
But when I’m rebuilding solution I get this exception:
How to solve this issue?
asked Jan 2, 2019 at 8:24
How to enable Just In Time Debugger in Visual Studio 2017?
First, please make sure you have installed the component Just-In-Time debugger in the installer:
Then restart your Visual Studio, you will get that Just-In-Time in Options.
If you still have issue after install the component Just-In-Time debugger, you can try to update your Visual Studio to latest version.
Besides,
This also could have happened when installing VS2017 on a machine that
once had a previous version of VS installed (the JIT debugger does not
uninstall with VS for backward compatibility reasons).To work around these issues until the fixes are released, run repair
to register the JIT debugger (assuming it was selected to be
installed) or uninstall and reinstall making sure to select the JIT
debugger.Once VS2017 is repaired/installed, start VS as administrator and go to
the JIT options page. Check all checkboxes and click OK.
Check the detail info from Just-in-time debugging disabled and options missing.
Hope this helps.
answered Jan 3, 2019 at 1:48
Leo LiuLeo Liu
69.4k10 gold badges110 silver badges130 bronze badges
1
In this tutorial you ‘ll find instructions to stop the Just-In-Time Debugger dialog box from appearing. The dialog box “Just-In-Time Debugger: An unhandled win32 exception occurred in Outlook.exe” (or at any other program), appears because the reported application in the dialog box, cannot start.
The ‘Choose Just-In-Time Debugger” dialog box, gives you the option to launch Visual Studio to debug the error. But, if the Visual Studio is not installed or it cannot debug the error, the reported application crashes and closes.
If you want to prevent the “Choose Just-In-Time Debugger” dialog from appearing, then you have to disable the Just-In-Time Debugger, by following the instructions below.
How to Stop the Just-In-Time Debugger. *
* Note: If the “Just-In-Time Debugger – An unhandled win32 exception occurred…” dialog box appears when launching Outlook, then, before proceeding to the methods below, apply the following actions:
1. Repair the Outlook PST data file and then open Outlook.
2. Repair the Office installation.
Method 1. Modify the Data Execution Prevention (DEP) to Default Settings.
1. Right click on My PC and select Properties.
2. Click Advanced system settings on the left.
3. At ‘Advanced’ tab click Settings at ‘Performance’ section.
4. At ‘Performance Options’ select the Data Execution Prevention tab.
5. Choose Turn On DEP for Essentials for Essentials Windows programs and services only and click OK.
6. Restart your PC and check if the Just-In-Time Debugger dialog box has stopped appearing.
Method 2. Disable Just-In-Time Debugger in Visual Studio.
If you have the Visual Studio installed, then proceed and disable the Just-In-Time Debugger in Visual Studio. To do that:
1. navigate to Control Panel -> Programs and features.
2. Highlight the Visual Studio and click Change.
3. On a new opened window choose the Individual Components tab.
4. Uncheck the Just in Time Debugger and click Modify.
Method 3. Disable the Just-In-Time Debugger from Registry.
1. Open Registry editor. To do that:
1. Press Windows
+ R keys to open the run command box.
2. In the “Open” box, type: regedit & click OK.
+ R keys to open the run command box.
2. Find and Delete the following registry entries (in bold letters):
- HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkDbgManagedDebugger
- HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionAeDebugDebugger
3. If you have 64-bit Operating System, delete also the following registry entries (in bold letters):
- HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkDbgManagedDebugger
- HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindows NTCurrentVersionAeDebugDebugger
4. Close Registry Editor and restart the computer.
5. After restart the “Just-In-Time Debugger – An unhandled win32 exception occurred…” will disappear.
* Note: If the Just-In-Time Debugger dialog box, still appears, navigate to Control Panel -> Programs and features and uninstall the Microsoft Visual Studion 2010 Shell (Isolated).
That’s all folks! Did it work for you?
Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.
If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us.
