psmsrv.dll Errors: Restore Windows Background Tasks Safely

psmsrv.dll is a genuine Microsoft Windows system file, not a normal game or application DLL. If Windows says it is missing, cannot load it, or reports a Bad Image, repair the Windows component rather than downloading a replacement file.

What psmsrv.dll does

The file is described as Process State Manager (PSM) Service. It is associated with the Windows Background Tasks Infrastructure Service, whose service name is BrokerInfrastructure. This service helps control which background tasks packaged Windows applications can run.

As an Amazon Associate I earn from qualifying purchases.

On a normal installation, the file is located at:

%WinDir%System32psmsrv.dll

That usually means:

C:WindowsSystem32psmsrv.dll

The Windows installation directory can differ if Windows was installed on another drive.

Version and architecture guide

Windows component detail	What it means
Microsoft Windows system DLL	It belongs to Windows, not a Visual C++ or DirectX package
System32 location	The normal location for the installed Windows copy
x86 and x64 builds	Windows servicing supplies architecture-specific files
Version and file size	Must match the installed Windows build
BrokerInfrastructure relationship	A crash involving this service may identify the DLL without proving the DLL is defective

Microsoft servicing records show different psmsrv.dll builds for Windows 8, Windows 8.1, Windows 10, and both x86 and x64 editions. Do not use an old version from a servicing record to replace a file on a newer Windows build.

What the error message really means

You may see one of these messages:

• “The program can’t start because psmsrv.dll is missing from your computer.”
• “There was a problem starting psmsrv.dll.”
• “Error loading psmsrv.dll. The specified module could not be found.”
• “The code execution cannot proceed because psmsrv.dll was not found.”
• “psmsrv.dll is either not designed to run on Windows or it contains an error.”

These messages do not all indicate the same failure.

Missing file

If psmsrv.dll is absent from %WinDir%System32, Windows component corruption, an incomplete update, disk damage, security software action, or malware may be involved.

Missing dependency

“The specified module could not be found” can mean that Windows found psmsrv.dll but could not find one of the files it needs. The message does not prove that psmsrv.dll itself is missing.

Bad Image

A Bad Image message commonly indicates corruption, a mismatched architecture, an incomplete update, or a file with an invalid Microsoft signature.

BrokerInfrastructure crash

If Event Viewer reports svchost.exe_BrokerInfrastructure and lists psmsrv.dll as the faulting module, repair Windows first. A faulting-module entry identifies where Windows detected the failure, not necessarily the underlying cause.

Fix 1: Install Windows updates first

A failed or incomplete Windows update is a common reason for protected system files to become mismatched.

1. Open Start > Settings.
2. Select Windows Update.
3. Choose Check for updates.
4. Install every available update.
5. Restart the computer, even if Windows does not immediately require it.
6. Check for updates again after restarting.

Try the affected program or Windows feature again. If the error remains, continue with DISM and SFC instead of copying a DLL manually.

On Windows 11, you may also see a repair-reinstall option:

1. Open Start > Settings > System > Recovery.
2. Find Fix problems using Windows Update.
3. Select Reinstall now.
4. Follow the prompts.

This reinstalls the current Windows version while preserving apps, files, and settings when the option is available. Its availability depends on the Windows edition and system state.

Fix 2: Repair Windows with DISM and SFC

Microsoft recommends running DISM before System File Checker when protected Windows files are missing or corrupted.

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 this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for DISM to finish. It may appear to pause for a while. Do not close the window while it is working.

When DISM completes, run:

sfc /scannow

Wait until verification reaches 100 percent, then restart Windows.

How to interpret the result

• Windows Resource Protection did not find any integrity violations: SFC found no damaged protected files. Continue with the diagnostic checks below.
• Windows Resource Protection found corrupt files and successfully repaired them: Restart and test the affected program.
• Windows Resource Protection found corrupt files but was unable to fix some of them: Run DISM again, restart, and run SFC again. If it still cannot repair the files, use System Restore or an in-place Windows repair.
• DISM reports that source files could not be found: Windows servicing may be damaged. Use official Windows installation media or the Windows repair-reinstall option.

Running these commands is free, but manually interpreting repeated SFC and DISM results can be difficult when several components are damaged. Outbyte PC Repair can scan for system problems and show what needs attention; its repair functions require the full version, and it is not a substitute for reinstalling a damaged application.

Fix 3: Check Windows Security quarantine

Security software can quarantine a legitimate system file after a false detection. Do not restore a file merely because an application reports it missing.

1. Open Start.
2. Type Windows Security and open it.
3. Select Virus & threat protection.
4. Choose Protection history.
5. Look for an entry involving psmsrv.dll.
6. Verify that the file path is the Windows system directory.
7. Check that the file is identified as a Microsoft Windows component and has a valid Microsoft signature.
8. Restore it and choose Allow on device only after the file and detection have been verified.

If the item is unsigned, stored in a game folder, stored in a temporary directory, or associated with suspicious software, do not restore it. Update Windows Security and run a full scan instead.

Fix 4: Verify the file path and signature

If the file exists, confirm that it is the correct Windows copy.

1. Press Windows key + E.
2. Enter %WinDir%System32 in the address bar.
3. Locate psmsrv.dll.
4. Right-click it and select Properties.
5. Check the Digital Signatures tab.
6. Select the Microsoft signature and choose Details.
7. Confirm that Windows reports the signature as valid.

A file with the right name in an application folder is not automatically genuine. Do not replace the System32 copy with a file from another computer unless an advanced Microsoft-supported recovery procedure identifies a known-good copy from the same Windows version.

