Windows 7 64 bit DLL problems

Question

I have a problem with our executable  I m running this C   32-bit executable on my Windows nbsp 7 64-bit development box that also has all those Microsoft applications  Visual Studio 2008   2010  TFS  SDK  Microsoft Office     And it s still running just fine   Now I got the client installation of the very same program and was asked to test it with a clean Windows nbsp 7 installation  Thus I got one Windows nbsp 7 64-bit VMware and updated it to Windows nbsp 7 SP 1  the very same version my developer box is tuning   But while on my developer box everything is fine the program does not work with the VMware  30 days trial  box   The x86 Dependency Walker is telling me that the following DLL files are missing    API-MS-WIN-CORE-COM-L1-1-0 DLL API-MS-WIN-CORE-WINRT-ERROR-L1-1-0 DLL API-MS-WIN-CORE-WINRT-L1-1-0 DLL API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0 DLL API-MS-WIN-CORE-WINRT-STRING-L1-1-0 DLL API-MS-WIN-SHCORE-SCALING-L1-1-0 DLL DCOMP DLL GPSVC DLL IESHIMS DLL   I googled for those API-MS-WIN-    DLL files and found they should actually already be part of Windows nbsp 7  some sites claiming the belong to Windows nbsp 8 and Windows Server 2012 though    I already tried the suggested fixes I found  which are    running  sfc  scannow  installing Visual Studio 2008 SP1 runtime executables   But that didn t solve anything   -   Side note  My development box does not have them either  and does not seem to need them  For example  the user32 dll on my box does not link against one of those  while the installation on the VMware does   Any idea on how to fix this issue  I tried to find a suitable download   fix on the Microsoft pages  but I failed     After solving my issue I wanted to report what I found out  and I can t post this as an answer because the question has been closed   Actually all the DLL files reported missing by the Dependency Walker tool  namely those    API-MS-WIN-CORE-      type DLL files were not part of the actual problem   In my case the registration of three OCX files was missing and after that everything was just fine  BUT Dependency Walker tool still listed all the very same DLL files as before even when the program was just running fine now   The gist of it  As someone elsewhere stated  the tool is a bit dated by now and does not always work properly with a newer OS  Thus keep an eye open and don t get mislead by missing  API-MS-WIN-CORE-COM-L1-1-0 DLL       the problem probably lies entirely elsewhere

User · Answer

I suggest also checking how much memory is currently being used.

It turns out that the inability to find these DLL files was the first symptom exhibited when trying to run a program (either run or debug) in Visual Studio.

After over a half hour with much head scratching, searching the web, running Process Monitor, and Task Manager, and depends, a completely different program that had been running since the beginning of time reported that "memory is low; try stopping some programs" or some such. After killing Firefox, Thunderbird, Process Monitor, and depends, everything worked again.

User · Answer

This solved the issue for me   Uninstall the Visual nbsp Studio nbsp 2010 redistributable package if you have it installed already  and then install Microsoft Windows nbsp 7 SDK

User · Answer

I had the same problem  After spending hours searching on the web  I found a solution for me    I copied the file combase dll file  C  Windows System32  to the release folder  and it resolved the problem

User · Answer

This problem is related to missing the Visual Studio  redistributable package   It is not obvious which one is missing based on the dependency walk  but I would try the one that corresponds with your compiler version first and see if things run properly   Visual Studio 2015  Visual Studio 2013  Visual Studio 2010  Visual Studio 2008  I ran into this problem because I am using the Visual Studio compilers  but not the full Visual Studio environment     Going to dare to inject a new link here  The latest supported Visual C   downloads  Stein   smul  29 11 2018

User · Answer

I just resolved the same problem with C   Qt nbsp 5 and Windows nbsp 7 64 bits with MSCVC 2012   In the beginning I thought it was a MSVC Windows DLL file problem  but as BorisP said  the problem was in my project dependencies  The key is  How to know your project dependencies in Qt nbsp 5     As I didn t find any clear way to know it  Dependency Walker didn t help me a lot      I followed next the  inverse procedure  that takes no more than 5 minutes and avoid a lot of headaches with DLL file dependencies    Compile your project and take the executable file to an empty folder  myproject exe Try to execute it  It will retrieve an error  missing DLL files      Now  copy all the DLL files from Qt  in my case they were in C  Qt Qt5 1 1 5 1 1 msvc2012 64 opengl bin  to this folder  Try to execute again  it will probably works fine  Start to delete progressively and try every time your executable still works  trying to leave the minimum necessary DLL files    When you have all the DLL files in the same folder it is easier to find which of them are not valid  XML  WebKit      whatever     and consequently this method doesn t take more than five minutes

