api-ms-win-crt-multibyte-l1-1-0.dll Errors: Safe Repair Path

If api-ms-win-crt-multibyte-l1-1-0.dll is missing, not found, or could not be loaded, repair the Microsoft Visual C++ runtime rather than downloading an individual DLL. api-ms-win-crt-multibyte-l1-1-0.dll is part of the Windows Universal C Runtime, and the correct package depends on whether the failed program is 32-bit or 64-bit.

What this file is

This filename belongs to a Microsoft Universal CRT/API-set component. It provides multibyte-character C-runtime functions used by applications built with modern Microsoft C and C++ tools, including functions such as _mbstrlen, _mbstowcs_l, and _ismbbalpha. Microsoft documents these APIs as beginning with Windows version 10.0.10240 in its Win32 extension API reference.

As an Amazon Associate I earn from qualifying purchases.

It is not a standalone program, game, DirectX component, .NET assembly, or ordinary hardware driver. A game or application may need it because that program was built with Microsoft development tools, and its installer may deploy a local copy beside the executable. The runtime itself is Microsoft software.

Windows API-set names can represent loader contracts or aliases rather than conventional libraries. Microsoft also documents physical api-ms-win-*.dll forwarder files as part of Universal CRT deployment, so the filename should not be dismissed as meaningless just because it looks like an API-set name. See Microsoft’s explanation of Windows API sets and API-set loader operation.

File identification

There is no single version or size that applies to every Windows installation. Servicing level, Windows build, architecture, and whether the copy is system-wide or application-local can change the details.

Property	What can be stated safely
Filename	api-ms-win-crt-multibyte-l1-1-0.dll
Component	Microsoft Universal C Runtime/API-set component
Main purpose	Multibyte-character C-runtime functions
Internal description	Microsoft does not publish a definitive internal description for this file
Verified baseline	Microsoft’s file table lists version 10.0.10240.16390 and a size of 19,808 bytes for its x86 and x64 entries
Windows 10 and 11	The Universal CRT is serviced as an operating-system component
Older Windows	The Universal CRT is supplied through an update or compatible redistributable deployment
Typical package	Microsoft Visual C++ Redistributable
Local copy	Some application installers bundle the file beside their executable

The baseline values in the table are reference information, not a requirement to find that exact version or size on every computer. Do not replace a system file merely because its version differs.

What the error means

Windows loads an application and its native dependencies before the program can start. If the loader cannot resolve the Universal CRT API set, it stops and displays an error naming this file.

Common wording includes:

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

The code execution cannot proceed because api-ms-win-crt-multibyte-l1-1-0.dll was not found. Reinstalling the program may fix this problem.

There was a problem starting api-ms-win-crt-multibyte-l1-1-0.dll. The specified module could not be found.

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

api-ms-win-crt-multibyte-l1-1-0.dll is either not designed to run on Windows or it contains an error.

The wording varies between Windows releases, applications, and loader paths. “The specified module could not be found” can also mean that another dependency needed by the named module is missing. The filename in the dialog is therefore a useful clue, but not always the only damaged or unavailable component.

The usual causes are:

• The Visual C++ runtime is missing or damaged.
• The wrong architecture was installed.
• Windows Update has not installed the Universal CRT on an older Windows version.
• A local runtime bundled with one application is incomplete or corrupt.
• Windows system components are damaged.
• Antivirus software quarantined a runtime file.
• A game or application update stopped before its prerequisites were installed.
• The program is launching from a different folder, launcher, service, or scheduled task than expected.

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

This is the best first repair for most users.

Download the current packages only from Microsoft’s Latest supported Visual C++ Redistributable downloads. The relevant installers are:

• vc_redist.x86.exe for 32-bit applications.
• vc_redist.x64.exe for 64-bit applications on Intel or AMD Windows.
• vc_redist.arm64.exe for ARM64 applications on ARM64 Windows.

