- You receive the following error message:"Just -In-Time Debugging Handler and CLR Remote Host: An exception 'unhandled win32 exception' has occurred in process 'processID'. However, Visual Studio 7 just-in-time debugging has failed. Would you like to try debugging with the previously registered debugger (msdev path/msdev.exe)?"
- You receive an error message and the JIT Debugger does not start.
Steps to Reproduce the Behavior
- Verify that the Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\shell value is eitherc:\windows\explorer.exe or c:\winnt\explorer.exe.
- Right-click Taskbar, and then click
- In the Task Manager window, click the
- Select Image Name from the list that you want to debug. For example, if you want to debug on a notepad, select
Notepad.exe from the list.
- Right-click the image that you selected, and then click
Debug. You may receive the following warning message:
- Click Yes. The error message that is mentioned in the "Symptoms" section of this article is displayed.
- Change the registry key value to explorer.exe, and then repeat steps 4, 5, and 6 from the "Steps to Reproduce the Behavior" section earlier in this article. Verify that JIT Debugger starts.
- You can also start JIT Debugger from a Microsoft Visual Studio command-prompt window. To do this:
- Locate the Vs7jit.exe file in the C:\Program Files\Common Files\Microsoft Shared\VS7Debug folder.
- At the command prompt, type vs7jit -p
Process ID of the application you want to debug, and then press ENTER to start the debugger.
Article ID: 811191 - Last Review: Mar 25, 2008 - Revision: 1