api-ms-win-crt-math-l1-1-0.dll Not Found: Runtime Repair Guide

api-ms-win-crt-math-l1-1-0.dll errors usually mean that the Microsoft Universal C Runtime is missing, damaged, or the wrong architecture for the program you are launching. Install or repair the official Visual C++ Redistributable that matches the application, then repair Windows components if the error remains.

What this file actually does

api-ms-win-crt-math-l1-1-0.dll is part of Microsoft’s Universal C Runtime, usually abbreviated as UCRT. It provides an API-set contract for mathematical C-runtime functions, including routines used for trigonometry, logarithms, floating-point calculations, and related operations. Microsoft lists this API set as introduced with Windows version 10.0.10240. See Microsoft’s UCRT API reference.

As an Amazon Associate I earn from qualifying purchases.

The important detail is that this name is not necessarily a normal standalone library containing all of those functions. Windows API-set names are virtual contracts that the loader maps to an implementation. The physical implementation is associated with ucrtbase.dll, while api-ms-win-crt-*.dll names act as API-set forwarders in applicable Windows deployments. Microsoft explains this design in its documentation for Windows API sets.

That is why manually downloading a file with this exact name is usually the wrong repair. The loader may be reporting one API contract while the real problem is a missing Universal C Runtime deployment, a damaged Windows component store, a missing companion file, or an architecture mismatch.

In a file inventory, the component may appear under the program that installed or bundled it. That does not make it a game-specific math library. The application depends on the Microsoft runtime, and the runtime may be supplied centrally by Windows, through the Visual C++ Redistributable, or through an application installer.

Microsoft’s current Universal CRT deployment documentation describes the UCRT as:

• A Windows component on Windows 10 and later
• A Windows component on Windows Server 2016 and later
• A Windows Update or package-installed component on older supported Windows versions
• A runtime that can also be deployed with an application in specific developer-controlled scenarios

The file name contains “math” because the program linked against the UCRT’s mathematical API contract. That does not mean the program is a calculator, benchmark, or scientific application. Games, launchers, Python-based tools, graphics utilities, installers, and driver-management software can all call ordinary C-runtime functions that eventually use the math portion of the runtime.

Causes and symptoms at a glance

What you see	Most likely cause	Best first action
“The program can’t start because api-ms-win-crt-math-l1-1-0.dll is missing from your computer”	Missing UCRT or Visual C++ runtime	Install the matching Microsoft Visual C++ Redistributable
“This application has failed to start because api-ms-win-crt-math-l1-1-0.dll was not found”	Runtime not installed, incomplete, or wrong architecture	Install x86 for a 32-bit app or x64 for a 64-bit app
“Error loading api-ms-win-crt-math-l1-1-0.dll”	Another dependency may be missing	Repair the runtime, then repair the application
“The specified module could not be found” while the named file exists	A dependent module, UCRT implementation, or architecture does not match	Check the program architecture and run DISM followed by SFC
“The code execution cannot proceed”	The loader could not resolve the runtime contract	Install or repair the correct redistributable
“The file is either not designed to run on Windows or it contains an error”	Generic loader failure, not proof that this one file is corrupt	Reinstall the official runtime and check Windows servicing
The error began after an application update	Interrupted or incomplete application installation	Use the launcher’s Verify or Repair feature
The error affects many unrelated programs	Windows UCRT or component-store problem	Install updates, then run DISM and SFC
Only one program fails	That program’s files or local dependencies may be damaged	Repair or reinstall that program
The problem began after antivirus activity	A runtime or application file may have been quarantined	Inspect Protection History, then reinstall from Microsoft or the application vendor

The exact dialog wording varies by Windows version and loader path. “Not designed to run on Windows” should be treated as a general loading failure rather than evidence that the named API-set file alone is defective.

Before changing anything, identify the application and Windows architecture

The redistributable must match the application, not merely the computer.

A 64-bit Windows installation can run both 64-bit and 32-bit programs. Therefore, a 64-bit PC often needs both the x64 and x86 Visual C++ packages.

Use these rules:

• 32-bit application: install the x86 redistributable.
• 64-bit application: install the x64 redistributable.
• ARM64 application on ARM64 Windows: install the ARM64 redistributable.
• 64-bit Windows running both types of software: installing both x86 and x64 is reasonable.

Check the Windows version

On Windows 10 or Windows 11:

1. Press Windows + R.
2. Type winver.
3. Press Enter.
4. Record the Windows version shown in the dialog.
5. Close the dialog.

For more detail:

1. Open Start.
2. Select Settings.
3. Open System.
4. Select About.
5. Check System type under device specifications.
6. Check the Windows edition and version under Windows specifications.

Check whether the application is 32-bit or 64-bit

The most reliable source is the application vendor’s system-requirements page or installer documentation. If that is not available, use one of these checks:

1. Start the program until the error appears.
2. Press Ctrl + Shift + Esc to open Task Manager.
3. Select Details.
4. Look for the program process.
5. On some Windows builds, right-click the column headings and enable Platform.
6. A process marked 32-bit needs x86 runtime files.
7. An unmarked native process on 64-bit Windows is generally 64-bit, but verify with the vendor when possible.

For a program that never remains open long enough to appear in Task Manager:

1. Open File Explorer.
2. Browse to the program’s installation folder.
3. Right-click the main .exe file.
4. Select Properties.
5. Open the Details or Compatibility tabs if the vendor has provided architecture information.
6. Check the program’s documentation or installer options if the architecture is still unclear.

Do not decide based only on the presence of a 64-bit Windows installation. System32 contains native 64-bit system files on 64-bit Windows, while SysWOW64 contains 32-bit system files. The names are historically confusing because of Windows-on-Windows redirection. Microsoft documents this behavior in File System Redirector.

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

This is the best first fix on Windows 10 and Windows 11.

Microsoft’s current supported v14 runtime packages are available from its Latest Supported Visual C++ Redistributable Downloads page. The direct Microsoft packages are:

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

Install the correct package

1. Close the affected program and its launcher.
2. Open the Microsoft Visual C++ Redistributable page linked above.
3. Download the package matching the application architecture.
4. Right-click the downloaded installer.
5. Select Run as administrator.
6. Accept the license terms.
7. Select Install.
8. If the installer reports that the runtime is already installed, select Repair when offered.
9. Restart Windows.
10. Launch the affected program again.

If you use both 32-bit and 64-bit software on 64-bit Windows, repeat the process with both x86 and x64 packages. Installing only x64 does not supply the 32-bit runtime required by a 32-bit game, launcher, Python distribution, or utility.

What success looks like

The original program should launch without the API-set error. You may not see a new DLL appear in the application folder because the UCRT is commonly supplied as a Windows component or through the shared runtime deployment.

If the same dialog appears after installing the correct package:

1. Confirm that you installed the package for the application, not just the operating system.
2. Run the installer again as administrator.
3. Use Repair if the package is listed as installed.
4. Restart Windows.
5. Continue with the application repair and Windows component checks below.

Do not remove older Visual C++ packages

Different Visual C++ runtime generations can coexist. Visual Studio 2015 and later use the compatible v14 runtime family, but older applications may depend on separate Visual C++ 2013, 2012, 2010, or earlier packages.

Do not uninstall older entries merely because a newer redistributable is present. Removing them can break unrelated games and tools.

To inspect installed packages:

1. Open Start.
2. Search for Installed apps.
3. Open it.
4. Search for Microsoft Visual C++.
5. Review the x86 and x64 entries.
6. Leave older versions installed unless the application vendor or Microsoft’s troubleshooting procedure specifically requires their removal.

Fix 2: Install Windows updates and restart

On current Windows versions, the UCRT is serviced as part of Windows. A pending, failed, or interrupted update can leave the runtime incomplete even when the operating system appears to be working normally.

1. Open Start.
2. Select Settings.
3. On Windows 11, select Windows Update.
4. On Windows 10, select Update & Security, then Windows Update.
5. Select Check for updates.
6. Install all available updates.
7. Restart Windows even if the update screen does not insist on a restart.
8. Check for updates again after the restart.
9. Launch the affected program.