A 32-bit program needs the x86 runtime even when Windows itself is 64-bit. Installing only x64 does not reliably satisfy a 32-bit application.

If you do not know the application architecture and are using 64-bit Windows, install both the current x86 and x64 packages. They can coexist because they serve different application architectures. On ARM64 Windows, use the package appropriate to the application; Microsoft also states that the x64 package contains required ARM64 binaries on ARM64 devices.

Install the packages

1. Open Microsoft’s Visual C++ downloads page.
2. Download the current x86 installer.
3. Run vc_redist.x86.exe.
4. Accept the license terms.
5. Select Install.
6. If the installer says a newer version is already installed, select its repair option if offered.
7. Restart Windows.
8. Launch the affected program again.

If the failed program is known to be 64-bit, repeat the process with vc_redist.x64.exe. If the application architecture is unknown, install both packages before testing again.

The Microsoft redistributable is a family of compatible v14 runtime packages. Repeatedly installing old packages from unrelated sources is not a good way to repair this error. Use the current supported package unless the application vendor specifically requires a separate legacy runtime.

Repair an existing installation

If Visual C++ is already installed, repair it rather than assuming the installation is healthy.

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Installed apps.
5. Search for Microsoft Visual C++ Redistributable.
6. Find the x86 or x64 entry that matches the failed application.
7. Select the three-dot menu.
8. Choose Modify.
9. Approve the administrator prompt.
10. Select Repair.
11. Restart Windows.

On Windows 10:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Apps & features.
5. Select the relevant Microsoft Visual C++ Redistributable entry.
6. Choose Modify.
7. Approve the administrator prompt.
8. Select Repair.
9. Restart Windows.

The exact menu wording can vary slightly by package version. The result you want is a completed repair followed by a restart. Test the application before changing anything else.

Microsoft’s general application repair instructions cover the same Windows settings paths.

Choosing x86 or x64 correctly

The package must match the application, not simply the operating system.

Situation	Package to install
32-bit application on 32-bit Windows	x86
32-bit application on 64-bit Windows	x86
64-bit application on 64-bit Intel or AMD Windows	x64
ARM64 application on ARM64 Windows	ARM64
Unknown application architecture on 64-bit Windows	Install both x86 and x64

This is why a 64-bit gaming PC can still need vc_redist.x86.exe. Many games, launchers, utilities, installers, and older tools remain 32-bit even when they run on a 64-bit edition of Windows.

Windows stores native 64-bit system files under %windir%\System32 and redirects 32-bit access through %windir%\SysWOW64. Those names are historically counterintuitive. Do not use the folder names as a reason to copy DLLs manually. Microsoft explains the behavior in its WOW64 file-system redirector documentation.

If installing both current packages does not help, the next question is whether the application is using a private copy beside its executable. That is handled later in this guide.

Fix 2: Install pending Windows updates

Windows 10 and Windows 11 treat the Universal CRT as an operating-system component. A partially updated installation can therefore produce a runtime error even when Visual C++ appears in the installed-programs list.

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install all available updates.
6. Restart when Windows requests it.
7. Return to Windows Update.
8. Select Check for updates again.
9. Repeat until Windows reports that no further updates are ready.

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. Check again after restarting.

Use Microsoft’s Windows Update instructions if the update process reports an error.

Test the affected program after the restart. If several unrelated programs began failing after an interrupted update, continue to the DISM and SFC repair steps below.

Fix 3: Install the Universal CRT update on older Windows

Windows 7 SP1, Windows 8.1, and other downlevel systems may need Microsoft’s Universal CRT update rather than relying only on the current Visual C++ package. Microsoft historically distributed this support through the Universal CRT update associated with KB2999226.

Use Microsoft’s Universal CRT update page and select the package matching the Windows edition and architecture.

The documented prerequisites include:

• Windows 7 or Windows Server 2008 R2 with Service Pack 1.
• Windows Vista or Windows Server 2008 with Service Pack 2.
• Windows 8.1 or Windows Server 2012 R2 with update rollup 2919355.

