es.dll Missing on Windows: Trace COM+ and Repair It Safely

Before changing anything, note three details:

• Which program or game reports the error?
• Does it happen during Windows startup, or only when launching that program?
• Is the affected application 32-bit or 64-bit?

The es.dll file is a genuine Microsoft Windows component called the COM+ EventSystem Library. If es.dll is missing, Windows or an application may fail to start, but downloading a replacement DLL from a random website is not the safe fix.

What es.dll does

es.dll belongs to Windows COM+ Services. COM+ provides infrastructure that Windows and applications use to publish and receive events, allowing components to react to system and application activity.

The related Windows service is COM+ Event System, whose service name is EventSystem. It is normally hosted through svchost.exe, so you should not expect to launch es.dll like a normal application.

Microsoft documents COM+ as a Windows component rather than as part of a separate Visual C++, DirectX, or .NET redistributable. See Microsoft’s COM+ Component Services documentation and COM+ Event System protocol documentation.

Where es.dll should be located

On a normal Windows installation, native system DLLs are kept below:

%windir%System32

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

%windir%SysWOW64

This naming is confusing: System32 generally contains 64-bit system files on 64-bit Windows, while SysWOW64 commonly contains 32-bit system files.

The exact location depends on the Windows release, architecture, servicing state, and the program making the request. An application might also contain a private copy, but a copy outside the Windows directories is not automatically malware. Check its publisher, signature, path, and application context before drawing conclusions.

Do not treat an old file-size or version list as a universal requirement. Windows releases can contain different builds, and replacing a current component with an older catalogue copy can create servicing and compatibility problems.

What the common es.dll errors mean

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

Windows cannot find the DLL at a location available to the program. The file may have been deleted, quarantined, damaged, or become inaccessible because of broader system corruption.

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

The application requested a function or component associated with es.dll, but Windows could not locate a usable copy. This can affect one application or several programs.

“There was a problem starting es.dll” or “es.dll could not be loaded”

Windows found a reference to the file but could not load it. Possible causes include file corruption, incorrect architecture, missing dependencies, permissions problems, or a damaged Windows component store.

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

This usually indicates a corrupt, incompatible, incomplete, or incorrectly replaced DLL. It can also appear when a 32-bit and 64-bit component are mixed.

“The procedure entry point … could not be located in es.dll”

The file loaded, but it does not contain the function the calling program expects. This often points to a mismatched or obsolete copy rather than a simple missing-file problem.

A 0xc000007b error can also indicate an architecture or dependency mismatch, but it does not prove that es.dll itself is the faulty component.

First check: identify the scope of the failure

The fastest way to choose the right repair is to determine whether Windows or one application is responsible.

1. Restart Windows once.
2. Try a second affected application if possible.
3. Check whether the error appears before sign-in, immediately after sign-in, or only after launching one program.
4. Record the exact application name and error text.
5. Note whether the issue began after a Windows update, failed upgrade, system restore, antivirus action, disk cleanup, malware incident, or application reinstall.

If several programs fail or the message appears during startup, treat this as a Windows component problem and begin with DISM and SFC.

If only one game or application fails, repair that application as well. The application may be damaged even when the Windows copy of es.dll is healthy.

Check the file path and Microsoft signature

Do not start by copying a DLL. First see whether Windows can locate the file.

Open Windows Terminal or Command Prompt as administrator:

1. Open Start.
2. Type Terminal.
3. Right-click Windows Terminal.
4. Select Run as administrator.
5. Approve the User Account Control prompt.
6. Run:

where es.dll

If Windows finds the file, the command displays its path. If it returns a message that no matching files were found, the file is not available through the normal search path.

You can check the expected Windows locations manually:

1. Press Windows key + R.
2. Enter %windir%System32.
3. Press Enter.
4. Search for es.dll.
5. On 64-bit Windows, also inspect %windir%SysWOW64.

Next, check the signature of the expected 64-bit system copy in PowerShell:

Get-AuthenticodeSignature "$env:windirSystem32es.dll"

For a 32-bit copy on 64-bit Windows, use:

Get-AuthenticodeSignature "$env:windirSysWOW64es.dll"

A valid Microsoft signature supports the file’s legitimacy. A signature check is useful evidence, but it is not a complete malware assessment. If the file is in an unexpected application folder, scan the file and the system before allowing it to run.

Check the COM+ Event System service

A service failure is not exactly the same as a missing DLL. The service can exist while failing to start because of dependencies, permissions, or wider Windows damage.

In an elevated Terminal or Command Prompt, run:

sc query EventSystem

Look for the service state.

• RUNNING means the service is active.
• STOPPED means it exists but is not currently running.
• An error stating that the service does not exist suggests a deeper Windows component problem.
• A service that refuses to start needs service and Event Viewer investigation, not repeated DLL copying.

You can also inspect it graphically:

1. Press Windows key + R.
2. Type services.msc.
3. Press Enter.
4. Find COM+ Event System.
5. Double-click it.
6. Note the Startup type, Service status, and Dependencies tabs.

Do not randomly change service startup settings. If the service is present but will not start, continue with the system repair steps below.

Fix 1: repair Windows with DISM, then SFC

This is the safest first repair for a missing or corrupted Windows copy of es.dll. DISM repairs the Windows component store, which SFC uses as a source for replacing damaged protected files. Microsoft recommends running DISM before System File Checker when the component store may be damaged. The Microsoft SFC and DISM guidance documents this process.

1. Save your work.
2. Open Start.
3. Type Terminal.
4. Right-click Windows Terminal.
5. Select Run as administrator.
6. Run this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the operation to finish.
2. Without closing the administrator window, run:

sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.

The result matters:

• Windows Resource Protection did not find any integrity violations means SFC found no damaged protected files.
• Windows Resource Protection found corrupt files and successfully repaired them means the repair completed.
• Windows Resource Protection found corrupt files but was unable to fix some of them means continue with the recovery steps below.
• A DISM error means the component store or repair source still needs attention.

Running these commands repeatedly without recording the result rarely adds useful information. If you want to reduce the manual work of hunting through repair logs and repeating SFC/DISM blindly, Outbyte PC Repair can scan for reported problems; its free scan shows what it finds, while repair actions require the full version. It is optional, and Microsoft’s built-in DISM and SFC remain the appropriate first repair.

Fix 2: repair DISM from matching Windows installation media

DISM normally obtains repair files through Windows servicing. If it cannot find the required files, use a matching official Windows installation image.

The image must match the installed Windows edition, language, architecture, and release. Using an unrelated image can produce another repair failure.

Microsoft explains the /Source and /LimitAccess options in its Windows image repair documentation.

After mounting the official installation image, identify its drive letter. For this example, assume it is D:. The exact command depends on whether the image contains an install.wim or install.esd, and on the edition index inside that image. Do not guess the index.

A typical WIM-based command is:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:wim:D:sourcesinstall.wim:<index> /LimitAccess

An ESD-based source uses:

DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:esd:D:sourcesinstall.esd:<index> /LimitAccess

After DISM completes, run:

sfc /scannow

Restart Windows and test the affected program again.

If SFC still cannot repair files, inspect:

%windir%LogsCBSCBS.log

The log is technical and large, but it can show which protected components remain damaged. If storage errors or repeated corruption appear, check the drive before attempting more file replacement.

Fix 3: repair or reinstall the affected application

If only one game or program displays the error, Windows may be fine. The application could have an incomplete update, damaged installation files, or an incorrect private dependency.

Use the application’s own repair facility first:

1. Open the application’s launcher or installer.
2. Select the affected game or program.
3. Open its settings, manage, or properties screen.
4. Choose Verify, Repair, or Verify integrity of files, if available.
5. Let the process finish.
6. Restart the application.

For a Microsoft Store application:

