api-ms-win-crt-private-l1-1-0.dll: Causes and Safe Windows Fixes

api-ms-win-crt-private-l1-1-0.dll errors usually mean that the Microsoft Universal C Runtime is missing, damaged, mismatched, or incompatible with the application trying to start. Repair the correct Visual C++ runtime or Windows component first, and do not download this DLL from a random file website.

If only one application fails, repair or reinstall that application after checking the runtime. If several unrelated programs fail, use Windows Update, DISM, and SFC to repair Windows itself.

As an Amazon Associate I earn from qualifying purchases.

What this file actually does

api-ms-win-crt-private-l1-1-0.dll is part of the Universal C Runtime, or UCRT, used by applications built with Microsoft Visual C++. Microsoft introduced the UCRT with the Visual Studio 2015 CRT changes and distributes it through Windows servicing, Visual C++ Redistributables, and sometimes an application’s own installer.

The name is unusual because this is an API-set forwarder or stub DLL. An API-set name describes a contract that Windows maps to an implementation such as ucrtbase.dll. The name does not always represent a normal, standalone library that must be visible as a physical file on disk. Microsoft explains this API-set behavior in its Windows API sets documentation.

The word private does not mean that the file belongs to a private company or that it should be hidden. It is part of the contract name used by the runtime.

The local copy may have been supplied by the program that installed it, particularly if the file is in the application’s own directory. The underlying runtime family is Microsoft’s UCRT, but a particular file’s description or publisher metadata may not be useful or may not be listed.

This is not:

• A DirectX component
• A .NET assembly
• A hardware-driver binary
• A game-specific library
• A COM component that needs registry registration

Microsoft describes the UCRT as a Windows component on Windows 10 and later. Windows 7, Windows 8, and Windows 8.1 receive it through Windows Update, the Universal C Runtime update, or a compatible Visual C++ package. See Microsoft’s Universal CRT deployment guidance.

On Windows 10 and Windows 11, the API-set contract may be resolved by the loader without a same-named file physically appearing in System32. Therefore, searching for this exact filename is not always a useful diagnosis.

Error symptoms and what they usually mean

Symptom	Most likely cause	Best first repair
“The program can’t start because api-ms-win-crt-private-l1-1-0.dll is missing from your computer”	Missing UCRT, incomplete installation, or quarantined application file	Repair the matching Visual C++ runtime, then repair the application
“The code execution cannot proceed because … was not found”	Missing runtime or incompatible local DLL	Install Windows updates and repair the application
“The procedure entry point could not be located in the dynamic link library api-ms-win-crt-private-l1-1-0.dll”	The file exists but is the wrong version, or related UCRT files do not match	Repair the runtime set instead of replacing one DLL
Only one game or launcher fails	Damaged game files or an application-local runtime	Use the launcher’s repair or verification feature
Only a 32-bit program fails on 64-bit Windows	The x86 runtime is missing	Install or repair the x86 Visual C++ package
Several unrelated applications fail	Corrupted Windows components or a broader servicing problem	Run Windows Update, DISM, and SFC
The problem began after antivirus activity	The DLL or parent application may have been quarantined	Check Windows Security Protection History
The problem began after an application update	The update may have installed an incompatible local runtime	Update, roll back, repair, or reinstall that application
The message includes 0xc000007b or “Bad Image”	Wrong architecture or mismatched runtime files	Install the correct x86 or x64 runtime and remove unofficial copies

Before changing anything, note whether one application fails or many. That distinction is more useful than the filename alone.

Fix 1: Install or repair the correct Visual C++ Redistributable

For most users, this is the safest direct repair.

Microsoft provides current Visual C++ v14 Redistributables through its latest supported Visual C++ downloads page. The official packages include:

• vc_redist.x86.exe for 32-bit applications
• vc_redist.x64.exe for 64-bit applications
• vc_redist.arm64.exe for compatible ARM64 applications

A 32-bit application needs the x86 runtime even when Windows itself is 64-bit. A 64-bit application needs x64. Many 64-bit PCs should have both because they run both 32-bit and 64-bit programs.

How to identify the package

Use the failing program’s installation location as a clue:

• C:\Program Files (x86)\... usually indicates a 32-bit program.
• C:\Program Files\... usually indicates a 64-bit program.
• A launcher may use a different folder from the game it starts.
• An installer may be 32-bit even when it installs a 64-bit application.

