ucrtbase.dll Missing on Windows: Fix Apps and Games Safely

The exact startup message is often:

×Worth Installing

Windows Errors? Fix Them Before They Spread

Outbyte PC Repair · freeRepair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFix My PC Now →

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The code execution cannot proceed because ucrtbase.dll was not found. Reinstalling the program may fix this problem.

When ucrtbase.dll is missing, damaged, or mismatched, Windows may refuse to start a game or application. The right repair depends on where the file is expected to be and whether one program or several unrelated programs are affected.

As an Amazon Associate I earn from qualifying purchases.

Which fix applies to you

Use the path and symptoms to choose the correct repair:

• Several unrelated programs fail, and the message refers to C:\Windows\System32\ucrtbase.dll or C:\Windows\SysWOW64\ucrtbase.dll
  Install pending Windows updates, restart, then run DISM followed by SFC.

  #1 Best Overall

  

  Rpanle Tech-Shop-pro USB for Windows 11 Install Recover Repair Restore Boot USB Flash Drive, 64 Bit Systems Home&Professional, Antivirus Protection&Drivers Software, Fix PC, Laptop and Desktop

  • Does Not Fix Hardware Issues - Please Test Your PC hardware to be sure everything passes before buying this USB Windows 11 Software Recovery USB.
  • Make sure your PC is set to the default UEFI Boot mode, in your BIOS Setup menu. Most all PC made after 2013 come with UEFI set up and enabled by Default
  • Does Not Include A KEY CODE, LICENSE OR A COA. Use your Windows KEY to preform the REINSTALLATION option
  • Free tech support

  Buy on Amazon

• Only one game or application fails, and the DLL is inside its installation folder or an AppData folder
  Repair or reinstall that program from its official source.

• The error also mentions VCRUNTIME140.dll, MSVCP140.dll, or api-ms-win-crt-*.dll
  Repair or install the Microsoft Visual C++ Redistributable with the architecture required by the application.

• The affected computer runs Windows 7, Windows 8.1, or an older Windows Server release
  Install the applicable Universal C Runtime update, including Microsoft’s KB2999226 update, and its prerequisites.

  ×Recommended: Crashes or Glitches? A Free Driver Scan Usually Finds the Culprit →Free scan · under a minuteRecommended: Fix Windows Errors and Clear Junk Files in Minutes - Free Scan →Free scan · no reinstall
  Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

• The file disappeared after an antivirus detection or a failed installation
  Check Windows Security Protection History, then prefer a clean reinstall from the application’s official source.

• Event Viewer says ucrtbase.dll is the “faulting module,” but the file exists
  Treat this as an application, driver, plugin, or compatibility crash first. The filename alone does not prove that the Microsoft DLL is corrupt.

Do not begin by downloading a replacement DLL from a random website. A file can have the right name but the wrong architecture, Windows build, dependencies, or security status. It may also leave the actual Visual C++ installation, Windows component store, or application installation broken.

What ucrtbase.dll actually is

ucrtbase.dll is part of Microsoft’s Universal C Runtime, usually abbreviated as UCRT. It supplies standard C runtime functions used by software built with modern Microsoft C and C++ development tools.

Visual Studio 2015 and later toolsets use the Universal CRT rather than maintaining separate, unrelated C runtime generations for each compiler release. Games, launchers, creative applications, utilities, and hardware software may depend on it.

It is:

• A Microsoft Windows component on Windows 10 and later.
• Also included with Windows Server 2016 and later.
• Used by programs built with Microsoft C/C++ tools.
• Sometimes deployed locally beside an application.
• Not a standalone application.
• Not a graphics driver, DirectX component, or .NET runtime.
• Not normally a COM or ActiveX DLL that should be registered with regsvr32.

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

• %WINDIR%\System32\ucrtbase.dll for the 64-bit system copy.
• %WINDIR%\SysWOW64\ucrtbase.dll for the 32-bit system copy.

The directory names are confusing, but this is normal Windows behavior. System32 contains native 64-bit system files on 64-bit Windows, while SysWOW64 contains 32-bit system files.

A 32-bit application therefore needs the x86 runtime even when the operating system itself is 64-bit. A 64-bit application needs the x64 runtime. Many gaming PCs need both because they run a mixture of 32-bit launchers, older games, tools, and modern 64-bit applications.

The separate file ucrtbased.dll is the debug version of the runtime. It is intended for development or Debug builds and is not the normal release runtime that an end user should download.

Read the error before changing anything

The filename is less useful than the complete path and error type.

“The code execution cannot proceed because ucrtbase.dll was not found”

