I've built an application with Visual Studio 2015 Community edition. When some of my users try to run it it they receive the following error:
The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.
Api ms win crt runtime l1 1 0.dll free download - Java Runtime Environment (JRE), Microsoft Visual C++ 2005 SP1 Redistributable Package (x64), Microsoft Visual C++ 2005 SP1 Redistributable Package.
Nick jonas levels free download. Title is 'StandAloneShell.exe - System Error' and the message is 'The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.' Look through the information below, which explains how to resolve your issue. On this page, you can download the api-ms-win-core-crt-l1-1-0.dll file as well. The file api-ms-win-core-crt-l1-1-0.dll is a 32/64bit Windows DLL module for Microsoft Windows Operating System software or other related programs. The file is also referred as apisetstub. The file and the associated Microsoft Windows Operating System software was developed by Microsoft Corporation. The error “api-ms-win-crt-stdio-l1-1-0.dll is missing” is typically encountered when the user tries to open an Office application, Origins or iTunes.
Clearly this is solved by installing the Update for Universal C Runtime in Windows (KB2999226). I could check for the hotfix during the install script but all of the methods I've found to do this are either too slow or unreliable.
How can I prevent this error from occurring? Can I change my solution so that I don't require this dependency? Am I linking against something I can remove? Can I redistribute the hotfix along with my application?
Edit: In the project properties, the 'Target Platform Version' is 8.1 and the 'Platform Toolset' is 'Visual Studio 2015 (v140)', if that helps at all.
Edit 2: I've tried copying all of the Universal C Runtime Library DLL's to the application directory since Microsoft now allows (but doesn't recommend) local mode installation of the UCRT. There are 41 files in
C:Program Files (x86)Windows Kits10RedistucrtDLLsx64
and api-ms-win-crt-runtime-l1-1-0.dll
is one of them. However, now running the application results in this error:The application was unable to start correctly (0xc0000142). Click OK to close the application.
I've tried debugging the application with MSVS 2015 but got nowhere. I opened the executable in Dependency Walker and it appears that I'm missing similar DLLs listed in this answer, which says that Dependency Walker is old and this is a red herring.
I tried running the application through Process Monitor (procmon) and there's nothing unusual. The application simply calls 'Process Create' on WerFault.exe and then 'Thread Exit.'
Edit 3: I enabled loader snaps on the executable and got this when running it from cdb, if it helps:
Community♦
a paid nerda paid nerd
2 Answers
You should link statically with the CRT. For a consumer application there are a lot of scenarios which result in particular DLL missing or its configuration botched. I was the installer technical lead for a very popular Windows application (thousands of installs per day) and you would not believe how common misconfigured Windows machines are out there. At the bottom I'll give a short list.
The universal CRT is a good idea but relatively new and it will be a while, (possibly a long while) until it being broken prevents your customers' PC from booting. That should be the threshold: If your customer cannot log in without DLL X then it is ok to depend on it.
Common Weird states:
- MSI installer in progress : Somehow Windows thinks that there is aninstallation in progress
- COM database inconsistent : The HKCU part ofthe registry is a rough place
- Missing MSVC crts or pre-release versions in there
- Pre-release versions of Windows : we guess thatpre-release Windows are easier to pirate.
- Still in sysprep : The OEMforgot to seal the machine configuration.
- Fonts corrupt: Specially painful if you use DirectWrite
- Overclocked: eventual bit flips in filesystem buffers equal corrupted files.
AlienRancherAlienRancher
I could check for the hotfix
Pretty important to keep in mind that this is not a hotfix. It is a normal update that is automatically delivered through Windows Update. So there's one fact you know, these machines are not being maintained. That's Very Bad News of course and having problems is to be expected.
api-ms-win-crt-runtime-l1-1-0.dll is missing
It is an operating system DLL that is normally supplied along with the operating system install, starting with Win7. That ought to narrow down what's wrong with these machines, they are likely to boot XP. Small odds for Vista. XP is no longer maintained by Microsoft so seeing the update missing is not a coincidence.
the 'Target Platform Version' is 8.1 and the 'Platform Toolset' is 'Visual Studio 2015 (v140)'
That's fine but you need to double-check this in your installer and refuse to install on XP. Targeting XP is still possible, you have to change the Platform Toolset setting to 'v140_xp'. Not sure if that option is available in the Community edition, it would surprise me if it was.
There are 41 files in ..
Only one counts, ucrtbase.dll. The rest of them are the api-ms-win*.dll files that ought to be present in the Windows install directory. They are included so you can still get it going on XP and Vista, you should deploy these to c:windowssystem32 or c:windowssyswow64, depending on the bitness. Do note that you documented the x64 directory, verifying that the user has a 64-bit version of Windows is another thing you have to double-check in your installer.
The application was unable to start correctly (0xc0000142).
Api Ms Win Core Crt L1 1 Dll Download For Windows 10
That is STATUS_DLL_INIT_FAILED, the DllMain() entrypoint of one of the DLLs you have a dependency on returned FALSE. Here comes the boom download. Pretty bad news, not easy to debug and you certainly won't get anywhere trying to tackle this with VS2015 since it won't fail on your machine. You need to turn on loader snaps so the OS loader becomes chatty. Having access to a machine that has this problem is of course mandatory.
Clearly this is solved by installing the Update ..
Yeah, time to cut your losses I'd say. Nobody can reasonably expect your app to work when they intentionally don't maintain their machine or refuse to update it. Verify in your installer that ucrtbase.dll is present and when it is not then just stop the install and tell them to update their machine first.
Not the answer you're looking for? Browse other questions tagged c++windowsvisual-studiodll or ask your own question.
Api-ms-win-core-crt-l1-1-0.dll Download
Compatible with Windows 10, 8, 7, Vista, XP and 2000
Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall
Overview of Api-ms-win-core-crt-l1-1-0.dll
![Api-ms-win-crt-core-processthreads-l1-1-1.dll Api-ms-win-crt-core-processthreads-l1-1-1.dll](https://praxistipps-images.chip.de/wVPefApk7nck0FTk0vQbmb60esQ=/0x0/filters:no_upscale():format(jpeg)/praxistipps.s3.amazonaws.com%2Fhilfe-windows-fehler-beheben_5d65f6ec.png%3F5965396fab169)
What Is Api-ms-win-core-crt-l1-1-0.dll?
Api-ms-win-core-crt-l1-1-0.dll is a type of DLL file associated with Windows 8 Pro developed by Microsoft for the Windows Operating System. The latest known version of Api-ms-win-core-crt-l1-1-0.dll is 1.0.0.0, which was produced for Windows. This DLL file carries a popularity rating of 4 stars and a security rating of 'UNKNOWN'.
What Are DLL Files?
DLL ('dynamic link library') files such as api-ms-win-core-crt-l1-1-0.dll are small programs, similar to EXE ('executable') files, which allow multiple software programs to share the same functionality (eg. printing).
For example, let's say you are running Windows and editing a document in Microsoft Word. The DLL file that controls printing does not need to load unless it's function is needed - eg. you decide to print your document. When you select 'Print', Microsoft Word calls the printer DLL file, and it is loaded into memory (RAM) at that time. If you want to print a document in another program, Adobe Acrobat for example, that same printer DLL file will be used as well.
Why Do I Have DLL Errors?
Because they are shared files, DLL files exist outside of the software application itself. Although this provides many benefits for software developers, this separation also provides an opportunity for problems to occur.
Quite simply, if Windows cannot properly load your api-ms-win-core-crt-l1-1-0.dll file, you will encounter an error message. Please see 'Causes of api-ms-win-core-crt-l1-1-0.dll Errors' below for more information.
When Do DLL Errors Occur?
DLL errors, such as those associated with api-ms-win-core-crt-l1-1-0.dll, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. printing).
Common Api-ms-win-core-crt-l1-1-0.dll Error Messages
The most common api-ms-win-core-crt-l1-1-0.dll errors that can appear on a Windows-based computer are:
- 'Api-ms-win-core-crt-l1-1-0.dll not found.'
- 'The file api-ms-win-core-crt-l1-1-0.dll is missing.'
- 'Api-ms-win-core-crt-l1-1-0.dll Access Violation.'
- 'Cannot register api-ms-win-core-crt-l1-1-0.dll.'
- 'Cannot find C:WindowsSystem32api-ms-win-core-crt-l1-1-0.dll.'
- 'Cannot start Windows 8 Pro. A required component is missing: api-ms-win-core-crt-l1-1-0.dll. Please install Windows 8 Pro again.'
- 'This application failed to start because api-ms-win-core-crt-l1-1-0.dll was not found. Re-installing the application may fix this problem.'
These DLL error messages can appear during program installation, while a api-ms-win-core-crt-l1-1-0.dll-related software program (eg. Windows 8 Pro) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your api-ms-win-core-crt-l1-1-0.dll error occurs is a critical piece of information in troubleshooting the problem.