The folder is not an absolute guarantee. If the program’s own installer or support page identifies its architecture, follow that information.

Repair the package

1. Open Start.
2. Type Installed apps.
3. Open Installed apps.
4. Search for Microsoft Visual C++.
5. Find the relevant Microsoft Visual C++ Redistributable entry.
6. Select the three-dot menu beside it.
7. Choose Modify.
8. Select Repair.
9. Allow the repair to finish.
10. Restart Windows.
11. Start the affected application again.

On older Windows versions:

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Find the Microsoft Visual C++ Redistributable entry.
5. Select it.
6. Choose Change.
7. Select Repair.

If you are unsure whether the application is 32-bit or 64-bit, installing both official x86 and x64 packages is reasonable on 64-bit Windows. This is not a substitute for checking the application if the error continues.

What success looks like

The application starts normally, the missing-file message disappears, and no new Bad Image or entry-point message appears.

If repair fails

Download the matching package again from Microsoft, run it, and choose Repair or Install. If the latest v14 package refuses to install on Windows 7 or another unsupported legacy system, do not keep forcing it. Follow the Windows 7, 8, or 8.1 instructions below instead.

Do not uninstall every older Visual C++ package. Different applications can depend on different runtime generations, and several versions can correctly coexist.

Fix 2: Repair Windows 10 or Windows 11 through Windows Update

Windows 10 and Windows 11 normally receive the UCRT as part of Windows servicing. If the problem affects multiple applications, or appeared after an interrupted update, repair Windows before reinstalling every program.

Install pending updates

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install every available update.
6. Restart the computer, even if Windows does not insist.
7. Return to Windows Update.
8. Check again until no additional updates are offered.

Microsoft’s general instructions are available under Install Windows updates.

After restarting, test the application. If it still fails, continue with DISM and SFC.

Fix 3: Run DISM and System File Checker

DISM repairs the Windows component store. SFC then checks protected system files against that repaired store. Running SFC first can leave it without a healthy source from which to repair files.

Run DISM

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes if User Account Control asks for permission.
6. Enter this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Press Enter.
2. Wait for the operation to complete.

The progress percentage may pause for a while. Do not close the window simply because the number appears unchanged.

Run SFC

When DISM finishes, enter:

sfc /scannow

Press Enter and wait until verification reaches 100 percent.

Restart Windows after both commands finish, then test the affected program.

How to interpret the result

• “Windows Resource Protection did not find any integrity violations” means SFC found no protected-file problem.
• “Windows Resource Protection found corrupt files and successfully repaired them” means Windows repaired files. Restart and test again.
• “Windows Resource Protection found corrupt files but was unable to fix some of them” means the problem needs further servicing investigation.
• If DISM reports that the source files could not be found, install pending updates and retry. Continued failure can indicate a damaged component store, servicing issue, disk problem, or an installation that needs a more advanced repair.

Microsoft’s DISM repair guidance and System File Checker documentation explain these tools.

If repeatedly hunting through Windows components and interpreting SFC or DISM results is becoming impractical, Outbyte PC Repair can scan for the reported problems and show what it identifies; the repair itself is performed by the full version, and it is not required for this fix.

If DISM and SFC complete successfully but only one program still fails, stop treating the issue as a Windows-wide problem and repair the application instead.

Fix 4: Install the Universal CRT on Windows 7, Windows 8, or Windows 8.1

Older Windows releases do not receive the UCRT in exactly the same way as Windows 10 and Windows 11. A program built with a newer Visual C++ toolchain can therefore fail immediately after installation or after an application update.

Microsoft’s official package is the Update for Universal C Runtime in Windows, identified as KB2999226. It is available through Windows Update and Microsoft’s Universal C Runtime Download Center page.

Prepare the operating system

1. Open Control Panel.
2. Select System and Security.
3. Select Windows Update.
4. Select Check for updates.
5. Install all important updates.
6. Restart the computer.
7. Check for updates again.
8. Repeat until Windows Update offers no further important updates.

Windows 7 must have Service Pack 1. Windows 8.1 requires its April 2014 update prerequisite before KB2999226 can apply.

Install the matching KB2999226 package

The Microsoft download package contains operating-system-specific MSU files, including:

• Windows6.1-KB2999226-x86.msu
• Windows6.1-KB2999226-x64.msu
• Windows8-RT-KB2999226-x86.msu
• Windows8-RT-KB2999226-x64.msu
• Windows8.1-KB2999226-x86.msu
• Windows8.1-KB2999226-x64.msu

Choose the package matching both the Windows release and the system architecture. Do not select an x64 package merely because the computer has an x64 processor if the application itself is 32-bit. The operating-system package and application runtime architecture are related but not identical decisions.

1. Download the appropriate MSU from Microsoft.
2. Open the downloaded file.
3. Confirm the Windows Update Standalone Installer prompt.
4. Allow the installation to finish.
5. Restart Windows.
6. Start the affected program.

If KB2999226 says it does not apply

That usually points to one of these conditions:

• The wrong Windows release was selected.
• The wrong architecture was selected.
• A required service pack or prerequisite is missing.
• The update is already installed.
• Windows servicing is damaged.
• The installation contains a later replacement update.

Install all available Windows updates first, confirm the exact Windows edition and architecture, and then retry. If Windows reports that the update is already installed, repair or install the compatible Visual C++ package instead.

Microsoft also provides a Visual C++ 2015 Update 3 Redistributable, which can repair the C runtime on compatible older systems. Use the x86 or x64 package that matches the failing program.

Fix 5: Repair the affected application or game

If every other program works, the application is the strongest suspect. It may have:

• An incomplete installation
• A damaged local runtime
• An incompatible update
• A missing file after antivirus quarantine
• A launcher that failed while updating
• A private copy of the UCRT in its own folder

Use Windows’ application repair option

For a modern Windows application:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Installed apps.
5. Find the affected application.
6. Select its three-dot menu.
7. Select Advanced options, if available.
8. Select Repair.
9. Test the application.

Use Reset only if Repair does not help and you understand that it may remove local settings or cached data.

For a traditional desktop application:

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Select the application.
5. Choose Change, Repair, or Modify, depending on what the installer provides.
6. Complete the repair.
7. Restart Windows if requested.
8. Test the application.

Verify game files

If the error belongs to a game, use the launcher’s built-in verification function before deleting the entire game.

The usual process is:

1. Open the game launcher.
2. Open the game library.
3. Find the affected game.
4. Open its menu.
5. Choose Verify, Repair, or Scan and repair.
6. Allow the launcher to replace damaged files.
7. Restart the launcher.
8. Start the game again.

If verification does not help, uninstall and reinstall the game from its normal official source. A game reinstall may repair an application-local UCRT copy, but it will not necessarily repair a missing Windows UCRT component. If several unrelated programs fail, return to Windows Update, DISM, and SFC.

Check the application folder

If api-ms-win-crt-private-l1-1-0.dll appears in the same folder as the failing executable, it may be an application-local runtime. That file is not automatically malware. Some software publishers deploy runtime files beside their executable.

However, replacing it with a downloaded copy is unsafe. Repair or reinstall the application so its own installer can restore the complete, matching runtime set.

Fix 6: Check Windows Security quarantine

Antivirus software can remove a legitimate runtime file, especially after an interrupted installation or an application update. It can also correctly remove a malicious file that merely uses a Microsoft-looking name.

1. Open Start.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Select Protection history.
6. Look for an event created when the error began.
7. Expand the event and note the original file path.
8. Check whether the affected application or DLL was quarantined.

Microsoft documents this screen in its Protection History guidance.

Do not restore a file solely because its name is api-ms-win-crt-private-l1-1-0.dll. Restore it only when the original location, parent application, installation source, and digital signature are trustworthy.

To inspect a file that still exists:

1. Right-click the file.
2. Select Properties.
3. Open the Digital Signatures tab if it is present.
4. Select the signature.
5. Choose Details.
6. Confirm that Windows reports the signature as valid.

If the file came from a game or application folder and its signature is absent or invalid, reinstall the application instead of restoring the file manually. If Windows Security repeatedly removes the file, run a full scan and investigate the parent program.

Fix 7: Check 32-bit and 64-bit locations

Architecture mismatches cause both missing-file messages and entry-point failures.

On 64-bit Windows:

• C:\Windows\System32 normally contains native 64-bit system files.
• C:\Windows\SysWOW64 normally contains 32-bit system files.

