EXO macOS Uninstall Leaves APFS Container Behind

[JohnLyonX]

Summary

After uninstalling EXO on macOS using the official uninstaller script, a dedicated APFS container and volume named EXO remain on disk. The software components are fully removed, but the disk structure created by the application is not cleaned up.

What Was Removed Successfully
• Background network daemon
• LaunchDaemon service
• Network configuration changes
• Log files
• EXO network location

No EXO processes, services, or network extensions remain active.

What Remains

An APFS container (~890 MB) with a single volume:
• Container: disk6
• Volume Name: EXO
• Role: None
• Mount Point: Not mounted
• Not part of system volume group

This container is separate from the macOS system container and does not affect system operation, but it occupies disk space and cannot be removed from normal macOS mode.

Disk Structure Evidence
diskutil apfs list

Shows:
• Main system container (≈1TB) with standard macOS volumes
• Separate small container (~890MB) containing only the EXO volume

Issue

The official uninstaller does not remove the APFS container created by EXO.
Users are left with a persistent disk container that requires Recovery Mode or advanced disk operations to remove.

[JohnLyonX]