Background items added loop bug on Fusion 13

[MikeRundle]

VMware Fusion 13 keeps on adding these launch agents / daemons files on every start and deleting them on every exist

Please fix this bug it's really annoying and it seems like it happened before with older versions

https://communities.vmware.com/t5/VMware-Fusion-Discussions/2-items-added-to-LaunchDaemons-on-each-l...

macOS Ventura 13.0.1

VMware Fusion Professional 13.0.0 (20802013)

[Technogeezer]

It's annoying, but I wouldn't consider it a bug.

Fusion adds its background items each time you start it and uses macOS Launch Services to start them up. Fusion also removes them when you finish with Fusion. That's so they won't get launched and consume resources when you don't need them.  It's done that for a couple of releases now, so it's not new behavior.

What is new is how Ventura reacts. Ventura changed behavior over prior versions of macOS. It now alerts you to the fact that something's being added as a background launch item. It's good for security for Ventura to let you know about this.  But now Fusion's behavior gets to be a bit annoying.

That being said, I hope that VMware can come up with a way to stop the annoyance.

[MikeRundle]

OK I got it now, The problem is that you can't even silence that behavior from macOS Notification settings

[Technogeezer]

Don't get me wrong.  I know it's annoying - and I see it every time I start Fusion as well. There doesn't seem to be any way for mere mortals to silence it. It's up to VMware to do so if Apple will allow it. 

[BMcGroarty]

I'd still consider it a bug. Programs should minimize configuration changes on the host OS. VMWare doesn't have to add and remove items continuously in order to achieve its current functionality. Instead, it could add a configuration check. On each launch, it can exit quickly if it isn't needed. If performance is the consideration, it can be accomplished in a few lines of shell script or with a small stub binary that doesn't load additional libraries. Either option would have an imperceptible performance impact as long as it doesn't introduce any significant sequence dependencies in the launch configuration.

[Technogeezer]

Agreed.

This reminds me of two absolutely infuriating responses I would get when reporting things like this: “It’s not a bug, it’s a feature” or “working as designed”. 

Both used to defend the indefensible: bad design or implementation decisions..

[ColoradoMarmot]

I expect that caught them off guard with Ventura - it was added late in the beta cycle.  Hopefully 13.1 will fix it.

[jcasalino]

Still happens with Fusion 13.0.1 😞

It's definitely annoying - it would be less so if Ventura made it a sliding notification but I don't know if that can be changed either.

[ColoradoMarmot]

No, you can't hide the system security notifications.

I've gotten into the habit of 'start vm, kill notification' double click 🙂

[TomsCat · Accepted solution]

For me with VMware Fusion the following solution helped:

1. Launch VMWare Fusion.

2. In the finder go to /Library/LaunchDaemons .

3. Open /Library/LaunchAgents in another finder window.

4. Copy the 4 files that contain the word vmware from /Library/LaunchDaemons to /Library/LaunchAgents. Your admin password will be required.

[Doc69]

Thanks, you made my day! After months of seeing the "Background Items Added" pop-up every time I launch Fusion, it's finally gone! 

[TECH198]

Thanks.  This continues to work in Fusion 13.0.1

What is this "Background items" for ..btw?