The naming is confusing, but this is normal Windows behavior. A 32-bit process cannot load a 64-bit DLL, and a 64-bit process cannot load a 32-bit DLL. Microsoft describes the behavior in its file system redirector documentation.

Do not manually copy a DLL between these folders. If a 32-bit application fails, repair or install the x86 Visual C++ Redistributable. If a 64-bit application fails, repair or install x64. If both types of applications fail, install or repair both official packages.

An entry-point error is especially important. It means Windows found a file with the expected name but could not find the required function inside it. Common reasons include:

• The file is from the wrong runtime generation.
• The application folder contains an old local copy.
• ucrtbase.dll and the API-set forwarders are from different builds.
• The application update expects a function that the installed runtime does not provide.
• The wrong architecture was loaded.

Replacing only the named DLL can make this mismatch worse.

Fix 8: Do not use Windows Features as a random DLL repair

Windows Features are not a general-purpose way to install the UCRT.

You can inspect them as follows:

1. Press Windows key + R.
2. Type:

optionalfeatures

1. Press Enter.
2. Review the available features.

Do not enable .NET Framework, Legacy Components, DirectPlay, or another feature merely because a runtime error appears. Enable a feature only when the affected application specifically requires it or its official documentation identifies it as a prerequisite.

This error is normally addressed through the Visual C++ Redistributable, Windows servicing, or application repair. Toggling unrelated features can add time without repairing the dependency.

Fix 9: Update a driver only when the failing program belongs to a hardware utility

The filename identifies a runtime dependency, not a device driver. Updating a graphics, audio, chipset, printer, or motherboard driver will not normally repair the UCRT.

A driver repair is relevant when the failing executable belongs to a manufacturer’s control panel, hardware utility, driver installer, or device-management package.

Check the failing executable

1. Right-click the application shortcut.
2. Select Properties.
3. Open the Shortcut tab.
4. Read the Target path.
5. Identify the hardware vendor or utility name.
6. Use the vendor’s official support package for that exact product and Windows version.

Check Device Manager

1. Open Start.
2. Type Device Manager.
3. Open Device Manager.
4. Expand the relevant category, such as Display adapters, Sound, video and game controllers, or Network adapters.
5. Right-click the affected device.
6. Select Properties.
7. Open the Driver tab.
8. Note the provider, date, and version.
9. Use Update Driver only when an appropriate driver is available, or install the correct package from the hardware manufacturer.
10. Restart Windows.

Do not remove a working device driver simply because a separate program reports this DLL.

When checking many hardware components by hand, identifying which driver is stale can take longer than the actual installation. Outbyte Driver Updater can scan and show the driver problems it finds; the driver installation is performed by the full version, and updating a driver remains irrelevant if the failing file belongs to a specific game or application.

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

Why regsvr32 does not fix this error

Do not run:

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

regsvr32 is intended for self-registering COM, OLE, and ActiveX DLLs that expose a registration function such as DllRegisterServer. Runtime libraries and API-set forwarders are not normally registered in the Windows Registry.

The command may produce an error stating that the module was loaded but the entry point DllRegisterServer could not be found. That result does not mean the DLL needs a different regsvr32 command. It means the tool does not apply.

Microsoft explains this behavior in its Regsvr32 troubleshooting documentation.

Why downloading one DLL is a bad repair

Random DLL download pages are risky because the file can be:

• Malware
• The wrong architecture
• An obsolete runtime build
• Modified or unsigned
• Incomplete without matching UCRT files
• Intended for a different Windows release
• A copy that creates a new Bad Image error

Even a genuine DLL may not solve the problem. The UCRT is a coordinated group of files involving ucrtbase.dll and related API-set forwarders. Windows 10 and Windows 11 may resolve the API-set contract through the loader rather than through a same-named file.

The safe sources are:

• Windows Update
• Microsoft’s latest supported Visual C++ Redistributable downloads
• Microsoft’s Universal C Runtime package for compatible older Windows releases
• The affected application’s own official installer or repair function

The only reasonable manual deployment scenario is for a software publisher deploying a complete, signed, architecture-matched UCRT set beside its own executable according to Microsoft’s UCRT deployment rules. That is not the same as downloading one file and placing it in System32.

Fix 10: Investigate malware, disk errors, or recurring corruption

