api-ms-win-crt-heap-l1-1-0.dll Is Missing: A Safe Fix Path

“The program can’t start because api-ms-win-crt-heap-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.”

api-ms-win-crt-heap-l1-1-0.dll is a Microsoft Universal C Runtime component, so the reliable repair is to restore the Windows runtime or the application’s official runtime package, not to download one DLL from a random website.

As an Amazon Associate I earn from qualifying purchases.

You may also see:

The code execution cannot proceed because api-ms-win-crt-heap-l1-1-0.dll was not found.

×Worth Installing

PC Slower Than It Used to Be?

Outbyte PC Repair · freeA free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Run a Free PC Scan →

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

api-ms-win-crt-heap-l1-1-0.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor.

#1 Best Overall

Sale

Microsoft Windows 11 (USB)

• Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
• Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
• Make the most of your screen space with snap layouts, desktops, and seamless redocking.
• Widgets makes staying up-to-date with the content you love and the news you care about, simple.
• Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)

$128.99

Buy on Amazon

Error loading api-ms-win-crt-heap-l1-1-0.dll. The specified module could not be found.

The wording changes with the Windows version, application loader, language, and the underlying failure. “Not designed to run on Windows” does not prove that the filename is fake or that this one file is the only damaged component.

The 60-second answer

Follow this order:

1. Press Win+R, type winver, and identify your Windows version.
2. Install all pending Windows updates, restart, and check for updates again.
3. Install or repair the official Microsoft Visual C++ Redistributable that matches the failing application.
4. Use x86 for a 32-bit application and x64 for a 64-bit application. On 64-bit Windows, installing both is normal when you use applications of both types.
5. If only one application fails, repair, verify, or reinstall that application from its official installer.
6. If several applications fail, run DISM and SFC from an elevated Command Prompt.
7. Check Windows Security Protection History if the problem began after an update or antivirus detection.

The official package hub is Microsoft’s Latest supported Visual C++ Redistributable downloads. Do not download api-ms-win-crt-heap-l1-1-0.dll separately from a DLL archive.

What api-ms-win-crt-heap-l1-1-0.dll actually is

This filename belongs to Microsoft’s Universal C Runtime, commonly abbreviated UCRT. More precisely, it is an API-set forwarder. API-set files provide a stable Windows API contract that applications can call, while the underlying implementation is provided elsewhere, including by ucrtbase.dll. Microsoft describes this API-set model in its documentation for Windows API sets.

The heap-related contract includes C runtime functions such as:

• malloc
• free
• calloc
• realloc
• aligned-allocation functions

That does not mean this small API-set file is the main heap implementation. It helps the application resolve the correct runtime functions for the Windows environment.

The filename does not identify a particular game, graphics driver, or business application. Bethesda games, The Elder Scrolls Online, QGIS, OpenSceneryX, Haltech ICC software, and software built with Unreal Engine have all been associated with errors involving this runtime component. Those applications consume the runtime or may redistribute a private copy. They do not own the Microsoft API-set itself.

Microsoft’s Windows 10 extension API list documents the related Universal CRT API contracts. The internal description is not consistently published as a single product description, so “Universal CRT API-set forwarder” is the most useful and accurate description.

Where the file comes from

There are two normal deployment models.

On Windows 10, Windows 11, and newer supported Windows Server versions, the Universal C Runtime is part of Windows. Microsoft explains this in its Universal CRT deployment documentation.

An application can also deploy a private copy of UCRT files beside its executable. This is common when a publisher wants its installer to carry the runtime files required by that application. If an update fails or antivirus removes one of those files, the application can stop launching even though other programs continue to work.

On 64-bit Windows, the normal system locations are:

• C:\Windows\System32 for native 64-bit system files
• C:\Windows\SysWOW64 for 32-bit system files

The names are confusing. On 64-bit Windows, System32 normally contains 64-bit system files, while SysWOW64 contains 32-bit system files. Microsoft documents this behavior in its file-system redirector documentation.

Do not treat those paths as instructions to copy a downloaded DLL into them. The location alone does not prove that a file is genuine, compatible, or complete.

Why the error appears

The message says the loader could not satisfy a runtime dependency. “Missing” can therefore mean more than “the filename is absent.”

Common causes include:

Likely cause	What it usually means	Best first repair
Missing or outdated UCRT	Windows lacks the required Universal CRT files or updates	Install Windows updates
Wrong architecture	A 32-bit application is being given only a 64-bit runtime, or the reverse	Install x86 or x64 to match the application
Broken VC++ installation	The runtime is listed but files or installer metadata are damaged	Repair the official Redistributable
Failed application update	A private copy beside the program is incomplete	Verify, repair, or reinstall the application
Antivirus quarantine	A runtime file was removed after installation or update	Check Protection History and reinstall the trusted package
System-file corruption	Windows component files cannot be read correctly	Run DISM, then SFC
Incompatible private DLL	The application finds an old or wrong-architecture copy first	Repair or reinstall the application
Older Windows release	Windows 7, 8, or 8.1 lacks the required UCRT update or prerequisite	Install the applicable Windows updates and UCRT package

The most useful diagnostic question is whether one application fails or several unrelated applications fail.

• One failing application points toward its installer, private runtime files, antivirus quarantine, or a game-launcher update.
• Several failing applications point toward Windows Update, the system-wide UCRT, Visual C++ installation damage, or Windows system-file corruption.

Fix 1: Install Windows updates first

This is the safest first step because the UCRT is part of the operating system on modern Windows.

Windows 11

1. Select Start.
2. Open Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install every available update.
6. Restart the PC when prompted.
7. Return to Settings > Windows Update and select Check for updates again.
8. Repeat until Windows reports that no further updates are currently available.

Windows 10

1. Select Start.
2. Open Settings.
3. Select Update & Security.
4. Select Windows Update.
5. Select Check for updates.
6. Install the available updates.
7. Restart the computer.
8. Check Windows Update again after restarting.

Microsoft’s Windows Update instructions cover the current update process.

After the restart, launch the affected program again.

If it works, the missing runtime was supplied or repaired through Windows servicing. If it still fails, continue with the matching Visual C++ package rather than copying the DLL manually.

Important Windows 10 qualification

Microsoft ended normal Windows 10 support on October 14, 2025. A Windows 10 machine can still have a runtime problem caused by an incomplete earlier update, but an unsupported installation may not receive the same servicing path as a supported Windows release. Microsoft explains the support status in its Windows 10 security update notice.

Fix 2: Install or repair the matching Visual C++ Redistributable

The current Visual C++ Redistributable packages use the v14 runtime family. Visual Studio 2017 and later use the shared v14 runtime family, but the architecture still has to match the application.

Use Microsoft’s Latest supported Visual C++ Redistributable downloads. The current package names are:

• vc_redist.x86.exe
• vc_redist.x64.exe
• vc_redist.arm64.exe

Choose x86 or x64 correctly

The operating system’s architecture is not enough to choose the package.

• A 32-bit application needs the x86 Redistributable.
• A 64-bit application needs the x64 Redistributable.
• A 64-bit version of Windows can run both types of applications, so it is normal to install both x86 and x64.
• An ARM64 computer may need ARM64 for a native ARM application or x86 for a 32-bit application.

If you do not know whether the failing program is 32-bit or 64-bit, check the application’s documentation or installer. For a game, the publisher or launcher may identify the architecture. Installing both x86 and x64 on 64-bit Windows is usually the practical choice when several programs are involved.

Install the package

1. Close the affected application and its launcher.
2. Open Microsoft’s official Redistributable download page.
3. Download the required x86, x64, or ARM64 installer.
4. Right-click the downloaded installer.
5. Select Run as administrator.
6. Accept the license terms.
7. If the installer offers Repair, select Repair.
8. If it offers Install, select Install.
9. Wait for the operation to finish.
10. Restart Windows.
11. Launch the affected application.

The repair succeeded if the application opens without the missing-file message. If the installer reports that a newer version is already installed, use Repair rather than repeatedly installing the same package.

If repair fails, record the exact installer message. Microsoft provides VC++ Redistributable installation troubleshooting for permissions, Windows Installer, and incomplete-package problems.

Use the official installer’s repair options

Microsoft documents installer options including /install, /repair, and /uninstall in its Visual C++ redistribution documentation. Most users should use the graphical installer. Command-line options are useful for administrators deploying repairs consistently.

For example, from an elevated Command Prompt in the directory containing the official installer:

vc_redist.x64.exe /repair

For a 32-bit runtime:

vc_redist.x86.exe /repair

The command must match the actual installer filename and application architecture. If the installer does not support the requested operation or the package is not present, use the graphical installer and select Repair or install the package normally.

Do not uninstall every Visual C++ package as a first step. Other applications may depend on different runtime generations. Repair the architecture and runtime family relevant to the failing application.

Visual Studio 2015 package

Some older applications specifically require the Visual C++ Redistributable for Visual Studio 2015. Microsoft provides the official x86 and x64 packages on the Visual C++ Redistributable for Visual Studio 2015 download page.

Use the application’s original installer instructions when it explicitly requires that package. Do not assume that a single DLL copied from another PC can replace the complete runtime.