If Windows Update reports an error, note the error code. Do not repeatedly reinstall random DLL files while Windows servicing is failing. The runtime repair cannot remain reliable while the component store is unable to install or validate system components.

Check whether Windows Update is disabled

1. Press Windows + R.
2. Type services.msc.
3. Press Enter.
4. Find Windows Update.
5. Check whether it is running or disabled.
6. Do not change organizational or managed-device policies without authorization.
7. If this is your personal PC and updates were disabled by a cleanup utility, restore normal Windows Update operation and restart.

A third-party “optimizer” or cleanup program can remove servicing components or interfere with the Visual C++ installer. Remove or disable only software you recognize, and do not delete system folders manually.

Fix 3: Repair the affected game or application

If only one program fails, its installation may be incomplete even when the shared runtime is correctly installed. This is common after an interrupted update, an antivirus quarantine, a launcher crash, or a partial uninstall.

Use a built-in Windows repair option

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Installed apps.
5. Find the affected program.
6. Select the three-dot menu beside it.
7. Select Advanced options if available.
8. Select Repair.
9. Launch the program again.

If Repair does not help, return to the same screen and use Reset only if you understand that it may remove the application’s local settings or cached data. Not every desktop application provides these options.

Use a game launcher’s repair feature

The wording depends on the launcher, but the process is usually similar:

1. Open the game launcher.
2. Open the library or installed-games list.
3. Select the affected game.
4. Open its settings or three-dot menu.
5. Choose Verify, Verify integrity, Scan and repair, or Repair.
6. Wait for the launcher to replace missing or damaged files.
7. Restart the launcher.
8. Test the game again.

Do not copy a DLL into the game folder before verifying the installation. If the game uses an application-local runtime, the launcher may need to restore the complete matching set rather than one isolated API-set name.

Reinstall when repair cannot restore the dependency

If the program still fails:

1. Back up saves, profiles, presets, and configuration files if the application stores them locally.
2. Uninstall the program from Settings > Apps > Installed apps.
3. Restart Windows.
4. Download the installer from the original application or game publisher.
5. Run the installer as administrator if required.
6. Install the program again.
7. Apply its current updates.
8. Launch it before adding mods, overlays, injectors, or custom plugins.

Reinstalling the application does not always install the UCRT. Keep the matching Visual C++ Redistributable installed separately.

Programs that have been associated with this class of runtime problem include Python embeddable distributions, Unity and Unreal Engine tooling, and vendor utilities built with Microsoft Visual C++. The dependency is the important pattern, not the idea that one particular game owns this DLL.

Fix 4: Repair Windows with DISM, then SFC

If the redistributable and application repair do not work, repair Windows’ component store and protected system files. Microsoft’s documented order is DISM first and SFC second.

Run DISM

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.
6. Enter:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Press Enter.
2. Wait for the operation to finish.
3. Do not close the window while DISM is working.
4. Restart Windows when it completes.

DISM uses Windows servicing sources to repair the component store. It may appear to pause for a period of time. That does not necessarily mean it has stopped.

Run System File Checker

After restarting:

1. Open an elevated Command Prompt again.
2. Enter:

sfc /scannow

1. Press Enter.
2. Wait until verification reaches 100 percent.
3. Restart Windows.
4. Test the affected program.

Microsoft’s System File Checker guidance explains the result messages.

If SFC reports that it found and repaired corrupted files, restart and test the program. If it reports that it could not repair some files, run DISM again, restart, and run SFC a second time.

If DISM reports that the source files could not be found, use a genuine matching Windows repair source:

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

Replace C:\RepairSource\Windows with the path to a valid repair source matching the installed Windows edition and build. Microsoft’s SFC and DISM repair documentation explains the source requirement.

Repeating SFC without addressing a damaged component store often produces the same result. Repair the servicing source first.

If you want help identifying which component is damaged rather than repeatedly hunting through Windows folders, Outbyte PC Repair can scan for system problems and show what needs attention; the repair itself requires the full version, and it is optional rather than a requirement for fixing this runtime.

Fix 5: Check antivirus quarantine and protection history

