ucrtbase_clr0400.dll Is Missing: Repair the Right Runtime

If ucrtbase_clr0400.dll is missing, Windows is usually unable to load part of the Microsoft C runtime used by .NET Framework 4.x applications. ucrtbase_clr0400.dll is a legitimate Microsoft runtime component, but the correct repair depends on whether the problem affects Windows itself, one application, or a 32-bit and 64-bit runtime mismatch.

Start with this diagnostic checklist

Before changing files, note:

• Which program or game shows the error.
• Whether the error appears during Windows startup, program startup, installation, or gameplay.
• Whether one program fails or several .NET/WPF programs fail.
• Whether the message says “missing,” “not found,” “could not be loaded,” or “bad image.”
• Whether the dialog names C:\Windows\System32, C:\Windows\SysWOW64, or an application folder.
• Whether the affected application is 32-bit or 64-bit.
• Whether the error began after Windows Update, an application update, a failed installation, antivirus activity, a mod installation, or a system crash.

Do not download the DLL before checking these details. A matching filename does not prove that a file has the correct architecture, build, signature, or dependencies.

As an Amazon Associate I earn from qualifying purchases.

What ucrtbase_clr0400.dll is

ucrtbase_clr0400.dll is associated with the Microsoft C Runtime Library and the CLR, or Common Language Runtime, used by the .NET Framework 4.x native and WPF runtime stack. The clr0400 suffix distinguishes it from the ordinary ucrtbase.dll.

The two files are related, but they are not interchangeable:

• ucrtbase.dll is the normal Universal C Runtime file.
• ucrtbase_clr0400.dll is a CLR-specific runtime component used with .NET Framework 4.x.
• The file commonly appears with runtime components such as VCRUNTIME140_CLR0400.dll, VCRUNTIME140_1_CLR0400.dll, and, for WPF applications, MSVCP140_CLR0400.dll.

It is normally part of the Windows and .NET Framework runtime environment rather than a game-specific file, hardware driver, or ordinary application resource. Some application installers can also deploy runtime files beside their own program files, so the exact path matters.

The file is not the same as the modern .NET runtimes used by applications targeting .NET 6, .NET 8, or .NET 9. Microsoft treats .NET Framework and modern .NET as separate technologies. Installing modern .NET alone does not repair a damaged .NET Framework 4.x installation. See Microsoft’s .NET Framework installation guide.

Older file metadata can identify the product as Microsoft Visual Studio 2017, but that is build metadata. It does not mean you need to install Visual Studio to repair the problem.

Where the file should be located

On 64-bit Windows, the normal architecture split is:

• C:\Windows\System32\ucrtbase_clr0400.dll — 64-bit copy
• C:\Windows\SysWOW64\ucrtbase_clr0400.dll — 32-bit copy

The names are counterintuitive. On 64-bit Windows, System32 contains 64-bit system binaries, while SysWOW64 contains 32-bit system binaries.

A 64-bit application normally loads the System32 copy. A 32-bit application running under Windows-on-Windows 64-bit normally loads the SysWOW64 copy.

On 32-bit Windows, the 32-bit system copy is normally under C:\Windows\System32.

The application’s architecture matters more than the architecture of Windows when selecting Visual C++ packages. A 32-bit application needs the x86 runtime even when it is running on a 64-bit computer. When the application architecture is uncertain, installing both Microsoft’s x86 and x64 Visual C++ packages is reasonable.

Microsoft explains this architecture distinction in its Visual C++ deployment documentation.

Common error messages

The wording varies between Windows versions and application loaders. You may see:

The program can't start because ucrtbase_clr0400.dll is missing from your computer. Try reinstalling the program to fix this problem.

This application has failed to start because ucrtbase_clr0400.dll was not found. Re-installing the application may fix the problem.

The code execution cannot proceed because ucrtbase_clr0400.dll was not found.

There was a problem starting ucrtbase_clr0400.dll. The specified module could not be found.

“The specified module could not be found” does not always mean that the named DLL itself is absent. It can mean that the file exists but one of its dependencies is missing, damaged, blocked, or the wrong architecture.

