How to fix Error 1910 on Windows 11

by

Windows Error 1910: “The Object Exporter Specified Was Not Found” Troubleshooting Guide

Why This Error Happens

Error 1910 typically occurs when the Windows DCOM (Distributed Component Object Model) subsystem cannot locate a registered object exporter, often due to a corrupted or incomplete COM/DCOM registration in the registry. This can happen after a failed software uninstall, a botched Windows Update, or when a service tries to reference a GUID that no longer exists in the registry. Insufficient permissions on the DCOM configuration for the associated application can also trigger this error.

Step-by-Step Resolution Guide

Step 1: Identify the Affected Application via Event Viewer

  • Open Event Viewer by pressing Win + R, typing eventvwr.msc, and pressing Enter.
  • Navigate to Windows Logs > System and filter for Event ID 1910.
  • Note the Application ID (AppID) or GUID listed in the event details, as this identifies the broken DCOM exporter.

Step 2: Verify and Repair DCOM Permissions

  • Press Win + R, type dcomcnfg, and press Enter to open Component Services.
  • Navigate to Component Services > Computers > My Computer > DCOM Config.
  • Locate the application matching the GUID from Step 1, right-click it, select Properties, and go to the Security tab.
  • Under “Launch and Activation Permissions,” click Edit and ensure SYSTEM, Administrators, and INTERACTIVE have Local Launch and Local Activation rights.

Step 3: Re-register the Missing COM Component

  • Open Command Prompt as Administrator (right-click Start > Terminal (Admin)).
  • Run the following command to re-register the DLL associated with the exporter (replace with the actual file path):
  regsvr32 /s "C:\Windows\System32\[missing_component].dll"
  • If the exact DLL is unknown, run a full system file scan instead:
  sfc /scannow

Step 4: Clean Up Orphaned Registry Entries

  • Press Win + R, type regedit, and press Enter to open the Registry Editor.
  • Navigate to HKEY_CLASSES_ROOT\AppID\{GUID} (using the GUID identified in Step 1).
  • If the key exists but points to a non-existent file path, back up the key (right-click > Export) and then delete it to force Windows to reset the exporter reference.

Step 5: Restart the DCOM Server Process Launcher Service

  • Press Win + R, type services.msc, and press Enter.
  • Locate DCOM Server Process Launcher, right-click it, and select Restart.
  • Restart your computer to ensure the DCOM registry changes take full effect.

Alternative or Verification Steps

  • Verify the Fix: Reopen Event Viewer and check if Event ID 1910 reappears in the System log after reproducing the action that originally triggered the error (e.g., opening the specific application).
  • Alternative Solution: If the error persists, run System Restore (via rstrui.exe) to a restore point predating the issue, as this often resolves deep DCOM registry corruption that manual editing cannot fix.