The update also supports other downlevel server editions listed by Microsoft, including Windows Server 2012 and Windows Server 2012 R2.

Install the prerequisite updates first if Microsoft’s page says they are required. Then:

1. Download the correct Universal CRT update from Microsoft.
2. Run the update package.
3. Complete the installer.
4. Restart Windows.
5. Install or repair the matching Visual C++ Redistributable.
6. Test the affected application.

Do not use an old Windows version as a reason to download a loose DLL. The supported approach is to install the operating-system update and runtime package together.

Fix 4: Repair Windows components with DISM and SFC

Use this fix when:

• The DLL is absent from the Windows system directories.
• Several unrelated applications fail.
• The error started after an interrupted Windows update.
• A cleanup utility removed or damaged system files.
• Visual C++ repair completed but the loader error remains.

Microsoft recommends running DISM before System File Checker because DISM repairs the component store that SFC may need as a source.

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for DISM to finish. Do not close the window merely because progress appears to pause.
2. Then run:

sfc /scannow

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

The SFC result tells you what happened:

• Windows Resource Protection did not find any integrity violations: SFC found no damaged protected files.
• Windows Resource Protection found corrupt files and successfully repaired them: restart and test the application.
• Windows Resource Protection found corrupt files but was unable to fix some of them: run DISM again, restart, and run SFC again.
• DISM reports that source files could not be found: use a matching Windows installation source as described below.

If Windows Update cannot provide repair files, Microsoft documents specifying a matching repair source:

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

Replace C:\RepairSource\Windows with a valid repair source from the same Windows version and architecture. Do not invent a source path and do not point DISM at a random Windows folder.

If you are repeatedly hunting through Windows versions and rerunning SFC or DISM without knowing what changed, Outbyte PC Repair can scan for the condition and show what it identifies; the free scan shows the findings, while repair is performed by the full version, and it is not required for every case.

Microsoft’s full System File Checker and DISM guidance should be the reference if either command produces an error.

Fix 5: Repair or reinstall the affected application

If only one game or application fails while other native programs work, the application’s own installation is more likely to be incomplete.

This is especially common after:

• A game update was interrupted.
• The installer closed before prerequisites finished.
• A launcher downloaded only part of the installation.
• An application was moved to another drive.
• A cleanup tool removed files beside the executable.
• The program was uninstalled incompletely and then restored from a backup.

Use the application’s built-in repair process first:

1. Open the game launcher or application manager.
2. Select the affected program.
3. Open its settings or three-dot menu.
4. Choose Verify, Repair, Scan and repair, or the equivalent option.
5. Wait for validation to finish.
6. Restart the launcher.
7. Test the program.

If the launcher has no repair option:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Installed apps on Windows 11, or Apps & features on Windows 10.
5. Select the affected application.
6. Choose Advanced options if available.
7. Select Repair.
8. Test the application.
9. If it still fails, use Reset only if you understand that it may remove local application data.
10. As a final application-level step, uninstall and reinstall from the original vendor or launcher.

Some portable applications, installers, and launchers deploy the Universal CRT beside their executable. Microsoft supports local deployment for developers but recommends central deployment for security and servicing reasons. A local copy can therefore be stale or damaged even when the Windows-wide runtime is healthy.

Do not overwrite that local copy with a file copied from another computer. Repairing or reinstalling the owning application restores the complete set of files and the correct architecture.

Fix 6: Check antivirus quarantine

Security software can quarantine a runtime file after a failed installation or after detecting a suspicious file in an application directory. Quarantine does not prove that the file was malicious, and it does not prove that the detection was a false positive.

Check Windows Security:

1. Open Start.
2. Type Windows Security.
3. Open the app.
4. Select Virus & threat protection.
5. Select Protection history.
6. Look for the event matching the time the application stopped launching.
7. Expand the event and inspect the file path, detection name, and originating application.