A damaged image may produce a message similar to:

C:\Windows\SYSTEM32\ucrtbase_clr0400.dll is either not designed to run on Windows or it contains an error.

Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.

Error status 0xc000012f.

The 0xc000012f status belongs to the invalid-image family of Windows errors. It does not, by itself, prove that this one DLL is the only damaged component.

Fix 1: Repair or install the correct Visual C++ Redistributable

For this file category, the fastest repair is to repair the matching Microsoft Visual C++ Redistributable. The current Microsoft v14 packages cover applications built with Visual Studio 2017 and later, and many application installers bundle the required runtime.

This fix is especially important if the error also mentions:

• VCRUNTIME140_CLR0400.dll
• VCRUNTIME140_1_CLR0400.dll
• MSVCP140_CLR0400.dll
• VCRUNTIME140.dll
• MSVCP140.dll

Repair an installed package

1. Press Win + I to open Settings.
2. Select Apps.
3. Select Installed apps.
4. Search for Microsoft Visual C++ Redistributable.
5. Check both the x64 and x86 entries if they are installed.
6. Select the three-dot menu beside the relevant package.
7. Choose Modify.
8. Select Repair.
9. Repeat for the other architecture if the application may be 32-bit or if several programs are affected.
10. Restart Windows.

Launch the affected application after restarting. If it opens normally, the runtime installation was incomplete or damaged.

Install the official packages

If the Redistributable is missing, repair fails, or the installation appears corrupted:

1. Open Microsoft’s latest supported Visual C++ Redistributable downloads.
2. Download the x86 package for 32-bit applications.
3. Download the x64 package for 64-bit applications.
4. On 64-bit Windows, install both when the application architecture is unknown or more than one program is affected.
5. Run each installer.
6. Accept the license terms.
7. Choose Install or Repair, depending on what the installer reports.
8. Restart Windows.
9. Test the program again.

Do not install only x64 because Windows itself is 64-bit. Many older launchers, WPF utilities, game tools, mod loaders, and installers remain 32-bit.

The Visual C++ Redistributable is the correct first repair for a vcredist-related failure, but Microsoft does not publish a simple package page assigning this exact _CLR0400 filename to one downloadable installer. If the file is still missing from a Windows directory after the Redistributable repair, continue with Windows component repair and .NET Framework repair instead of copying a replacement DLL manually.

Fix 2: Install Windows updates, then repair Windows components

A missing or damaged copy under System32 or SysWOW64 can indicate Windows component corruption, an interrupted update, disk errors, or an incomplete runtime installation.

Install pending Windows updates

1. Open Start > Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install every available quality, security, and runtime update.
5. Restart when Windows asks.
6. Return to Windows Update and check again.
7. Repeat until no further updates are offered.
8. Launch the affected application.

The Universal CRT is a Windows component on modern Windows versions and is serviced through Windows Update. This is why downloading an isolated DLL is not the normal repair method. Microsoft documents the Universal CRT in its Universal CRT deployment guide.

Run DISM before SFC

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 the operation to reach completion.
2. Keep the window open and run:

sfc /scannow

1. Wait until System File Checker reaches 100 percent.
2. Restart Windows, even if SFC reports that it repaired files.
3. Test the affected application again.

Microsoft recommends running DISM before SFC because DISM can repair the component store that SFC uses as a source for replacing damaged protected files. The complete Microsoft procedure is documented in Use the System File Checker tool to repair missing or corrupted system files.

Typical results include:

• Windows Resource Protection did not find any integrity violations: protected Windows files appear intact, so continue with .NET, Visual C++, application, or antivirus checks.
• Windows Resource Protection found corrupt files and successfully repaired them: restart and test the program.
• Windows Resource Protection found corrupt files but was unable to fix some of them: run DISM again, restart, and then run SFC again. If the problem continues, repair .NET Framework and check the component path.
• DISM cannot find source files: finish Windows Update first, then retry. Persistent component-store failures may require Windows recovery or an in-place repair.

