How to Fix Windows Error 0x80080005 (“Server Execution Failed”)

Windows error 0x80080005 (also written 80080005) means “Server execution failed,” but it does not identify one universal crash. The correct repair depends on where it appears: Windows Update, COM+ or DCOM activation, IIS/MTS, Office automation, or another application. First copy the exact code and message, identify the failed operation, and then follow the matching branch below. The title’s 0X8008005 is probably missing a zero; verify the string in the dialog or event log before changing anything.

What 0x80080005 means

0x80080005 is an HRESULT commonly displayed as “Server execution failed.” “Server” here can mean a Windows service, a COM or COM+ server, or an application component that another program is trying to start. It does not, by itself, prove that Windows has suffered a full operating-system crash, that the computer is infected, or that one particular repair will work.

#	Preview	Product	Price
1		Microsoft Windows 11 (USB)	$128.99	Buy on Amazon
2		Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |...		Buy on Amazon

As an Amazon Associate I earn from qualifying purchases.

Microsoft documents the code in several materially different situations:

• Windows Update: corrupted system or update files, permissions problems, or an incorrect system configuration can prevent the update process from completing.
• COM+ and DCOM activation: when many COM+ applications run under different user accounts, Windows can run out of desktop heap needed to create another process.
• IIS, MTS, and COM automation: an ASP Server.CreateObject call can return 0177:80080005 when an MTS COM component cannot be created. A registration, identity, permission, or host-context problem may be specific to that component.

Because the same HRESULT spans these cases, do not start with a registry edit or delete update files until you know which operation failed.

#1 Best Overall

Sale

Microsoft Windows 11 (USB)

• Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
• Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
• Make the most of your screen space with snap layouts, desktops, and seamless redocking.
• Widgets makes staying up-to-date with the content you love and the news you care about, simple.
• Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)

$128.99

Buy on Amazon

Identify the failing context before you repair it

Record the exact message

Take a screenshot or copy the complete dialog text, including punctuation and any decimal or hexadecimal code. Microsoft documentation uses 0x80080005 and 80080005; a string such as 0X8008005 may simply be a transcription error. Also record the Windows edition and build, the date and time, the account that experienced the error, and what you clicked or launched immediately beforehand.

Use the location of the error as your first branch

Check Event Viewer for the server that failed

1. Press Windows key + R, type eventvwr.msc, and press Enter.
2. Open Windows Logs > System and Windows Logs > Application. For COM activation, also inspect entries whose source is DistributedCOM.
3. Filter or sort around the time of the failure. In the documented COM+ case, Microsoft reports DCOM Event ID 10010, which says that a server did not register within the required timeout.
4. Write down the event’s CLSID, application or server name, account, and timestamp. These details distinguish a single component failure from a machine-wide problem.
5. Open the event’s Details tab and save the XML or copy the complete text before making changes. Keep this evidence if you need to contact the component vendor or Microsoft support.

An Event ID 10010 entry is a diagnostic clue, not proof that every 0x80080005 case has a desktop-heap problem. Use the CLSID and the application context to select the appropriate branch.

Fix 0x80080005 when Windows Update shows it

The following sequence uses Windows’ built-in repair tools and follows Microsoft’s documented order. Run the commands from an elevated Command Prompt and allow each one to finish.

1. Run the Windows Update troubleshooter

1. Open Settings and go to System > Troubleshoot > Other troubleshooters on current Windows editions.
2. Select Windows Update, choose Run, and apply any repair the troubleshooter offers.
3. Restart the computer if requested, then try the update again. Record whether the same HRESULT returns.

On an edition that exposes a different Settings layout, search Settings for troubleshoot and select the Windows Update troubleshooter. The important point is to run the built-in Windows Update diagnostic before manually removing its cache.

2. Repair the Windows image with DISM

1. Open Start, type Command Prompt, right-click it, and choose Run as administrator.
2. Run:

DISM.exe /Online /Cleanup-image /Restorehealth

Wait for DISM to reach completion. Do not close the window merely because progress appears to pause; servicing can take time. If DISM reports an error, copy the exact code and message rather than guessing at a replacement command.