1. Open Settings.
2. Select Apps.
3. Select Installed apps.
4. Find the application.
5. Select the three-dot menu.
6. Choose Advanced options.
7. Try Repair.
8. If that fails, use Reset only after considering that it may remove the application’s local data.

For a traditional desktop application:

1. Open Settings > Apps > Installed apps.
2. Select the application’s menu.
3. Choose Uninstall, if no repair option is available.
4. Restart Windows.
5. Reinstall it from the publisher’s official installer or launcher.

Do not assume the application needs a private copy of es.dll. If the application installer places a different unsigned DLL beside its executable, inspect that file carefully rather than automatically accepting it.

Fix 4: check antivirus quarantine

Security software may quarantine a damaged or falsely detected copy. It may also remove an unauthorized replacement.

In Windows Security:

1. Open Start.
2. Type Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review entries that mention es.dll or the application that reports the error.
7. Expand an entry to see its path and detection details.

Do not restore a quarantined file merely because an application asks for it. Microsoft warns that restoring a detected threat can expose the system. Use the Microsoft Protection History guidance and restore the file only when its location, Microsoft signature, and security scan support that decision.

If the file repeatedly disappears:

1. Update Windows Security definitions.
2. Run a Full scan from Virus & threat protection.
3. If malware is suspected, use Microsoft Defender Offline scan.
4. Review third-party antivirus logs if another security product is installed.
5. Run the DISM and SFC sequence again after the scan.

A file that keeps being deleted may indicate malware, a false detection, unauthorized replacement, or failing storage.

Fix 5: install pending Windows updates

An interrupted update can leave Windows components inconsistent.

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

After the restart, run:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Test the program again. If the error began immediately after a particular update, use Windows recovery rather than downloading an older DLL.

Fix 6: use System Restore or remove a recent update

If the problem began after an update, driver installation, failed upgrade, or system configuration change, Windows recovery may restore the earlier working state.

For System Restore:

1. Open Start.
2. Search for Create a restore point.
3. Open it.
4. Select System Restore.
5. Choose a restore point from before the problem began.
6. Review the affected programs and drivers.
7. Confirm the restore.

System Restore normally rolls back system files, drivers, and settings without removing personal files. It does not replace a backup.

You can also review update removal options:

1. Open Settings.
2. Select Windows Update.
3. Select Update history.
4. Choose Uninstall updates.
5. Select a recent update when Windows provides that option.
6. Restart and test.

Microsoft’s Windows recovery options explain which recovery choices are available for the installed Windows version.

Fix 7: investigate drivers only after a hardware or update change

A graphics, storage, chipset, or security driver is not the normal source of es.dll, and reinstalling a Visual C++, DirectX, or .NET package is not a targeted repair for this Windows COM+ component.

Driver troubleshooting makes sense when the error began after a hardware change, driver update, crash, or failed Windows upgrade.

1. Right-click Start.
2. Select Device Manager.
3. Expand categories such as Display adapters, Storage controllers, System devices, and Network adapters.
4. Look for a warning icon.
5. Right-click the recently changed device.
6. Select Properties.
7. Check the General and Driver tabs.
8. Use Roll Back Driver if the option is available and the problem began after an update.
9. Otherwise choose Update driver and use Windows Update or the hardware manufacturer’s official driver package.
10. Restart Windows.

If you are manually tracking several hardware drivers and want a scan that identifies outdated items instead of guessing through Device Manager, Outbyte Driver Updater can show its findings; installing drivers through the full version is optional, and it does not replace DISM, SFC, or an application reinstall.

Do not use a driver utility as a substitute for checking the actual event log or identifying the device that changed.

Fix 8: check 32-bit and 64-bit compatibility

Windows loads 32-bit and 64-bit components differently. A 32-bit application may use the 32-bit system path, while a 64-bit application uses the 64-bit path on a 64-bit Windows installation.

To check an application’s architecture, consult its publisher’s documentation or inspect its installation layout. Do not replace a 64-bit es.dll with a 32-bit copy, or the reverse.

