erik5678's Posts

My solution was eventually to restore the VM from a backup from before the encryption, clone the disk of the encrypted one using Macrium Reflect, and then restore it to the new unencrypted VM. I never figured out the encryption password, but as long as the login keychain was unlocked it would boot. If it was not, it would ask for a password. The password was not in the keychain, at least not under any name showing up under vmware, fusion or the name of the VM. There is however a fusion encryption key in there, but no password that can be used to decrypt as far as I can tell.

Linux, BSD or anything else ARM native without licensing limitations that will run in VMware. With virtualization, the guest operating system has to use the same architecture as the host computer. x86 host means x86 guests, ARM host means ARM guests. Otherwise hardware has to be emulated which is slow and not something VMware Fusion does. I expect microsoft to open up ARM licenses for Windows at some point. Rumor is that they have an exclusivity deal with Qualcomm that's about to expire, but if that will change things or if ARM PC components have to be made available on the market for things to change we'll have to wait and see. When users can build their own ARM PCs they kinda have to sell ARM licenses. The limitation today isn't that Windows can't run on ARM, it's that there's no legal way of getting a Windows on ARM license, and thus no reason for VMware to put in the time and effort to support it.

Basically, as things are right now you can not run Windows in VMware on Apple Silicon. There are some ways to do it, but they don't work well and since there is no way to get a license VMware does not make any effort to support Windows on ARM. If Microsoft were to make a suitable license available I'm sure the VMware Fusion guys will support it eventually, but for now there are no VMware Tools available for Windows on ARM, and any methods to install it anyways are unsupported and most likely won't work well if at all. What you can do is run Linux VMs, such as Ubuntu and Fedora, that are available for ARM. Linux has been supporting ARM for several years, so ARM support in modern Linux distributions is very good. open-vm-tools is available through most package managers in these Linux distributions and is usually installed by default when installing a Linux OS in a VM. It works really well.   Long story short: If you need a Windows VM you need to run a suitable version of VMware on an x86 platform, meaning Intel or AMD processor. An Intel Mac (VMware Fusion) or a PC with Windows or Linux (VMware Workstation). If you need a Linux VM that's very much possible on Apple Silicon, and it works well using the VMware Fusion Tech Preview.

Hi, It was quick. Less than 20 seconds. The disks are not taking up the whole assigned space, so they aren't fully encrypted. The vTPM article explains it then, but it doesn't explain why this happened severals days after adding the vTPM line to the vmx file. I had rebooted and shut down the VM several times since, but all of a sudden today it did the encryption. Thanks for the link to the article, now I know what I have to pay attention to going forward

I've done this, and the tool still complains about no TPM 2.0 support. It doesn't really matter because my Core i7-7700K isn't supported by Windows 11 for whatever reason, but I'm not sure how to make the virtual TPM work.

I'm having the same issue. I have converted the disk to GPT, but there is no firmware type option in advanced settings, and I can't find any guidance on how to edit the vmx file to properly change this. This is the guide I found: Configure a Firmware Type - Fusion 12   

Interesting. Glad to know it's been filed. I spent some time scratching my head as to why the VM wouldn't boot until I tried changing the RAM setting. The interesting thing is that 6192 works, but it's not on the slider so I'm not sure that's the whole story. I tried that since it was 2x 3096 and I figured maybe there's something to it but there wasn't.

This has now gotten so bad for me that I'm about to uninstall Fusion and see if it's the only problem. Maybe I'll install it again after a few days, or maybe I'll wait for an update (which for all we know could take months). I just launched Fusion to check my version number, and almost immediately got a disconnect/reconnect of my magic trackpad. Then I closed it again, and got another disconnect/reconnect. Then I realized that I had forgot to check my build number and launched Fusion again. Now my trackpad lost it's connection, and it didn't come back. After a few seconds I tried to turn bluetooth off and on again (btw, I'm always thinking about IT Crowd when I turn something off and on again), but it wouldn't turn off. Less than a minute later I got the "Bluetooth not available" error and now I'm using a USB mouse that I have placed on my desk for the countless times this happens. I avoid using my VM's as much as I possibly can to not have to deal with this, but it also sometimes happen when VMware isn't running (although I just get a disconnect/connect then), and when VMware had been running hours ago (often bluetooth not available at this point). It's absolutely ridiculous that this issue hasn't been fixed yet! (This happens on a 2017 iMac btw. I initially though I had a hardware error and would have to send it in for service, but I eventually made the connection between Fusion and this issue and later found this thread)

I have the same problem. Bluetooth disconnects my magic trackpad for a few seconds. Sometimes when I launch fusion, sometimes when I start a VM, sometimes when I close fusion. It also happens when I have not been running fusion since boot, interestingly enough, so I may have another problem too, unless fusion install something that's constantly affecting bluetooth. Right now it's so bad that my mac reports "Bluetooth not available" and I have had to pull a USB mouse out of a drawer while waiting for a suitable time to reboot. I hope the update is release very soon.