diagperf.dll Missing: Restore Windows Diagnostics Safely

If diagperf.dll is missing, Windows or an application may display “The program can’t start because diagperf.dll is missing from your computer” or “The code execution cannot proceed because diagperf.dll was not found.” The file is a genuine Microsoft Windows component called Microsoft Performance Diagnostics, not a Visual C++, DirectX, .NET, or game-specific DLL.

The safest repair is to update Windows, restart, then run DISM followed by System File Checker. These tools restore protected Windows components without requiring you to download a loose DLL.

As an Amazon Associate I earn from qualifying purchases.

The 60-second answer

diagperf.dll belongs to Windows Diagnostic Infrastructure and the Diagnostic Policy Service. It normally comes from Windows servicing and should be restored through Windows Update, DISM, or SFC.

Try these steps in order:

1. Open Settings > Windows Update and install all available updates.
2. Restart the computer.
3. Open Command Prompt as administrator.
4. Run:

DISM.exe /Online /Cleanup-image /Restorehealth

1. After DISM finishes, run:

sfc /scannow

1. Restart Windows again and test the affected program.

Do not download diagperf.dll from a random DLL website. A loose copy may have the wrong architecture, an incompatible build, malware, or a missing dependency. It may also hide the underlying Windows component-store problem.

What is diagperf.dll?

diagperf.dll is identified as Microsoft Performance Diagnostics. Its publisher and product identity are Microsoft Corporation and Microsoft Windows Operating System.

It is associated with Windows diagnostics rather than with a particular game or application. Windows Diagnostic Policy Service can use this type of module when detecting and reporting problems with system components, devices, networking, and other Windows functions.

The file may appear in Diagnostic Policy Service events, including records involving svchost.exe_DPS. That does not automatically mean diagperf.dll is damaged. Event Viewer may identify it as a faulting or participating module while another component is the real cause.

There is no single universal “latest” file version for every Windows installation. Windows builds, editions, cumulative updates, language packs, and servicing changes can all affect system files. Windows should therefore supply the replacement copy.

Where should diagperf.dll be located?

On a 64-bit Windows installation, the native 64-bit copy normally belongs here:

%WINDIR%System32diagperf.dll

Usually, that expands to:

C:WindowsSystem32diagperf.dll

On 64-bit Windows, 32-bit system components normally use:

%WINDIR%SysWOW64diagperf.dll

The names can be confusing. System32 contains native 64-bit system files on 64-bit Windows, while SysWOW64 contains 32-bit system files. Windows uses file-system redirection so that 32-bit applications see the appropriate system location. Microsoft explains this behavior in its File System Redirector documentation.

Do not copy a file from SysWOW64 into System32, or the other way around. Do not copy it into an application folder unless the application’s official repair process specifically requires a private copy.

To check whether the file exists:

1. Press Windows key + E.
2. Click the address bar.
3. Enter %WINDIR%System32.
4. Search for diagperf.dll.
5. If you are using 64-bit Windows, also check %WINDIR%SysWOW64.

The absence of the file is useful evidence, but its presence does not prove that it is healthy. It may be corrupted, the wrong architecture, or unable to load because one of its dependencies is damaged.

What the common errors mean

“The program can’t start because diagperf.dll is missing from your computer”

Windows could not find the DLL in the location expected by the process. The file may have been removed, quarantined, damaged, or made unavailable by a failed update.

“This application has failed to start because diagperf.dll was not found”

This is similar wording from the Windows loader. It does not identify the original cause. Repair Windows first, then repair the application if only one program shows the message.

“Error loading diagperf.dll. The specified module could not be found”

“Specified module” can refer to a dependency required by diagperf.dll, not necessarily the named file itself. If the file exists in the correct system directory, investigate Windows component damage and Event Viewer rather than immediately replacing the DLL.

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

The program stopped before it could run because Windows could not resolve the required module. This can affect startup, a diagnostic utility, or an application that indirectly calls Windows diagnostics.

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

This commonly indicates a corrupted file, wrong architecture, incompatible private copy, or damaged dependency. A manually copied DLL is especially suspicious if the error began after someone placed a file in the application directory.

“Cannot find C:WindowsSystem32diagperf.dll”

The application or Windows component specifically expected the native system path and did not find a usable file there. Do not simply download a replacement. Use Windows servicing tools.

“Failed to load diagperf.dll”

This is a general loading failure. Check whether the issue affects Windows itself, one application, or only a particular event recorded by Diagnostic Policy Service.

Fix 1: Install Windows updates and restart

A partial update, failed upgrade, or damaged component store can remove or leave behind inconsistent system files.

1. Press Windows key + I to open Settings.
2. Select Windows Update.
3. Click Check for updates.
4. Select Download & install for available updates.
5. Restart when Windows requests it.
6. Return to Windows Update and check again until no further updates are offered.
7. Test the program that reported diagperf.dll.

If the error started immediately after an update, complete any pending restart before attempting other repairs. A system can remain in an incomplete servicing state until it reboots.

