wintrust.dll Is Missing: Fixes That Work on Windows 11 and 10

wintrust.dll is a protected Microsoft Windows system library, not a standalone runtime that you should download from a DLL website. It provides trust and Authenticode-signature verification functions used by Windows and applications, including the documented WinVerifyTrust API. (Microsoft Learn)

The safest first repair is to install pending Windows updates, restart, and run DISM followed by SFC from an elevated Command Prompt. Do not copy a replacement file into System32, run regsvr32 wintrust.dll, or reinstall DirectX merely because an error mentions this file.

What wintrust.dll does

Windows and applications use wintrust.dll to check whether files, installers, drivers, and other code can be trusted. It is associated with the Microsoft Trust Verification APIs and is part of the Windows operating system.

It is not:

• A Visual C++ runtime
• A DirectX redistributable
• A .NET runtime
• A game-specific middleware file
• A graphics, chipset, printer, or other hardware driver

Microsoft supplies it through Windows servicing and the protected component store. A damaged or missing copy can result from failed servicing, malware, antivirus quarantine, storage errors, an interrupted shutdown, or an application loading an incorrect private DLL.

On ordinary 64-bit Windows, the expected locations are:

C:\Windows\System32\wintrust.dll
C:\Windows\SysWOW64\wintrust.dll

System32 contains the native 64-bit system files on 64-bit Windows. SysWOW64 contains the 32-bit versions used by 32-bit applications. This naming is counterintuitive but is part of Windows file-system redirection. (Microsoft Learn)

On 32-bit Windows, the relevant system copy is normally in System32.

There is no universal “latest wintrust.dll” version or file size. The correct file depends on the Windows release, build, servicing branch, and architecture. Microsoft update tables show different architecture-specific versions and sizes for different Windows builds, so choosing a replacement by file size is unsafe. (Microsoft file information)

Error messages you may see

The exact wording depends on Windows, the application, the file architecture, and the point at which loading fails. Common messages include:

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

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

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

Error loading wintrust.dll.
The specified module could not be found.

C:\Windows\System32\wintrust.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 procedure entry point [function name] could not be located
in the dynamic link library C:\Windows\System32\WINTRUST.dll.

The path in the message is important:

• C:\Windows\System32\wintrust.dll usually points toward a Windows component, servicing, quarantine, malware, or storage problem.
• C:\Windows\SysWOW64\wintrust.dll can indicate a problem affecting the 32-bit Windows copy.
• C:\Program Files\... or a game directory may indicate an application-bundled DLL, an incompatible private copy, or DLL hijacking.
• “The specified module could not be found” can mean that a dependency is missing, even when wintrust.dll itself exists.

Windows searches several locations when loading a DLL. An application-folder copy can be found before the genuine system copy, depending on the loader rules and how the application starts. (Microsoft Learn)

Fix 1: Install Windows updates and restart

Time needed: a few minutes, plus the time required for Windows to restart.

A pending update can contain the repaired system component or correct a servicing problem that caused the error.

1. Open Start.
2. Select Settings.
3. Open Windows Update.
4. Select Check for updates.
5. Choose Download & install if updates are offered.
6. Restart Windows when prompted.
7. Open the affected application again.

The official Windows Update path is documented by Microsoft. (Microsoft Support)

If Windows Update reports an error, remains stuck, or installs successfully but the same message returns, continue with DISM and SFC. Do not treat a failed update as proof that the DLL itself needs to be downloaded manually.

Fix 2: Repair Windows with DISM and SFC

Time needed: several minutes, sometimes followed by a restart.

This is the main repair for a missing or corrupted copy in System32 or SysWOW64. DISM repairs the Windows component store, while SFC checks protected system files and restores valid copies from that store.

Microsoft recommends running DISM before SFC.

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes if User Account Control appears.
6. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait until DISM finishes.
2. Run:

sfc /scannow

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

Microsoft’s supported sequence is documented in its System File Checker guidance. (Microsoft Support)

The SFC result tells you what to do next:

• Windows Resource Protection did not find any integrity violations: SFC did not detect protected-file corruption. Continue with the application and dependency checks below.
• 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 if necessary, inspect the logs, and use a matching repair source or Windows repair reinstall.
• Windows Resource Protection could not start the repair service: restart Windows, open Command Prompt as administrator again, and repeat the process.

Repeating SFC without repairing the component store usually does not address the underlying problem. If you prefer help identifying which files are damaged rather than manually interpreting DISM and SFC output, Outbyte PC Repair can scan for the problem and show what needs attention; its free scan identifies issues, while repair is performed by the full version. It is optional, and Windows Update, DISM, and SFC remain the supported repair route.

Fix 3: Check whether the correct file exists and is signed

Time needed: a few minutes.

