Jit debugger error

Did you check that version is compatible with Windows 8? If it is, you will need to get in touch with Avanquest. I have found them very helpful.

Type "Regedit" in your Run menu and then click ok. Then navigate to the following path and delete the following registry keys.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\AeDebug\Debugger HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

On a 64-bit operating system also delete the following registry keys: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\WindowsNT\CurrentVersion\AeDebug\Debugger HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedD

Hope this helps.

long write

When you launch the TunePlus Application the first window you see should say version 2010.05.04.0 If it does not you will need to preform an update by clicking on the Tools menu inside of the program and select the option for Check For Updates.

I was just reading the thread! Kinda hilarious though.
JIT is used to catch real time errors especially run-time. It is very useful for developers. To catch un handled exceptions.
Jit comes as a part of Visual Studio. If you do not know how to manage Jit its better not to install Visual Studio (no skills to manage it will give you lots of trouble). Just the programing skills does not make a good developer. Well its not a fault of VS developer team or Bill Gates. Doh!
Jit will be invoked if enabled by Visual studio, instead of Dr Watson. If programs crash the crash handlers will be invoked and you will see Dr.Watson process running in the background. It will call dumprep and will create error logs; Errors will be logged in Event Viewers as well. Even a simple failure will be handled and Jit will be invoked. So programs will begin to crash while they run or install.
Some developers set programs to use Jit and Jit will be enabled instead of Dr.Watson. Dr.Watson will be invoked in serious errors however. Its obvious. But specially if you have installed Visual Studio, you will be using JIT as well. JiT overrides the Dr.Watson Program. But you can reverse it back using two methods.
Its a third party piece however. I wonder why these MSDN people do not know how to provide a complete answer. Each and every person does not understand Administration of programs. So its their responsibility. That is a laughing matter though. But people will be pissed off. Can't blame them either. Some of them are not familiar with regedit tools. So the answers have to be flexible and complete.
The bad behavior of JIT is it will suspend the program an once when an error occur. You will never be allowed to run further. So its kinda piece of ****. It also has security issues with it.
Unfortunately if a program Invokes JIT intensionally its not possible to reverse the process.
Stop JIT while you have Visual Studio installed (Its a stupid thing to uninstall it without removing JIT. No way!)
How this thing will be enabled?

1. Open VS:
2. Go to Tools and then Options.
3. In the Options Dialog box Double click Debugging and then click JIT
4. Enabling options:

• Manage
• Native
• Script

Click on OK.
This sets the Registry key and will start JIT. So do the Revers to Disable it.
You have to Disable the Keys. Method one:

1. Click on Start Menu and Type Run (for P Hit Run box)
2. Type in regedit and hit Enter
3. Expand the Keys to located the place
4. HKLM\Software\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger is one location.
5. HKLM\Software\Microsoft\.NETFramework\DbgManagedDebugger
6. Delete these keys. Or set the Auto key's value to 1.
7. On a 64bit system the paths will be: HKLM\Software\Wow6432Node\Microsoft\...
8. You may need to reboot the system as well.

Method two: Enable Dr.Watson using an alternative method:

• Get a Command Window (Command Prompt)
• Type drwtsn -i and
• Hit enter

If you were using a third party debugger read this Microsoft Support
Next step

Open Start>Control Panels>Internet Options: Advanced and activate (check box)

• Disable Script Debugging (Internet Explorer)
• Disable Script Debuggung (Other)

If you have enabled Server Side Script Debugging the pages will freeze if an error occurs. Read the enabling procedure. Steps to enable debugging portion. Do the Reverse to disable it.
For Script Debuggers: Here is how you enable the JIT:

• Click on Options then Tools
• Click on Debugger
• Select JIT debugger and attach to programs running on this machine
• So now you know how it happened. Do the reverse to disable it!

Using third party tools and software may enable this tool. If you detect one you have to avoid using it. Just posted this in the MSDN thread as well.
Please rate the answer as well! Feel free to contact if you have further issues.
Thanks for using Fixya! -Lasitha

Not sure whether this is a Q.
To enable just in time (JIT) debugging, the config file for this application or machine (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the machine rather than being handled by this dialog.
In VS the way to enable/disable that is: 1-On the "TOOLS" menu, click Options. 2-In the Options dialog box, select the Debugging folder. 3-In the Debugging folder, select the Just-In-Time page. 4-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. 5-Click OK.
It has to be done by the developer and its his responsible to guide the application error reporting to the system event handlers. If this is an issue which occurs in a certain app, have to check for the .net version (specially in vista). Many 1.0 and 1.1 based apps give the problem. To install dotnet fw 1.1 on Vista will give an error. Most of the time caused by DEP (Data Execution Prevention). But the thing is some software forces the installation of .net framework (older versions). How ever Vista is packed with .net 3.0 and 2.0. Even if you allowed to install will not be able to uninstall 2.0 (possible to remove 3.0 though).
How to solve the installation issue: This issue is resolved in Microsoft .NET Framework 1.1 SP1, however you will need to use the following procedure to install both the .NET Framework and the Service Pack at the same time: Download Microsoft .NET Framework 1.1 Redistributable Package and Microsoft .NET Framework 1.1 Service Pack 1 using links below: Dotnet Framework 1.1 Redest Dotnet Framework 1.1 SP1
Save both installations in the same directory Ensure that the Microsoft .NET Framework 1.1 Redistributable Package is named dotnetfx.exe. If not, change its name to dotnetfx.exe. Ensure that Microsoft .NET Framework 1.1 Service Pack 1 is named dotnetfxsp1.exe. If not, change its name to dotnetfxsp1.exe. Open command prompt as Administrator, and change to the directory where the two installations are saved. Run the following commands using the order shown below dotnetfx.exe /c:"msiexec.exe /a netfx.msi TARGETDIR=C:dotnet" dotnetfxsp1.exe /Xp:C:dotnet etfxsp.msp msiexec.exe /a c:dotnet etfx.msi /p c:dotnet etfxsp.msp Install both Microsoft .Net Framework 1.1 and Service Pack 1 by running C:dotnet etfx.msi
The systems must be backed up before trying this specially the system state. How ever the keys can be repaid in a damage This thread will also be helpful http://blogs.msdn.com/b/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx...

you most likely need Jave Runtime Installer installed

java download link

After installation try and run it again - if that does not work post back and let me know and I will try and assist further

Dear rmakrishnan2,

JIT stands for Just In Time and I believe it's some sort of compiler and sounds like your .NET infrastructure may need to to be reinstalled. Try the Add/Remove programs control panel to Repair or Reinstall your .NET infrastructure.

Good luck!