For Windows 11, check whether the deeper repair option is available:

1. Open Settings.
2. Select System.
3. Select Recovery.
4. Find Fix problems using Windows Update.
5. Click Reinstall now.
6. Follow the prompts and keep the computer connected to power.

Microsoft says this process reinstalls the current Windows version while preserving personal files, installed applications, and settings. The option is not available on every device or servicing configuration. Details are provided in Microsoft’s guide to reinstalling the current Windows version.

Fix 2: Repair Windows with DISM and SFC

This is the most important repair for a missing or corrupted diagperf.dll.

DISM repairs the Windows component store. SFC then uses that repaired source to check and replace protected system files. Microsoft recommends running DISM before SFC in its System File Checker guidance.

Run DISM

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

DISM.exe /Online /Cleanup-image /Restorehealth

1. Press Enter.
2. Wait for the operation to complete.

The scan can appear to pause at a percentage for some time. Do not close the window while it is working.

A successful result normally states that the restore operation completed successfully. If DISM reports that it cannot find repair source files, install pending updates and run the command again. Windows may use Windows Update as its repair source. If Windows Update itself is damaged, an official installation source matching your Windows version and edition may be required.

Run SFC

After DISM finishes:

1. Keep the elevated Command Prompt open.
2. Enter:

sfc /scannow

1. Press Enter.
2. Wait until verification reaches 100 percent.
3. Restart Windows.

SFC may report that it found no integrity violations, repaired corrupted files, or found files it could not repair. If it repaired files, test the affected application after restarting.

If SFC cannot repair everything, do not replace diagperf.dll manually. Check the log at:

%WINDIR%LogsCBSCBS.log

You can also continue with the repair options below.

When manually repeating DISM and SFC becomes difficult to track, Outbyte PC Repair can show what it finds in a scan; its free scan identifies issues, while repair actions are handled by the full version. It is optional, and Microsoft’s DISM and SFC remain the authoritative repair route for a Windows system DLL.

Fix 3: Check antivirus quarantine

Security software may quarantine a system file after a false detection, particularly if the problem appeared after malware removal or a security scan.

In Windows Security:

1. Open the Start menu.
2. Type Windows Security.
3. Open the app.
4. Select Virus & threat protection.
5. Click Protection history.
6. Review recent detections.
7. Open any entry that identifies diagperf.dll.
8. Check its path and detection details before taking action.

Restore or allow the file only if you have confirmed that it is the genuine Microsoft file in the expected Windows directory and the detection is a false positive. Do not restore a copy from an application folder or an unfamiliar location.

Microsoft’s Protection history documentation explains the available actions. Protection History is time-limited, so an older quarantine event may no longer be visible.

After restoring a legitimate file, update Windows Security and run a full scan. If the file repeatedly disappears, investigate malware, disk errors, or a damaged Windows installation rather than repeatedly restoring it.

Fix 4: Repair the affected application

If the error appears only when launching one program, the application installation may be damaged even when Windows itself is healthy.

For a Microsoft Store application:

1. Open Settings.
2. Select Apps.
3. Select Installed apps.
4. Find the affected application.
5. Click the three-dot menu.
6. Select Advanced options.
7. Choose Repair.
8. Test the application.
9. If Repair does not help, choose Reset if available.

For a traditional desktop program, open its installer or uninstall panel and look for Repair, Modify, or Change. If no repair option exists, uninstall and reinstall it from the publisher’s official source.

For a game, use the launcher’s Verify files, Verify integrity, or Repair command. Do not obtain diagperf.dll from a third-party download page. No particular game or installer is established as the normal distributor of this Windows component.

If the program is 32-bit, it may use the 32-bit Windows view under SysWOW64. A 64-bit program uses the native system view. Copying a 64-bit DLL into a 32-bit program directory can produce a “not designed to run on Windows” or “bad image” message.

Fix 5: Check Windows architecture and remove private DLL copies

A manually added DLL can take precedence over the protected Windows copy because of DLL search order.

Check for diagperf.dll in:

• The folder containing the affected program
• Its launcher folder
• %WINDIR%System32
• %WINDIR%SysWOW64 on 64-bit Windows

If an unfamiliar copy exists in the application directory, do not overwrite it with another download. Rename it temporarily, for example to diagperf.dll.old, then repair the application and Windows. Only remove it after confirming that it was manually added and is not part of the application’s official installation.

Microsoft documents the risks of private DLL copies and redirection in its guidance on DLL redirection and versioning.

Fix 6: Check Diagnostic Policy Service and Event Viewer

Do not delete diagperf.dll because it appears in an Event Viewer record. The file may be listed because it was involved in a crash or diagnostic event, not because it is missing.

To inspect relevant records:

1. Press Windows key + R.
2. Enter:

eventvwr.msc

1. Press Enter.
2. Expand Applications and Services Logs.
3. Expand Microsoft.
4. Expand Windows.
5. Open Diagnosis-DPS.
6. Select Operational.
7. Review events near the time of the error.