If the file disappears repeatedly, many programs fail, or Windows repairs do not remain fixed, investigate the wider system.

Run a full Microsoft Defender scan:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Scan options.
4. Choose Full scan.
5. Select Scan now.

For a persistent or serious concern, use Microsoft Defender Offline from the same Scan options screen. Microsoft provides Defender malware troubleshooting guidance.

Also consider:

• A failing storage drive
• An interrupted Windows update
• A broken application updater
• A damaged user profile
• Repeated antivirus quarantine
• Malware changing or deleting files
• Corruption in the Windows servicing store

If the error began immediately after a known system change and a suitable restore point exists:

1. Open Start.
2. Type Create a restore point.
3. Open the result.
4. Select System Restore.
5. Choose a restore point from before the failure.
6. Review the affected programs.
7. Complete the restore.

Microsoft describes the process in its System Restore documentation.

System Restore is not a replacement for runtime installation. It is useful when the timing clearly points to a recent update, driver installation, or software change.

What to do when the error returns

If the normal repair works temporarily and the message returns, record what happens immediately before it returns.

Check these possibilities:

• The application updater reinstalls an incompatible local DLL.
• Antivirus quarantines the same file again.
• A Windows update fails repeatedly.
• The disk has file-system or hardware errors.
• The program is installed inside a damaged user profile.
• Malware is restoring or deleting files.
• A launcher is using a different executable from the one you repaired.
• The application requires an older runtime than the one currently installed.

Create a new local Windows user account and test the same application there. If it works only in the new profile, the problem may be profile-specific rather than a system-wide UCRT failure.

If several applications fail after every repair, collect the Windows version, update history, SFC result, DISM result, and relevant Windows servicing logs before making more changes.

FAQ

Is api-ms-win-crt-private-l1-1-0.dll a Windows file?

It belongs to Microsoft’s Universal C Runtime, which is integrated into Windows 10 and Windows 11 and delivered to older Windows versions through updates or compatible redistributables. The exact API-set name may be a virtual loader contract and may not exist as a physical file on every modern Windows installation.

Is this part of Visual C++?

Yes. It is associated with the Universal C Runtime used by Microsoft Visual C++ applications. Repairing the matching Visual C++ Redistributable is often the fastest fix.

Do I need x86 or x64?

Use x86 for a 32-bit application and x64 for a 64-bit application. A 64-bit Windows computer can need both packages because it commonly runs both types of programs.

Should I install the latest Visual C++ package on Windows 7?

Not automatically. Current v14 redistributables target supported modern Windows versions. Windows 7, Windows 8, and Windows 8.1 may need KB2999226 and the compatible Visual C++ 2015 package instead.

Does Windows 10 or Windows 11 need KB2999226?

Normally, Windows 10 and Windows 11 receive the UCRT through Windows servicing. Start with Windows Update, then use DISM and SFC if multiple programs fail. KB2999226 is mainly relevant to older Windows releases.

Why does the file exist but Windows still report an entry-point error?

The file may be the wrong version, wrong architecture, or part of a mismatched group of UCRT files. An application-local copy can also override the correct Windows runtime. Repair the complete runtime or the owning application rather than replacing one file.

Can I copy the file into System32 or SysWOW64?

Do not do this as a normal repair. The wrong architecture or build can cause a Bad Image error, and modern Windows may not need a physical file with this exact name.

Should I run regsvr32?

No. This is a runtime/API-set dependency, not a normal COM registration DLL. regsvr32 does not repair it.

Is the file related to DirectX, .NET, or a driver?

Not normally. It belongs to the Visual C++/Universal C Runtime family. Only investigate drivers when the failing executable is specifically part of a hardware vendor’s utility or driver package.

What if only one game fails?

Verify the game files through its launcher, repair the launcher or game, and reinstall it if necessary. Also repair the Visual C++ package required by the game.

What information should I provide when asking for help?

Include:

• The exact error text
• The application and version
• The executable path
• The Windows version and build from winver
• Whether Windows is 32-bit or 64-bit
• Whether the application is 32-bit or 64-bit
• Whether one program or many programs fail
• Whether the issue began after an update, reinstall, antivirus action, disk cleanup, or Windows repair
• The results of DISM and sfc /scannow

That information usually distinguishes a missing Windows runtime from a damaged application-local copy or an architecture mismatch.

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.