3. Check protected system files with SFC

In the same elevated Command Prompt, run:

sfc /scannow

Let the scan reach 100 percent. Restart Windows when it finishes, then retry Windows Update. SFC repairs protected files when it can; its result is useful evidence even if the update still fails.

4. Reset the Windows Update service and cache

If the troubleshooter, DISM, and SFC do not clear the error, Microsoft documents resetting the update download cache. Use an elevated Command Prompt:

1. Stop the Windows Update service:

net stop wuauserv

2. Open File Explorer and browse to C:WindowsSoftwareDistribution.
3. Delete the contents of that folder, not the folder itself. If Windows says a file is in use, confirm that the Windows Update service has stopped and close applications that may be accessing the folder.
4. Start the service again:

net start wuauserv

5. Restart Windows and check for updates again.

This removes downloaded update data so Windows can obtain a fresh copy. It does not change the COM+ catalog or repair an unrelated IIS component, so do not use this branch as a universal solution.

5. If the update still fails

• Capture the new Windows Update error text and the date and time of the attempt.
• Keep the DISM and SFC result lines, including any message that files could not be repaired.
• Check Event Viewer for servicing or Windows Update events at the same time.
• Provide the Windows build, exact HRESULT, update name or knowledge-base identifier shown in Update history, and the steps already completed when requesting support.

Fix the documented COM+ desktop-heap scenario

Microsoft describes a specific COM+ condition in which many COM+ applications run under different user accounts. Windows then cannot allocate enough additional desktop heap for another user’s server process, so activation fails with 80080005. The registry workaround below applies only when your evidence matches that scenario. It is not a general fix for Windows Update, IIS registration, or every DCOM timeout.

Rank #2

Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC | Branded by Microsoft

• STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
• OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
• OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
• PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
• GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.

Buy on Amazon

Validate the scenario first

• Confirm that the failure occurs while starting or activating a COM+ application, not while installing an update.
• Check Event Viewer for the related DistributedCOM event, including Event ID 10010 where applicable.
• Confirm that multiple COM+ applications are running under different user accounts and that a new activation fails when another account is added.
• Identify the affected COM+ application and preserve the event details before editing the registry.

Back up the registry

1. Press Windows key + R, type regedit, and press Enter.
2. In Registry Editor, select File > Export.
3. Choose a location you can access offline, select All under Export range, give the backup a descriptive name, and save it.
4. Do not continue if you cannot create or securely store the backup. A wrong registry edit can prevent services or Windows from starting correctly.

Apply Microsoft’s narrow SharedSection change

1. In Registry Editor, navigate to:

HKEY_LOCAL_MACHINESystemCurrentControlSetControlSession ManagerSubSystems

2. In the right pane, double-click the value named Windows.
3. Find the SharedSection portion of the value. Microsoft’s documented workaround adds 512 as the third number, producing the form:

SharedSection=1024,3072,512

4. Preserve the rest of the value exactly as it appears. Change only the SharedSection numbers required by the documented workaround, click OK, and close Registry Editor.
5. Restart Windows so the session-manager setting takes effect, then retry the same COM+ activation.

The numbers are expressed in kilobytes in the Windows subsystem setting. Increasing the third value consumes more kernel-managed desktop-heap address space; that is why this change belongs only on systems matching the documented multi-account COM+ condition. If the activation still fails, restore the exported registry backup or reverse only the change you made, then continue troubleshooting the component identity and event details instead of increasing the value repeatedly.

Troubleshoot IIS, MTS, and other COM automation failures

An ASP 0177:80080005 response from Server.CreateObject means the host could not create the requested MTS/COM component. Treat the CLSID and host identity as the center of the investigation.

Confirm the component is registered

Identify the ProgID or CLSID used by the application and verify that the corresponding COM component is installed and registered in the same Windows environment as IIS or the calling application. A 32-bit component must be available to the 32-bit host mode that loads it, while a 64-bit component must match the 64-bit host; determine the application’s configured bitness before changing it. Do not register an unknown DLL simply because its file name resembles the component name.