The repeated manual cycle of checking Windows versions, running SFC and DISM, and working out which component changed can be difficult to track. Outbyte PC Repair offers a free scan that shows what it identifies, while the repair is performed by the full version; it is optional, and Microsoft’s built-in DISM, SFC, Windows Update, and .NET repair steps remain appropriate when the file belongs to a specific application.

Fix 3: Repair the .NET Framework 4.x installation

If Windows repair completes but WPF or other .NET Framework applications still fail, repair the .NET Framework runtime.

This step is especially relevant when:

• Several unrelated .NET or WPF applications fail.
• The error names clr.dll, wpfgfx_v0400.dll, or another _CLR0400 companion.
• The file is missing from a Windows directory.
• The failure started after an interrupted .NET update or installer.
• The program uses Windows Presentation Foundation, often abbreviated WPF.

Use Microsoft’s .NET Framework Repair Tool

1. Download Microsoft’s .NET Framework Repair Tool.
2. Save the installer to a local folder.
3. Right-click it and select Run as administrator.
4. Accept the license terms.
5. Allow the tool to inspect the .NET Framework installation.
6. Apply the recommended repairs.
7. Restart Windows.
8. Test the affected program.

The tool is designed to repair common .NET Framework setup and configuration problems. It does not replace the need to repair the application itself when only one program remains broken.

Install or repair .NET Framework 4.8.1

If the computer supports it and the application is compatible:

1. Open Microsoft’s .NET Framework 4.8.1 download page.
2. Select the runtime installer, not a developer pack.
3. Run the downloaded installer as administrator.
4. Allow setup to repair or install the runtime.
5. Restart Windows.
6. Test the application.

If the application specifically requires .NET Framework 4.8, use Microsoft’s .NET Framework 4.8 download page instead.

Do not assume that installing a newer modern .NET runtime repairs .NET Framework 4.x. They have different runtime families and servicing paths.

Check Windows Features

Some Windows installations expose .NET Framework components through Windows Features.

1. Press Win + R.
2. Type:

optionalfeatures

1. Press Enter.
2. Look for .NET Framework 4.8 Advanced Services or a similarly named 4.x entry.
3. If it is listed and unchecked, select it.
4. Expand it if necessary and leave the default subfeatures selected.
5. Select OK.
6. Allow Windows to download or apply the required files.
7. Restart Windows.
8. Test the application.

Do not enable .NET Framework 3.5 solely because this file contains clr0400. .NET Framework 3.5 is a separate legacy feature and should be enabled when an application specifically requires it.

Fix 4: Repair the affected application or game

If only one program fails, the application may have lost its own runtime files during an update, uninstall, security scan, mod installation, or interrupted setup.

Repair a Windows application

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

If Repair does not help:

1. Return to the application’s Advanced options.
2. Select Reset if available.
3. Understand that Reset can remove application settings or local data.
4. Reopen the application.
5. If it still fails, uninstall and reinstall it from the publisher’s official installer.

For a traditional desktop application, open Control Panel > Programs > Programs and Features, select the application, and look for Repair or Change. If the installer offers a repair mode, use that before uninstalling.

Verify a Steam game

For a Steam game:

1. Open Steam.
2. Open Library.
3. Right-click the game.
4. Select Properties.
5. Select Installed Files.
6. Select Verify integrity of game files.
7. Wait for the scan to complete.
8. Start the game without mods or overlays.

Verification can replace files deleted or damaged by an interrupted update or security software. If the game still fails, temporarily disable third-party mods, injectors, overlays, and custom launch parameters. Reinstalling the game or its official launcher remains the definitive repair when the missing file belongs to that application’s installation folder.

Fix 5: Check antivirus quarantine

Antivirus software can quarantine a runtime file after a failed installation, a false positive, or a damaged file scan.

Check Windows Security

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent quarantined or blocked items.
7. Look for an entry naming ucrtbase_clr0400.dll or the affected application.

Restore the file only when all of these conditions are satisfied:

• The file came from Windows Update, a Microsoft installer, or a trusted application installer.
• The path is expected.
• The file’s digital signature identifies Microsoft or the trusted application publisher.
• The detection has been confirmed as a false positive.

Microsoft Defender’s Restore action returns a quarantined file to its original location, but Defender may detect it again. Do not disable antivirus protection or create an exclusion for an unverified DLL. Microsoft describes these controls in Protection History in the Windows Security app.

If the file was quarantined from an application directory, repair or reinstall that application after confirming the installer is legitimate. If it was quarantined from System32 or SysWOW64, run DISM and SFC after resolving the detection.

Fix 6: Check the exact architecture and path

A 32-bit DLL in a 64-bit location, or a 64-bit DLL in a 32-bit application directory, can produce a missing-file or invalid-image error even when the filename looks correct.

Check the locations from an elevated or ordinary Command Prompt:

dir "%windir%\System32\ucrtbase_clr0400.dll"
dir "%windir%\SysWOW64\ucrtbase_clr0400.dll"

If the file exists, check its Microsoft signature:

Get-AuthenticodeSignature "$env:windir\System32\ucrtbase_clr0400.dll"

For the 32-bit system copy on 64-bit Windows:

Get-AuthenticodeSignature "$env:windir\SysWOW64\ucrtbase_clr0400.dll"

A valid Microsoft signature is a useful confirmation that the file originated from Microsoft. A missing, invalid, or unexpected signer means the file should not be trusted merely because its name is correct.

Check version and publisher metadata:

(Get-Item "$env:windir\System32\ucrtbase_clr0400.dll").VersionInfo |
  Format-List FileVersion,ProductVersion,CompanyName,FileDescription

Repeat with SysWOW64 when the failing application is 32-bit.

Public inventories show multiple legitimate builds. One observed 64-bit build is 14.10.25028.0, with a file size of about 0.74 MB. That is an example of a valid build, not a universal version or target for manual replacement. The exact build can vary according to Windows release, architecture, .NET Framework servicing, and installed updates.

Do not replace a file simply because another computer has a different version.

Fix 7: Remove mods, overlays, and plug-ins

A crash report naming ucrtbase_clr0400.dll does not prove that the runtime caused the crash. The DLL may simply be the module where an application bug, invalid call, memory problem, or incompatible plug-in became visible.

This is common with:

• Game mods.
• Mod loaders.
• Graphics overlays.
• Compatibility layers.
• Third-party launchers.
• WPF configuration tools.
• .NET-based game utilities.

Test the program in a clean state:

1. Close the application and its launcher.
2. Disable mods and plug-ins.
3. Disable overlays from gaming clients, recording tools, and hardware utilities.
4. Remove custom launch parameters temporarily.
5. Use the application’s file verification feature.
6. Create a clean application profile if the program supports profiles.
7. Launch the unmodified application.
8. Re-enable modifications one at a time.

If the unmodified program works, the runtime file was probably not the original cause. Update or remove the plug-in that reintroduces the failure.

Fix 8: Consider drivers only when the evidence points there

A graphics or chipset driver normally does not install or repair ucrtbase_clr0400.dll. Driver work is therefore a low-priority step for a straightforward missing-file message.

Consider a driver repair when:

• The problem began immediately after a graphics or chipset driver change.
• A WPF or graphics-heavy application crashes without a missing-DLL dialog.
• Event Viewer names a graphics driver module.
• Multiple graphics applications fail.
• The application works in a clean software configuration but fails after a driver update.

Check Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics adapter.
5. Select Properties.
6. Open the Driver tab.
7. Note the provider, date, and version.
8. If the failure began after an update, try Roll Back Driver if available.
9. Otherwise select Update Driver and allow Windows to search.
10. Restart Windows.

For a serious graphics issue, download the driver only from the graphics or computer manufacturer’s official support page. Do not use a random driver package or a DLL download site.

Hunting through hardware entries, comparing driver versions, and guessing which of many drivers is stale can take longer than the actual repair. Outbyte Driver Updater provides a free scan that identifies what it finds, while driver installation is performed by the full version; use it as an optional convenience, not as a required fix for a missing runtime file.

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