User · Answer

I also ran into this problem  but the solution that seems to be a common thread here  and I saw elsewhere on the web  is   re install the redistributable package   However  for me that does not work  as the problem arose when running the installer for our product  which installs the redistributable package  to test our shiny new Visual nbsp Studio nbsp 2015 builds   The issue came up because the DLL files listed are not located in the Visual Studio install path  for example  C  Program Files  x86  Microsoft Visual Studio 14 0 VC redist  and thus had not been added to the install  These api-ms-win-  dlls get installed to a Windows 10 SDK install path as part of the Visual Studio 2015 install  e g  C  Program Files  x86  Windows Kits 10 Redist    Installing on Windows 10 worked fine  but installing on Windows 7 required adding these DLL files to our product install  For more information  see Update for Universal C Runtime in Windows which describes the addition of these dependencies caused by Visual nbsp Studio nbsp 2015 and provides downloads for various Windows platforms  also see Introducing the Universal CRT which describes the redesign of the CRT libraries  Of particular interest is item 6 under the section titled Distributing Software that uses the Universal CRT      Updated September 11  2015  App-local deployment of the Universal CRT is supported  To obtain the binaries for app-local deployment  install the Windows Software Development Kit  SDK  for Windows 10   The binaries will be installed to C  Program Files  x86  Windows Kits 10 Redist ucrt  You will need to copy all of the DLLs with your app  note that the set of DLL files are necessary is different on different versions of Windows  so you must include all of the DLL files in order for your program to run on all supported versions of Windows

User · Answer

For anybody who came here  but with a Photoshop problem  my solution was to uninstall the MS VC   redistributable first x86 and 64 both  Then install one appropriate to the Windows version and architecture  86 or 64

User · Answer

Just to confirm answers here  my resolution was to copy the DLL that was not loading AND the ocx file that accompanied it to the system32 folder  that resolved my issue

User · Answer

As mentioned  DCOMP is part of the VC   redistributables  implementing the OpenMP runtime  and is the only truly missing component  All the rest are false reports   Specifically API-MS-WIN-XXXX DLL are API-sets - essentially  an extra level of call indirection introduced gradually since Windows nbsp 7  Dependency Walker development seemingly halted long before that  and it can t handle API sets properly   So there is nothing to worry about there  You re not missing anything more   A better alternative to find the truly needed DLL files that are missing  if that is indeed the problem  is to run Process Monitor and step backwards from the failure  searching for sequences of failed probes for a specific DLL file in all the system path

User · Answer

I came here with this problem occurring  after trying a fresh Windows nbsp 7 OEM install  upgrading to Windows nbsp 10   After some searching of Microsoft forums and such I found the following solution which worked for me      Replace C  Windows10Upgrade wimgapi dll with the one from C  Windows System32 wimgapi dll

User · Answer

I just resolved the same problem   Dependency Walker is misleading in this case and caused me to lose time  So  the list of  missing  DLL files from the first post is not helpful  and you can probably ignore it   The solution is to find which references your project is calling and check if they are really installed on the server    Ben Brammer  it is not important which three  ocx files are missing  because they are missing only for Leo T Abraham s project  Your project probably calls other DLL files   In my case  it was not three  ocx files  but missing MySQL connector DLL file  After installing of MySQL Connector for  NET on server  the problem disappeared   So  in short  the solution is  check if all your project references are there

User · Answer

Installation of SQL Server Management Studio 2014 on a freshly installed Windows 7 resolved this problem at our client after a two-day ridiculous battle

User · Answer

This contribution does not really answer the initial question  but taking into account the hit-rate of this thread I assume that there are quite a few people dealing with the problem that API-MS-WIN-CORE- libraries cannot be found   I was able to solve a problem where my application refused to start with the error message that API-MS-WIN-CORE-WINRT-STRING-L1-1-0 DLL is not found by simply updating Visual Studio   I don t think that my build environment  Windows nbsp 7 Pro SP1  Visual Studio Ultimate 2012  was messed up completely  it worked fine for most of my projects  But under some very specific circumstances I got the error message  see below    After updating Visual Studio 11 from the initial CD-Version  I forgot to look up the version number  to version 11 0 61030 00 Update 4 also the broken project was running again

User · Answer

I solved the problem  When I registered the OCX files  I ran it with the Command Window that had been executed as an administrator

[windows] Windows 7, 64 bit, DLL problems

Examples related to windows

Examples related to dll