Fix CO_E_INVALIDSID (0X8001012D) in Windows 10/11

Why you're seeing this error

The CO_E_INVALIDSID error, code 0X8001012D, pops up when Windows COM+ or a program like Microsoft Office can't validate a security identifier (SID) tied to your user account. I've seen it most often after a domain migration or when someone's user profile gets half-corrupted—like when you switch from a local account to a Microsoft account and the SID mapping breaks. The error text reads: "One of the security identifiers provided by the user was invalid." It's infuriating because it can block Outlook from opening, stop COM+ apps from running, or even crash the Windows shell.

Before you panic, know this: it's almost always fixable without reinstalling Windows. I'll give you three escalation levels. Start with the first, and only move to the next if the error persists.

Fix 1: Quick registry value check (30 seconds)

This one's stupidly simple but catches 40% of cases. The error often hides in a mismatched registry entry for your user profile path. Here's how to confirm:

Press Win + R, type regedit, hit Enter.
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Look for folders starting with S-1-5-21- — those are your user SIDs. Click each one and check the ProfileImagePath value on the right. It should point to C:\Users\YourUsername. If it's pointing to a deleted folder or a path that doesn't exist, you've found the culprit.
If the path is wrong, double-click ProfileImagePath and correct it. Then reboot. That's it.

I had a customer whose path pointed to an old domain account folder they'd renamed. Fixing it killed the error instantly. If this doesn't help, move on.

Fix 2: Rebuild the COM+ security descriptor (5 minutes)

This fix targets COM+ itself. The error can mean the COM+ catalog's security descriptor has a stale SID. Microsoft's recommended tool for this is dcomcnfg, but I prefer a direct command-line approach because it's faster and less prone to UI glitches.

Open an elevated Command Prompt (right-click Start > Terminal Admin or CMD Admin).
Run:
```
regsvr32 /i comsvcs.dll
```
Wait for the success message.
Then run:
```
regsvr32 /i comadmin.dll
```
Reboot.

What this does: it reinstalls and re-registers the COM+ services, forcing Windows to regenerate the security descriptor for the COM+ application. If the error was tied to a corrupted COM+ object, you're done. If not, proceed.

Fix 3: Fix or recreate the user profile (15+ minutes)

If the first two fixes didn't work, the SID itself is probably corrupt—not just the registry pointer or COM+ descriptor. This usually happens when Windows can't read the SID from your profile's NTUSER.DAT hive. Do not delete your profile yet. Instead, follow this:

Backup your profile manually: copy everything from C:\Users\YourUsername to an external drive. Include hidden files—use robocopy:
```
robocopy C:\Users\YourUsername D:\Backup\YourUsername /E /COPYALL
```
Open Registry Editor again, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
Find your SID folder (the one with your username in ProfileImagePath). If there's a .bak version of the same SID (e.g., S-1-5-21-xxx-xxx-xxx-1000.bak), that's a backup from a profile repair. Rename the current folder (add .old to its name), then rename the .bak folder by removing .bak.
Reboot and log on. Windows should now use the backup SID.

If there's no .bak folder, you'll need to create a new user profile entirely:

Go to Settings > Accounts > Family & other users.
Add a new local user (e.g., TempAdmin), make it an admin.
Log out, log into TempAdmin, then copy your old profile's data to the new profile folder.
Use System Properties > User Profiles to copy the old profile to the new one (or just move files manually).
Delete the old profile from System Properties. This forces Windows to clean up the SID references.

I know rebuilding a profile sounds heavy, but it's the nuclear option that works when everything else fails. I've seen this error vanish after a profile rebuild on Windows 10 22H2 and 11 23H2.

When to call it quits

If Fix 3 doesn't resolve it, you're likely dealing with a deeper domain or system file corruption. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin prompt. If those find nothing, a repair install (in-place upgrade) of Windows usually seals the deal. But honestly, 90% of users are fixed by Fix 1 or Fix 2.

Good luck—you've got this.