Home / Guides / Program and file errors

api-ms-win-core-libraryloader-l1-2-0.dll is missing - what it really means

api-ms-win-core-libraryloader-l1-2-0.dll is not a normal DLL you can lose: it is part of the internal API of newer Windows versions. On Windows 7 this exact part simply does not exist, so the error appears when a program built for newer Windows starts on an older system. On Windows 10 and 11 the file is part of the system, and the error means system files got damaged. Either way, downloading the DLL from a site is not the fix.

Ask Chipps

Describe what is happening in your own words, for example: "The program won't open, it says api-ms-win-core-libraryloader-l1-2-0.dll is missing". Chipps checks your PC, shows what it found and proposes a fix. Nothing changes until you click Allow.

Download Chipps Downloads the Chipps setup file for Windows.

Quick answer

Press Win+R, type winver and check your Windows. On Windows 7: install an older version of the program that still supports it, or move to a newer Windows. On Windows 10/11: run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an admin terminal and restart.

Symptoms - how this problem looks

"The program can't start because api-ms-win-core-libraryloader-l1-2-0.dll is missing from your computer"
A freshly downloaded program fails on an older PC with Windows 7
An installer quits immediately with this message
The same program works on a PC with Windows 10 or 11
Reinstalling the program changes nothing
On Windows 10/11 several system tools also misbehave

Why it happens

The program requires a newer Windows

The most common case. The program uses Windows API parts that Windows 7 does not have - no single file can add them.

Windows 7 lost support in new releases

Many vendors dropped Windows 7. The last compatible versions of their programs usually still exist and still work.

Damaged system files on Windows 10/11

If this error shows on a modern Windows, an update failure or disk problem damaged the API files - the built-in system repair restores them.

A fake DLL from a download site

API-set DLLs only forward calls into the system. On Windows 7 the functions behind them are missing, so a copied file just moves the crash elsewhere.

The fixes, in order

1. Check which Windows the program expects

  1. Press Win+R, type winver, press Enter.
  2. Open the program's download page and look at the system requirements.
  3. On Windows 7, download the last version that still supports it - vendors usually keep older releases available.

Honest note: if the program needs Windows 8 or newer and your PC runs Windows 7, no downloaded DLL makes it work reliably.

2. On Windows 10/11: repair the system files

  1. Right-click Start, open Terminal (Admin).
  2. Run sfc /scannow and wait for it to finish.
  3. Run DISM /Online /Cleanup-Image /RestoreHealth.
  4. Restart and start the program again.

3. Install pending Windows updates

  1. Settings, Windows Update - install everything offered, restart.
  2. A feature update replaces the whole API layer if repairs did not help.

Frequently asked questions

Can I copy this file from a Windows 10 PC to Windows 7?

It will not help: the file only points to functions that live deeper in newer Windows. Windows 7 does not have them, so the program crashes one step later with a stranger error.

Is this the same problem as api-ms-win-core-path-l1-1-0.dll?

Same family and same logic - another part of the newer Windows API. Our api-ms-win-core-path guide covers that variant.

I run Windows 10 and still see it after sfc and DISM. What then?

Install the pending feature update in Windows Update - it replaces the whole system API layer. If that is not possible, an in-place repair install of Windows keeps your files and programs.

Or let Chipps take a look

Describe the problem in your own words. Chipps reads the Windows logs, points to the likely cause and proposes the narrowest fix. Nothing is changed without your Allow, and at the end it shows what it did and what it did not do.

Download Chipps Downloads the Chipps setup file for Windows.
Your own wordsno technical terms
Your OKbefore any change
Clear reportof what was done