A file’s presence does not prove that it is the correct file. Check its path, architecture-related location, version information, and Authenticode signature.

Open PowerShell and run:

Get-Item "$env:windir\System32\wintrust.dll",
         "$env:windir\SysWOW64\wintrust.dll" -ErrorAction SilentlyContinue |
  Select-Object FullName, Length,
    @{Name="FileVersion";Expression={$_.VersionInfo.FileVersion}}

On 64-bit Windows, you may see two results. On 32-bit Windows, the SysWOW64 path may not exist.

To check the native Windows copy’s signature, run:

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

A genuine protected Windows file should be in the Windows system directory and should have a valid Microsoft signature. Microsoft documents Get-AuthenticodeSignature for checking Authenticode signatures. (Microsoft Learn)

A suspicious result includes:

• The file is in an application or temporary folder instead of the Windows directory.
• The signature status is not valid.
• The file keeps changing after repair.
• Multiple unrelated Windows files are also unsigned or damaged.
• The application folder contains its own wintrust.dll even though the program should use Windows’ copy.

Do not delete or overwrite a system DLL based only on a version number. If the file is in the correct Windows directory but appears damaged, use targeted SFC checks.

To verify the native file only:

sfc /verifyfile=C:\Windows\System32\wintrust.dll

To repair the native file only:

sfc /scanfile=C:\Windows\System32\wintrust.dll

Microsoft documents /verifyfile and /scanfile as targeted SFC options. (Microsoft Learn)

If the affected program is 32-bit, do not assume that repairing only the System32 copy addresses the problem. The program may be using the 32-bit copy in SysWOW64, or it may be loading a private copy from its own directory.

Fix 4: Check Windows Security quarantine

Time needed: a few minutes for the history check, longer for a full scan.

Antivirus software can quarantine a file after a detection or false positive. Malware can also damage, replace, or repeatedly remove system files.

1. Open Start.
2. Type Windows Security.
3. Open the app.
4. Select Virus & threat protection.
5. Select Protection history.
6. Look for an entry involving wintrust.dll.
7. Expand the entry and inspect its location, detection name, and action.

Do not restore the file merely because a program will not start. Microsoft notes that restoring a quarantined item puts it back, but Defender may detect it again. (Microsoft Support)

If malware is plausible:

1. Return to Virus & threat protection.
2. Select Scan options.
3. Run a Full scan.
4. If the system still behaves suspiciously, select Microsoft Defender Offline scan.
5. Save open work before starting the offline scan.

Use DISM and SFC to restore the protected Windows copy after the security issue has been addressed. If the file was quarantined from System32 or SysWOW64, verify the file and system state before considering any restoration.

Warning signs that require more than a simple restore include:

• An invalid Microsoft signature
• An unexpected file path
• Disabled security services
• Repeated file replacement after SFC repairs it
• Several unrelated Windows programs failing
• Browser, account, or system settings changing without permission

If Windows cannot be trusted after malware cleanup, back up personal files and use Windows recovery or a clean installation from official Microsoft media. Microsoft’s recovery guidance covers the available recovery paths. (Microsoft Support)

Fix 5: Repair or reinstall one affected application

Time needed: a few minutes for Repair, longer for a reinstall.

If only one program fails and both Windows copies exist and have valid signatures, the application may be damaged or may contain an incompatible private DLL.

Try the built-in repair option:

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

If Repair is unavailable or does not help, use Reset where appropriate. Reset can remove application data and settings, so check the program’s own documentation first.

If the error remains:

1. Uninstall the affected application from Settings → Apps → Installed apps.
2. Restart Windows.
3. Download the installer from the application publisher’s official source.
4. Install the correct build for your Windows architecture.
5. Test the program before adding optional plugins or modifications.

For games, use the launcher’s built-in file verification function before reinstalling the entire game. Steam and Epic Games Launcher both provide file-verification options. If verification repeatedly restores or removes the same file, check Windows Security and the game’s installation directory for a conflicting app-local DLL.

Do not replace the Windows copy with a DLL supplied inside a game folder. If the error path points to the game folder, repair the game installation instead.

Fix 6: Check 32-bit and 64-bit compatibility

Time needed: a few minutes for diagnosis, longer if the application must be reinstalled.

A 32-bit application on 64-bit Windows normally uses the 32-bit system libraries in SysWOW64. A 64-bit application uses the native files in System32.

Architecture problems are more likely when the message mentions:

• A procedure entry point that cannot be found
• A bad image
• A file that is “not designed to run on Windows”
• An application that stopped working immediately after an update
• A program installed from an old or unofficial installer

Check the path in the error dialog and compare it with the application’s architecture. Do not select a DLL based on the largest version number or a matching-looking file size.

