libuv.dll Not Found on Windows: Trace the App and Fix It

Start with this quick checklist

Before replacing anything, record:

• The application or game named in the error
• The full path to its executable, if shown
• Whether the error appears at launch, after an update, or during installation
• Whether the application is 32-bit, 64-bit, or ARM64
• Whether libuv.dll exists beside the application’s .exe file
• Whether the message also names VCRUNTIME140.dll, MSVCP140.dll, ucrtbase.dll, or another file
• Whether antivirus software recently quarantined the file

libuv.dll is a Windows DLL built from libuv, an open-source library used by Node.js and many other applications. It supplies functions for asynchronous networking, files, timers, processes, threads, and event-loop operations.

It is not a Windows system component. It normally belongs to the application that installed it and is usually stored beside that program or inside its runtime directory. There is no single libuv.dll that works for every application. Builds can differ by application, architecture, packaging, and dependency requirements.

As an Amazon Associate I earn from qualifying purchases.

Do not download a random copy from a DLL website, copy it into System32, or register it with regsvr32. A random file may contain malware, use the wrong architecture, be incompatible with the application, or leave the real installation problem unresolved.

1. Repair or verify the application first

An incomplete, damaged, or incorrectly updated application installation is the most likely cause.

For a regular Windows application

1. Open Settings.
2. Select Apps.
3. Open Installed apps.
4. Find the application named in the error.
5. Select the three-dot menu beside it.
6. Choose Advanced options, if available.
7. Select Repair.
8. Start the application again.

Windows may repair the program without removing its settings. If Repair is unavailable or does not work, return to the same screen and choose Reset only if you understand that it may remove application data.

If the application has its own installer, updater, or repair option, use that instead. Download the installer only from the application’s official publisher. Close the program first, then reinstall it over the existing installation or uninstall it and install a fresh copy, following the publisher’s instructions.

For a game or launcher-managed program

Open the launcher and look for a menu named Verify files, Verify integrity, Repair, or Scan and repair. The exact wording varies by launcher.

Allow the check to finish, then restart Windows and launch the game again. This process can restore the application’s matching native files without placing them in a global Windows folder.

Check the application folder

Right-click the application shortcut and choose Open file location. If that opens a shortcut folder, right-click the shortcut again, choose Properties, and inspect the Target field.

Look for libuv.dll in the same folder as the executable or in a clearly related runtime directory. If it is absent, the application installation or deployment is incomplete. Repairing or reinstalling that application is safer than copying a file from another computer.

If libuv.dll is present but Windows still reports that the module cannot be found, continue to the dependency checks below.

2. Match the application architecture

A 32-bit application needs a compatible 32-bit native library. A 64-bit application needs a 64-bit build. ARM64 applications have their own compatibility requirements.

Do not choose a replacement based on the file’s size or on a version listed by a third-party file index. Resource metadata sometimes shown for this filename, including 1.0.2.0 or 0.0.0.0, is not a universal libuv release identifier. The official libuv project uses its own release numbering, and applications can package different builds.

To check whether a program is 32-bit or 64-bit:

1. Open Task Manager with Ctrl + Shift + Esc.
2. Select Details.
3. Right-click a column heading and choose Select columns.
4. Enable Platform, if that column is available.
5. Find the application process.

Some Windows versions display a 32-bit process with a suffix such as *32. For a more reliable answer, check the application’s documentation or installation package.

A message such as Bad Image, error 0xc000007b, or “not designed to run on Windows” can indicate an architecture mismatch or a corrupted binary. Reinstall the complete application using its official installer rather than replacing only libuv.dll.

3. Repair a missing Microsoft Visual C++ dependency

A file can be present while Windows reports “The specified module could not be found.” The missing item may be a dependency loaded by libuv.dll, not libuv.dll itself.

Pay particular attention if the error names:

• VCRUNTIME140.dll
• MSVCP140.dll
• ucrtbase.dll

Install the Microsoft Visual C++ Redistributable that matches the application:

• Microsoft Visual C++ Redistributable downloads
• Official x86 package for a 32-bit application
• Official x64 package for a 64-bit application
• Official ARM64 package where applicable

Run the installer, choose Repair if offered, and restart Windows. Then launch the affected program.

Installing Visual C++ does not install libuv.dll. It repairs a runtime dependency that an application-owned DLL may need. If the same error remains and no runtime file is named, repair the application itself.

Older applications may require an older Visual C++ Redistributable rather than the current v14 package. Do not uninstall existing redistributables simply because a newer one is available. Older supported runtimes can remain installed side by side.

4. Check antivirus quarantine

Security software may remove or quarantine a native DLL after an application update or installation.

In Windows Security:

1. Open Start and search for Windows Security.
2. Select Virus & threat protection.
3. Choose Protection history.
4. Look for an event matching the application directory or libuv.dll.
5. Confirm the file path and the application’s publisher before taking action.

Restore or allow the file only when the application came from a legitimate publisher and the path is correct. If the file was downloaded from an unknown source, do not restore it. Uninstall the application and reinstall it from the official installer.

Protection History entries are retained for a limited period, so an older quarantine event may no longer appear. If the file disappears repeatedly after reinstalling, check the security product’s quarantine and exclusions, update its definitions, and contact the application publisher before creating an exclusion.

5. Fix older .NET and ASP.NET Core deployments