Fix 3: Handle Windows 7, 8, and 8.1 UCRT requirements

The subject of this guide is Windows 10 and Windows 11, but older Windows installations are a common source of this error when running older applications.

Windows 7, Windows 8, and Windows 8.1 may require the operating-system Universal C Runtime update rather than only a Visual C++ Redistributable. Microsoft identifies the relevant update as the Update for Universal C Runtime in Windows, initially associated with KB2999226.

On Windows 8.1, Microsoft identifies the April 2014 update, KB2919355, as a prerequisite for the relevant UCRT package. See Microsoft’s KB2919355 documentation.

The safe sequence is:

1. Open Control Panel.
2. Select System and Security.
3. Select Windows Update.
4. Select Check for updates.
5. Install all applicable updates and prerequisites.
6. Restart when required.
7. Install the UCRT update appropriate to the Windows edition and architecture.
8. Restart again.
9. Install or repair the application’s required Visual C++ Redistributable.
10. Launch the program.

Do not install an update intended for a different Windows edition or architecture. If Windows Update cannot service the machine, use Microsoft’s update documentation and the operating system’s supported recovery path instead of obtaining a package from an unofficial archive.

Fix 4: Repair or reinstall the affected application

If only one application fails, the application’s own files deserve priority over system-wide changes.

Repair a Windows application

Windows may expose a repair option for installed programs.

1. Open Start.
2. Select Settings.
3. In Windows 11, select Apps > Installed apps.
4. In Windows 10, select Apps > Apps & features.
5. Find the affected application.
6. Select the application’s menu or Advanced options, depending on the application type.
7. Select Repair if available.
8. Launch the program after the repair completes.

Microsoft documents these paths in Repair apps and programs in Windows.

For a traditional desktop program, also check:

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Select the affected program.
5. Choose Repair or Change if the installer provides it.
6. Complete the wizard.
7. Restart Windows if requested.

If repair does not restore the program, reinstall it using the publisher’s official installer. This matters because the installer may place a coordinated set of runtime files beside the executable. Replacing only api-ms-win-crt-heap-l1-1-0.dll may leave other required files missing or mismatched.

Verify game files

For a game installed through Epic Games Launcher:

1. Open Epic Games Launcher.
2. Select Library.
3. Find the game.
4. Select the three dots beside the game.
5. Select Manage.
6. Select Verify.
7. Wait for the file check and repair to finish.
8. Start the game again.

Epic documents this process in its game-file verification instructions.

Other launchers use similar names, such as Verify, Scan and repair, or Validate files. Use the launcher’s built-in function instead of deleting random files from the game directory.

This step is especially important after:

• A game update
• A failed installation
• Moving a game between drives
• Restoring files from a backup
• Antivirus quarantine
• Copying a game directory from another computer

Fix 5: Check antivirus quarantine safely

A legitimate runtime file can be quarantined, but a malicious file can also use the same filename. The filename alone is not enough to approve a restore.

To inspect Microsoft Defender’s history:

1. Open Start.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review detections around the time the error began.
7. Open a relevant detection and inspect the original file path.
8. Confirm whether the path belongs to Windows or to a trusted application installation.

Microsoft explains Protection History and the risks of restoring detections in its Windows Security Protection History documentation.

Restore a file only when its source is trusted and verified. If the file came from a normal Microsoft component or a trusted application installation, reinstalling the official package is preferable to restoring an isolated file. Microsoft warns that Defender may detect a restored file again.

Do not disable antivirus protection just to copy a DLL into a system directory. If the detection remains active, investigate the application installer and the detection details before proceeding.

Fix 6: Repair Windows components with DISM and SFC

Use this step when:

• Several unrelated applications fail
• Windows Update does not repair the problem
• The runtime appears to be missing from the system
• Other Windows components are also behaving incorrectly
• The error began after a failed update or disk problem

Open an elevated Command Prompt

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes at the User Account Control prompt.

Run DISM first:

DISM.exe /Online /Cleanup-image /Restorehealth

Wait for it to complete. It may take time and may appear to pause at a percentage. Do not close the window while it is running.

Then run System File Checker:

sfc /scannow

Microsoft’s current order is DISM followed by SFC, as described in Using System File Checker in Windows.

Restart Windows after both commands finish.

Interpret the result

If SFC says it found corrupt files and repaired them, restart and test the application.

If SFC says it found corrupt files but could not repair some of them, run DISM again, restart, and run SFC again. If the same problem remains, use Windows recovery options or an in-place repair installation.

If SFC says it found no integrity violations but the application still fails, the problem is more likely to be the application’s private files, the wrong runtime architecture, a missing dependency, or an incompatible local DLL.