This usually means that Windows could not load the file from the location required by the application.

If the missing file is expected in System32 or SysWOW64, investigate Windows servicing and system-file integrity.

If the application searches its own installation folder, repair or reinstall that application. A program-local copy can be damaged, incomplete, or incompatible with the other runtime files installed beside it.

“ucrtbase.dll is either not designed to run on Windows or it contains an error”

This is commonly called a bad-image error. It can indicate a damaged or mismatched local DLL, but it can also involve companion API-set files or another dependency.

If the path points into a program folder, reinstall that program as a complete unit. Do not copy a different ucrtbase.dll over the existing one.

If the path points into Windows, use Windows Update and the DISM/SFC repair process later in this guide.

“The procedure entry point could not be located”

Older systems may show an API-set error involving a name such as api-ms-win-crt-runtime-l1-1-0.dll and an entry point such as ucrtbase.terminate.

This generally points to an incomplete or mismatched Universal CRT deployment. It does not mean that registering ucrtbase.dll will solve the problem.

Event Viewer names ucrtbase.dll as the faulting module

A crash report may contain:

Faulting module name: ucrtbase.dll

This only tells you where Windows observed the failure while the program was running. The real trigger may be the application, a graphics driver, a plugin, an overlay, corrupted game data, or an incompatibility.

Exception codes such as 0xc0000409 or 0xc0000005 also do not automatically prove that the runtime file is defective.

To inspect the event:

1. Press Win+X.
2. Select Event Viewer.
3. Expand Windows Logs.
4. Select Application.
5. Find the error at the time of the crash.
6. Record the application name, faulting module path, exception code, and fault offset.

The application name and path are often more useful than the faulting-module name.

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

For a program that reports a missing runtime file, the most direct repair is to install or repair the Microsoft Visual C++ Redistributable package required by that program.

Microsoft’s current v14 redistributable is shared by applications built with Visual Studio 2017, 2019, 2022, and newer supported toolsets. Use Microsoft’s latest supported Visual C++ Redistributable downloads rather than a third-party DLL site.

The permanent Microsoft download links are:

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

Choose x86 or x64 correctly

Use the application’s architecture, not the architecture of Windows:

• A 32-bit game or application needs x86.
• A 64-bit game or application needs x64.
• An ARM64 application needs ARM64.
• A 64-bit PC running both old and modern software often needs both x86 and x64.

Installing only x64 will not repair a 32-bit application. Installing both x86 and x64 is appropriate when the PC runs applications of both types.

The program’s installer may bundle the correct package. If it does, rerun the original installer or use its repair option before installing unrelated packages.

Repair an existing package

1. Close the affected program and its launcher.
2. Open Settings.
3. Select Apps.
4. Open Installed apps on Windows 11, or Apps & features on Windows 10.
5. Search for Microsoft Visual C++ Redistributable.
6. Find the x86 or x64 package matching the affected application.
7. Select the three-dot menu on Windows 11, or select the package on Windows 10.
8. Choose Modify.
9. Select Repair in the installer.
10. Restart Windows.
11. Start the affected program again.

If the Settings entry does not provide a repair option, open:

Control Panel → Programs → Programs and Features

Right-click the relevant Microsoft Visual C++ Redistributable package, choose Change or Repair, and follow the installer.

Install the package when it is missing

Download the matching package from Microsoft, close running applications, and run the installer as administrator if necessary.

After installation:

1. Restart Windows.
2. Start the affected program.
3. If it still fails, check whether the error names a different runtime or a program-local copy.
4. If only the 32-bit version fails, install or repair x86 even if x64 is already installed.
5. If only the 64-bit version fails, install or repair x64.

Several Visual C++ Redistributables can remain installed side by side. Do not remove every older package simply because a newer one is present. Older applications may depend on older runtime generations.

If the redistributable installer fails

Microsoft recommends checking Windows updates, running the installer as administrator, and reviewing its logs in %TEMP%.

Try this order:

1. Restart Windows.
2. Install all pending Windows updates.
3. Temporarily close other installers and hardware-management utilities.
4. Right-click the redistributable installer and choose Run as administrator.
5. Check %TEMP% for Visual C++ installer logs if the installation fails.
6. Note any installer code, including codes such as 1603, 1612, or 1714.
7. Repair Windows components using the DISM and SFC steps below.
8. Run the redistributable installer again.

If the application carries its own runtime files, repairing the redistributable may not replace the broken local copy. In that situation, repair or reinstall the application itself.

Fix 2: Update Windows, then repair the Windows component store

Use this path when the error points to System32 or SysWOW64, when several unrelated programs fail, or when Windows reports that a system file is missing or damaged.

