locked
0xc000007b Error on Vista

    Question

  •  

     

    Hi all,

     

    I got a VC++  application that runs fine on XP-64 platform (IDE environment).    But on my Vista 64 Business platform, it cannot run at all, from command line and from the IDE environment.  This stop me from debugging the application if I am on the Vista box.

     

    Whenever I start to debug the application, it comes back with the following error:

         "The application failed to initialize properly (0xc000007b).  Click OK to terminate the application"

     

    And the Windows event log has the following error posted:

     

    Faulting application xxxxx.exe, version 7.0.220.0, time stamp 0x463910a1, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549d372, exception code 0xc000007b, fault offset 0x0000000000001d28, process id 0xa9c, application start time 0x01c78d0a21423fd9.

     

    Have you run into a similar Vista 64 problem likes this one.  Is there any configuration settings that I have to ...config?

     

    Thanks

    Wednesday, May 02, 2007 10:41 PM

All replies

  •  

    I found out what the problem was.  The project has an embedded manifest file with the following block:

     

    <assemblyIdentity version="1.0.0.0"  processorArchitecture="X86"   name="IsUserAdmin"     type="win32"/>

     

    Somehow Windows Vista does not like that block and bombs out.  After removed the block, my application is running fine in Windows.

     

    I know what causes the problem, but still don't know why and how.

     

    Can some wise-folks explain to us the why and the how?

     

    Thanks.

     

     

    Friday, May 04, 2007 8:46 PM
  • Much more interesting - maybe? How do I remove the block?

    Wednesday, October 03, 2007 8:38 AM
  • when ever i want 2 play music this error shows up 0xc000007b i want 2 know how should get rid of it i always click ok but when i open another file it still appears.
    Sunday, November 18, 2007 5:03 AM
  • I ran into the same problem. I had a 64-bit EXE and two 64-bit DLLs, but a third DLL was a 32-bit release. I copied in the 64-bit DLL to correct the issue.

    I used a PEViewer utility to tell the difference between the DLLs. Not sure if there is a faster way

    Thursday, May 06, 2010 1:43 AM