You are not missing those DLLs.Those DLLs are Windows's implementation detail and are subject to change at anytime. Basically Microsoft started moving around APIs starting from Windows 8. For example, APIs in Windows 8's api-ms-win-core-file-l1-2-0.dll got moved to api-ms-win-core-file-l1-2-1.dllin Windows 8.1. Old software still work because the dlls developer linked to are now just placeholders redirecting calls to the actual implementation.
![]()
But nobody should link to the implementations directly, as that would be defeating the purpose of havingsuch a redirection. Any software that report those dlls are missing are failing to accommodate the redirection (e.g. Reporting a delay-loaded dependency as hard one).Don't try to obtain those dlls. The only supported way to get those DLLs is to do a major Windows upgrade (e.g. From Windows 7 to Windows 10). Distributing those files is against Windows end user agreement, and those files you get from a higher version ofWindows won't work if your Windows version is too low.If you are a developer, just use the APIs documented in the Windows SDK (unless absolute necessary like writing antivirus) and do not take any dependency on those dlls, as they may only exist in one Windows version.
Fix: Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. If the issue is with your Computer or a Laptop you should try using Reimage Plus which can scan the repositories and replace corrupt and missing files. Once you've added, it will create the necessary string files in the appropriate lproj directories for the given language.-EDIT-Just to be clear, iOS will swap out the string for your Plist file based upon the user's currently selected language using the plist entry's key as the key in the localized strings file.
Those APIs may or may not use the DLLsyou listed, but their dependencies are not yours to worry. You should only depend on documented APIs, not implementation details like the name of those DLL. Instead of taking a direct dependency on api-ms-win-core-file-l1-2-0.dll you should takea dependency on kernel.dll which supports Windows 7 as well. As you said, the API Sets sound like they might be. The 'umbrella' libs in API sets, MinCore.lib and MinCoreDownlevel.lib are provided in the Microsoft Windows Software Development Kit (SDK) that encompasses the API surface defined in API Setsplus additional APIs that are contained in well-layered system DLLs. So try include MinCore.lib and MinCoreDownlevel.lib maybe useful. I have search in my win7 and these are in SDK directory.
But notice that binaries that link to MinCore.lib or MinCoreDownlevel.libare not designed to work on Windows 7. You are not missing those DLLs.Those DLLs are Windows's implementation detail and are subject to change at anytime. Basically Microsoft started moving around APIs starting from Windows 8. For example, APIs in Windows 8's api-ms-win-core-file-l1-2-0.dll got moved to api-ms-win-core-file-l1-2-1.dllin Windows 8.1. Old software still work because the dlls developer linked to are now just placeholders redirecting calls to the actual implementation. But nobody should link to the implementations directly, as that would be defeating the purpose of havingsuch a redirection.
![]()
Any software that report those dlls are missing are failing to accommodate the redirection (e.g. Reporting a delay-loaded dependency as hard one).Don't try to obtain those dlls. The only supported way to get those DLLs is to do a major Windows upgrade (e.g. From Windows 7 to Windows 10). Distributing those files is against Windows end user agreement, and those files you get from a higher version ofWindows won't work if your Windows version is too low.If you are a developer, just use the APIs documented in the Windows SDK (unless absolute necessary like writing antivirus) and do not take any dependency on those dlls, as they may only exist in one Windows version.
Those APIs may or may not use the DLLsyou listed, but their dependencies are not yours to worry. You should only depend on documented APIs, not implementation details like the name of those DLL. Instead of taking a direct dependency on api-ms-win-core-file-l1-2-0.dll you should takea dependency on kernel.dll which supports Windows 7 as well. As you said, the API Sets sound like they might be. The 'umbrella' libs in API sets, MinCore.lib and MinCoreDownlevel.lib are provided in the Microsoft Windows Software Development Kit (SDK) that encompasses the API surface defined in API Setsplus additional APIs that are contained in well-layered system DLLs. So try include MinCore.lib and MinCoreDownlevel.lib maybe useful.
I have search in my win7 and these are in SDK directory. But notice that binaries that link to MinCore.lib or MinCoreDownlevel.libare not designed to work on Windows 7. This is not (totally) misinformation. Rather this is 'blinkered' future-oriented view - ignoring those few retarded customers that still use ancient OS versions - like, anything older than Win10.I'm still trying to understand how these API DLLs work.The short story is that they.should.
be present on any supported Windows version, at least with some updates installed.If they are not present on certain machine - its Windows is either unsupported or not updated.To build for these Windows versions, use Visual Studio older than 2015, which will not create references to those DLLs. Downloading stuff from dodgy dll websites is not supported. It may or may not work, at your own risk.Build with VC 2015 and WinXP compatible platform toolset seems to run on XP SP3. I have not fully verified this, a simple 'hello world' program built without VC runtime DLLs does run.Regards,-pa. Hi Sheng, thanks!
Just wanted to point out that these statements 'nobody should link to the implementations directly, as that would be defeating the purpose' and 'Any software that report those dlls are missing are failing to accommodate theredirection ' sound quite funny now, because I ended up on this post after an similar error thrown by a Microsoft application: the DPM 2016 agent. It's disappointing how some Microsoft's own products fail so badly to accommodate prerequisites, andhave so many limitations, while lacking proper documentation about it.By the way, if someone got here because of a DPM 2016 agent installation error, such as 'missingapi-ms-win-core-heap-l1-2-0 dll', take a look at this post. No app targeting windows 7 should report this error as the API set used by the DLL is introduced in Windows 8. Dear all,i run into the same problem today.Suddenly, after a clean and a build i got the ReflectionRypeLoadException. Looking at the ExceptionLoader it says that is impossible to find an assembly 'name.dll' or its dependencies. Of course 'name.dll' is there. Using 'DependencyWalker' i can see that all these dll are not found (referenced by SPAACIS.dll)I'm using Visual Studio Community 2013, the pc came with Win10, no updates where installed recently.
Everything worked smooth for months till today.Some help would be appreciated.ThanksBR1.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |