none
an unhandled win32 exception occurred in devenv.exe[2908]

    Question

  • when i instal vs2008 that instaled successfully but when am using vs2008 i get the just in time error in that shows error like an unhandled win32 exception occurred in devenv.exe[2908] whwt should i do working with vs2008 in my system
    • Moved by Neddy Ren Thursday, August 11, 2011 7:31 AM VS Installation issue (From:Windows Forms Designer)
    Tuesday, August 09, 2011 6:45 AM

Answers

  • Hi sam.path,

    Thanks for your post.

    Would you please let me know what is the version of your OS? Also, did you have any third party VS add-ins/extensions installed?

    According on your description, Visual Studio crashed when starting up. To troubleshooting this issue, we can enable Visual Studio logging to log all activity to the specified log path. Then check and analyze the log file to see if there are anything incorrect. Please try running devenv.exe /log <log path> in Command Prompt, the log files will be generated in the <log path>.  For more information, please see: http://msdn.microsoft.com/en-us/library/ms241272.aspx

    You can also try:

    • Open Visual Studio Command Prompt (2008) under Start menu -> All Programs -> Microsoft Visual Studio 2008 -> Visual Studio Tools (run it with Administrator privilege: right-click the program -> Run as administrator);
    • Run devenv /Resetsettings to eliminate the cause of corrupted settings;
    • Run devenv /ResetSkipPkgs in Command Prompt;
    • Run devenv /Safemode to see if you can apply it correctly. This can eliminate the possibility that third party Add-ins or packages are causing problems;
    • Reboot the machine in Safe Mode. This can isolate some third party application/driver's interference;
    • Switch and try a new user account. This can rule out the possibility of corrupted user profile.

    Additionally, another useful tool is the Process Monitor tool which can capture the access log. Filter the process name devenv.exe in the log so that you see only the related list. This should give you more infomation on what the registry keys/ files are being accessed when the error happens.

    If these steps still not working, you can try to use some tool like Procdump to get the dump file of the crash. Then you report your issue with dump file to MSDN feedback site: http://connect.microsoft.com/visualStudio/ 
    Or you can use Windbg Tool to analyze dump file. Please see: http://blogs.msdn.com/b/msdnts/archive/2006/11/24/how-to-debug-application-crash-hang-in-production-environment.aspx.

    If there are any updates, please feel free to let me know.

    Best Regards,


    Andrew Wu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, August 12, 2011 2:50 AM
    Moderator

All replies

  • Hi sam.path,

    I will help you to move your thread to the Visual Studio Setup & Installation forum for more professional supports since your question is not the Windows Form related. Thank you for understanding.

    Best Regards


    Neddy Ren [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, August 11, 2011 7:30 AM
  • Hi sam.path,

    Thanks for your post.

    Would you please let me know what is the version of your OS? Also, did you have any third party VS add-ins/extensions installed?

    According on your description, Visual Studio crashed when starting up. To troubleshooting this issue, we can enable Visual Studio logging to log all activity to the specified log path. Then check and analyze the log file to see if there are anything incorrect. Please try running devenv.exe /log <log path> in Command Prompt, the log files will be generated in the <log path>.  For more information, please see: http://msdn.microsoft.com/en-us/library/ms241272.aspx

    You can also try:

    • Open Visual Studio Command Prompt (2008) under Start menu -> All Programs -> Microsoft Visual Studio 2008 -> Visual Studio Tools (run it with Administrator privilege: right-click the program -> Run as administrator);
    • Run devenv /Resetsettings to eliminate the cause of corrupted settings;
    • Run devenv /ResetSkipPkgs in Command Prompt;
    • Run devenv /Safemode to see if you can apply it correctly. This can eliminate the possibility that third party Add-ins or packages are causing problems;
    • Reboot the machine in Safe Mode. This can isolate some third party application/driver's interference;
    • Switch and try a new user account. This can rule out the possibility of corrupted user profile.

    Additionally, another useful tool is the Process Monitor tool which can capture the access log. Filter the process name devenv.exe in the log so that you see only the related list. This should give you more infomation on what the registry keys/ files are being accessed when the error happens.

    If these steps still not working, you can try to use some tool like Procdump to get the dump file of the crash. Then you report your issue with dump file to MSDN feedback site: http://connect.microsoft.com/visualStudio/ 
    Or you can use Windbg Tool to analyze dump file. Please see: http://blogs.msdn.com/b/msdnts/archive/2006/11/24/how-to-debug-application-crash-hang-in-production-environment.aspx.

    If there are any updates, please feel free to let me know.

    Best Regards,


    Andrew Wu [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, August 12, 2011 2:50 AM
    Moderator