If the error appeared immediately after a security alert, the antivirus may have quarantined a runtime file or an application file. Do not restore a file solely because its name looks familiar.

For Microsoft Defender:

1. Open Start.
2. Search for Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review events around the time the program stopped launching.
7. Expand any matching event.
8. Verify the file path, publisher, and originating application.
9. Restore an item only when its origin and signature are known to be safe.
10. Prefer reinstalling the signed Microsoft runtime or the affected application.

Microsoft notes that Protection History retains events for only a limited period. If the quarantine record is gone, reinstall the official package instead of trying to reconstruct the deleted file manually.

If antivirus repeatedly removes a legitimate application file:

1. Update the security product.
2. Update Windows.
3. Reinstall the affected program from its original publisher.
4. Check the publisher and digital signature.
5. Contact the security vendor or application vendor if the detection continues.

Do not disable antivirus permanently to install an unknown DLL.

Fix 6: Install the UCRT on Windows 7, 8, or 8.1

The main subject here is Windows 10 and Windows 11, but older Windows installations can produce the same error. Windows 7 through Windows 8.1 require the appropriate Universal C Runtime update path.

Microsoft provided the UCRT through Windows Update and OS-specific packages, principally KB2999226. The official Universal CRT deployment documentation describes the supported deployment methods.

The Microsoft Windows 10 Universal C Runtime download package includes OS-specific packages such as:

• Windows 7 x64 and x86 packages
• Windows 8 x64 and x86 packages
• Windows 8.1 x64 and x86 packages

Before installing:

1. Press Windows + R.
2. Type winver.
3. Press Enter.
4. Confirm the Windows edition and version.
5. Open Control Panel.
6. Select System and Security.
7. Select System.
8. Confirm whether Windows is 32-bit or 64-bit.
9. On Windows 7, confirm that Service Pack 1 is installed.
10. On Windows 8.1, install the servicing prerequisite specified by Microsoft where required.

Download the matching KB2999226 package from Microsoft, not from a file mirror. Install the package, restart Windows, then install the Visual C++ Redistributable required by the application.

The current v14 redistributable page does not mean that the newest package supports every old Windows release. Older systems may need an OS-specific UCRT package and a legacy Visual C++ runtime selected by the application vendor.

Fix 7: Check whether a vendor utility or driver package is the real failing program

The error can appear while launching a graphics utility, virtual-GPU component, hardware monitor, driver manager, or installer. That does not mean the DLL belongs to the graphics driver itself.

First repair the Visual C++ runtime. Then repair or reinstall the specific utility that shows the error.

Use Device Manager only for the actual device problem

Device Manager does not install the UCRT. It is useful when the runtime error appeared together with a device failure or after a driver change.

1. Press Windows + X.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters, Network adapters, or System devices.
4. Right-click the affected device.
5. Select Properties.
6. Open the Driver tab.
7. Review the driver provider, date, and version.
8. Use Update Driver only with a driver from Windows Update or the hardware vendor.
9. If the issue began immediately after a driver update, use Roll Back Driver when available.
10. Restart Windows.

Do not delete runtime files from a driver folder. A vendor utility may require Visual C++ 2015 or a later compatible runtime even though the device driver itself is unrelated to the UCRT error.

If you want to avoid manually checking hardware categories and version histories, Outbyte Driver Updater can scan for outdated drivers and identify what needs attention; driver installation through the full version is optional, and reinstalling the affected vendor utility remains the definitive fix when its own files are damaged.

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

Windows Features is not the normal fix

api-ms-win-crt-math-l1-1-0.dll is not installed by toggling a random Windows Feature. Enabling or disabling .NET Framework, SMB, legacy media components, or other optional features will not substitute for the UCRT.

Use Windows Features only when the application’s own requirements specifically identify an optional Windows component.

To inspect the list:

1. Press Windows + R.
2. Type:

optionalfeatures

1. Press Enter.
2. Review the enabled features.
3. Change a feature only when the application vendor or Microsoft documentation specifically requires it.
4. Restart Windows if Windows asks you to do so.

