COMADMIN_E_BASEPARTITION_REQUIRED_IN_SET (0X8011081F) Fix

Why This Error Happens

You're trying to delete a base partition in COM+ and Windows won't let you. The error says it all — the base application partition has to exist in every partition set. But here's the thing: you're probably not trying to remove the actual default partition. You're stuck with a leftover or misconfigured partition that won't go away cleanly.

I've seen this most often on Windows Server 2016 and 2019 boxes where someone installed an app that created extra COM+ partitions, then uninstalled it badly. The partition registry entries stay behind, and when you try to clean them up through Component Services, you get this 0X8011081F error. Had a client last month whose entire print queue died because of this — their ERP software's COM+ partition got corrupted and nothing else would work until we cleaned it out.

Cause 1: You're Trying to Delete the Wrong Partition

The most common scenario is you're mistaking a base partition for a regular one. Every COM+ partition set has exactly one base partition — it's the default one created when COM+ was installed. You can't remove it because every partition set needs it.

How to Check What You're Dealing With

1. Open Component Services: dcomcnfg from Run or Command Prompt
2. Expand Console Root → Component Services → COM+ Applications
3. Right-click the partition you want to remove and select Properties
4. Look at the Partitions tab — if you see "Base Application Partition" listed, you can't remove it

If it's the base partition, don't try removing it. Instead, check if you have duplicate partitions by going to COM+ Partitions folder and seeing what's there. If you see multiple base partitions (should only be one), that's where the real problem is.

The fix: Leave the base partition alone. If you have a legitimate app partition that's stuck, jump to Cause 2. If you have orphaned partition entries, go to Cause 3.

Cause 2: Corrupted Partition Set Reference

This one's subtle. The partition set metadata gets out of sync — you might have a partition that references itself as a base partition in its own properties, but the system sees it differently. I've seen this happen after a failed migration from Windows Server 2012 R2 to 2019.

Step-by-Step Fix

1. Open Component Services as Administrator
2. Go to Console Root → Component Services → Computers → My Computer → COM+ Applications
3. Sort by the Partition column — look for any apps showing Base Application Partition that shouldn't be there
4. Right-click any such app → Properties → Advanced tab → uncheck Enable Partitioning
5. Apply, then restart the COM+ System Application service: net stop COMSysApp && net start COMSysApp
6. Now try removing the partition again

If that doesn't work, you might need to export the partition's apps first, delete them, then remove the partition. Export the apps: right-click each app → Export → save as .MSI. Delete them, remove the partition, then reimport.

Cause 3: Orphaned Base Partition in Registry

This is the dirty one. Apps that create COM+ partitions sometimes leave registry keys behind. I've seen this with older versions of: SAP Business One, Sage 100, and certain HP management tools. The partition shows in the UI but doesn't delete properly.

Manual Registry Cleanup (Backup First — No Joke)

Before you touch the registry, export the entire COM+ Applications branch: HKEY_CLASSES_ROOT\CLSID\{0000030C-0000-0000-C000-000000000046} is a safe export point. But here's what you actually need:

1. Open Regedit as Administrator
2. Go to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\COM+ Partitions

3. Look for keys under PartitionSets — each set has a GUID. Expand each one
4. Find BasePartition value — if it points to a partition GUID that no longer exists or is corrupted, you need to fix it
5. Check under Partitions key — locate the partition you're trying to remove. If it shows Type = 1 (base) but shouldn't be, change it to Type = 2 (regular) and try removing again

If that doesn't help, delete the entire partition key under Partitions (after exporting it). Then restart the COM+ System Application service and run regsvr32 comadmin.dll from an elevated prompt. This forces COM+ to rebuild its partition list.

Quick-Reference Summary Table

One last thing: if you're doing this on a production server (and you shouldn't be without testing), shut down any apps using COM+ first. I've seen the fix work perfectly on a test VM and then blue-screen a live box because something was holding the partition open. Always test.