The commands do not download a replacement from an unofficial source. They use Windows servicing and the component store to repair protected system files.

Running these commands repeatedly without reading the result rarely adds useful information. Outbyte PC Repair can provide a scan that shows what it identifies before its full version performs repairs, which can reduce the manual work of repeating SFC and DISM without knowing what changed.

Fix 7: Check the application directory for a wrong local copy

A file can exist and still fail to load. The loader may be finding:

• A 32-bit file for a 64-bit program
• A 64-bit file for a 32-bit program
• An outdated private copy
• A corrupted file
• A file whose dependency is missing

To inspect the application directory:

1. Right-click the application shortcut.
2. Select Properties.
3. Open the Shortcut tab.
4. Select Open File Location.
5. Look for api-ms-win-crt-heap-l1-1-0.dll in the application directory.
6. Do not delete or replace it immediately.
7. Use the application’s repair, verification, or reinstall process.

If the file is present beside the executable, that does not establish that it is valid. The safest correction is to let the publisher’s installer place the complete matching runtime set.

If the application was copied from another computer or extracted from a ZIP file, reinstall it through the publisher’s installer. Copied applications can lack prerequisites, registry entries, services, or the correct architecture-specific runtime.

Fix 8: Use System Restore after a known change

System Restore is appropriate when the error began immediately after a software installation, Windows update, driver change, or similar system modification and a suitable restore point exists.

1. Press Win+R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point dated before the problem began.
4. Select Scan for affected programs if available.
5. Review the affected software and drivers.
6. Select Next.
7. Select Finish.
8. Confirm the restore.

System Restore rolls back system files, settings, drivers, and installed programs, but it normally does not remove personal files. Microsoft explains the process in its System Restore documentation.

If Windows cannot start normally:

1. Open Windows Recovery Environment.
2. Select Troubleshoot.
3. Select Advanced options.
4. Select System Restore.
5. Choose the appropriate restore point.

A restore point may be unavailable because System Restore was disabled, expired, or never created. If that happens, use Windows repair options or an in-place repair installation. Microsoft lists alternatives in Recovery options in Windows.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 9: Update a driver only when there are separate driver symptoms

api-ms-win-crt-heap-l1-1-0.dll is not a graphics or hardware-driver DLL. A graphics-driver update can still be relevant to a game that has additional rendering or device errors, but it is not the normal repair for this runtime component.

Use Device Manager when:

• The application vendor specifically recommends a driver update
• Device Manager shows a warning icon
• The game also reports graphics initialization errors
• The problem began with a driver installation
• Windows reports a device problem separately from the DLL error

Device Manager steps

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters.
4. Right-click the affected device.
5. Select Properties.
6. Open the Driver tab.
7. Note the provider, date, and version.
8. Select Update Driver.
9. Select Search automatically for drivers.
10. Restart Windows if a driver is installed.

If the issue began immediately after a driver update:

1. Open Device Manager.
2. Expand the affected device category.
3. Right-click the device.
4. Select Properties.
5. Open the Driver tab.
6. Select Roll Back Driver if available.
7. Restart Windows.

For a clean reinstall, use the hardware manufacturer’s official support process. Do not remove unrelated drivers merely because the DLL error mentions a missing runtime.

Outbyte Driver Updater can scan for outdated drivers and identify what it finds before its full version installs updates, which is useful when manually checking many device categories and matching each driver to the hardware.

Why downloading the DLL manually is unsafe

Random DLL download sites websites create several risks:

• The file may contain malware.
• It may be the wrong architecture.
• It may belong to a different Windows build.
• It may be modified or unsigned.
• It may be accompanied by other missing dependencies.
• It may cause the loader to find an incompatible private copy.
• It does not repair the underlying UCRT, Visual C++, Windows Update, or application installation problem.

Microsoft describes the UCRT as a coordinated deployment of runtime files. That is why copying one filename into System32 or SysWOW64 is not a dependable repair. Use Windows Update, Microsoft’s official Redistributable packages, or the application publisher’s official installer.

A Microsoft update may list a particular file version and size, but those values change as Windows is serviced. They are not universal download targets.

Why regsvr32 is not the fix

Do not run:

regsvr32 api-ms-win-crt-heap-l1-1-0.dll

This file is an API-set forwarder, not an ordinary COM component that should be manually registered. Microsoft explains that self-registering DLLs must expose DllRegisterServer and DllUnregisterServer; runtime and API-set files are not repaired by registering them with regsvr32. See Microsoft’s self-registration documentation.