Do not enable legacy features merely because the dialog mentions older compatibility components. The correct repair for this error is the UCRT or Visual C++ runtime, not an unrelated optional feature.

Why regsvr32 does not fix this error

regsvr32 is used to register DLLs that expose registration entry points such as DllRegisterServer, commonly for COM components. It does not install the Visual C++ Redistributable, repair the UCRT, or rebuild Windows API-set mappings.

Do not run:

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

against this API-set contract. It will not solve the missing-runtime problem and may produce another error about a missing entry point or registration function.

Microsoft documents the command’s actual purpose in regsvr32.

Why manually copying the DLL is unsafe

An isolated DLL download can be:

• The wrong architecture
• From the wrong Windows build
• Missing companion runtime files
• Incompatible with the application
• A fake or modified file
• Unable to repair the underlying Windows servicing problem

Copying files into System32, SysWOW64, or a program directory can also create version conflicts and make later servicing harder.

Microsoft supports application-local UCRT deployment for software developers, but that means deploying the complete architecture-specific runtime set as part of a controlled application package. It is not the same as downloading one file and copying it into a system folder. On Windows 10 and Windows 11, the system UCRT is used even when an application includes a local copy in applicable deployment scenarios.

For ordinary users, use Windows Update, the official Microsoft redistributable, the application’s own repair system, or Windows component repair.

If the redistributable installer fails

A Visual C++ installer can fail because files are locked, an older runtime installation is damaged, antivirus software interferes, or the installer cache is corrupted.

Try these steps in order:

1. Close all games, launchers, development tools, and installers.
2. Restart Windows.
3. Run the Microsoft redistributable installer as administrator.
4. Select Repair if it is already installed.
5. Temporarily investigate security-software interference without downloading files from untrusted locations.
6. Open Settings > Apps > Installed apps.
7. Search for the relevant Microsoft Visual C++ entry.
8. Use its Modify or Repair option if present.
9. If Microsoft’s documented procedure requires removing a damaged entry, record the architecture first and reinstall the correct package afterward.
10. Review the installer log named in Microsoft’s documentation, typically following the dd_vcredist_<arch>_<timestamp>.log pattern.

Microsoft provides additional steps in Visual C++ Redistributable installation troubleshooting.

Do not uninstall every Visual C++ package as a general cleanup step. Other applications may need those separate runtime generations.

If the error persists after reinstalling everything

At this point, stop treating the named file as the whole diagnosis. The loader may be reporting an API-set contract while another dependency is failing.

Work through this checklist:

1. Confirm whether one application or many applications fail.
2. Confirm the application architecture.
3. Install the matching x86, x64, or ARM64 runtime.
4. Confirm that Windows Update completed successfully.
5. Run DISM followed by SFC.
6. Check antivirus Protection History.
7. Use the application’s Verify or Repair feature.
8. Test the program under another local Windows user account.
9. Confirm that the application supports the installed Windows release.
10. Check whether the failing executable is inside the expected installation directory.
11. Remove recently added overlays, injectors, mods, or plugins temporarily.
12. Review the application’s own logs.
13. Reinstall the specific vendor utility or driver package.
14. Check Windows Event Viewer for an application error at the same time as the failed launch.

Test another Windows user account

A per-user configuration or permission problem can make one account fail while the application works elsewhere.

1. Open Settings.
2. Select Accounts.
3. Select Other users.
4. Select Add account.
5. Create a temporary local test account if appropriate.
6. Sign out.
7. Sign in to the test account.
8. Launch the affected program.

If it works under the second account, the runtime may be fine and the original profile, permissions, configuration, or application cache may be damaged. Do not delete the original account before backing up its data.

Check application compatibility

A current redistributable cannot make an unsupported application compatible with every Windows release. Check the program’s system requirements, especially if it targets an old operating system or depends on a legacy runtime.

If the program requires an older Visual C++ generation, install the version specified by its vendor while keeping the current runtime packages needed by newer applications.

Use System Restore after a known change

System Restore is reasonable when the error began immediately after a driver installation, Windows update, cleanup operation, or application installation and the normal repair steps failed.