The UCRT is a Windows component on Windows 10 and later. Windows servicing, rather than a random DLL download, is the correct way to restore it.

Install pending Windows updates

On Windows 11:

1. Open Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install all available updates.
5. Restart when prompted.
6. Return to Windows Update and check again until no required updates remain.

On Windows 10:

1. Open Settings.
2. Select Update & Security.
3. Select Windows Update.
4. Choose Check for updates.
5. Install the available updates.
6. Restart Windows.

Try the affected application after restarting. If the error remains, continue with DISM and SFC.

Run DISM before SFC

Open an elevated Command Prompt:

1. Press the Windows key.
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

Wait for the operation to finish. Do not close the window just because progress appears to pause.

After DISM completes successfully, run:

sfc /scannow

DISM repairs the Windows component store that SFC uses as a source for replacement files. Running SFC first can leave it without a healthy source for the repair.

How to interpret SFC

Useful results include:

• Windows Resource Protection did not find any integrity violations
  Windows did not find damaged protected system files. Continue with application, redistributable, driver, or dependency troubleshooting if the error remains.

• Windows Resource Protection found corrupt files and successfully repaired them
  Restart Windows and test the program again.

  ×Worth Installing

  PC Slower Than It Used to Be?

  Outbyte PC Repair · freeA free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Run a Free PC Scan →
  Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

• Windows Resource Protection found corrupt files but was unable to fix some of them
  Run DISM again, restart, and run SFC again. If the issue remains, extract the SFC details with:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

The resulting sfcdetails.txt file will be placed on the desktop.

Do not select a replacement based only on the DLL’s file size. The correct file must match the Windows build, architecture, servicing state, and companion files.

Repeating SFC and DISM without knowing what changed can make troubleshooting tedious. I recommend Outbyte PC Repair as an optional way to scan for the Windows issues involved; its free scan shows what it finds, while repair is handled by the full version, and it is not required when the manual Microsoft commands resolve the problem.

If DISM reports that it cannot find source files

A failed DISM repair can indicate a deeper Windows servicing problem, unavailable update files, or broader corruption. Record the exact DISM message, restart, install pending updates, and try the command again.

If Windows still cannot repair itself:

• Check whether other Windows components are failing.
• Investigate unexpected disk errors.
• Use System Restore if the issue began after a recent change.
• Consider an in-place Windows repair or another official recovery option.
• Do not download individual system DLLs from unverified sources.

Microsoft’s recovery options for Windows explain the available repair paths.

Fix 3: Repair or reinstall the affected game or application

If one program fails while everything else works, and the reported DLL path is inside the program folder, the application installation is the leading suspect.

A local copy may have been:

• Interrupted during installation.
• Removed by antivirus software.
• Updated without its companion API-set files.
• Replaced by an incompatible version.
• Damaged after a failed patch.
• Left behind by an incomplete uninstall.

Use Windows app repair

On Windows 11:

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

On Windows 10:

1. Open Settings.
2. Select Apps.
3. Select Apps & features.
4. Select the affected application.
5. Choose Advanced options.
6. Select Repair.

Repair normally preserves application data. If Repair is unavailable or does not help, use the application’s own repair feature or reinstall it.

Reinstall from the official source

Before uninstalling, check whether the program stores saves, profiles, mods, screenshots, or configuration files in an AppData folder. Back up important data when the application does not synchronize it automatically.

Then:

1. Uninstall the affected program through Settings → Apps or Control Panel → Programs and Features.
2. Restart Windows.
3. Download the installer from the original software vendor or use the original launcher.
4. Install the application again.
5. Allow its bundled prerequisites to install.
6. Start the program before restoring mods, overlays, injectors, or custom plugins.

For OneDrive, Microsoft provides an official OneDrive reinstall procedure.

For a game, use the launcher’s Verify, Repair, or Scan and repair command before deleting installation files. This replaces changed or damaged game files while usually preserving saved data.

If reinstalling the application restores the program, the problem was most likely its local installation rather than the central Windows copy of ucrtbase.dll.

Fix 4: Repair game files and remove add-ons temporarily

A crash that names ucrtbase.dll can still be caused by damaged game data or third-party code running inside the game.

Before changing Windows system files:

1. Open the game launcher.
2. Find the affected game in the library.
3. Open the game’s menu.
4. Choose Verify, Repair, or the equivalent integrity-checking command.
5. Wait for the scan to finish.
6. Restart the launcher.
7. Test the game without mods, reshade injectors, overlays, or unofficial plugins.