Only restore a file when its source, signature, and location are trusted. If the quarantined file came from a temporary folder, an unknown download, a startup location, or an unexpected roaming-profile folder, do not restore it blindly.

The safer sequence is:

1. Record the detected file path.
2. Run a full scan.
3. Obtain the application again from its original vendor or launcher.
4. Repair or reinstall the Visual C++ runtime from Microsoft.
5. Restart Windows.
6. Test the program.

Microsoft’s Protection History guidance explains how to review and respond to detections.

If a legitimate installer is repeatedly quarantined, update Windows Security definitions and contact the application vendor. Do not disable antivirus protection merely to force a DLL into a system directory.

Fix 7: Investigate an application-local copy

The file may appear beside the application executable even though it is a Microsoft runtime component. That happens when an installer uses local deployment, placing a set of runtime files in the application directory.

To check the active executable path:

1. Start the application or launcher if it opens far enough to appear in Task Manager.
2. Press Ctrl + Shift + Esc.
3. Select the Details tab.
4. Right-click the relevant process.
5. Select Open file location.
6. Note the folder containing the executable.
7. Look for api-ms-win-crt-multibyte-l1-1-0.dll and related UCRT files in that folder.

If the program never stays open long enough to appear in Task Manager, inspect the shortcut:

1. Right-click the application shortcut.
2. Select Properties.
3. Review the Target field.
4. Check the Start in field.
5. Confirm that the shortcut points to the installation you repaired.

This matters when two copies of a game or utility exist, or when a launcher still starts an old executable from another drive.

If the local file is missing or appears damaged, use the program’s repair or verification feature. If only one application fails, reinstalling that application remains the definitive repair for its private deployment.

Fix 8: Check for a failed installer or uninstall

A program uninstall can remove shared files incorrectly, while a failed update can leave a launcher pointing at an incomplete directory. The Visual C++ installer may also report that a newer version already exists even though its files need repair.

If the failure started immediately after an application update or uninstall:

1. Restart Windows.
2. Repair the Visual C++ x86 package.
3. Repair the Visual C++ x64 package if installed.
4. Run the application launcher’s verification process.
5. Repair the application from Windows Settings if that option exists.
6. Reinstall the application if verification cannot restore the missing runtime.

Microsoft documents redistributable installer options including /install, /repair, /uninstall, /quiet, /norestart, and /log. For example, after downloading the official x86 installer, an administrator can run:

vc_redist.x86.exe /repair /norestart /log "%TEMP%\vc-redist-x86-repair.txt"

Use the same structure with the x64 installer when repairing the x64 package. The log path helps determine whether the installer completed or encountered a Windows Installer problem.

Do not repeatedly install random older packages when the installer says a newer version is already present. Repair the existing package or use Microsoft’s documented redistributable command-line options.

Fix 9: Consider a driver installer only when the error occurs there

There is no authoritative Microsoft evidence tying this specific filename to one graphics, audio, printer, or chipset driver package. If the error appears inside a hardware vendor’s installer, the driver package may be incomplete or the installer may be launching a bundled helper program that needs the Visual C++ runtime.

First repair the runtime using the steps above. Then repair the hardware driver through the vendor’s complete installer.

For a graphics or other device driver:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters, Sound, video and game controllers, or Printers.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Record the provider and driver version.
8. Use the hardware vendor’s complete driver package.
9. Follow the vendor’s clean-install or repair instructions.
10. Restart Windows.
11. Test the installer or application again.

Do not use Device Manager’s generic update search as a substitute for repairing the Visual C++ runtime. Device Manager manages device drivers, while this filename belongs to the Universal CRT.

If identifying which of dozens of installed drivers is stale is the difficult part, Outbyte Driver Updater can scan and identify driver issues; the free scan shows what it finds, while driver installation is handled by the full version, and it is not required when the error is clearly limited to a game or application runtime.

Windows Features are usually unrelated

Windows Features does not install the Visual C++ Redistributable or repair the Universal CRT.

You can confirm this without changing anything:

1. Open Start.
2. Type Windows Features.
3. Select Turn Windows features on or off.
4. Review the list.
5. Close the window without enabling random features.

Do not enable legacy components such as .NET Framework 3.5 or older media features merely because a native DLL error mentions a missing file. Those features can matter to a particular application, but there is no evidence that toggling them repairs api-ms-win-crt-multibyte-l1-1-0.dll.

.NET repair also does not replace the native Microsoft C runtime. DirectX repair is not the default solution either. Use those components only when the affected application separately reports a documented dependency problem.

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

What not to do

Do not download the individual DLL from a random website

Loose DLL downloads are risky because the file may be:

• Malware or modified code.
• The wrong architecture.
• An incompatible build.
• Missing its companion UCRT files.
• Intended for a different Windows servicing level.
• Placed in a directory the loader does not use.

Even a clean-looking file may not fix the root cause. The application could be missing ucrtbase.dll, another forwarder, a dependent runtime, or a valid API-set mapping.

Use Microsoft’s Visual C++ Redistributable page, Windows Update, the original application installer, DISM, and SFC instead.

Do not copy an x86 file into System32

Likewise, do not copy an x64 file into SysWOW64. The names are not intuitive, and manually placing one DLL does not install the matching runtime family.

Windows 10 and Windows 11 service the UCRT as an operating-system component. Older Windows versions may require the Universal CRT update. Both situations call for a supported package or system repair, not a random replacement file.

Do not run regsvr32 on this file

regsvr32 is for self-registering COM and ActiveX DLLs that expose registration entry points such as DllRegisterServer. This Universal CRT/API-set component is not a COM server.

Running a command such as this does not repair the runtime:

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

It may produce an entry-point error, and successful registration would not install the runtime or restore loader resolution. Microsoft explains the purpose and limitations of Regsvr32.

Do not use registry cleaners

Registry cleaners do not install the Universal CRT and can make application repair harder by removing installer registration data. If a Visual C++ installer says a newer version exists, repair that installation instead.

Inspect the system copies

If you need to determine whether the file exists in the normal Windows locations, use PowerShell rather than copying anything.

1. Open Start.
2. Type PowerShell.
3. Right-click Windows PowerShell.
4. Select Run as administrator.
5. Run:

$files = @(
  "$env:windir\System32\api-ms-win-crt-multibyte-l1-1-0.dll",
  "$env:windir\SysWOW64\api-ms-win-crt-multibyte-l1-1-0.dll"
)

Get-Item $files -ErrorAction SilentlyContinue |
  Select-Object FullName, Length,
    @{Name="FileVersion"; Expression={$_.VersionInfo.FileVersion}}

An absent result does not automatically prove that the entire runtime is broken. The file may be represented through API-set resolution, deployed locally beside an application, or affected by a different missing dependency. Conversely, a present file does not prove that the application can load it.

If the file exists but the error remains, inspect:

• The exact executable path.
• Whether the program is 32-bit or 64-bit.
• Whether the matching x86 or x64 runtime is installed.
• Whether the application has a local runtime folder.
• Whether other UCRT files are missing.
• Whether the error occurs only under a launcher, service, or scheduled task.

If several unrelated programs fail

Failure across unrelated programs points away from one game’s installation and toward a shared runtime or Windows component problem.

Work through this order:

1. Install pending Windows updates.
2. Restart.
3. Repair Visual C++ x86.
4. Repair Visual C++ x64 if present.
5. Run DISM.
6. Run SFC.
7. Restart again.
8. Check Windows Security Protection History.
9. Test more than one affected program.

If the problem began immediately after a Windows update, driver installation, cleanup operation, or failed application installer, System Restore may be appropriate. Microsoft’s System Restore documentation explains how to choose a restore point and what it changes. System Restore normally affects system files, registry settings, and installed programs rather than personal documents.

If the error persists

When reinstalling the runtime does not work, avoid cycling through unrelated fixes. Narrow down the failing loader path.