1. Open Start.
2. Search for Create a restore point.
3. Open it.
4. Select System Restore.
5. Choose a restore point from before the change.
6. Review the affected programs and drivers.
7. Confirm the restore.
8. Restart Windows and test the application.

System Restore normally does not remove personal files, but it can roll back recently installed applications, drivers, updates, and settings. Microsoft describes this and other recovery choices in its Windows recovery options.

Use Windows 11 repair reinstall as a last system-level step

If Windows Update and the component store remain damaged on a supported Windows 11 installation:

1. Open Settings.
2. Select System.
3. Select Recovery.
4. Find Fix problems using Windows Update.
5. Select Reinstall now.
6. Follow the prompts.
7. Keep the computer connected to power and the internet.
8. Restart when Windows finishes.

This reinstalls the current Windows version while preserving applications, files, and settings when the feature is available and applicable. Microsoft documents the process in Fix issues by reinstalling the current version of Windows.

Frequently asked questions

Is api-ms-win-crt-math-l1-1-0.dll a Windows file or a Visual C++ file?

It is part of Microsoft’s Universal C Runtime. On Windows 10 and later, that runtime is integrated with Windows servicing. Applications built with Microsoft Visual C++ can depend on it, and the Visual C++ Redistributable supplies the runtime components required by many applications.

Why does a non-mathematical game need a math DLL?

The application may call standard C-runtime functions indirectly through its engine, launcher, graphics code, physics code, installer, or third-party libraries. The “math” label identifies the API contract, not the purpose of the entire application.

Does the file always exist as a normal DLL?

No. API-set names are loader contracts and virtual aliases. They may be represented by forwarders or mapped by the loader to an implementation such as ucrtbase.dll. The error message does not prove that a standalone file should be copied into a system folder.

Should I install x86 or x64?

Match the application:

• 32-bit program: x86
• 64-bit program: x64
• ARM64 program: ARM64

A 64-bit Windows PC commonly needs both x86 and x64 because it runs both 32-bit and 64-bit applications.

Is the latest Visual C++ Redistributable compatible with every Windows version?

No. Microsoft’s current package page focuses on currently supported Windows versions. Windows 7, 8, and 8.1 may require KB2999226, a legacy runtime, or an application-specific package.

Does reinstalling the game always install this runtime?

No. Some installers bundle the required redistributable, while others expect it to be installed separately. Install or repair the official Microsoft runtime even after reinstalling the application.

Could Python, Unity, or Unreal tools trigger this error?

Yes. Python distributions, game engines, editors, launchers, and tools built with Visual C++ can depend on the UCRT. Repair the runtime architecture that matches the failing executable, then repair the affected tool if necessary.

Does this belong to my graphics driver?

Usually not. A graphics utility or driver-management program can depend on the Visual C++ runtime, but that does not make the API-set a graphics-driver DLL. Repair the runtime first, then reinstall the specific utility or driver package if its installation is damaged.

Should I use regsvr32?

No. regsvr32 is for registering DLLs that support registration entry points. It does not install or repair the UCRT and does not apply to this API-set forwarder.

What if the file exists but Windows still reports it as missing?

The loader may be failing on another dependency, an incompatible architecture, ucrtbase.dll, an application-local runtime, or a damaged Windows component. Confirm the application architecture, repair the matching redistributable, run DISM followed by SFC, and repair the application.

Should I restore the file from antivirus quarantine?

Only when the file’s origin, path, publisher, and signature are known to be safe. In most cases, reinstalling the official Microsoft runtime or the affected application is safer than restoring an isolated quarantined file.

Is application-local UCRT deployment appropriate for normal users?

Usually no. Application-local deployment is a developer or software-publisher deployment method that requires the complete matching runtime set. General users should use Windows Update, the Microsoft Visual C++ Redistributable, or the application’s official installer.

What is the safest fix?

On Windows 10 or Windows 11, install Windows updates, install or repair the matching official Visual C++ Redistributable, restart, and repair the affected application. If the problem remains across programs, run:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

On Windows 7, 8, or 8.1, add the appropriate Microsoft KB2999226 UCRT update path and verify that the application supports the operating system.

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.