Temporarily disable overlays from chat clients, graphics utilities, recording software, and performance monitors. These programs inject code into games and can turn an application bug into a crash reported through a runtime DLL.

If the game works without modifications, add them back one at a time. The first modification that recreates the crash is the most useful lead.

Fix 5: Check antivirus quarantine

An antivirus product can remove or quarantine a file from an application installation. This is especially relevant when the error appeared immediately after installing, updating, or launching a program.

In Windows Security:

1. Open Windows Security from the Start menu.
2. Select Virus & threat protection.
3. Select Protection history.
4. Review detections around the time the DLL disappeared.
5. Expand a detection to view its path and status.

If the file belonged to a trusted application, verify:

• The program came from its official source.
• The installation path is expected.
• The application publisher and digital signature are valid.
• The detection is associated with the current installer or update.

Windows Security may offer Restore, but Microsoft warns that restoring a detected threat can cause it to be detected again. Reinstalling the application from its official source is safer when the file’s origin is uncertain.

Do not permanently disable antivirus protection to force an application to start. If a trusted file is repeatedly detected, submit the detection to the security vendor and contact the application vendor.

Fix 6: Install the correct legacy Universal CRT update

Windows 7 SP1, Windows 8.1, Windows Server 2008 R2, and Windows Server 2012-era systems do not receive the UCRT in the same way as Windows 10 and later.

If an older application explicitly requests the Universal CRT, install the applicable update and prerequisites from Microsoft’s Universal C Runtime update information.

KB2999226 is the important update commonly associated with this error. Microsoft also documents KB3118401 as a later UCRT update in its deployment guidance.

After installing the applicable package:

1. Restart Windows.
2. Install the matching Visual C++ Redistributable if the application requires it.
3. Start the affected program again.
4. If the installer reports missing prerequisites, follow the requirements on Microsoft’s update page.

Do not install a current redistributable package while assuming it supports every legacy Windows version. Current runtime support is limited to supported operating systems, while older systems need the appropriate UCRT servicing path.

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

Fix 7: Update or roll back graphics and chipset drivers

Use this path for crashes rather than straightforward “file not found” messages, especially when Event Viewer identifies ucrtbase.dll as the faulting module.

Start with the graphics driver because games frequently exercise the graphics stack immediately before a crash.

Update through Device Manager

1. Press Win+X.
2. Select Device Manager.
3. Expand Display adapters.
4. Right-click the graphics device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart Windows if a driver is installed.

Repeat the process for relevant entries under:

• System devices
• Network adapters
• Sound, video and game controllers

Device Manager may not provide the newest driver for every system. If the crash began after a graphics driver update, open the device’s Properties, select the Driver tab, and use Roll Back Driver when that option is available.

You can also use the support page for the graphics card, laptop, or motherboard manufacturer. Install only drivers intended for the exact hardware and Windows version.

Manually checking graphics, chipset, audio, and storage drivers can mean hunting through several hardware pages and guessing which version is stale. I recommend Outbyte Driver Updater as an optional way to scan for outdated drivers; its free scan shows what it finds, while driver installation is handled by the full version.

After updating drivers, test the application without overlays and custom plugins. If the problem began after a driver change, rollback is often more informative than installing several new versions in succession.

Fix 8: Use System Restore after a recent system change

System Restore is useful when the error started immediately after a driver, update, application, or prerequisite installation.

1. Press Win+R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select an appropriate restore point.
3. Choose Scan for affected programs if available.
4. Review the applications and drivers that will be changed.
5. Start the restore.
6. Allow Windows to restart.

System Restore normally rolls back system files, registry settings, drivers, updates, and installed programs without changing personal files. It does not replace a current backup and does not guarantee that an application-local DLL will be repaired.

Test the affected program after Windows returns. If the problem remains, continue with application repair and the official recovery options.

Do not use regsvr32 for ucrtbase.dll

Do not run:

regsvr32 ucrtbase.dll

regsvr32 is intended for DLLs that expose the COM registration entry point required by the tool. ucrtbase.dll is a runtime library, not a normal self-registering COM component.

The typical result is an error similar to:

The module “ucrtbase.dll” was loaded but the entry-point DllRegisterServer was not found.

Running the command does not repair the runtime. If you already tried it, move on to Windows servicing, Visual C++ repair, or application reinstallation.

Do not enable random Windows Features

Windows Features do not provide a general installation route for ucrtbase.dll.

To inspect the feature list:

1. Press Win+R.
2. Type:

optionalfeatures

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

Do not enable unrelated features such as legacy DirectPlay, .NET components, or media features unless the application’s own error specifically requires them. DirectX, .NET, and optional Windows features do not own the Universal C Runtime.