Use the application’s current official installer or a build that explicitly supports your Windows version. If the application includes a private wintrust.dll, allow its installer to manage that file. Do not manually move it into System32 or SysWOW64.

A “specified module could not be found” message can also mean that a dependency of the application is missing. In that situation, replacing wintrust.dll will not solve the actual loader failure.

Fix 7: Do not reinstall DirectX, Visual C++, or .NET by default

Time needed: a few minutes to identify the real dependency.

The file name can appear while an installer verifies a signed package, which can make the installer appear to be responsible for the error. That does not mean the installer owns or should reinstall wintrust.dll.

The official DirectX End-User Runtime is named dxwebsetup.exe and installs older side-by-side libraries such as D3DX, XInput, XAudio, XACT, and Managed DirectX. Microsoft says it does not modify the core DirectX runtime included with Windows. (Microsoft Download Center)

The official Visual C++ packages are named:

vc_redist.x86.exe
vc_redist.x64.exe
vc_redist.arm64.exe

They install Microsoft C and C++ runtime libraries, not the Windows trust-verification component. (Microsoft Learn)

If an application separately reports a missing DirectX, Visual C++, or .NET component, install the prerequisite from Microsoft or the application publisher. Do not use that package as a substitute for DISM and SFC.

You can also check optional Windows components:

1. Open Start.
2. Type Windows Features.
3. Select Turn Windows features on or off.
4. Review the features required by the affected application.
5. Enable a feature only when the application’s documentation specifically requires it.
6. Select OK and restart if Windows requests it.

There is no Windows Features checkbox that functions as a general wintrust.dll repair.

Fix 8: Investigate a driver only when the error is device-specific

Time needed: several minutes, plus a restart.

A driver installer may use Windows trust verification, but reinstalling a graphics, chipset, printer, or other driver will not normally restore the Windows trust DLL.

Consider driver repair only when:

• The error appears while installing or starting a specific device.
• Device Manager shows a warning icon.
• The message explicitly names a driver.
• The problem affects one device rather than ordinary Windows programs.

To reinstall a device through Device Manager:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant category.
4. Right-click the affected device.
5. Select Uninstall device.
6. Confirm the uninstall.
7. Restart Windows.
8. Install the replacement driver through Windows Update or the hardware manufacturer’s official support channel.

Microsoft documents the Device Manager driver process here. (Microsoft Support)

If manually identifying stale drivers across several devices is the problem, Outbyte Driver Updater can scan and show which drivers need attention; its free scan identifies the issues, while driver installation is handled by the full version. It is optional, and a program-specific wintrust.dll problem still requires repairing or reinstalling that program.

Fix 9: Use System Restore after a recent system change

Time needed: several minutes to review restore points, followed by a restart.

System Restore is useful when the problem began immediately after a Windows update, driver installation, application installation, or other system 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.
5. Review the programs and drivers that will be affected.
6. Select Close.
7. Select Next, then Finish.
8. Confirm the restore and allow Windows to restart.

System Restore normally preserves personal files, but it rolls back system files, settings, drivers, and installed programs. (Microsoft Support)

If there are no suitable restore points, continue with the repair reinstall options.

Fix 10: Repair Windows when DISM and SFC cannot finish the job

Time needed: longer than the command-line repair and usually requires one or more restarts.

If DISM cannot obtain repair files through Windows Update, use a matching Windows installation source. The source must match the Windows edition, release, architecture, and servicing state closely enough for DISM to use it.

The following path is only a placeholder:

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

Replace C:\RepairSource\Windows with the actual Windows source path. Do not run the command with the placeholder unchanged. Microsoft documents this repair-source process for Windows images. (Microsoft Learn)

Check these logs after a failed repair:

C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\DISM\dism.log

CBS.log records SFC and component-based servicing activity. dism.log records DISM operations and repair errors.

On supported Windows 11 systems, Microsoft provides a simpler repair reinstall:

1. Open Start.
2. Select Settings.
3. Select System.
4. Select Recovery.
5. Find Fix problems using Windows Update.
6. Select Reinstall now.
7. Follow the instructions.

This option reinstalls the current Windows version while preserving apps, files, and settings, but it may be unavailable on managed, older, or otherwise unsupported systems. (Microsoft Support)

If the option is unavailable, use official Windows installation media and choose a supported in-place repair option. Microsoft provides Windows 11 installation and ISO options on its download page. (Microsoft Windows 11 download)

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

Why regsvr32 wintrust.dll is not a fix

Do not run either of these commands as a repair:

regsvr32 wintrust.dll
regsvr32 /u wintrust.dll

regsvr32 is intended for self-registering COM DLLs that export functions such as DllRegisterServer and, for removal, DllUnregisterServer. wintrust.dll is an API and trust-provider library, not a COM component that should be registered this way. (Microsoft regsvr32 documentation, Microsoft DllRegisterServer documentation)

