The application was unable to start correctly 0xc000007b

Question

I have a client server app which I have been developing on a single PC  Now it needs two serial ports  so I borrowed a PC from a friend   When I build my app and try to run or debug it  whether in the Delphi IDE or from Windows File manager   it errors  The application was unable to start correctly  0xc000007b     Googling doesn t bring up much  but seems to indicate that this is nothing Delphi specific and happens with other apps  It seems to be caused by calling into a 32 bit DLL from a 64 bit app or vice versa    both PCs are Windows 7  64 bit both have Delphi Xe2 starter edition which can only handle 32 bits The app runs fine on my PC  but not on my friend s Other Delphi apps run just fine on both PCs   Can anyone give me a hint as to how to track this down

User · Answer

It is possible that you have multiple versions of the dll s  on your system  You can search your system to find out   The issue may be solved by simply changing the order of the directories in your path   This was my issue   Cannot run Qt Creator GUI outside of Qt   quot The application was unable to start correctly  0xc000007b  quot  error

User · Answer

That can happen if for some reason a x86 resource is loaded from a x64 machine  To avoid that explicitly  add this preprocessor directive to stdafx h  of course  in my example the problematic resource is Windows Common Controls DLL    if defined  WIN64   pragma comment linker      manifestdependency type  win32  name  Microsoft Windows Common-Controls  version  6 0 0 0  processorArchitecture  amd64  publicKeyToken  6595b64144ccf1df       endif

User · Answer

Also download and unzip  Dependencies  into same folder where you put the wget exe from  http   gnuwin32 sourceforge net packages wget htm  You will then have some lib  dll files as well as wget exe in the same folder and it should work fine    I also answered here https   superuser com a 873531 146668 which I originally found

User · Answer

The main problem  of course  is that a DLL file is missing  or  even more likely  corrupt   If this is the case  then I have some pretty good ideas  especially if you ve downloaded and installed a DLL manually      TLDR  Delete every manually copy pasted DLL you ve done  uninstall old redistributable installs  and reinstall new redistributables for both 32-bit and 64-bit installs  What To Do This solution of copying pasting missing DLL s into system32  etc   used to work since I can remember in the 1990 s  but it doesn t seem to work anymore  2020    So if you run into this problem recently  I suggest   Within windows system32 and windows SysWOW64  delete all files that match ms  dll  that the operating system will allow you delete as admin  Uninstall all Visual C   Redistributables that you have with Windows   This prevents the  quot You already have this  quot  dialogue showing up upon reinstall  as detailed in the next step when we re-install  Reinstall the 2015-2019 Visual C   Redistributable from a regularly available download site   If this does not work  download and install the others  but personally  the 2015-2019 covered everything for me   Regardless of your machine  install both x32 and x64 packages    All Download Links  Collected VC   Download Links  MSVCR120 dll Fix  MFC140U dll Fix    How You Know It s Working There s a lot of variation in coders experiencing this  so  the idea that there s one single  possible solution is often discarded  but let s be positive   If deleting the matching ms  dll files worked  then you will no longer get an error about error code 0xc000007b   Instead  you ll get a message about a missing  dll   This tells you that you re hitting the right code path  If installing the redistributable works  then certain popular  DLL files should appear in the above-mentioned system32 and SysWO64 folders   For instance  MSVCR120 dll  MSVCR140 dll  MSVCR100 dll  MSVCP100 dll  MSVCP120 dll  MSVCP140 dll  and friends   Last  Possible Best Chances Sometimes things don t work according to plan  as we all in the Windows world know    You can also try the following   Open the  quot Turn Windows Features on or off quot  tab in Windows  supported in Windows 8-10    Uncheck the  NET Framework installations   You ll see a small installation go by  Restart the system   Go to the above feature again  recheck  NET Framework  and click  quot okay quot    If this works  you ll see a  quot installing and updating  NET framework quot  message that takes maybe a minute or so to go by   Once this is done  I recommend a reboot again   Good luck

User · Answer

I just ran into this issue  I searched for  C    under my  Apps  amp  Features  in Windows 10 control panel and noticed that some kind of update had just run a few days prior and installed VC   Redistributable 2012-2017  The app that was running into the error message only required VC   2010  I uninstalled all of them and then reinstalled just 2010 x86 x64  and the error went away and the application functioned as expected

User · Answer

To start  I would suggest to test whether there is a problem between your application and its dependencies using dependency walker

User · Answer

It has been mentioned in earlier answers that using dependency walker is the way to go  in my case  my application keeps failing with the error code    dependency walker showed a few dll that are NOT relevant   Finally figured out that I can run profiling by going to  profile  menu and it will run the application and stop at the exact dll that s cause the problem   I found out a 32bit dll was picked because of path and fixed it

User · Answer

