Fix COMADMIN_E_PARTITION_MSI_ONLY (0X80110819) in 2 Steps

Yeah, this one's annoying—you're trying to install a COM+ application and Windows just flat-out refuses with COMADMIN_E_PARTITION_MSI_ONLY (0X80110819). You're not alone, and the fix is simpler than you'd think.

The Quick Fix

What's actually happening here is that COM+ is trying to install your application onto a partition that isn't NTFS. COM+ only allows MSI-based installs to go to NTFS volumes, and if your default partition is FAT32 or something else, you get this exact error.

Here's what to do, step by step:

1. Open Disk Management — right-click Start and pick it, or run diskmgmt.msc.
2. Check which partition is marked as Active or System. That's the one COM+ will try to use by default.
3. If that partition isn't NTFS, you've found your problem. The easiest fix is to convert it: run convert C: /fs:ntfs in an elevated command prompt (replace C: with your drive letter). This won't wipe the drive, just changes the filesystem.
4. If conversion isn't possible (e.g., it's a recovery partition), then change the COM+ partition mapping instead.

Remap the COM+ Partition

If you can't convert the system partition, you can tell COM+ where to put its stuff:

1. Open Component Services — run dcomcnfg.
2. Expand Component Services → Computers → My Computer → COM+ Partitions.
3. Right-click COM+ Partitions and select Properties.
4. Go to the Default Partition tab.
5. Change the Partition location to an NTFS drive you have, like D:\.
6. Click OK and restart the COM+ service (or just reboot — it's faster).

That's it. After this, try your install again and it should go through.

Why This Works

The reason this error exists is that COM+ applications are distributed as MSI files. MSI files require a Windows Installer service, and on non-NTFS volumes, some of the transactional features that MSI depends on simply aren't available. NTFS supports transactions (via the TxF layer), and FAT32 doesn't. So COM+ refuses to even start the install, returning the 0X80110819 code.

By either converting the drive to NTFS or pointing COM+ to an NTFS partition, you're giving the installer what it needs to operate. The error isn't about your code or the MSI itself—it's purely a filesystem compatibility check.

Less Common Variations

Sometimes the error shows up in a different context. Here are a few I've seen:

1. Happens Only for 32-bit Apps on 64-bit Windows

If you're on a 64-bit OS and installing a 32-bit COM+ app, there's a separate partition for 32-bit stuff. That partition might not exist or could point to a non-NTFS location. Check HKLM\Software\Wow6432Node\Microsoft\COM3\Partitions in the registry and fix the path there.

2. Error After Moving the System Drive

If you cloned or moved your system drive, the COM+ partition mapping might still point to the old drive letter. Re-map it in dcomcnfg as shown above, but also check that the registry keys under HKLM\Software\Microsoft\COM3\Partitions match your current layout.

3. Group Policy Overrides

In a domain environment, a GPO might force the default partition to a network share or a non-NTFS local drive. If your local fix doesn't stick, check gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Application Compatibility and look for anything COM+ related. You might need to override with a local policy.

Prevention Tips

Now that you've fixed it, keep it from coming back:

• Always keep your system partition NTFS. Modern Windows won't even install on FAT32, but if you've got an old dual-boot setup, fix it.
• When setting up COM+ partitions manually, pick a drive you know is NTFS and stays mounted. Don't use removable drives.
• After major OS updates, check the COM+ partition mapping. Updates occasionally reset it.
• If you're a developer, ensure your installer checks for NTFS availability before trying to register COM+ components. A simple check in your MSI will save your users this headache.

That's the whole story. The error is dumb, but the fix is clean. Now go install that app.