Check the launch identity and permissions

• Identify the IIS application-pool identity, Windows service account, or scheduled-task account that actually launches the COM server.
• Confirm that account can read the component’s files and required registry entries.
• Check the component’s DCOM launch and activation permissions where the application uses a configured DCOM identity.
• Compare an interactive test with a test launched under the real service account; a component that works for an administrator may fail for a restricted identity.

Reproduce in the same host context

Use the same website, application pool, service, account, and bitness as the failing request. If a standalone test succeeds but the IIS request fails, the difference in identity, environment, or host process is significant evidence. Record whether the failure is consistent, whether only one CLSID is affected, and whether Event Viewer logs a matching DCOM timeout.

Repair the component rather than the whole operating system

For an application-specific failure, repair or reinstall the application component using its documented installer, correct its configured identity, or contact the component vendor with the CLSID and event data. Avoid applying the SharedSection edit unless the documented multi-account COM+ desktop-heap conditions are actually present.

What not to do

• Do not treat the code as proof of malware or a full system crash. The HRESULT describes a failed server execution or activation; it does not identify the cause by itself.
• Do not edit the registry first. The SharedSection workaround is narrow and carries more risk than DISM, SFC, or the Windows Update troubleshooter.
• Do not delete the entire SoftwareDistribution folder while the service is running. Stop Windows Update, clear its contents, and start the service again.
• Do not repeatedly increase SharedSection values. Validate the scenario, make a backup, apply the documented change once, and measure whether the activation succeeds.
• Do not assume an administrator test proves an IIS or service account is configured correctly. Reproduce the failure under the identity that normally launches the component.
• Do not register random DLLs from the internet. Use the application’s legitimate installer and preserve the original component version and bitness.

When to escalate and what to include

Escalate when the code returns after the correct branch has been completed, when DISM or SFC reports unrepaired corruption, when a registry rollback does not restore COM+ activation, or when the failing CLSID belongs to software you cannot repair safely.

Send support a compact evidence bundle:

• The exact HRESULT and complete dialog or HTTP/ASP message.
• Windows edition, version, and build.
• The operation that failed and whether it was Windows Update, COM+, DCOM, IIS/MTS, Office automation, or another host.
• Event Viewer entries, especially DistributedCOM details, Event ID 10010, CLSID, application name, account, and timestamp.
• DISM and SFC completion messages, plus whether the Windows Update service/cache reset was performed.
• For COM automation, component bitness, registration status, host identity, and a description of a reproduction under the same account.

This information lets support distinguish machine-wide servicing damage from a single server identity, registration, or desktop-heap problem without repeating risky changes.

As an optional shortcut after trying the manual steps, Outbyte PC Repair can look for more than 100 common Windows issues, including broken system elements and shared DLL problems, and offers cleanup, settings, vulnerability checks, and an app-crash log. It runs on Windows 11, 10, 8, and 7; its free trial lasts at least two days by category before a subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.

Decision checklist

• Update screen: run the Windows Update troubleshooter, DISM, SFC, then stop the service and clear C:WindowsSoftwareDistribution.
• COM+ activation with many accounts: check for the matching DCOM evidence, back up the registry, and consider the documented SharedSection=1024,3072,512 change.
• IIS/MTS or Server.CreateObject: investigate the CLSID, registration, host bitness, launch identity, and permissions.
• Unclear context: stop and collect the full message and Event Viewer details before selecting a repair.

The durable fix is the one that matches the failing server: repair Windows servicing for an update error, correct desktop-heap capacity only for the documented COM+ case, or repair the specific component and identity for IIS and other COM automation.

Quick Recap

SaleBestseller No. 1

Microsoft Windows 11 (USB)

Make the most of your screen space with snap layouts, desktops, and seamless redocking.; FPP is boxed product that ships with USB for installation

$128.99

Bestseller No. 2

Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC | Branded by Microsoft

GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.

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.

0x80080005COMDCOMIIS troubleshootingWindows errorsWindows Update