Raw Message My computer came with Windows XP Media Center Edition 2004 installed. One day I could no longer access Media Center. I'd appreciate any feedback I can get regarding a solution. I get the following error messages: ehshell.exe - Entry point not found The procedure entry point SymSetSymWithAddr64 could not be located in the dynamic link library DBGHELP.dll ehshell.exe Common Language Runtime Debugging Services Application has generated an exception that could not be handled. Process id = 0xf18 (3864) Thread id = 0x1720 (5920) Click OK to terminate the application Click CANCEL to debug the application ehshell.exe - No debugger found Registered JIT debugger is not available. An attempt to launch a JIT debugger with the following command resulted in an error code of 0x2 (2).

Please check your computer settings. Cordbg. Download Antemasque. exe!a 0xf18 Click RETRY to have the process wait while attaching a debugger manually. Click CANCEL to abour the JIT debug request. My computer came with Windows XP Media Center Edition 2004 installed. One day I could no longer access Media Center. I'd appreciate any feedback I can ehshell.exe - Entry point not found The procedure entry point SymSetSymWithAddr64 could not be located in the dynamic link library DBGHELP.dll ehshell.exe Common Language Runtime Debugging Services Application has generated an exception that could not be handled.

Process id = 0xf18 (3864) Thread id = 0x1720 (5920) Click OK to terminate the application Click CANCEL to debug the application ehshell.exe - No debugger found Registered JIT debugger is not available. An attempt to launch a JIT debugger with the following command resulted in an error code of 0x2 (2). Please check your computer settings.

Cordbg.exe!a 0xf18 Click RETRY to have the process wait while attaching a debugger manually. Click CANCEL to abour the JIT debug request.

Hi daiyueweng, Causes: This situation is caused because the version of dbghelp.dll supplied with Windows XP (and possibly other Windows versions as well) is too old. Versions can be found. Solution: We can try to install a recent version of Debugging Tools for Windows from to fix this issue. Then, grab dbghelp.dll installed with it from 'C: Program Files Debugging Tools for Windows (x86)' and copy it to your executable's path. The motivation can be found: To use VLD with your project, follow these simple steps: • Copy the VLD library ( *.lib) files to your Visual C++ installation's ' lib' subdirectory. • Copy the VLD header files ( vld.h and vldapi.h) to your Visual C++ installation's ' include' subdirectory. • In the source file containing your program's main entry point, include the vld.h header file.

It's best, but not absolutely required, to include this header before any other header files, except for stdafx.h. If the source file, include stdafx.h, then vld.h should be included after it. • If you are running Windows 2000 or earlier, then you will need to copy dbghelp.dll to the directory where the executable being debugged resides. • Build the debug version of your project. More information: If you have solved this issue, please mark the useful reply as answer. Best regards, Lucy Lucy Liu [MSFT] MSDN Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. Hi daiyueweng, Causes: This situation is caused because the version of dbghelp.dll supplied with Windows XP (and possibly other Windows versions as well) is too old.

Versions can be found. Solution: We can try to install a recent version of Debugging Tools for Windows from to fix this issue. Then, grab dbghelp.dll installed with it from 'C: Program Files Debugging Tools for Windows (x86)' and copy it to your executable's path. The motivation can be found: To use VLD with your project, follow these simple steps: • Copy the VLD library ( *.lib) files to your Visual C++ installation's ' lib' subdirectory. • Copy the VLD header files ( vld.h and vldapi.h) to your Visual C++ installation's ' include' subdirectory.