Fix 9: Scan for malware and disk problems

Malware is not the most direct explanation for every _CLR0400 error, but it deserves attention when files repeatedly disappear or become corrupted.

Run a full scan when:

• Windows files are repeatedly modified.
• Antivirus detections are present.
• The file returns after repair and then becomes damaged again.
• Other applications show unexpected system-file errors.
• The computer has unexplained crashes or disk warnings.

To run a Microsoft Defender scan:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Scan options.
4. Choose Full scan.
5. Select Scan now.
6. Follow any remediation instructions.
7. Restart Windows and test again.

If malware may be active during normal Windows operation, choose Microsoft Defender Offline scan from the same menu. Microsoft documents these options in Virus and threat protection in Windows Security.

If corruption returns after successful DISM and SFC repairs, check available disk space, review Event Viewer for disk errors, and use the storage manufacturer’s diagnostic tools where appropriate.

Fix 10: Use System Restore after a recent change

System Restore can help when the error began immediately after a driver, application, update, or system configuration change.

1. Press Win + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the error began.
4. Select Scan for affected programs if available.
5. Review the changes.
6. Select Next, then Finish.
7. Allow Windows to restart.

System Restore rolls back system files, settings, drivers, and installed programs without normally removing personal documents. It does not replace a missing application installation if the application itself is damaged. Microsoft explains the process in its System Restore guidance.

Fix 11: Repair Windows while keeping apps and files

If DISM, SFC, Windows Update, .NET repair, and Visual C++ repair all fail, Windows itself may need a deeper repair.

On supported Windows 11 installations:

1. Open Start > Settings.
2. Select System.
3. Select Recovery.
4. Look for Fix problems using Windows Update.
5. Select Reinstall now.
6. Follow the prompts.
7. Keep the computer connected to power and the internet.
8. Test the application after Windows finishes.

Microsoft says this process reinstalls the current Windows version while preserving applications, personal files, and settings when the option is available. See Fix issues by reinstalling the current version of Windows.

If that option is unavailable, use Windows installation media for an in-place repair and select the option to keep personal files and applications. Back up important data before beginning any operating-system repair.

Do not run regsvr32 on this file

regsvr32 is intended for self-registering DLLs such as certain ActiveX and OLE components. A runtime library such as ucrtbase_clr0400.dll normally does not expose the registration entry point that regsvr32 requires.

Do not run:

regsvr32 ucrtbase_clr0400.dll
regsvr32 /u ucrtbase_clr0400.dll
regsvr32 /i ucrtbase_clr0400.dll

If you try, Windows may report:

The module was loaded but the entry-point DllRegisterServer was not found.

That message does not mean the DLL needs another registration command. It means the DLL is not a self-registering component. Microsoft describes this behavior in Regsvr32 troubleshooting documentation.

Do not download a loose DLL

Avoid DLL download sites and random file mirrors. A loose replacement can have:

• The wrong 32-bit or 64-bit architecture.
• The wrong Windows build.
• An incompatible application binary interface.
• Missing companion files.
• An invalid or missing digital signature.
• Malware or a modified payload.
• A version that is overwritten by the next Windows update.

Copying a file into System32, SysWOW64, or an application directory can also bypass Windows component servicing and make future troubleshooting harder.

Microsoft supports limited local Universal CRT deployment in developer scenarios, but it is not the recommended normal repair for Windows users. Use Windows Update, DISM, SFC, the .NET Framework Repair Tool, official Visual C++ packages, or the application’s own installer instead.

The safe sources are:

• Windows Update.
• Microsoft’s official Visual C++ Redistributable download page.
• Microsoft’s official .NET Framework 4.8 or 4.8.1 runtime pages.
• Microsoft’s .NET Framework Repair Tool.
• The affected application’s official installer or repair function.

When the file exists but the error remains

If dir shows the file but the application still says it is missing, investigate the loader context rather than copying another version.

Likely causes include:

• A dependency of the DLL is missing.
• The application is 32-bit but only the x64 runtime was installed.
• The file is corrupt despite being present.
• The application is searching a different directory.
• Antivirus software is blocking the load.
• The application has an incompatible local copy.
• A plug-in or mod is loading a conflicting runtime.
• The application itself has a damaged installation.

Check the exact path in the error dialog and in Event Viewer:

1. Right-click Start.
2. Select Event Viewer.
3. Expand Windows Logs.
4. Select Application.
5. Find the error at the time of the crash.
6. Record the faulting application, faulting module, exception code, and module path.

A faulting-module entry naming ucrtbase_clr0400.dll identifies where Windows observed the failure. It does not prove that the DLL caused the original problem.

If SFC and DISM did not fix it

Use this order:

1. Install all Windows updates and restart.
2. Repair or install the correct x86 and x64 Visual C++ packages.
3. Run the .NET Framework Repair Tool.
4. Repair or reinstall .NET Framework 4.8 or 4.8.1 as appropriate.
5. Repair or verify the affected application.
6. Check Windows Security Protection History.
7. Test without mods, overlays, and plug-ins.
8. Check the file signature and exact path.
9. Try System Restore if the failure began after a recent change.
10. Use Windows 11’s repair reinstall option when available.

If several unrelated .NET or WPF programs fail, prioritize Windows, .NET Framework, and antivirus checks.

If only one program fails and its DLL path is inside the application directory, prioritize application repair, verification, and the application publisher’s support channel.

Information to collect before contacting support

Record the following:

• Exact error text.
• Any status code, including 0xc000012f.
• Application name and version.
• Windows version from winver.
• Whether the program is x86, x64, or ARM64.
• Exact DLL path shown in the dialog or Event Viewer.
• File version and product version.
• Digital signature status.
• Whether x86 and x64 Visual C++ packages are installed.
• Whether other .NET or WPF applications fail.
• Whether the issue began after an update, reinstall, antivirus event, driver change, or mod installation.
• Results from DISM and SFC.
• Whether the problem remains in a clean Windows user profile.

A clean user profile can help distinguish a system-wide runtime problem from damaged per-user application settings. If the program works in a new profile, repair or reset its settings in the original profile before replacing system files.

Frequently asked questions

Is ucrtbase_clr0400.dll safe?

It is a legitimate Microsoft runtime filename. Safety still depends on where the file came from, its path, and its digital signature. A copy in an expected Windows directory with a valid Microsoft signature is substantially more trustworthy than an unsigned copy downloaded from an unknown source.

Do I need to install Visual Studio?

No. Visual Studio may appear in older file metadata, but end users normally need the Microsoft Visual C++ Redistributable and the applicable .NET Framework runtime, not the Visual Studio development environment.

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

On 64-bit Windows, installing both is reasonable when the affected application’s architecture is unknown or multiple programs are involved. A 32-bit application requires x86 even on 64-bit Windows.

Will installing modern .NET fix the error?

Not necessarily. Modern .NET and .NET Framework 4.x are separate technologies. Repair or install the .NET Framework runtime when the affected application requires .NET Framework or WPF.

Should I copy the file from another computer?

Normally no. The other computer may have a different Windows build, architecture, servicing level, or companion runtime. Use official servicing and repair tools instead.

Should I register the DLL?

No. ucrtbase_clr0400.dll is a runtime library, not normally a self-registering ActiveX or OLE component. regsvr32 is not an appropriate repair method.

Why does the error say the module is missing when the file exists?

A dependency may be missing, the architecture may be wrong, or Windows may be blocking a damaged file. Check the exact path, signature, Visual C++ architecture, antivirus history, and Event Viewer entry.

Can a game mod cause this error?

Yes. A mod, overlay, launcher extension, or .NET-based game utility can load the runtime or trigger a crash that surfaces in this module. Test the unmodified application and verify its files before blaming the Windows DLL.

What if only one application still fails?

Repair or reinstall that application from its official source. If Windows, .NET Framework, and Visual C++ checks pass and other programs work, the remaining fault is more likely specific to that application, its settings, or its plug-ins.

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.