Also check Windows Logs > Application for entries mentioning svchost.exe_DPS, diagperf.dll, or a different faulting module.

Record:

• The event date and time
• The application or service involved
• The faulting module
• Any named dependency
• Whether the problem occurs during startup or only in one application

If Event Viewer identifies another DLL or service, repair that component instead of assuming diagperf.dll is the root cause.

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

Fix 7: Update or repair device drivers when diagnostics fail

A driver problem can trigger Windows diagnostics or cause Diagnostic Policy Service events. This is not the primary repair for a missing diagperf.dll, but it is relevant when the error began after a device change or driver update.

1. Right-click the Start button.
2. Select Device Manager.
3. Expand the category related to the failing device.
4. Right-click the device.
5. Select Update driver.
6. Choose Search automatically for drivers.
7. Restart if Windows requests it.

If the issue began immediately after a driver update:

1. Open Device Manager.
2. Right-click the device.
3. Select Properties.
4. Open the Driver tab.
5. Select Roll Back Driver if available.
6. Restart Windows.

Avoid downloading drivers from unofficial driver repositories. Use Windows Update or the device manufacturer’s official support channel.

When checking every device manually is the main obstacle, Outbyte Driver Updater can scan for outdated drivers; the free scan reports what it finds, while driver installation is handled by the full version. It is optional, and updating a driver will not replace the need to repair Windows if diagperf.dll itself is corrupted.

Do not use regsvr32 as a routine fix

regsvr32 registers DLLs that expose registration entry points such as DllRegisterServer. It does not restore a missing Windows component, repair the component store, or fix a wrong-architecture file.

Do not run this as a generic repair:

regsvr32 diagperf.dll

A registration error after running it would not prove that the DLL is damaged. Microsoft describes regsvr32 in its official command documentation. For this Windows diagnostics component, DISM, SFC, Windows Update, and an official repair installation are the appropriate paths.

Fix 8: Use System Restore

System Restore can help when the problem began after a driver installation, failed update, registry change, or program installation.

1. Press Windows key + R.
2. Enter:

rstrui.exe

1. Press Enter.
2. Select a restore point created before the error began.
3. Click Scan for affected programs if available.
4. Confirm the restore point.
5. Allow Windows to restart and complete the operation.

System Restore can undo recent system files, drivers, registry settings, and installed-program changes without removing personal files. It does not replace a backup, and it may not be available if protection was disabled.

You can also start Windows Recovery Environment and select Troubleshoot > Advanced options > System Restore.

Fix 9: Perform an in-place Windows repair

If DISM, SFC, updates, quarantine checks, application repair, and System Restore do not resolve the problem, use official Windows installation media for an in-place repair.

Use installation media that matches the installed Windows version and edition. Start setup.exe from within Windows and choose the option to keep personal files and apps. Follow Microsoft’s instructions for reinstalling Windows with installation media.

Back up important files first. If the error returns after an in-place repair, investigate storage health, malware, failing hardware, or broader system corruption.

Frequently asked questions

Is diagperf.dll safe?

A copy supplied by Windows in the expected system directory is a legitimate Microsoft component. Location, digital signature, and Windows servicing history matter more than the filename alone. A copy in a temporary folder or an unfamiliar application directory deserves investigation.

Is diagperf.dll part of Visual C++?

No. diagperf.dll is a Windows diagnostics component. Reinstalling Visual C++ is relevant only when the error also names a runtime such as VCRUNTIME140.dll or MSVCP140.dll.

Should I download diagperf.dll?

No. Restore it through Windows Update, DISM, SFC, System Restore, or an in-place Windows repair. A downloaded DLL can be malicious, incompatible, or the wrong architecture.

Does every Event Viewer error mentioning diagperf.dll mean it is missing?

No. It may be a faulting module in a Diagnostic Policy Service crash or a module involved in reporting another problem. Inspect the event details and check whether the file is present.

Why does “specified module could not be found” appear when the file exists?

The loader may be unable to find a dependency required by diagperf.dll. Repair Windows, review Event Viewer, and avoid assuming that replacing the named file will solve the issue.

Should I enable a Windows Feature?

There is no general Windows Feature that should be enabled to restore diagperf.dll. It ships with Windows and should be repaired through servicing tools. Enabling unrelated features can add complexity without restoring the protected component.

What if SFC says it cannot repair some files?

Run DISM first if you have not already done so, restart, and run SFC again. If it still cannot repair the files, use System Restore or an in-place repair, and inspect %WINDIR%LogsCBSCBS.log for details.

What is the correct fix if only one application reports the error?

Repair or reinstall that application after repairing Windows. If the application has a file-verification feature, use it first. A program-specific failure does not prove that Windows is missing the component globally.

When should I contact Microsoft support?

Escalate when the error survives Windows Update, DISM, SFC, security checks, application repair, System Restore, and an in-place repair. Repeated corruption can indicate malware, disk problems, failing storage, or broader Windows damage.

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.