C++ application fails to start correctly (0xc000000d)

5 down vote favorite 3

I'm writing a C++ application using VS2010 on two dev computers - both are Win7 64bit SP1. I use git to sync the repositories. On one of the machines the compiled executable (and also the test exec) stopped working with the following error, while on the other machine it works fine and I'm able to continue development. The application was unable to start correctly (0xc000000d). Click OK to close the application. I tried deleting the repository and cloning it again. I also made sure I have the same versions of Boost, git, Visual Studio. Also, I tried debugging (stepping in) but the error occurs before any line of code is reached. Notice as far as I understand I'm tracking Visual Studio's solution\project configuration files as detailed here. I'm at a loss, how would you debug this? UPDATE 1: Only the Debug version fails to run. The Release version runs fine UPDATE 2: The executable that doesn't work does work on the other computer! UPDATE 3: I've reinstalled VS2010 (exactly the same version) - didn't help. Surprisingly the compiled files are not the same size between the two machines. c++  visual-studio share improve this question edited Apr 16 '11 at 21:06 asked  Apr 13 '11 at 11:25 Jonathan 14.3k 30 119 200

4   Use Dependency Walker - dependencywalker.com - see if there's DLL version differences. –   Erik  Apr 13 '11 at 11:31 Can you debug it and check until where it is able to run? –   rturrado  Apr 13 '11 at 11:34 @rturrado - I tried debugging (stepping in) but the error occurs before any line of code is reached –  Jonathan  Apr 13 '11 at 11:37 1   Check the references to the WinSXS cache. The same library VC90.CRT (this is for VS2008, asume the predecessor) may be available in different versions. This can be caused by a VS service pack installed only on one of the computers. Check the version required by the developped application and the version found in WinSXS. –   harper  Apr 13 '11 at 12:34 3   Can you look in the event logs for more information regarding this exception, as well as the address it's occurring at? –   Collin Dauphinee  Apr 13 '11 at 17:08 show 8 more comments

7 Answers

active oldest votes

up vote 3 down vote

I got the same problem as you mentioned. My solution: Clean the manifest file and rebuild In the property page-> Manifest tool -> make sure "Additional Options" is set to nothing. (I set it as "/validate_manifest" before). Or you can try "Embed Manifest -> NO", rebuild and then set back to Yes. It sounds to be ridiculous, but it really works sometimes. I don't know why. share improve this answer edited May 26 '12 at 9:15 Martijn Pieters 350k 32 631 827 answered  May 26 '12 at 2:33 Steve 31 2

add a comment

up vote 2 down vote

I got the same phenomenon suddenly without a warning on Win7 / VS2010 / C++. Debug App couldn't be launched, got 0xC000000D at initializing and loading multiple dlls. Found one base dll of my own responsible, played around with linker settings. Modifying settings, incremential rebuild -> app starts, rebuild all -> app crashes again. After setting "generate manifest" to "no" in the linker settings the sample app works, but the main app still crashes. After setting "generate manifest" to "no" for the most of my dlls -> the app starts in debug mode again. The stuff is very spurious, because some dlls need the modified settings others do not. share improve this answer edited Nov 10 '12 at 20:22 gwhitake 5,466 4 31 49 answered  Sep 28 '11 at 19:48 Martin Seck 21 2

add a comment

up vote 1 down vote

Have a look at the top two answers to this question Program crashes with 0xC000000D and no exceptions - how do I debug it? On the machine where it fails, try running the debug executable NOT under the debugger, and update your question to say what happens. If it crashes, are you able to then attach the debugger whilst the message box is still there and get a stack trace that tells you what function it is crashing in? share improve this answer answered  Apr 16 '11 at 21:30 James Crook 1,350 6 13

The error occurs both when I run it in VS2010 (F5) and when I run the executable. The error is a pop-up with a single OK button (no abort\retry\ignore options) –   Jonathan  Apr 17 '11 at 14:39  So at that stage, are you able to attach the debugger using debug->attach-to-process ? –   James Crook  Apr 17 '11 at 14:42 add a comment

up vote 1 down vote	This is the weirdest thing.... Try deleting the "ipch" directory and then rebuilding. Hope it works for you, I have wasted hours on this. share improve this answer answered  May 13 '11 at 21:40 Amir 11 1
	I tried git cleanup several times, which also deletes the ipch directory to no avail –   Jonathan  May 14 '11 at 9:59 add a comment

up vote 1 down vote	disabling/enabling precompiled headers fixed the issue for me. I was facing crash on Debug x64 only - I guess it was related to an upgrade from boost 1.50 to 1.52, while keeping pch files. share improve this answer answered  Feb 27 '13 at 16:06 hervé meunier 11 1
	add a comment

up vote 0 down vote	in my case i got it working again by setting generate manifest to NO on all projects share improve this answer answered  Dec 10 '12 at 9:56 ColacX 912 2 9 19
	add a comment

up vote 0 down vote

I have changed "Embed manifest" setting to NO and then back to YES but it didn't help. For me setting General->Platform Toolset to Windows SDK 7.1 for my program and all dependent libraries compiled with it helped. share improve this answer answered  Jan 8 '13 at 10:51 user1957825 1

