Free tools Windows power users keep installed
One-click scans. No signup required.
Error 0x80020009 means DISP_E_EXCEPTION, or “Exception occurred.” Microsoft defines it as a COM/OLE Automation result returned when an application or automation component raises an exception. The code is only a wrapper: it does not identify the failed program, add-in, script, file, or Windows component. The reliable fix is therefore to capture the exact context, repair Windows components, isolate startup conflicts, and then troubleshoot the application that produced the message.
What error 0x80020009 means
Microsoft’s MS-ERREF HRESULT table maps 0x80020009 to DISP_E_EXCEPTION and defines it as “Exception occurred.” The MS-OAUT specification describes the same result as an application needing to raise an exception and provide exception information to the caller through the pExcepInfo structure.
As an Amazon Associate I earn from qualifying purchases.
COM, or Component Object Model, lets Windows applications call components supplied by other programs. OLE Automation is a related mechanism commonly used by Office applications, scripts, plug-ins, and automation hosts. When the called component fails, the host may show 0x80020009 instead of the detailed exception. That is why the same code can appear while opening a workbook, running an Excel macro, launching a PowerShell automation task, loading an add-in, or performing an unrelated operation in another program.
The hexadecimal value is not a diagnosis of a bad disk, a failed device, malware, or a specific Windows Update defect. It is evidence that an exception crossed an automation boundary. The application name, the action that triggered the error, and the detailed exception text are the useful diagnostic information.
#1 Best Overall
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- 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 PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
Is 0x80020009 a Windows Update or hardware error?
Not by itself. There is no single Windows 10 or Windows 11 defect that Microsoft assigns to this HRESULT. A Windows Update operation, an Office add-in, a script, or a third-party integration can all be the immediate caller. Hardware can be involved only indirectly—for example, if a device-related application or driver causes its host application to fail—but the HRESULT itself does not identify hardware.
If the message appears during Windows servicing, follow the Windows Update checks below. If it appears only in Excel, PowerShell, a line-of-business program, or another host, prioritize that program’s logs, add-ins, scripts, and recent changes instead of replacing hardware or downloading DLL files.
Record the failure before changing anything
Write down the information below while the error is reproducible. A complete record often reveals whether the problem is in Windows, the host application, or an automation component.
- The application and its exact version.
- Your Windows edition, version, and build (press
Win+R, enterwinver, and record the result). - The precise action: opening a file, running a macro, launching a script, installing an add-in, exporting data, or another operation.
- The complete dialog text, including any description, source, or secondary error number.
- The date and time, the file or account involved, and whether the failure occurs every time or only with one item.
- Any application log, crash report, or Event Viewer entry created at the same time.
- Recent changes such as an application update, Windows update, add-in installation, script change, or security-policy change.
Do not discard a longer exception message just because it also contains 0x80020009. The longer text is usually more actionable than the wrapper HRESULT.
Choose the least disruptive diagnostic path
| Layer | Typical action | Reversibility | Evidence produced |
|---|---|---|---|
| Application | Update, repair, disable add-ins or macros, or reinstall the affected program | Usually reversible; reinstall may require settings or license recovery | Application logs and whether one operation or all operations fail |
| Windows component store | Run DISM.exe /Online /Cleanup-image /Restorehealth |
Repairs Windows component files without removing personal files | DISM completion result and servicing logs |
| Protected system files | Run sfc /scannow after DISM |
Repairs protected Windows files where possible | SFC result and CBS servicing information |
| Startup services and drivers | Perform a clean boot, then re-enable items in groups | Fully reversible when normal startup is restored | Whether a non-Microsoft service or startup item causes the error |
Start with evidence-preserving steps. Avoid registry cleaners, random DLL downloads, or broad deletions: they do not address what this HRESULT actually tells you and can make the original failure harder to reproduce.
1. Update Windows and the triggering application
Check Windows 11
- Open Settings and select Windows Update.
- Select Check for updates, install pending updates, and restart when Windows requests it.
- Run the same action that produced 0x80020009.
Check Windows 10
- Open Settings and go to Update & Security > Windows Update.
- Select Check for updates, install available updates, and restart.
- Retest the failing action.
Use the Windows Update troubleshooter when servicing is the trigger
On Windows 11, open Settings > System > Troubleshoot > Other troubleshooters, locate Windows Update, and select Run. On Windows 10, open Settings > Update & Security > Troubleshoot > Additional troubleshooters, select Windows Update, and run the troubleshooter. Use this branch when the error occurs during an update or maintenance operation; it is not a universal remedy for an Excel or script failure.
Update the application
Install the latest update offered by the application’s own Help, Account, or About screen, or by its supported installer. Restart after updating and test the exact operation again. If only one file, macro, script, or integration fails while other operations work, an application update may not be sufficient; continue with the isolation steps below.
Recommended Free Tools
Rank #2
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
2. Repair Windows with DISM and SFC
Microsoft documents Deployment Image Servicing and Management (DISM) and System File Checker (SFC) as Windows image and protected-file repair tools. Run DISM first, then SFC.
- Save your work and open an elevated Command Prompt. Open Start, type
Command Prompt, right-click it, and select Run as administrator. Approve the User Account Control prompt. - Enter this command exactly and press
Enter:DISM.exe /Online /Cleanup-image /Restorehealth - Wait for DISM to finish. Do not close the window merely because progress appears to pause.
- After DISM completes, run:
sfc /scannow - Wait for SFC to reach 100 percent, restart Windows, and repeat the action that produced the HRESULT.
Record the final DISM and SFC messages. If either command reports an error, preserve the exact wording and code for escalation rather than repeatedly running unrelated cleanup utilities. These commands repair Windows components and protected files; they cannot repair a broken third-party add-in, a faulty macro, or an application-specific integration.
3. Use a clean boot to isolate interference
A clean boot starts Windows with a minimal set of Microsoft services and startup programs. It is a diagnostic test: if the error disappears, a non-Microsoft service, startup utility, or integration is a likely contributor.
- Sign in with an account that has administrative rights.
- Press
Win+R, typemsconfig, and pressEnter. - Open the Services tab. Select Hide all Microsoft services, then select Disable all. Hiding Microsoft services first prevents you from disabling core Windows services accidentally.
- Open the Startup tab and select Open Task Manager.
- In Task Manager’s Startup apps list, disable each currently enabled nonessential startup item. Close Task Manager.
- Select OK in System Configuration and restart the computer.
- Run the exact application action that previously failed.
Interpret the result
- The error remains: startup interference is less likely. Return to the application and Windows-component steps.
- The error disappears: open
msconfigagain and re-enable services in small groups, restarting and retesting after each group. Re-enable startup items in similarly small groups through Task Manager. When the error returns, divide that group further until you identify the conflicting service or add-in.
When testing is complete, open msconfig, select Normal startup on the General tab, apply the change, and restart. Do not leave normal security and required vendor services disabled after the test.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors4. Isolate the application, add-in, macro, or script
Disable recent additions one at a time
Remove or disable the newest add-in, macro, script module, connector, or integration temporarily, then repeat the same action. If the error stops, restore items one at a time until the failure returns. This identifies the component without permanently removing unrelated software.
Excel and Office automation
If Excel is the host, first test whether the failure is limited to one workbook or macro. Then open Excel’s add-in management and disable COM add-ins individually: File > Options > Add-ins, set Manage to COM Add-ins, select Go, and clear one item at a time. Restart Excel after each meaningful change. Apply the same approach to Excel add-ins, macros, and external data connections that were added or changed recently.
If a clean workbook works but one workbook fails, preserve a copy of the original and investigate that file’s macros, links, or embedded automation rather than changing Windows globally.
Rank #3
- 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)
PowerShell or another scripting host
Record the exact command, script file, module or application it calls, and the line or operation at which the exception appears. Test the host with the smallest reproducible action, then add modules, parameters, and external calls back one at a time. If the script invokes Office, a database, a device utility, or another COM component, the exception information from that component is more valuable than the generic HRESULT.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Repair or reinstall the affected application
Use the vendor’s supported repair option before uninstalling. For applications that expose Windows repair controls, open Settings > Apps > Installed apps on Windows 11 or Settings > Apps > Apps & features on Windows 10, select the application, and use its available Repair option. Some desktop programs provide repair only in their own installer or Control Panel entry. If repair does not help, reinstall using the vendor’s instructions and retain the application version, logs, and configuration details for support.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.5. Read Event Viewer and application logs
Event Viewer can contain the underlying exception, faulting module, or application name that the short dialog omits.
- Press
Win+R, entereventvwr.msc, and pressEnter. - Open Windows Logs > Application.
- Locate errors at the recorded time and inspect the General and Details tabs.
- Note the application name, faulting component, exception text, event ID, and any referenced file path.
Also inspect the affected program’s own log or crash-report location. Keep the original event details in a text file; do not paraphrase a module name or exception code when contacting the vendor.
6. Use profile or Safe Mode tests only when the symptom points there
Safe Mode, a new Windows profile, and controlled service tests are appropriate when the failure is tied to sign-in, a user profile, or startup. They are not default fixes for every 0x80020009 occurrence.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- If the error appears only for one Windows account, test the same operation in a separate profile created for diagnosis. A difference between profiles points toward per-user settings, add-ins, permissions, or profile data.
- If the error occurs during logon or immediately after sign-in, use Windows’ supported Safe Mode and profile-repair guidance for that symptom.
- If the error occurs in all accounts and in a clean boot, focus on the application, its shared component, or Windows repairs rather than repeatedly changing profiles.
Security and recovery precautions
- Do not download a DLL from an unverified website to replace a file named in an error. The HRESULT does not prove that a missing DLL is the cause.
- Do not use a registry cleaner as a substitute for identifying the failing application or component.
- If security software must be disabled briefly for a controlled compatibility test, disconnect unnecessary network access, test only long enough to reproduce the issue, and restore normal protection immediately. Treat this as an isolation step, not a repair.
- Create a backup of important workbooks, scripts, and configuration files before repairing or reinstalling an application.
- Keep a copy of every command result, event entry, and change made during troubleshooting so you can undo the last change.
When to escalate
Escalate to the affected application’s vendor when the error persists after updates, DISM, SFC, a clean boot, and add-in or script isolation—or when the failure is clearly limited to that application. Include:
- Application name and exact version.
- Windows edition, version, and build.
- A short, numbered reproduction procedure.
- The complete dialog text and the full exception details from logs.
- The time of the failure and relevant Event Viewer entry.
- Whether the issue occurs with a clean boot, another user profile, or a different file.
- Recent updates, add-ins, macros, scripts, integrations, or configuration changes.
- DISM and SFC final messages, if you ran those commands.
For a vendor, “0x80020009” alone is not enough to reproduce or diagnose the failure. The application context and detailed exception information are the key evidence.
Quick Recap
As an optional shortcut after the manual checks, Outbyte PC Repair can look for more than 100 common Windows issues, adjust settings, clear temporary and cache files, check Windows settings and missing updates, and record app crashes. It complements antivirus software rather than replacing it; results vary, and no tool repairs every crash. It runs on Windows 11, 10, 8, and 7, with a free trial by category of at least two days before a subscription.
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.