I experienced the same problem developing a client-server app using Microsoft Visual Studio 2012   If you used Visual Studio to develop the app  you must make sure the new  i e  the computer that the software was not developed on  has the appropriate Microsoft Visual C   Redistributable Package   By appropriate  you need the right year and bit version  i e  x86 for 32 bit and x64 for 64 bit  of the Visual C   Redistributable Package      The Visual C   Redistributable Packages install run-time components that are required to run C   applications built using Visual Studio    Here is a link to the Visual C   Redistributable for Visual Studio 2015    You can check what versions are installed by going to Control Panel -  Programs -  Programs and Features   Here s how I got this error and fixed it   1  I developed a 32 bit application using Visual Studio 2012 on my computer   Let s call my computer ComputerA   2  I installed the  exe and the related files on a different computer we ll call ComputerB   3  On ComputerB  I ran the  exe and got the error message   4  On ComputerB  I looked at the Programs and Features and didn t see Visual C   2012 Redistributable  x64    5  On ComputerB  I googled for Visual C   2012 Redistributable and selected and installed the x64 version   6  On ComputerB  I ran the  exe on ComputerB and did not receive the error message

User · Answer

A load time dependency could not be resolved  The easiest way to debug this is to use Dependency Walker  Use the Profile option to get diagnostics output of the load process  This will identify the point of failure and should guide you to a solution   The most common cause of this error is trying to load a 64 bit DLL into a 32 bit process  or vice versa

User · Answer

I tried all the things specified here and found yet another answer   I had to compile my application with 32-bit DLLs   I had built the libraries both in 32-bit and 64-bit but had my PATH set to 64-bit libraries   After I recompiled my application  with a number of changes in my code as well  I got this dreaded error and struggled for two days   Finally  after trying a number of other things  I changed my PATH to have the 32-bit DLLs before the 64-bit DLLs  they have the same names    And it worked   I am just adding it here for completeness

User · Answer

You can have this if you are trying to manifest your application that it has a dependancy on the Microsoft Windows Common-Controls assembly  You do this when you want to load Version 6 of the common controls library - so that visual styles are applied to common controls    You probably followed Microsoft s original documentation way back from Windows XP days  and added the following to your application s manifest    lt  -- Dependancy on Common Controls version 6 -- gt   lt dependency gt       lt dependentAssembly gt           lt assemblyIdentity                 type  win32                  name  Microsoft Windows Common-Controls                  version  6 0 0 0                  processorArchitecture  X86                  publicKeyToken  6595b64144ccf1df                  language      gt       lt  dependentAssembly gt   lt  dependency gt    Windows XP is no longer the OS  and you re no longer a 32-bit application  In the intervening 17 years Microsoft updated their documentation  now it s time for you to update your manifest    lt  -- Dependancy on Common Controls version 6 -- gt   lt dependency gt       lt dependentAssembly gt           lt assemblyIdentity                 type  win32                  name  Microsoft Windows Common-Controls                  version  6 0 0 0                  processorArchitecture                     publicKeyToken  6595b64144ccf1df                  language      gt       lt  dependentAssembly gt   lt  dependency gt    Raymond Chen has a lovely history of the Common Controls    The history of the Windows XP common controls  archive

User · Answer

I recently had an issue where I was developing an application  that used a serial port  and it worked on all the machines I tested it on but a few people were getting this error   It turns out all the machines that the error happened on were running Win7 x64 and had NEVER ONCE been updated    Running a Windows update fixed all of the machines in my particular case

User · Answer

This may be a case where debugging the debugger might be useful   Essentially if you follow the instructions here you can run two ide s and one will debug into the other   If you un your application in one  you can sometimes catch errors that you otherwise miss   Its worth a try

User · Answer

In my case the error occurred when I renamed a DLL after building it  using Visual Studio 2015   so that it fits the name expected by an executable  which depended on the DLL  After the renaming the list of exported symbols displayed by Dependency Walker was empty  and the said error message  The application was unable to start correctly  was displayed   So it could be fixed by changing the output file name in the Visual Studio linker options

User · Answer

It is a missing dll  Possibly  your dll that works with com ports have an unresolved dll dependence   You can use dependency walker and windows debugger  Check all of the mfc library  for example  Also  you can use nrCommlib - it is great components to work with com ports

User · Answer

I have seen the error trying to run VC   debug executable on a machine which did not have Visual C   installed   Building a release version and using that fixed it

User · Answer

Actually this error indicates to an invalid image format  However  why this is happening and what the error code usually means  Actually this could be appear when you are trying to run a program that is made for or intended to work with a 64 bit Windows operating system  but your computer is running on 32 bit Operating system    Possible Reasons    Microsoft Visual C   Need to restart DirectX  NET Framework Need to Re-Install Need to Run the application as an administrator   Source  http   www solveinweb com solved-the-application-was-unable-to-start-correctly-0xc000007b-click-ok-to-close-the-application

User · Answer

Just solved this problem for my personal project  thanks to Dries for that   For me it was because the project path was too long  After saving the  sln to a shorter path  C  MyProjects  and compiling from there it ran without the error

[windows] The application was unable to start correctly (0xc000007b)

Examples related to windows

Examples related to delphi

Examples related to 64-bit