Older ASP.NET Core applications could use the Kestrel Libuv transport and the Libuv package. A deployment may fail when its native asset was not restored, was published for the wrong runtime identifier, or was left out of the deployed output.

For a project that still requires the old transport, restore and publish the complete application for its actual architecture. For example:

dotnet restore
dotnet publish -c Release -r win-x64

Use win-x86 for a 32-bit deployment or the appropriate runtime identifier for the target system. Copy the complete publish output, not only the main executable or managed assemblies.

For maintained ASP.NET Core projects, the old Libuv transport is obsolete. Microsoft deprecated it in ASP.NET Core 5, and ASP.NET Core 7 removed the package and its libuv.dll dependency. Remove the obsolete Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv package and UseLibuv configuration, then use the default Sockets transport as directed by Microsoft’s ASP.NET Core Libuv removal guidance.

If you are consuming the application rather than developing it, do not edit its files. Install a build supplied by the developer that targets the correct runtime.

6. Repair Windows components only when other programs are also failing

System repair is lower priority because Windows normally does not supply application-owned libuv.dll. Use it when multiple programs show unexplained launch failures or Windows itself reports corrupted components.

Open Command Prompt as administrator:

1. Open Start.
2. Type cmd.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Run these commands in order:

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Wait for each command to finish before running the next. Restart Windows afterward.

DISM repairs the Windows component store. SFC checks protected Windows system files. Neither command will normally recreate a missing DLL belonging to a third-party application. If the application still reports libuv.dll, return to its repair or reinstall process.

When manually repeating DISM and SFC becomes guesswork, Outbyte PC Repair can scan for reported problems and identify what needs attention; the repair function is available in the full version, but reinstalling the application remains the definitive fix for an app-owned libuv.dll.

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

7. Consider drivers only when the owning product points there

Driver repair is not a general solution for libuv.dll. It becomes relevant when the error comes from a driver-dependent product, development environment, hardware utility, or game that has recently changed alongside a graphics or device driver.

To update a driver manually:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category, such as Display adapters or Network adapters.
4. Right-click the device.
5. Choose Update driver.
6. Select Search automatically for drivers.
7. Restart Windows if prompted.

Prefer the hardware manufacturer’s official driver when Device Manager reports that no newer driver is available. Do not install a driver simply because it is listed as outdated by an unrelated utility.

When checking many devices manually becomes impractical, Outbyte Driver Updater can scan and show which drivers need attention; the driver installation feature is handled by the full version, and it is not a substitute for reinstalling the application that owns libuv.dll.

8. Scan for malware or undo a recent system change

If the error began after an unknown installer, suspicious download, or unexplained file deletion:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Choose Scan options.
4. Run a Full scan.
5. If necessary, use Microsoft Defender Offline scan.

Microsoft describes the available scan choices in its Windows Security virus and threat protection guidance.

If the failure clearly started after an application, driver, or system change, System Restore may help:

1. Press Win + R.
2. Type rstrui.exe.
3. Press Enter.
4. Choose a restore point from before the problem.
5. Select Scan for affected programs.
6. Review the changes and complete the restore if appropriate.

System Restore does not replace a missing application package in every case. It is a fallback for a clearly timed system change, not a reason to download a replacement DLL.

What not to do

Do not copy libuv.dll into System32 or SysWOW64

The application directory is searched before system locations. Copying a private application DLL into a global folder can create version conflicts, DLL hijacking risk, and failures in unrelated programs.

If you are an administrator or developer with a verified copy from the same installer or package, placing it back in the application’s own directory can be appropriate. A random download is not.

Do not use regsvr32 for libuv.dll

regsvr32 is intended for self-registering COM, OLE, or ActiveX components. A normal libuv runtime DLL is not a COM server.

This command is not a repair:

regsvr32 libuv.dll

It commonly produces an error saying that DllRegisterServer was not found. Repair the application or its dependencies instead.

Do not install unrelated Windows Features

DirectX, .NET, and optional Windows Features do not generally restore libuv.dll. Install them only when the application separately identifies a missing DirectX, .NET, or Windows component.

Frequently asked questions

Is libuv.dll a Windows system file?

No. It is an application dependency built from the cross-platform libuv library. It is normally installed by a specific application, not by Windows itself.

Does Node.js use libuv?

Yes. Node.js uses libuv internally for its event loop and asynchronous operations. Repair Node.js through its official installer rather than downloading a standalone DLL.

Why does Windows say the module is missing when the file is present?

A dependency of libuv.dll may be missing, the file may be corrupted, or the application may be loading an incompatible architecture. Check the complete error for a named Visual C++ runtime and repair the application.

Can one copy work for every program?

No. Applications may use different builds, packaging methods, architectures, and runtime dependencies.

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

Install the architecture required by the application. A 32-bit application needs x86 even on 64-bit Windows. Install x64 for a 64-bit application, and ARM64 where applicable.

What if only one Windows user account has the problem?

Repair the application first, then test it under another account. If it works there, the original profile may have damaged settings or permissions. Creating a new profile is a diagnostic step, not a replacement for fixing the application installation.

What information should I give the developer?

Provide the complete error, executable path, application and Windows versions, application architecture, whether libuv.dll is present, and any named dependent DLL. The application publisher owns the correct build and packaging for its program.

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.