Hi Developers, I've run into an interesting issue when upgrading my system extension powered app. I use system extensions to provide security software to protect users. We recently released a new version of our software and extension. A small subset of users upon upgrade are running into an issue where both the old system extension and new system extension are listed as [active enabled]. Both the old and new extension have identical signing, bundle IDs, and team IDs, with the only difference being a version change. Our container app logged out an error code 3 and then error code 4 on subsequent launch attempts. 3 means it was trying to launch from a location other than /Applications which doesn't make sense as our app is located in /Applications. 4 means "extension not found" It's looking pretty clear that something has gone wrong during the upgrade/replacement process but we're not sure what. We have several questions: How can we resolve this issue without requiring users to disable SIP and use systemextensionsctl? This is not a customer friendly way of resolving the issue and our customers are not necessarily technical, making this a challenge to support. What could have possibly gone wrong during our upgrade to result in multiple system extensions with the same teamID and bundleID being installed? Running ps aux does show only one system extension running, so even though systemextensionsctl list shows multiple as active and enabled, only one is running Is this possibly a bug in Big Sur that needs to be addressed by Apple? At a minimum, it would be great if a user or software developer could uninstall their own system extensions as easily as they can install... Thanks, Trace