If you already ran regsvr32 and received an error, that result does not identify the root cause. Continue with Windows Update, the correct Visual C++ architecture, application repair, and DISM/SFC.

What to do when the file exists but the error remains

Check the following in order:

1. Confirm whether the failing application is 32-bit or 64-bit.
2. Install the matching x86 or x64 Redistributable.
3. If the application directory contains its own copy, repair or reinstall the application.
4. Check whether antivirus quarantined another runtime file.
5. Run DISM followed by SFC if multiple applications are affected.
6. Check the full error message for a named dependency or entry-point failure.
7. Use System Restore if the problem clearly follows a recent change.

The loader can report this filename when another dependency is missing. The visible filename is not always the only defective component.

Windows Features: what to change and what not to change

The Windows Features dialog does not install or repair the Universal C Runtime.

You can open it by:

1. Opening Start.
2. Typing Windows Features.
3. Selecting Turn Windows features on or off.

Do not randomly enable or disable features in an attempt to restore this DLL. Features such as legacy components or .NET components may matter for a separate application error, but they do not replace the Visual C++ Redistributable or the UCRT.

If a specific application’s official documentation names a Windows feature, enable only that feature, restart if requested, and retest the application. For this filename alone, Windows Features is not the correct repair path.

How to identify the correct branch

Use this short decision path:

Only one game or application fails

Repair or verify that application first. Then repair the matching Visual C++ package. Check antivirus history if the problem began after an update.

Several unrelated applications fail

Install Windows updates, repair the Visual C++ packages for both architectures used on the machine, then run DISM and SFC.

The computer runs Windows 7, 8, or 8.1

Install all applicable Windows updates, including the Universal C Runtime update and required prerequisites, before troubleshooting the application.

The application was copied from another PC

Reinstall it with the publisher’s installer. A copied folder may not contain the correct runtime, services, registry entries, or architecture-specific components.

The error says “not designed to run on Windows”

Treat it as a compatibility, corruption, or dependency-resolution error. Check the application-local copy, runtime architecture, antivirus history, and application repair path.

The problem follows a graphics-driver change

Use Device Manager to roll back or update the driver, but continue to treat the DLL as a runtime component rather than a driver file.

FAQ

Is api-ms-win-crt-heap-l1-1-0.dll safe?

The genuine Microsoft UCRT component is legitimate. The filename alone cannot prove that a particular copy is safe. Verify its path and source, and prefer Windows Update, Microsoft’s Redistributable installer, or the trusted application installer.

Does this file belong to Visual C++ or Windows?

Both descriptions can be relevant. On modern Windows, the Universal C Runtime is part of the operating system. Applications can also install or carry the runtime through Visual C++ deployment packages or private application-local files.

Should I install x64 because my computer is 64-bit?

Not automatically. Choose the package based on the application. A 32-bit program needs x86 even on 64-bit Windows. Many 64-bit PCs should have both x86 and x64 packages because they run applications of both architectures.

Is it normal to have both x86 and x64 Redistributables installed?

Yes. They are separate runtime architectures and support different applications.

I installed Visual C++ but the error remains. What next?

Repair the installed package, confirm the application architecture, install the other architecture if needed, and repair or verify the affected application. If several programs fail, run DISM and SFC.

Can I copy the file from another computer?

Do not. The copy may be from another Windows build, architecture, or servicing state. Restore the runtime through Microsoft’s official update or installer process.

Should I put the DLL in System32 or SysWOW64?

No. Manual copying can create the wrong-architecture or wrong-version problem and does not restore the coordinated runtime files. Use the correct official package.

Why does regsvr32 fail?

API-set forwarders are not ordinary COM components and are not repaired through manual registration. regsvr32 is not appropriate for this runtime file.

What if antivirus quarantined the file?

Inspect Windows Security > Virus & threat protection > Protection history. Verify the original path and source. Reinstall the trusted application or Microsoft runtime rather than blindly restoring an isolated file.

Could a driver be responsible?

A driver may be related to a separate game or device failure, but this filename is a Universal C Runtime component, not a graphics-driver DLL. Update or roll back drivers only when there are separate driver symptoms or the application vendor recommends it.

Why does only one program fail when Windows seems fine?

That usually points to an application-local runtime copy, a failed application update, missing bundled prerequisites, or a launcher file problem. Repair, verify, or reinstall that application before making broad system changes.

What should I do if every repair fails?

Record the Windows version, application name, application architecture, exact error text, application path, antivirus detection details, and the output from DISM and SFC. Then use Windows recovery options or the application publisher’s support process. The filename by itself is not enough to distinguish a missing system component from a wrong local copy or another dependency failure.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.