Check these questions:

Does only one program fail?

Repair or reinstall that program. Check its launcher, shortcut target, and application-local runtime files.

Do both 32-bit and 64-bit programs fail?

Repair both Visual C++ architectures, install Windows updates, and run DISM followed by SFC.

Did the problem begin after antivirus activity?

Inspect Protection History and scan the system. Restore only a trusted file from a trusted location.

Does the dialog say “specified module could not be found”?

Treat the named DLL as a clue, not proof that it is the only missing file. A dependency of the named module may be absent.

Does the program come from a portable folder?

Look beside the executable for an incomplete local runtime. Re-download or reinstall the complete application from its original vendor.

Does a driver installer fail?

Repair Visual C++, then use the hardware vendor’s complete driver installer. Do not treat this DLL as a driver file.

Did the problem follow a Windows update or failed cleanup?

Run Windows Update, DISM, and SFC. If the problem clearly began at a known change, consider System Restore.

Is the application architecture unknown?

On 64-bit Windows, install both current x86 and x64 Visual C++ packages. On ARM64 Windows, account for the application’s architecture and Microsoft’s ARM64 package guidance.

FAQ

Is api-ms-win-crt-multibyte-l1-1-0.dll a virus?

The filename is a genuine Microsoft Universal CRT/API-set component. A copy found in an unexpected temporary or startup directory still deserves investigation, because malware can use legitimate-looking filenames. Check the path, signature, source, and Windows Security Protection History instead of assuming either a false positive or a safe file.

Is this a DirectX file?

No authoritative Microsoft source identifies it as a DirectX component. It is part of the Universal CRT used by native applications. Repair Visual C++ and Windows components first.

Is it part of .NET?

No. .NET repair does not normally replace this native C-runtime dependency.

Should I install x86 or x64?

Install x86 for a 32-bit program and x64 for a 64-bit program. A 32-bit program needs x86 even on 64-bit Windows. If the architecture is unknown, install both current Microsoft packages on 64-bit Windows.

Why does the file appear in a game folder?

Some applications deploy runtime files locally beside their executable. That does not mean the game created the Microsoft runtime or that the file should be replaced separately. Verify or reinstall the complete game or application.

Can I copy the file from another computer?

For ordinary troubleshooting, no. The copy may have a different architecture, Windows build, or servicing level, and other UCRT files may also be needed. Use Microsoft’s redistributable, Windows Update, DISM, or SFC.

Should I register it with regsvr32?

No. It is not a self-registering COM or ActiveX server. regsvr32 does not install or repair the Universal CRT.

Does Windows 10 include this runtime?

Windows 10 and Windows 11 treat the Universal CRT as an operating-system component, although applications can also carry local runtime files. An incomplete update or damaged component store can still cause loading failures.

What about Windows 7 or Windows 8.1?

Those systems may require Microsoft’s Universal CRT update and its documented prerequisites, followed by the appropriate Visual C++ Redistributable package.

Why does Visual C++ say it is already installed?

The installed package may be present but damaged, or a newer compatible package may already exist. Use Modify and Repair, then restart. Do not repeatedly install random older versions.

What if only one game fails?

Verify the game files, repair its installation, check its launcher path, and reinstall it if necessary. A single failing application commonly has an incomplete local deployment or failed update.

What if every native application fails?

Install pending Windows updates, repair both Visual C++ architectures, run DISM, run SFC, and check antivirus quarantine. Widespread failures suggest a shared runtime or Windows component problem rather than one game folder.

Can a driver cause this error?

A driver installer can launch a helper program that depends on the Universal CRT, but this filename is not established as belonging to a particular driver package. Repair the runtime, then reinstall the complete driver package from the hardware vendor if the failure is limited to that installer.

The reliable repair path is to restore the supported runtime environment: install the correct Microsoft Visual C++ package, update Windows, repair the application when only one program fails, and use DISM followed by SFC when Windows components appear damaged.

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.