Technogeezer's Posts

It looks like VMware is now requiring the XSAVE CPU instruction, which was first made available in Intel Sandy Bridge and AMD Bulldozer architecture chips. They are not very clear on what Intel processor families are supported and try to dumb it down to the point where it's not very accurate.  There's a hint in a post by William Lam from VMware https://williamlam.com/2023/10/heads-up-esxi-8-0-update-2-requires-xsave-cpu-instruction-even-with-allowlegacycputrue.html that VMware now not-so-silently is enforcing the XSAVE requirement in ESXi 8.0U2. Given that ESXi and Workstation share technology, it would not surprise me if that hard requirement has made its way into Workstation. The article also indicates that XSAVE was introduced in the Intel Sandy Bridge and AMD Bulldozer CPUs in 2011 - I bet that's where VMware has gotten the date that they publish in their release notes. My concern is that it looks like your Celeron is a Silvermont microarchitecture used in low power Atom, Celeron and Pentium chips. It does not appear to be derived from a Sandy Lake or later CPU architecture. If that's indeed the case, then there's nothing you can do except drop back to 17.0.2.  

You wrote: But sharing (which didn't work in this VM before upgrading to 13.5) seems enabled on far too much, - so much so that I cant actually run windows explorer on the drive any more. Every instance I try to run gives me only the files on the host! In fact even the VM's desktop shows the files on the host's desktop! I have never seen this before?? Have you tried turning off sharing in the VM's properties then turning, disabling all shares, and then turning them on again one-by-one?

For any recent Linux distribution, open-vm-tools and open-vm-tools desktop packages are the VMware-recommended in-guest tools. If the older tools packages are installed, they should be removed as they are only maintained for older Linux distributions that don't have the open-vm-tools packages. In fact, for newer Linux distributions, Fusion will gray-out the option Virtual Machine > Install VMware Tools.  The open-vm-tools and open-vm-tools-desktop packages should be available in the Linux distro's repositories - the distro maintainer is responsible for distributing them, VMware just provides the open-source code. Some times the distros will install open-vm-tools and open-vm-tools-desktop for you. Other times they will not. Use your distro's package manager (apt, dnf, or zypper) to determine if the packages are already installed, and if not use the package manager to install them. Installing Fusion does not guarantee that the tools are installed in guests. On Windows unless you chose Easy Install when you created the VM, the tools may not be automatically installed (which means no copy/paste/drag/drop). . Doesn't hurt to try to install or upgrade Tools on Windows using the Fusion menus.

Like the "background items added" message, some times these repeated notifications are annoying.  If you don't want to put up with the nagging, at least there is a way out by editing the vmx file. You don't get the error on your laptop because Fusion on Apple Silicon never implemented virtual printers/thinprint. It never had the capability to insert those thinprint-related entries into the VM's configuration file.  It would be nice, however, if Fusion had a IPP-compatible print server built into it to replace ThinPrint. That way you wouldn't have to depend on a shared network printer or enabling printer sharing on your Mac - and could just use printers defined on your Mac.

The "current" log file can be viewed by right clicking on the VM in the Virtual Machine Library window, the holding down the Command key. The "Show in Finder" option will turn into "Open latest log file". However this is not ideal if you want to post a copy of the log file. You want access to the log file so you can zip it up and post it.  The easy way to find the log file if you want to post it is to go to the Finder, locate the VM "bundle", right click on it, and select "Show Package Contents".   

Since you are running on a 13th Gen Intel Core CPU, did you disable Windows' power throttling on vmware-vmx.exe : Drop into a command line prompt as Administrator Execute: powercfg /powerthrottling disable /path "C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe"  

You're going to need to unencrypt the VM before editing the file if you've selected the option to fully encrypt the VM. That also means removing the TPM first, decrpyting, make your edits, re-encrypt, and re-add the TPM device. That's not a big deal unless you decided to run Bitlocker in the VM - then you'll need to know how to recover Bitlocker.  Another thought might be this tool https://github.com/RF3/VMwareVMX (disclaimer: I've never used it and I'm not sure if it works for Workstation 17 or 17.5). Unless you have an absolute need to encrypt the VM's VMDK file, avoid the hassle and performance hit and choose to encrypt only the files needed for the TPM device. 

If you connect a USB device to the virtual machine, it is not available to the Mac. If you want to share the device between the Mac and a Windows virtual machine, leave the device connected to the Mac and do one of the following: Go to the VM's settings, enable Sharing, and add the drive's folder to the list of shared folders. This only works on an Intel Mac with Windows . Open the macOS System Preferences/System Settings, enable file sharing, and also enable Windows File Sharing. this works on both Intel and Apple Silicon Macs. Review the macOS documentation if you have questions on how to set up file sharing.. Once you have it configured, in WIndows you access the share by \\<ip address of your Mac> in Windows File Explorer.

@coolryg wrote: Windows ARM drivers for VMCI/vsock will be included in an upcoming release of VMtools. VMware does not actively maintain EHCI drivers. Microsoft has eliminated inbox EHCI drivers for Windows ARM. To disable the EHCI device, add usb.uhci.present = "FALSE" to the vmx configuration. That's a good tip, and I'll include it in the next version of the Companion document. 

Have you tried rebooting your Mac? If it won’t gracefully shut down, code down as much as you can and force restart the Mac.  It’s generally not a good idea to remove virtual machines from the Finder while a virtual machine may be running.  Still need to know what Mac you have, and what Ubuntu version you are trying to run in the VM.. 

Ouch... Well that's certainly not what you'd want... Some thoughts.... Fusion 12 definitely won't run on Mojave. The last version that ran on it was Fusion 11.5.x. Fusion 8 probably will not install on Mojave, but hey, you can give it a try if you want. There are reports of people saying it will work, but it may not, and it's 100% unsupported on Mojave. Were you running Mojave on that Mac with Fusion 8 before this started?  If you did, you were lucky that it worked. VMware doesn't sell a key that can be downgraded to  Fusion 11 any more. But if you purchased a Fusion 12 Pro key and it's still listed in the VMware licensing portal, you might still be able to downgrade that key to Fusion 11. If you have a Fusion 12 Player license (either free personal use or paid "commercial" license) that can't be downgraded. Fusion Player did not exist for Fusion 11. The migration path for Fusion 11 was to Fusion 12 Pro.    

If you deleted the VM from the disk and removed it from the Virtual Machine Library, Fusion shouldn't know anything more about it. Except... Did you happen to set the VM to start automatically when Fusion starts? Just curious. What version of Fusion are you running, what macOS version, what Mac hardware, and what Ubuntu server version? And by "the server crashed", does that mean that the VM crashed (with the typical Linux error messages) or did Fusion simply stop running the VM and present an error message?  

There's something definitely strange about that Windows 10 VM.  I have a Windows 10 x64 VM running on Fusion 13.5 and am not seeing this. Could you post the vmware.log file for that Windows 10 VM? Did you upgrade the virtual hardware version and/or VMware Tools in the VM when you upgraded to Fusion 13.5?? Did you download or copy the Photoshop Elements installer to the VM's hard disk or are you trying to extract it from a VMware shared folder?  

This is a known issue and discussed many times in the forum. It’s not really a bug but it is an annoyance. It’s a result of an older way that Fusion defines and launches the background tasks it needs. That method triggers the security related notifications you are seeing in macOS Ventura and later. The notices are annoying but harmless. There’s nothing you can do about them but click on the “x” in the upper left corner of the notification to dismiss them. VMware is aware of this,  and really needs to change the product so that the message does not keep popping up.