How to Fix Event ID 10029 Errors on Windows 11
If you found Event ID 10029 in Event Viewer and searched for a fix, the most important fact is this: the number alone does not tell you what happened. The same event ID is used by more than one Windows component, and in the two most common cases it is not a serious error at all. Before you change any service, permission, or setting, check one field first — the Source. That single detail decides whether 10029 means success, a harmless timeout, or something actually worth investigating.
The Number Alone Tells You Almost Nothing
Windows reuses event IDs across different logs and providers. An ID that signals a failure in one log can signal a routine success in another, which is why generic advice based only on “Event ID 10029” is unreliable. The event’s Source, the log it sits in, its Level (Information, Warning, or Error), and the wording on its General tab are what give it meaning. Read those first, and often there will be nothing left to fix.
Case 1: The Source Is Microsoft Windows LAPS
On PCs managed with Windows LAPS — Microsoft’s Local Administrator Password Solution, which automatically manages and rotates a local administrator password — Event ID 10029 appears in the LAPS Operational log. You can find that log in Event Viewer under Applications and Services Logs > Microsoft > Windows > LAPS > Operational.
In that log, 10029 is a success event: it records that LAPS successfully updated the managed password in Microsoft Entra ID (formerly Azure Active Directory). In plain terms, the password was processed as intended. There is no fault to repair, no service to restart, and no setting to change. If you are checking whether LAPS is working, this event is actually reassuring evidence that it is.
If LAPS itself were failing, you would look instead for failure events in the same log and a pattern of the password not being updated — not for 10029. Treat a lone 10029 there as information, and move on.
Case 2: The Source Is DistributedCOM
The other common source is DistributedCOM, usually shortened to DCOM, in the System log. Here the wording is different. Typical messages say that activation of a CLSID timed out while waiting for a named service to stop, or that a server with a given identifier has not registered with DCOM within the required timeout.
DCOM is the machinery Windows and applications use to start and talk to COM components. A 10029 from this source means one such activation waited too long — often because the service it was waiting for was busy shutting down, restarting, or finishing an update. On a PC that otherwise starts normally, opens its apps, and installs updates, an occasional DCOM 10029 is usually harmless background noise rather than damage.
Step One: Check the Source in Event Viewer
- Press Windows key + R, type eventvwr.msc, and press Enter.
- For a DCOM event, open Windows Logs > System. For a LAPS event, open the LAPS Operational log using the path above.
- Find an entry with Event ID 10029 and double-click it.
- Read the Source and Level shown at the top, then read the full message on the General tab. Use the Details tab if you need the exact identifiers.
- Note the time of the event. Was the PC shutting down, restarting, or installing updates at that moment? That context often explains it.
How to Identify the CLSID or AppID in a DCOM Event
A DCOM 10029 message names one or more identifiers in curly brackets, such as a CLSID and sometimes an AppID. Those are registration IDs for a component, not the name of a virus or a broken file. To find out which component they belong to:
- Copy the CLSID exactly as shown in the event, including the brackets.
- Press Windows key + R, type regedit, and press Enter.
- Look under HKEY_CLASSES_ROOT\CLSID for a key with that same CLSID. Its default value often shows the component’s friendly name, and an AppID value may be listed there too.
- If you need the friendly view, open Component Services by running dcomcnfg, then expand Component Services > Computers > My Computer > DCOM Config and look for the component by name or AppID.
Use this only to identify the component. Do not change its launch or activation permissions just because it appears in an event — changing DCOM permissions blindly can break the very app you are trying to help, and it is not needed for an occasional timeout.
When It Is Safe to Ignore, and When to Investigate
| Situation | What it usually means |
|---|---|
| 10029 in the LAPS Operational log | Success — the managed password was updated. No action needed. |
| Occasional DCOM 10029 at shutdown, restart, or during updates, with no other symptoms | A component waited on a busy service. Safe to ignore. |
| DCOM 10029 repeating constantly for the same CLSID, alongside a real problem | Worth investigating — for example an app or service that will not start, freezes, or an update that stays stuck. |
The deciding factor is always the symptom, not the log entry. If a named service never starts, an application named by the CLSID fails every time you launch it, or the events arrive in a continuous flood rather than now and then, note the CLSID and the service name from the message and troubleshoot that specific app or service. If there is no visible problem, there is usually no hidden one either.
What Not to Do
- Do not delete event logs to make the entry disappear — that hides information without changing anything.
- Do not disable DCOM or stop unrelated services because of this ID.
- Do not run downloaded “registry fix” tools aimed at event IDs.
- Do not edit DCOM or registry permissions unless a specific, failing component has been identified and you understand the change you are making.
Frequently Asked Questions
Is Event ID 10029 always an error?
No. From the LAPS source it is a success event, and from DistributedCOM it is a timeout report that is often harmless. Check the Source and Level before treating it as a fault.
Can Event ID 10029 damage my PC?
The event itself is just a log entry — it does not damage anything. At most, a repeated DCOM version can point to an app or service that is struggling, which is the thing to check.
Should I clear the event log so the warnings stop?
No. Clearing the log does not fix a component, and the entry will simply return if the underlying timeout happens again. Read the Source first instead.