Fix 5: Repair the affected application

If the error appears only when opening one packaged Windows application, that application may be damaged even though psmsrv.dll belongs to Windows.

On Windows 11:

1. Open Start > Settings > Apps > Installed apps.
2. Find the affected application.
3. Select the More button beside it.
4. Choose Advanced options.
5. Select Repair.
6. Test the application.
7. If Repair does not help, return to the same screen and choose Reset.

Reset removes the application’s stored data, so use it only after Repair fails.

For a traditional desktop program:

1. Open Control Panel.
2. Select Programs > Programs and Features.
3. Right-click the affected program.
4. Choose Repair or Change, if available.
5. Complete the installer prompts and restart Windows.

If the application has its own official installer, update or reinstall it from the developer’s official source. Reinstalling the affected program can fix its configuration, but it should not be used as a reason to download psmsrv.dll separately.

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

Fix 6: Check for disk damage or interrupted servicing

If the problem began after a forced shutdown, disk failure, cloning operation, cleanup utility, malware infection, or interrupted update, Windows may have broader component damage.

After running DISM and SFC:

1. Open Event Viewer from the Start menu.
2. Select Windows Logs > System.
3. Look for disk, NTFS, servicing, or BrokerInfrastructure errors around the time of the failure.
4. In Command Prompt as administrator, review the SFC details in:

%WinDir%LogsCBSCBS.log

Do not delete or edit the CBS log. It can show whether Windows identified psmsrv.dll as damaged or whether another dependency failed.

Run a malware scan if the file disappeared unexpectedly. If DISM and SFC cannot repair the installation, use System Restore or an in-place repair from official Windows media.

Fix 7: Investigate drivers only when evidence points there

A driver is not the primary cause of a normal psmsrv.dll missing error. Consider driver repair only when Device Manager, Event Viewer, a crash dump, or the timing of a driver update identifies a related device.

To check drivers:

1. Right-click Start.
2. Select Device Manager.
3. Expand the device category related to the crash.
4. Right-click the device and select Properties.
5. Review the General and Driver tabs.
6. Use Update Driver, Roll Back Driver, or Uninstall Device only when the evidence supports that action.
7. Restart Windows and install the manufacturer’s current driver if required.

Finding which of many installed drivers is stale can take time, especially after a major Windows update. Outbyte Driver Updater can scan for driver issues and identify updates; the scan is available before its full-version driver installation features, and driver repair is not required for every psmsrv.dll error.

What not to do

Do not download psmsrv.dll from a DLL website

Random DLL downloads can contain malware, the wrong architecture, an old Windows build, or a file with an invalid signature. A copied file may also leave the damaged component store or missing dependency untouched.

The safe sources are Windows Update, DISM and SFC, Windows recovery, official Windows installation media, and a verified Microsoft-supported repair process. There is no verified official standalone psmsrv.dll download or redistributable package.

Do not copy it into random folders

Do not copy psmsrv.dll into an application directory, SysWOW64, or another computer’s System32 folder. x86 and x64 builds differ, and the correct file must match the Windows build and architecture.

Do not run regsvr32 automatically

regsvr32 is intended for self-registering COM, OLE, or ActiveX DLLs. psmsrv.dll is a Windows service component, not a DLL that should normally be registered manually. Running commands such as these will not repair the usual problem:

regsvr32 psmsrv.dll
regsvr32 /u psmsrv.dll

Use registration commands only when Microsoft specifically identifies a registration problem and provides the command.

Do not reinstall unrelated runtimes first

psmsrv.dll is not a Visual C++ redistributable, DirectX runtime, or .NET package. Reinstalling those products is unlikely to repair a missing Windows component unless a separate error specifically identifies one of them.

If the error continues

Use Windows recovery options in this order:

1. System Restore: Open Settings > System > Recovery > Open System Restore, or enter WinRE through Troubleshoot > Advanced options > System Restore.
2. Uninstall a recent update: In WinRE, choose Troubleshoot > Advanced options > Uninstall Updates.
3. Repair reinstall: Use Windows 11’s Reinstall now option when available.
4. In-place repair: Start official Windows installation media from within Windows and choose to keep personal files and apps.
5. Reset or reinstall Windows: Back up personal files first and use this only when supported repair paths fail.

FAQ

Is psmsrv.dll malware?

The legitimate file is a Microsoft Windows component normally located in %WinDir%System32 and covered by a valid Microsoft signature. A file with the same name in another location, or one with an invalid signature, deserves investigation.

Is it part of a game?

There is no reliable evidence that a particular commercial game normally ships its own copy. A game may expose the error while Windows’ Background Tasks Infrastructure Service is damaged, but that does not make the game the owner of the DLL.

Should I reinstall Visual C++, DirectX, or .NET?

Usually no. Repair Windows with Windows Update, DISM, and SFC first. Install another runtime only when the error explicitly identifies that runtime.

Why are there 32-bit and 64-bit versions?

Windows servicing maintains architecture-specific system files. Use the copy delivered for the installed Windows build. Do not decide by file size alone or replace an x64 file with an x86 download.

Why does Event Viewer name psmsrv.dll when the file exists?

The file may be present but corrupted, mismatched, unable to load a dependency, or involved in a broader BrokerInfrastructure failure. The name in a crash record does not prove that the DLL itself is the root cause.

What is the safest repair?

Install pending Windows updates, run DISM followed by SFC, and restart. If those steps fail, use Windows recovery or an in-place repair instead of downloading or manually registering the DLL.

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.