I can verify the Fusion update has started acting as expected since I first tried.

VMware Tools versions are not necessarily linked to the hypervisor version, so just because Fusion was v12 doesn’t mean that Tools would be v12: particularly when Workstation was v16 until this week, so Fusion going to v13 doesn’t mean Tools will be v13 too.

https://packages.vmware.com/tools/releases/

Yes, that is why I included my experience with it in my summary of my install.  I believe it isn't unreasonable to assume others might wonder the very same thing after the update. That is what makes this a community worth being part of. 

Perhaps a stupid question, but shouldn't the new Fusion update (13.5 I believe) automatically update for those that have the e.x.p. version installed?   Running an M1 Apple laptop.  When I "check for updates" on the e.x.p., nothing shows up.  Question:  should I even bother updating from e.x.p. if its function does everything I need?

Yes you should stop using the Tech Preview and start using 13.5. Hard Stop. In my humble opinion, VMware should hard-code an expiration date into any public betas so that they stop working at some point in time.

You continue to run the Tech Preview at your own risk. It's a public beta and the beta period is over. The reason it's a risk is that Tech Previews receive no support or updates from VMware (even security updates. If you should have a problem, the first thing that anyone will say is "can you reproduce this on the official 13.5 release?" Security issues that affect the Tech Preview will absolutely not be patched. And if Apple should change something that breaks Fusion (it's happened - for example with VoiceOver on Sonoma) it will not be fixed in beta releases. 

There are also features in the 13.5 release that weren't in the Tech Preview. The built-in tool for download of Windows 11 ARM is the big one. 

The Tech Previews do not offer to upgrade to official releases as they aren't part of any official release stream. They have no release number other than the build. Could VMware do that? Perhaps they could - but they've chosen not to. do that. In the grand scheme of things is it really that hard to download the official release and run the installer? Your VMs that worked on the Tech Preview will continue to work. 

My recommendation when moving from the Tech Preview to Fusion 13.5 is to drag the Tech Preview application from the Applications folder to the Trash, empty the Trash, and install Fusion 13.5 from the installer downloaded from VMware. That avoids any confusion about what version of Fusion you're running. 

@Technogeezerthank you as always for your help.  Updating from the previous Fusion (13.1? I think) to 13.5 on my other intel based iMac - which should have been like falling off a log - turned into a wasted morning.  Virtually noting worked as detailed in the upgrade notes.  I eventually got it done, and the access to the Windows 11 ARM was helpful.  This is the reason I asked about e.x.p. - I assume it will not be an easy migration because the 13.1 to 13.5 wasn't on my other computer.  As I think you said in another post, Parallels still has an easier install process.  But as I am a non-commercial user, you can't beat the price of free for Fusion.  You make a good case for doing away with the Tech Preview, and I will be doing so.  Thanks again.  

@dminter -That's unfortunate. I agree that a Fusion upgrade from a prior version should not have been a multi-hour science project. Especially on an Intel Mac. That's one reason why I like the full installer for single dot *x.0 -> x.5" releases. Make sure it's as close to a clean install as possible. 

if it's that problematic from official release to official release, I'd hate to think what kind of land mines would be out there from trying to upgrade over a beta release....

@Technogeezer Thanks for the great advice, which I followed to replace the e.x.p. version of VMware with the 13.5 version on my Apple M1 computer.  It was shockingly easy and fast.  It found and used the Windows 11 ARM I have been using, fully activated.  Literally took less than 10 minutes.