Monterey 12.6.8 and Fusion 13.0.2 upgrade Problem

[jazzwineman]

So what the devil is going on with Monterey 12.6.8 and Fusion version 13.0.2. We have had xero problems with the previous versions 13.0.1 and others that we have used for years. 

All of the below I was doing remotely, as I normally do.

Our host VM is a server 2008 r2 that is purely for the development and testing of some new software. It works fine and so has the MAC and all previous versions of Fusions.

Today i installed the new Monterey 12.6.8 and when i started the VM- everything worked except a license that reads back to the MAc for authentication of the developing software and all of a sudden  I get "Mac has refused connection". Never had the  problem before and can see everything from the VM on the Mac.

So I decided the do the latest update  to VM Fusion to 13.0.2. I shut down the VM and then let Fusion do the auto update vs. doing a manual update. I immediately lose connection to both machines and apparently it just turned off the MAC, which is , under any and all conditions not going to be turned on remotely.   So what gives and why would the MAC all of a sudden deny a connection it has been using for years?

I figured I would do the upgrade and upgrade the tools and I should be fine (also would check to see if any permissions had been changed on the MAC.

Has anyone else had this problem before?

I cannot get to the location until Monday, but trying to sort out why the MAC was apparently turned off in the middle of the Auto update by VM Fusions.

The MAC is Intel based IMAC Pro. 

Thanks

Tom in Dallas.

[Technogeezer]

I would withhold judgement that the Fusion upgrade caused a reboot of your Mac until you get a chance to examine it. Fusion upgrades on their own don’t request reboots of macOS. Perhaps something’s up with networking.

Gather some data from the machine in question and then let’s see if we can figure out what went wrong. 

[jazzwineman]

Thanks. The machine came back up some 24 hours later and indicated it had rebooted from an error and it had to do with the update to Fusion. Fusion got updated in the process,  and works fine, but something went wrong with allowing it to do it itself. I think users should not allow for anything but a hard update by download and installing themselves.

Thanks

Tom

[ColoradoMarmot]

Fusion doesn't auto-update - you have to choose to download and install the update.  Even then, it doesn't require a reboot of MacOS, unless something is very wrong with the permissions on the machine (e.g. set a root password or running not as a real admin user).

[jazzwineman]

You misinterpreted what I said. You can do a live, in place upgrade  or you can download the actual version of the update, shut down Fusion and install. The later is the safest bet,

TBB

[jazzwineman]

stop trying to blame something else other than the program. None of what you suggest is the issue.