5 down vote favorite 3

I'm writing a C++ application using VS2010 on two dev computers - both are Win7 64bit SP1. I use git to sync the repositories. On one of the machines the compiled executable (and also the test exec) stopped working with the following error, while on the other machine it works fine and I'm able to continue development. The application was unable to start correctly (0xc000000d). Click OK to close the application. I tried deleting the repository and cloning it again. I also made sure I have the same versions of Boost, git, Visual Studio. Also, I tried debugging (stepping in) but the error occurs before any line of code is reached. Notice as far as I understand I'm tracking Visual Studio's solution\project configuration files as detailed here. I'm at a loss, how would you debug this? UPDATE 1: Only the Debug version fails to run. The Release version runs fine UPDATE 2: The executable that doesn't work does work on the other computer! UPDATE 3: I've reinstalled VS2010 (exactly the same version) - didn't help. Surprisingly the compiled files are not the same size between the two machines. c++  visual-studio share improve this question edited Apr 16 '11 at 21:06 asked  Apr 13 '11 at 11:25 Jonathan 14.3k 30 119 200

4   Use Dependency Walker - dependencywalker.com - see if there's DLL version differences. –   Erik  Apr 13 '11 at 11:31 Can you debug it and check until where it is able to run? –   rturrado  Apr 13 '11 at 11:34 @rturrado - I tried debugging (stepping in) but the error occurs before any line of code is reached –  Jonathan  Apr 13 '11 at 11:37 1   Check the references to the WinSXS cache. The same library VC90.CRT (this is for VS2008, asume the predecessor) may be available in different versions. This can be caused by a VS service pack installed only on one of the computers. Check the version required by the developped application and the version found in WinSXS. –   harper  Apr 13 '11 at 12:34 3   Can you look in the event logs for more information regarding this exception, as well as the address it's occurring at? –   Collin Dauphinee  Apr 13 '11 at 17:08 show 8 more comments

7 Answers

active oldest votes

up vote 3 down vote

I got the same problem as you mentioned. My solution: Clean the manifest file and rebuild In the property page-> Manifest tool -> make sure "Additional Options" is set to nothing. (I set it as "/validate_manifest" before). Or you can try "Embed Manifest -> NO", rebuild and then set back to Yes. It sounds to be ridiculous, but it really works sometimes. I don't know why. share improve this answer edited May 26 '12 at 9:15 Martijn Pieters 350k 32 631 827 answered  May 26 '12 at 2:33 Steve 31 2

add a comment

up vote 2 down vote

I got the same phenomenon suddenly without a warning on Win7 / VS2010 / C++. Debug App couldn't be launched, got 0xC000000D at initializing and loading multiple dlls. Found one base dll of my own responsible, played around with linker settings. Modifying settings, incremential rebuild -> app starts, rebuild all -> app crashes again. After setting "generate manifest" to "no" in the linker settings the sample app works, but the main app still crashes. After setting "generate manifest" to "no" for the most of my dlls -> the app starts in debug mode again. The stuff is very spurious, because some dlls need the modified settings others do not. share improve this answer edited Nov 10 '12 at 20:22 gwhitake 5,466 4 31 49 answered  Sep 28 '11 at 19:48 Martin Seck 21 2

add a comment

up vote 1 down vote

Have a look at the top two answers to this question Program crashes with 0xC000000D and no exceptions - how do I debug it? On the machine where it fails, try running the debug executable NOT under the debugger, and update your question to say what happens. If it crashes, are you able to then attach the debugger whilst the message box is still there and get a stack trace that tells you what function it is crashing in? share improve this answer answered  Apr 16 '11 at 21:30 James Crook 1,350 6 13

The error occurs both when I run it in VS2010 (F5) and when I run the executable. The error is a pop-up with a single OK button (no abort\retry\ignore options) –   Jonathan  Apr 17 '11 at 14:39  So at that stage, are you able to attach the debugger using debug->attach-to-process ? –   James Crook  Apr 17 '11 at 14:42 add a comment

up vote 1 down vote	This is the weirdest thing.... Try deleting the "ipch" directory and then rebuilding. Hope it works for you, I have wasted hours on this. share improve this answer answered  May 13 '11 at 21:40 Amir 11 1
	I tried git cleanup several times, which also deletes the ipch directory to no avail –   Jonathan  May 14 '11 at 9:59 add a comment

up vote 1 down vote	disabling/enabling precompiled headers fixed the issue for me. I was facing crash on Debug x64 only - I guess it was related to an upgrade from boost 1.50 to 1.52, while keeping pch files. share improve this answer answered  Feb 27 '13 at 16:06 hervé meunier 11 1
	add a comment

up vote 0 down vote	in my case i got it working again by setting generate manifest to NO on all projects share improve this answer answered  Dec 10 '12 at 9:56 ColacX 912 2 9 19
	add a comment

up vote 0 down vote

I have changed "Embed manifest" setting to NO and then back to YES but it didn't help. For me setting General->Platform Toolset to Windows SDK 7.1 for my program and all dependent libraries compiled with it helped. share improve this answer answered  Jan 8 '13 at 10:51 user1957825 1