---

@Geoffrey84 wrote:

Whenever I launch the VMware Fusion application, up to 5 PLIST files are copied to /Library/LaunchDaemons but they all disappear upon restarting.  I tried to make each of these "Read Only" ("Locked") but they were still removed and then restored when reopening the application.  Perhaps the fact that I'm currently running VMware Fusion in macOS Ventura Beta 6 has something to do with this irregularity.

---

Interesting find. Never noticed that because I wasn't looking for it.

Yes, indeed Fusion does create entries in /Library/LaunchDaemons when you invoke it, and it's not just an artifact of Ventura (I'm running Monterey).

Fusion has for as long as I can remember dynamically loaded components that it needed. In the past that involved kernel extensions. My thought is that a similar mechanisms is used to dynamically load the system extensions that Fusion now uses. Which appears to be to move things into the areas that launchd looks for and then rely on launchd to start the required components.