Error : Application was unable o start correctly(0xc000007b).
-
Hello Friends I converted MFC application to 64 bit using VS 2013. My exe is working in Release build.But As I run in Debug Build,it pops up with Window error saying "The Application was unable to start correctly(0x0c000007b).Click OK to close the application." After Google, I tried different methods As suggested [Copied mfc100.dll,mfc00u.dll,msvcp100.dll,msvcr100.dll,msvcr100_clr0400.dll] to System32 folder. I installed vs2010,vs2013 redistributable package too bt no Luck. Any Ideas? Thanks & Regards Yogesh Sikri
-
Hello Friends I converted MFC application to 64 bit using VS 2013. My exe is working in Release build.But As I run in Debug Build,it pops up with Window error saying "The Application was unable to start correctly(0x0c000007b).Click OK to close the application." After Google, I tried different methods As suggested [Copied mfc100.dll,mfc00u.dll,msvcp100.dll,msvcr100.dll,msvcr100_clr0400.dll] to System32 folder. I installed vs2010,vs2013 redistributable package too bt no Luck. Any Ideas? Thanks & Regards Yogesh Sikri
Debug builds are not intended to be run on other machines than the development system. So try to start your program in the debugger of your VS. If that works, all is OK. Debug builds are linked to special versions of the runtime DLLs which did not exist on machines that have no VS installed. While it would be possible to copy these special DLLs, you should know that you are not allowed to do so.
-
Hello Friends I converted MFC application to 64 bit using VS 2013. My exe is working in Release build.But As I run in Debug Build,it pops up with Window error saying "The Application was unable to start correctly(0x0c000007b).Click OK to close the application." After Google, I tried different methods As suggested [Copied mfc100.dll,mfc00u.dll,msvcp100.dll,msvcr100.dll,msvcr100_clr0400.dll] to System32 folder. I installed vs2010,vs2013 redistributable package too bt no Luck. Any Ideas? Thanks & Regards Yogesh Sikri
-
Debug builds are not intended to be run on other machines than the development system. So try to start your program in the debugger of your VS. If that works, all is OK. Debug builds are linked to special versions of the runtime DLLs which did not exist on machines that have no VS installed. While it would be possible to copy these special DLLs, you should know that you are not allowed to do so.
-
Check if there is any manifest resource in the project and check that this resource also is updated for X64. Fast test: exclude the manifest from project and recompile.
-
Check the debug output window to see when the error appears. You may set a breakpoint at your
InitInstancemethod. If the error appears before that it may be some DLL that does not match. Does your application uses some self-build or other non-MS DLLs? If so ensure that these DLLs are present as 64-bit versions. Check also your debug project settings for those DDLs to ensure that there is no entry to an old one. The MS / MFC specific debug DLLs should be already present on your system (they have the letter 'd' at the end of the name). -
This error comes on 64bits OS's when the loader try to link a wrong DLL (typically a 32bits DLL in a 64bits executable). Check again your project and verify that you are correctly linking to 64bits versions of all DLL's. Maybe your program use a DLL built for 32bits. The linking could complete even with wrong import library, then the error is triggered at loading time. The most common case is when a manifest is present in whichever library reporting X86 build, the loader, and this made me mad, testardly try to load 32bits version of commctl32.dll :mad: