api-ms-win-crt-utility-l1-1-0.dll Missing: Safe Windows Fixes

api-ms-win-crt-utility-l1-1-0.dll missing on Windows 11 or Windows 10 usually means that the Universal C Runtime is missing, damaged, or unavailable to the application. The safest fix is to update Windows, repair the affected program, and install the correct Microsoft Visual C++ Redistributable package if the application requires it.

Do not begin by downloading this DLL from a random file website, copying it into System32, or running regsvr32. Those actions can introduce an incorrect or malicious file and often leave the real runtime problem unresolved.

As an Amazon Associate I earn from qualifying purchases.

What is api-ms-win-crt-utility-l1-1-0.dll?

api-ms-win-crt-utility-l1-1-0.dll is a Microsoft Universal C Runtime API-set component. It acts as a forwarder or stub that allows applications to reach utility functions provided by the UCRT, including functions such as _abs64, _byteswap_ulong, bsearch, and _lfind. Microsoft documents those APIs under this API-set name in its Win32 extension API list.

An API-set filename is not always an ordinary standalone library in the way many users expect. It is an interface contract used by the Windows loader, and the loader resolves it to the implementation supplied by the operating system or an application deployment. Microsoft explains this mechanism in its documentation for API-set loader operation.

The UCRT is part of Windows 10 and later. Older supported Windows versions receive it through Windows Update or the Universal CRT package identified by KB2999226. Applications can also deploy a private copy beside their executable, although Microsoft does not recommend general local deployment because of performance and security considerations. See Microsoft’s Universal CRT deployment guidance.

File identification

Property	What can safely be said
File name	api-ms-win-crt-utility-l1-1-0.dll
Function	Microsoft Universal C Runtime API-set forwarder or stub
Category	vcredist or Visual C++ runtime component
Ships with	The Windows UCRT or the application installer that deployed it
Internal description	Not listed in the supplied file metadata
Publisher field	Not listed in the supplied file metadata
Version and size	Not universal; they vary with Windows servicing and architecture
Typical role	Dependency used by applications built with Microsoft Visual C++
DirectX component	No
.NET component	No
Driver component	No

The filename alone does not prove that the file is missing. Windows may display a missing-module error when the named file exists but another dependency, such as ucrtbase.dll, is missing, damaged, or the wrong architecture.

Choose the right fix

Situation	Best next action
Several unrelated applications fail	Run Windows Update, DISM, and SFC
One application or game fails	Repair or reinstall that application
Windows 7, 8, or 8.1 is affected	Install the matching KB2999226 Universal CRT package
A 32-bit application fails on 64-bit Windows	Install the x86 runtime
A 64-bit application fails	Install the x64 runtime
A Steam game fails	Verify the game’s installed files
Security software removed a file	Check Windows Security Protection History
The message says “not designed to run”	Check architecture and file integrity
The file exists but the error continues	Repair the runtime and investigate dependencies or an app-local copy

Fix 1: Install Windows updates

On Windows 11:

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 immediately require it.
7. Try opening the affected application again.

On Windows 10:

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

This is the preferred first step because Windows 10 and later provide the UCRT as an operating-system component. If Windows Update reports that the system is fully updated but the error remains, continue with the application-specific and runtime steps below.

If Windows Update itself fails, restart the PC and try again before downloading individual system files. A failed update may leave a partially serviced component store, which is better repaired through DISM than by copying a DLL manually.

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

The application architecture must match the package architecture. A 32-bit application needs the x86 package, even when it runs on 64-bit Windows. A 64-bit application needs the x64 package. Many Windows PCs legitimately need both.

Microsoft’s current v14 packages are available from its latest supported Visual C++ Redistributable page:

• Visual C++ Redistributable x86 for 32-bit applications
• Visual C++ Redistributable x64 for 64-bit applications
• Visual C++ Redistributable ARM64 for ARM64 applications

The current v14 runtime is shared by applications built with supported Visual Studio generations including Visual Studio 2017, 2019, 2022, and 2026. Older Visual C++ generations remain side by side, so do not uninstall every existing Visual C++ package merely because one application is failing.

Install the package

1. Identify whether the failing program is 32-bit, 64-bit, or ARM64.
2. Download the matching package from Microsoft.
3. Close the affected application and its launcher.
4. Run the downloaded installer.
5. If the installer offers Repair, select it.
6. If it offers Install, complete the installation.
7. Restart Windows.
8. Start the application again.

If you do not know the application architecture, check the vendor’s system requirements or installer documentation. For a game, the launcher may identify whether it installs an x86 or x64 executable. Installing both x86 and x64 packages is normal on 64-bit Windows when the PC runs applications of both types.