If only one older application fails while current Windows tools work, architecture mismatch or application damage becomes more plausible. Repair or reinstall that application before changing Windows files.

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

Why regsvr32 es.dll is usually wrong

regsvr32 registers DLLs that expose registration entry points such as DllRegisterServer. It is not a universal DLL repair command.

Microsoft provides regsvr32 documentation, but there is no Microsoft instruction to register the Windows es.dll component with:

regsvr32 es.dll

Running it can produce an error because the DLL does not provide the expected registration entry point. It does not restore a missing file, repair the component store, correct a 32-bit/64-bit mismatch, or repair COM+ service dependencies.

Some application vendors ship self-registering COM+ event-class DLLs. Those are different from the Windows es.dll implementation, so follow the specific application’s official installation instructions instead.

Why random DLL downloads are unsafe

Do not download es.dll from a generic DLL catalogue or copy it from another computer. That approach can give you:

• Malware or an unauthorized replacement
• The wrong Windows build
• The wrong architecture
• A missing Microsoft signature
• A file that does not match the component store
• A temporary change that Windows servicing later overwrites

There is no verified Microsoft standalone es.dll redistributable download. Use Windows Update, DISM, SFC, official recovery features, or official Windows installation media instead.

If none of these fixes work

Use the escalation path that matches the evidence.

Windows 11 repair reinstall

On supported Windows 11 installations:

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

This reinstalls the same Windows version while preserving apps, files, and settings. Microsoft documents the process in its Windows repair-reinstall procedure.

In-place reinstall from official media

An in-place reinstall can repair deeper Windows damage while preserving personal files and applications when the correct Keep personal files and apps option is selected.

Use official installation media and confirm the edition, language, and architecture before starting. Microsoft explains the process in its installation-media reinstall guidance.

Back up important files first. Do not choose a clean installation unless you have deliberately backed up everything and intend to remove applications and existing data.

Check storage and system integrity

Repeated DLL corruption can result from failing storage or broader filesystem damage.

1. Review Event Viewer for disk or filesystem errors.
2. Check the drive manufacturer’s diagnostic software.
3. Back up important data.
4. Investigate recurring disk errors before continuing to repair Windows.

If malware remains a possibility, complete a Defender Offline scan and use official Windows recovery media if system integrity cannot be trusted.

FAQ

Is es.dll malware?

es.dll is a legitimate Microsoft Windows component associated with COM+ Event System. A file with that name is not automatically safe, however. Confirm its path, Microsoft digital signature, and scan results. An unexpected unsigned copy deserves investigation.

Is es.dll part of Visual C++, DirectX, or .NET?

No targeted evidence supports installing those redistributables as a repair for the Windows COM+ es.dll component. Use DISM and SFC for Windows corruption, or repair the specific application that fails.

Is es.dll part of a game?

Games can expose a Windows problem when they start, but es.dll itself is a Windows COM+ component, not a normal game runtime. Verify the game’s files and reinstall the game only when the failure is isolated to that game.

Should I enable COM+ in Windows Features?

Do not toggle random optional features to replace a missing system DLL. Check the COM+ Event System service with sc query EventSystem, then repair Windows with DISM and SFC. The service is part of Windows COM+ infrastructure.

Why does the error appear only in one program?

That often points to an application-specific installation problem, an architecture mismatch, or an application-specific DLL search path. Verify or reinstall the program, while still checking the Windows system files if other symptoms exist.

Can I copy es.dll from another PC?

No. The other computer may have a different Windows release, architecture, servicing state, or file signature. Use DISM, SFC, Windows Update, recovery, or official installation media.

What should I do if EventSystem exists but will not start?

Treat that as a service or dependency failure, not proof that the DLL is missing. Check Event Viewer, run DISM followed by SFC, review recent updates and antivirus actions, and avoid repeatedly copying files.

What is the correct fix in most cases?

For a startup error or failures across multiple programs, run:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart afterward. For a single affected program, combine that check with the application’s own Verify, Repair, or reinstall process.

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.