If an application needs a legacy feature as well as the UCRT, install that feature separately, but keep the runtime repair path separate.

Why manually copying the DLL is unsafe

Copying ucrtbase.dll from another computer or download site can fail because:

• The file may be the wrong architecture.
• It may belong to a different Windows build.
• It may require companion API-set files.
• It may not match the application’s runtime package.
• It bypasses Windows servicing.
• It may be tampered with.
• It can hide the real cause until another component fails.

The supported approach is to repair Windows, install the matching Visual C++ Redistributable, or reinstall the application that owns the local copy.

Microsoft does describe controlled local deployment for developers using the complete architecture-specific UCRT set. That is different from copying one DLL into System32, SysWOW64, or a game folder. Local deployment is not the recommended general-purpose repair method.

Advanced cases

The file exists, but Windows still says it is missing

A missing dependency can produce a misleading error naming ucrtbase.dll. The file may exist while another API-set or Visual C++ dependency is unavailable.

Check:

• The full error text.
• The path Windows names.
• Whether the failure affects one application or many.
• Whether the application is 32-bit or 64-bit.
• Whether other files such as VCRUNTIME140.dll or MSVCP140.dll are mentioned.
• Whether the file is in the system directory or application directory.

Repair the correct package rather than replacing the named file blindly.

A new Windows user profile works

This points toward a profile-local installation, AppData cache, startup entry, permissions issue, or per-user application file. It does not automatically prove that the system UCRT is damaged.

Compare the application paths between profiles and repair or reinstall the application. Also check whether the program creates a different configuration, cache, or plugin set for each user.

Several Visual C++ versions are installed

That is normal. Older runtime packages remain installed because different applications may require them. Visual Studio 2015 and later toolsets share the v14 runtime, but this does not mean every older package is unnecessary.

Remove a redistributable only when you know which application installed it and that the application no longer requires it.

The issue began after DirectX or another prerequisite installer

Do not assume the prerequisite owns ucrtbase.dll. Check whether the installer was interrupted, whether the application’s local files changed, and whether the correct Visual C++ package was installed.

Use Windows Update and DISM/SFC for system paths, and repair the application for local paths.

The issue persists after every normal repair

Collect the following before contacting the application vendor:

• Full error text.
• Affected executable.
• Full DLL path.
• Windows edition and build.
• Application architecture.
• Event Viewer application error.
• Exception code.
• DISM result.
• SFC result.
• Whether one program or several programs fail.
• Recent driver, antivirus, update, or disk-repair events.
• Whether the program works without mods, overlays, or plugins.

Then:

1. Reproduce the problem with all modifications disabled.
2. Repair or reinstall the application.
3. Update or roll back the graphics and chipset drivers.
4. Check the application vendor’s known issues.
5. Use System Restore if a suitable restore point exists.
6. Use an in-place Windows repair or official recovery option if Windows components remain damaged.

Prevention

Keep the runtime installation healthy by following a few practical rules:

• Install Windows updates before troubleshooting system DLL errors.
• Let game and application installers complete without interruption.
• Keep both x86 and x64 Visual C++ packages when the PC runs both application types.
• Do not remove redistributables indiscriminately.
• Use official installers rather than DLL download sites.
• Keep graphics and chipset drivers appropriate for the hardware.
• Verify game files after failed patches or unexpected shutdowns.
• Treat antivirus quarantine events as evidence to investigate, not as proof that the DLL is safe to restore.
• Keep backups of saves and important application data before reinstalling.
• Avoid mixing DLL files from different Windows builds.
• Do not use regsvr32 on runtime libraries.

Quick diagnostic checklist

Before making another change, confirm:

• Does the error say not found, bad image, or faulting module?
• Is the path under System32, SysWOW64, the application folder, or AppData?
• Does one program fail or do several unrelated programs fail?
• Is the application 32-bit, 64-bit, or ARM64?
• Have Windows updates been installed and the PC restarted?
• Has DISM completed before SFC was run?
• Is the matching x86, x64, or ARM64 Visual C++ package installed?
• Has the application been repaired or reinstalled from its official source?
• Did antivirus quarantine the file?
• Did the crash begin after a driver, update, overlay, plugin, or mod change?
• Are you confusing ucrtbase.dll with the debug-only ucrtbased.dll?
• Have you avoided random DLL downloads and regsvr32?

The filename alone does not identify the cause. The path, application architecture, error wording, and number of affected programs determine whether the correct fix is Windows servicing, Visual C++ repair, application reinstallation, a legacy UCRT update, antivirus recovery, or driver troubleshooting.

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.