The Visual C++ package may resolve the problem when the application needs the broader MSVC runtime. However, the filename itself belongs to the UCRT layer, so Windows Update or the application’s own prerequisite installer may still be required.

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

Windows 7, Windows 8, and Windows 8.1 do not receive the UCRT in exactly the same way as Windows 10 and later. Microsoft distributes the Universal CRT for these systems through packages associated with KB2999226.

Use Microsoft’s official Windows 10 Universal C Runtime download page. Select the package matching the installed Windows version and architecture. Package names include examples such as:

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

For Windows 8.1, Microsoft lists the applicable servicing-stack prerequisite, including KB2919355, for the relevant packages.

Install KB2999226

1. Press Windows key + R.
2. Type winver.
3. Press Enter and note the Windows version.
4. Open Microsoft’s Universal CRT download page.
5. Download the package for that Windows version and architecture.
6. Close running applications.
7. Double-click the .msu file.
8. Follow the Windows Update Standalone Installer prompts.
9. Restart the computer.
10. Install the matching Visual C++ Redistributable if the application also reports files such as vcruntime140.dll or msvcp140.dll.
11. Start the affected program.

If the .msu package refuses to install, do not rename it or extract individual DLLs. Confirm the Windows version, install the required servicing prerequisite, run Windows Update, and try the package again.

The file version and size are not fixed across all Windows installations. Microsoft’s support documentation lists historical examples, while later Windows servicing updates use different builds. Do not reject a legitimate file simply because its version or size differs from an example found in older documentation.

Fix 4: Repair or reinstall the affected application

If only one program or game displays the error, the application installation is a strong suspect. The installer may have been interrupted, an update may have failed, or security software may have removed an application-local runtime file.

For a supported 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.
8. Select Repair.
9. Restart the application and test it.

If Repair does not help, return to the same screen and use Reset only if you understand that application data may be affected. Traditional desktop applications may instead provide their own repair option:

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Right-click the affected program.
5. Choose Repair or Change.
6. Complete the vendor’s repair wizard.
7. Restart Windows and test the program.

If repair is unavailable, uninstall the application and reinstall it from its original vendor or launcher. Allow the installer to run its prerequisite steps. Do not copy a replacement DLL into the application directory unless the vendor explicitly provides a complete, matching local runtime deployment.

Verify a Steam game

For a Steam game:

1. Restart Windows and Steam.
2. Open Library.
3. Right-click the affected game, or select its gear icon.
4. Select Properties.
5. Select Installed Files.
6. Select Verify integrity of game files.
7. Wait for the process to finish.
8. Start the game again.

Verification can replace missing or corrupted game files. If the same error returns immediately, install or repair the Microsoft runtime separately because the game may depend on a system component rather than a single game file.

Fix 5: Check Windows Security Protection History

Antivirus software can quarantine an application-local runtime file or interrupt an installer. This is possible, but the filename alone does not establish that a security detection was a false positive.

To inspect Windows Security:

1. Open Start.
2. Select Settings.
3. On Windows 11, select Privacy & security. On Windows 10, select Update & Security, then Windows Security.
4. Select Windows Security.
5. Select Virus & threat protection.
6. Select Protection history.
7. Review recent events for the affected application, installer, or DLL.
8. Open the event details before taking action.

Restore a quarantined file only when all of the following are true:

• The application came from a legitimate vendor or official launcher.
• The file belongs to that application.
• The installer and file can be verified as genuine.
• A current security scan does not identify an active threat.

If the file was removed from a legitimate application, repairing or reinstalling the application is safer than restoring an isolated file. Do not create a broad exclusion for C:\Windows, System32, or the entire application directory.

Fix 6: Repair Windows system files with DISM and SFC

Use this path when multiple unrelated programs fail, Windows has recently experienced an interrupted update, or Windows itself reports damaged system files.

Open an elevated Command Prompt:

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

Run DISM first:

DISM.exe /Online /Cleanup-image /Restorehealth

Wait for DISM to finish. Then run System File Checker:

sfc /scannow

Restart Windows after both commands complete and test the application again. Microsoft recommends running DISM before SFC because DISM provides the repair source used by SFC. See Microsoft’s System File Checker repair guidance.

If Windows Update is unavailable and you have a valid repair source matching the installed Windows version, Microsoft documents this form:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess

Replace C:\RepairSource\Windows with the actual matching repair source. Do not use an arbitrary folder containing unrelated Windows files.

