Fix COMADMIN_E_APP_FILE_WRITEFAIL (0X80110407) – 2 Steps

I know this error is infuriating

You're trying to configure a COM+ application, maybe after a Windows update or a security policy change, and bam—COMADMIN_E_APP_FILE_WRITEFAIL (0X80110407). It feels like Windows just slammed the door. I've been there, and the fix is simpler than you'd think.

The real fix: give COM+ back its write access

The error means the COM+ system can't write to its internal application files. Usually, it's a permissions issue with the %SystemRoot%\registration folder or the COM+ catalog itself. Here's what actually works:

Step 1: Reset COM+ application permissions

Open Component Services (run dcomcnfg from the Run box).
Go to Component Services > Computers > My Computer > COM+ Applications.
Right-click the application that's throwing the error and choose Properties.
Go to the Security tab. Under Access Permissions, click Edit.
Make sure Everyone and NETWORK SERVICE have Allow checked for Local Access. If they don't, add them.
Under Launch and Activation Permissions, do the same—add NETWORK SERVICE with Local Launch and Local Activation.
Click OK twice.

Step 2: Repair the registration folder permissions

This is the part most guides skip. The C:\Windows\Registration folder stores the COM+ application files. If its permissions get borked, you get 0X80110407.

Open an elevated Command Prompt (Run as Administrator).

Run:

icacls %SystemRoot%\registration /grant "NT AUTHORITY\NETWORK SERVICE":(OI)(CI)F

Then:

icacls %SystemRoot%\registration /grant "BUILTIN\Administrators":(OI)(CI)F

Close the Command Prompt.
Restart the COM+ System Application service. Open services.msc, find it, right-click and choose Restart.

Now try opening your COM+ application again. The error should be gone.

Why this works

The COM+ system runs under the NETWORK SERVICE account. When Windows updates or security software tighten permissions, that account can lose write access to the registration folder. The error code 0X80110407 is literally saying "I can't write the app file." By restoring those permissions, you're giving the COM+ runtime exactly what it needs—no more, no less. The icacls commands with (OI)(CI) flags apply the permissions to existing files and any new ones created later, which prevents the same error from coming back when you create a new COM+ application.

Less common variations of this issue

Sometimes the problem isn't permissions—it's corruption. Here's what else I've seen:

Corrupted COM+ catalog

If the fix above doesn't work, the COM+ catalog itself might be toast. You can rebuild it using the COM+ Administration Tool:

Open an elevated Command Prompt.
Run:
```
regsvr32 /u comadmin.dll
```
Then:
```
regsvr32 comadmin.dll
```
Restart the COM+ System Application service.

This re-registers the COM+ admin DLL, which can fix catalog corruption without nuking your existing applications. I've used this on Windows Server 2019 after a bad rollback from a cumulative update.

Antivirus blocking writes

I once spent three hours on this error only to find that McAfee was locking C:\Windows\Registration\*.clb files. If you run enterprise AV (like Sophos or Trend Micro), temporarily disable it and try again. If the error vanishes, add an exclusion for %SystemRoot%\registration\*.clb and %SystemRoot%\registration\*.dll.

Disk space or file system issues

You'd think this would throw a different error, but I've seen 0X80110407 on a drive with less than 100 MB free. Check your system drive space. Also run chkdsk C: /f to rule out file system corruption—especially on older Windows Server 2012 R2 boxes.

How to prevent this from happening again

Once you've fixed it, here's how to keep it fixed:

Set explicit permissions on the Registration folder. That icacls command above? Put it in a startup script or Group Policy Object. Don't rely on inheritance—it gets broken by updates.
Don't let security scanners run wild on COM+ files. Exclude %SystemRoot%\Registration from real-time antivirus scanning. It's a static folder; it doesn't need scanning.
Patch Windows regularly, but test first. Cumulative updates have reset permissions on me twice (October 2021 and April 2023 updates on Server 2022). Always check COM+ functionality in a test environment after patching.
Monitor the COM+ System Application service. Set up a simple alert in Event Viewer for event ID 4199 under Applications and Services Logs > Microsoft > Windows > COM+. That event fires when write failures happen.

That's it. No fluff, no 20-step guide. You should be back to managing your COM+ apps in under 10 minutes. If you're still stuck, drop a comment with your exact Windows version and any recent changes—I'll help you narrow it down.