These commands can produce errors such as:

DllRegisterServer was not found

or:

The call to DllRegisterServer failed

Those messages do not mean that registration is the missing repair step.

Why downloading wintrust.dll is unsafe

Random DLL download pages are a poor solution for a protected Windows component. A downloaded file can be:

• The wrong Windows build
• The wrong architecture
• Unsigned or modified
• Malicious
• Missing its matching component-store metadata
• Incompatible with the application or its dependencies

Even a file that makes one error disappear may leave Windows servicing damaged or introduce a different security problem. Manual copying can also overwrite a valid system file with an incorrect one.

Use these supported sources instead:

• Windows Update
• DISM and SFC
• Windows 11’s Reinstall now recovery option when available
• Official Windows installation media
• The affected program’s official installer
• Windows Update or the hardware manufacturer for drivers

Manual copying is appropriate only for a private application DLL when the application vendor explicitly instructs you to use that file. It is not an appropriate method for restoring the Windows copy of wintrust.dll.

Common causes and the matching fix

Likely cause	Clues	Correct response
Corrupted protected Windows file	Several programs fail, or the path is System32 or SysWOW64	Windows Update, DISM, then SFC
Failed Windows servicing	The problem began after an update, and SFC cannot repair files	DISM, logs, matching repair source, or repair reinstall
Antivirus quarantine	Protection History names the file	Scan first, verify the file, then repair with DISM and SFC
Malware or tampering	Invalid signature, unexpected location, repeated re-corruption	Full or Offline scan, followed by Windows repair
Damaged application	Only one program fails and Windows copies are valid	Repair, verify, or reinstall the application
App-local DLL conflict	The path points into a program or game folder	Use the vendor installer and remove private copies only as documented
Architecture mismatch	Entry-point or bad-image error, often after an update	Install the correct application build and do not swap DLLs
Device-specific installer failure	A driver or device is explicitly named	Repair the device through Device Manager and official driver channels

No single cause can be assumed from the filename alone. The error path, the number of affected programs, the signature, and the timing of the failure provide the useful evidence.

FAQ

Is wintrust.dll safe?

A genuine copy in the Windows system directory is a normal Windows component used for trust and signature verification. The name alone does not prove that every copy is safe. Check the path and Authenticode signature, especially if a copy appears in an application folder.

Should I download wintrust.dll?

No. Do not download it from a random DLL website or copy it from another computer. Repair Windows through Windows Update, DISM, and SFC, or use supported Windows recovery media.

Should I register wintrust.dll with regsvr32?

No. wintrust.dll is not a COM self-registering DLL. regsvr32 is not a repair for this file.

Should I reinstall DirectX?

Not just because the error names wintrust.dll. DirectX redistributables provide legacy DirectX side-by-side libraries and do not repair the core Windows trust-verification component.

Should I reinstall Visual C++?

Only if the application separately reports a missing Visual C++ runtime. Visual C++ redistributables install C and C++ runtime libraries, not wintrust.dll.

Could .NET be responsible?

A .NET application can fail for its own missing or damaged runtime, but .NET is not the owner of wintrust.dll. Repair the Windows component first when the error specifically names this file.

Why does Windows say the file is missing when it is visible in System32?

The named file may be present but unusable, incorrectly signed, the wrong architecture, or unable to load because a dependency is missing. The program may also be loading an app-local copy from another directory.

Which copy should a 32-bit program use?

On 64-bit Windows, a 32-bit program normally uses the 32-bit system libraries in SysWOW64. A 64-bit program normally uses the native files in System32. Let Windows and the application’s installer manage the correct copy.

Is the “not designed to run on Windows” message proof of malware?

No. It can result from corruption, a failed update, an architecture mismatch, an incompatible application DLL, or malware. Check the path and signature before deciding what happened.

What if only one game fails?

Verify the game files through its launcher, check whether the error path points inside the game folder, and reinstall the game from its official source if verification does not help. If Windows programs also fail, repair Windows with DISM and SFC.

What if every program fails?

Treat that as a Windows-wide issue. Install updates, run elevated DISM followed by SFC, check Windows Security, and use System Restore or a repair reinstall if the commands cannot restore the component.

Does Windows 10 change the repair process?

The repair commands remain available, but Microsoft ended free Windows 10 updates and security fixes on October 14, 2025. In 2026, persistent component corruption on Windows 10 should also prompt an evaluation of migration to a supported Windows release. (Microsoft Support)

When should I stop troubleshooting and reinstall Windows?

Use a repair reinstall when DISM and SFC cannot restore the component, the file repeatedly becomes corrupted, malware cannot be confidently removed, or several unrelated Windows components are failing. Back up personal files first and use official Microsoft recovery or installation media.

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.