If repeating DISM and SFC leaves you hunting through component versions without showing what changed, Outbyte PC Repair can provide a free scan showing what it finds; repairs are performed by the full version, so it remains optional, and reinstalling the affected program is still the definitive fix when its local files are damaged.

Fix 7: Confirm the application architecture and runtime location

On 64-bit Windows, the standard system directories have easily misunderstood names:

• %windir%\System32 normally contains 64-bit system binaries.
• %windir%\SysWOW64 normally contains 32-bit system binaries.

Microsoft documents this behavior in its File System Redirector documentation.

A 32-bit application requires the x86 runtime even when Windows itself is 64-bit. A 64-bit application requires the x64 runtime. On ARM64 Windows, the correct package depends on whether the application is ARM64, x64, or x86.

To search the Windows directory for the filename, open Command Prompt and run:

where /r "%windir%" api-ms-win-crt-utility-l1-1-0.dll

To inspect the common system locations in PowerShell, run:

Get-Item "$env:windir\System32\api-ms-win-crt-utility-l1-1-0.dll",
         "$env:windir\SysWOW64\api-ms-win-crt-utility-l1-1-0.dll" `
         -ErrorAction SilentlyContinue |
  Select-Object FullName, Length,
    @{Name="Version";Expression={$_.VersionInfo.FileVersion}}

A missing result does not tell you whether the operating system or the application installer was supposed to provide the file. A result also does not prove that the file is valid or loadable.

Do not copy an x86 file into System32 simply because the error appears on 64-bit Windows. Install the matching runtime and allow Windows or the official application installer to place the files correctly.

Fix 8: Investigate an app-local or damaged copy

Applications can deploy UCRT files beside their executable. This is especially relevant when one application fails while other applications work.

Check the application’s installation directory:

1. Right-click the application shortcut.
2. Select Properties.
3. Select Open File Location.
4. Look for the executable and nearby runtime files.
5. Do not open, register, or replace suspicious DLLs manually.
6. Use the application’s repair, modify, or reinstall function instead.

A copy in %AppData%, %Temp%, or an unrelated random folder deserves additional scrutiny. It may be part of a legitimate updater, but it may also be an incomplete deployment or an unrelated file. Scan it and identify which application created it before taking action.

The UCRT normally consists of ucrtbase.dll together with API-set forwarders. Repairing only api-ms-win-crt-utility-l1-1-0.dll may not repair a missing or damaged dependency.

Fix 9: Use System Restore after a known recent change

If the error began immediately after a Windows update, application update, driver installation, cleanup operation, or other system change, System Restore may help when a suitable restore point exists.

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

rstrui.exe

1. Press Enter.
2. Select a restore point created before the problem began.
3. Review the affected programs and drivers.
4. Follow the wizard.
5. Allow Windows to restart.
6. Test the application.

Microsoft states that System Restore rolls back system files, settings, drivers, and installed programs without normally removing personal files. It is not a replacement for repairing the application or installing the correct runtime, so use it when the timing points to a specific recent change. Microsoft provides additional System Restore guidance.

Fix 10: Check drivers only when a hardware utility is involved

api-ms-win-crt-utility-l1-1-0.dll is not itself a driver component. Driver troubleshooting is low priority unless the message appears while launching a hardware vendor’s utility, control panel, installer, or updater that bundles Microsoft runtime files.

If that describes the failure:

1. Right-click Start.
2. Select Device Manager.
3. Expand the category related to the affected hardware.
4. Right-click the device.
5. Select Update driver.
6. Select Search automatically for drivers.
7. Restart Windows.
8. If the issue remains, download the complete driver or utility package from the hardware manufacturer and reinstall it.

Do not download the named DLL as a substitute for a driver package.

If manually checking every device means guessing which of many drivers is stale, Outbyte Driver Updater can scan for outdated drivers and show what it identifies; driver installation is handled by the full version, so it is optional and not a replacement for repairing the application that owns the missing runtime.

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

Windows Features will not repair this DLL

Windows includes a Turn Windows features on or off panel, but there is no general “UCRT” checkbox that repairs this API-set component.

To open it:

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

optionalfeatures

1. Press Enter.

Do not enable or disable unrelated features in an attempt to repair this error. DirectX, .NET Framework, and optional Windows features are not indicated by this filename. Use Windows Update, the Visual C++ Redistributable, and the application’s repair mechanism instead.

Why regsvr32 is not the answer

regsvr32 is intended for self-registering COM or OLE DLLs that export functions such as DllRegisterServer or DllUnregisterServer. It is not a general-purpose DLL repair command.

This UCRT API-set forwarder is not repaired by registering it. Running a command such as the following is irrelevant:

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

It may produce an entry-point or registration error and will not install the missing UCRT. Microsoft explains the proper use and troubleshooting of Regsvr32.

What not to do

Do not download the DLL from a random website

An isolated DLL download can be:

• Malware or a modified binary.
• The wrong architecture.
• From the wrong Windows build.
• Incompatible with the application.
• Missing related UCRT files.
• A replacement that gets quarantined again.

Use Windows Update, Microsoft’s official Redistributable packages, the official KB2999226 package for older Windows versions, or the application’s own installer.

Do not copy files blindly into System32 or SysWOW64

The correct directory depends on the application and operating system architecture. Copying an x86 file into the 64-bit system directory, or copying an unknown x64 file into the 32-bit runtime path, can make troubleshooting harder.

Do not remove every Visual C++ Redistributable

Multiple Visual C++ runtime generations can coexist. Removing all of them may break other applications and does not repair the UCRT. Repair the required package or install the correct architecture instead.

Do not assume the named file is the only missing file

The loader may report api-ms-win-crt-utility-l1-1-0.dll while a dependency such as ucrtbase.dll is missing or invalid. Repair the complete runtime rather than replacing one file at a time.

Do not create a broad antivirus exclusion

Restore a quarantined file only after verifying the application and file. Repairing or reinstalling from the official source is usually safer than excluding the Windows directory from scanning.

If the file exists but the application still fails

Work through this sequence:

1. Confirm whether the application is x86, x64, or ARM64.
2. Install or repair the matching Visual C++ Redistributable.
3. Update Windows and restart.
4. Repair or reinstall the application.
5. Check whether the application directory contains a damaged private runtime copy.
6. Run DISM and then SFC.
7. Check Windows Security Protection History.
8. Review the Windows Event Viewer for the application error.

To open Event Viewer:

1. Press Windows key + X.
2. Select Event Viewer.
3. Expand Windows Logs.
4. Select Application.
5. Look for an error recorded at the time the application failed.
6. Note the application name, faulting module, and architecture-related details.
7. Use that information when contacting the application vendor.

A “specified module could not be found” message may refer to a dependency rather than the displayed filename. A “not designed to run on Windows” message usually points to corruption, an architecture mismatch, an invalid binary, or an incompatible version, but the message alone does not identify which one.

FAQ

Is this a real Microsoft file?

Yes. It is a Microsoft Universal C Runtime API-set component. The filename is an interface contract used by the Windows loader, rather than a product-specific DLL.

Do I need DirectX?

No. This filename indicates a UCRT dependency, not a DirectX dependency. Repair DirectX only when a separate, clearly identified DirectX error requires it.

Do I need .NET Framework?

Not because of this filename alone. .NET and the UCRT are separate runtime layers.

Should I install both x86 and x64 Visual C++ packages?

On 64-bit Windows, installing both is normal when the PC runs both 32-bit and 64-bit applications. The x86 package is required for 32-bit programs, while the x64 package is required for 64-bit programs.

Where should the file be located?

That depends on the Windows architecture, application architecture, and deployment method. On 64-bit Windows, System32 normally contains 64-bit system binaries and SysWOW64 normally contains 32-bit system binaries. An application may also contain a private copy.

Can I register this DLL with regsvr32?

No. It is not a self-registering COM/OLE component. regsvr32 is not a repair method for this UCRT API-set file.

Why did reinstalling the program not help?

The installer may also need the UCRT before it can run, its prerequisite step may have been blocked, antivirus software may have removed the file again, or the wrong runtime architecture may have been installed. Update Windows, install the matching Microsoft runtime, check Protection History, and use the application’s file verification or repair function.

Is KB2999226 needed on Windows 10 or Windows 11?

Windows 10 and later include the UCRT as an operating-system component. KB2999226 is primarily relevant to supported older Windows versions such as Windows 7, Windows 8, and Windows 8.1.

Is the newest DLL version always correct?

No. UCRT versions and sizes vary with Windows builds and servicing updates. A newer-looking file from an unknown source is not automatically compatible or safe.

What if only one Windows user account has the problem?

Test the application from another local Windows account. If it works there, investigate per-user application data, launcher caches, user-level PATH entries, permissions, or profile corruption. This test does not prove that the system UCRT is defective.

What is the final escalation path?

If Windows Update, the matching runtime, application repair, antivirus review, DISM, and SFC do not resolve the problem, perform a clean reinstall from the official application source and contact the application vendor with the exact error, Windows version, application architecture, and relevant Event Viewer details.

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.