Fusion 13 crashes after asking to upgrade VM encryption

[Alexander Zavorine]

Host macOS Sequoia 15.3.1, Fusion 13.6.2, guest OS Windows 10.

I have Windows 10 encrypted VM that worked fine starting on Fusion 8 until the version 13. Now after launching VM I got a prompt to upgrade the encryption from CBC to XTS encryption mode.

My VM is on the removable drive and I use it sometimes with the older versions of Fusion. So, I decline (click "Don't upgrade"). After that the Fusion crashes and leaves the VM locked.

I tried to start VM with `vmcli` as suggested some thread on https://www.reddit.com/r/vmware/comments/1fywy7f/issues_with_encryption_in_fusion_136_fusion/?rdt=61185, and it works. But as my VM is on the removable drive `vmcli` uses default answer 'I copied it' on the silent question 'Did you move this virtual machine, or did you copy it?' After that VM get a new MAC address and all activation/licensing on guest OS fails.

Is there any way to help me?

[Technogeezer]

I'm curious about what happened when the VM "crashes and leaves the VM locked". Especially since you opted not to upgrade the VM. To do that we'll need to look at logs. 

Can you perform a quick data collection using the following attached script when Fusion is shut down? (my script collects a lot less information than even the Fusion quick support data collection option). 

Download it to your Downloads folder, extract it, then open a terminal and execute the script as follows:

cd ~/Downloads
./collect_info.sh /full-path-to-your-VM.vmwarevm

I don't think that there is any way to tell vmcli to avoid the "I copied it" question that leads to Windows re-activation. You're going to get that question in any case if you have used that VM on another machine. The "fingerprint" of where the VM was last used is somewhat based on system-specific information. 

I'm also assuming that you're using that VM on another system to run it with an older version of Fusion. It's generally considered a bad practice to have two versions of Fusion installed on the same machine - it's been reported to lead to problems. 

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

Attachment(s)

collect_info.sh.zip   1 KB 1 version

[Alexander Zavorine]

Hi Paul,

Thanks for looking into it. The collected info is attached.

Strange that it looks nobody reported this problem beside me. If you look into Reddit thread I cited before they have also the same problem, but for them Fusion 13.6 crashes regardless if they agree or not to upgrade encryption. And they have Windows 11 VM for which the encryption is not optional as for Windows 10.

Cheers,

Al

Attachment(s)

fusion_data.202503031811.zip   225 KB 1 version

[Technogeezer]

From an initial review of the logs, the power-on attempt on your newer Mac is complaining about a missing encryption key.  It's also using full encryption, which rules out a number of other issues. 

Some questions:

I assume that this VM still works if you try to power it up on your older Mac? The logs are indicating that it does, but just wanted to make sure.

When running this VM on the older Mac, do you physically connect it to the other Mac, or is it being run from a shared folder on this Mac?

Do you need to enter the password when attempting to power on this VM or do you have to enter it manually?

If the password is saved in the Keychain can you check it's entry (using the Keychain Access utility in both Macs) to see if the saved password is identical?

Does Fusion think that this VM is a Shared Virtual Machine in the GUI on the newer Mac?

If this VM is decrypted on the older Mac, does the VM power on (if you do this, power down the VM older Mac, close Fusion, then make a copy of this VM via the Finder. Locate the copy of the VM on the older Mac, add it to the virtual machine library, then try and decrypt the VM. Note that you'll need and additional 2x the disk space on the drive to to this - 1 extra copy for the "clone", and an additional 1x temp space to decrypt this VM. Then see if you can power up this unencrypted VM on both Macs. (we'll leave the original VM alone while we do this).

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Alexander Zavorine]

Yes, this VM works fine on older Macs (Catalina with Fusion 11, and High Sierra with Fusion 10.) Always use physical Mac with Thunderbolt removable SSD. And always input password manually, never save it. 

I think it is very likely the problem of the Fusion newer version (by the way just tried 13.6.3 with the same result) as it worked fine on the same Mac with the older version of Fusion (I remember this prompt to update encryption, which I always declined and thought why they cannot make an option to remember my decision?) and still works with vmcli now. I understand that with Fusion becoming a freeware (although I bought all versions of Fusion from 8 to 13) nobody will fix any edge case bugs. 

[Technogeezer]

> and still works with vmcli now.

Just so I'm clear. Do you mean vmcli or vmrun? If you're using vmrun start, I also assume you're providing the password on the command line with the -vp argument. Or if using vmcli power start, then you are responding with the password when prompted.

Can you check your user's login keychain to see if there are any "VMware encryption password" entries in there?

And can you post a copy of the vminventory files found in /Library/Application Support/VMware/VMware Fusion and /Users/<your user name>/Library/Application Support/VMware Fusion/vminventory from the failing Mac?

> I understand that with Fusion becoming a freeware (although I bought all versions of Fusion from 8 to 13) nobody will fix any edge case bugs. 

I too purchased Fusion licenses in the past, but did not purchase a support package. It was just as difficult in those days to get a bug reported and fixed, unfortunately.  Broadcom (and in the past, VMware) has no problems quickly putting out an update when a security vulnerability is found (such as with Fusion 13.6.3), but drags their feet on real bugs that people have found. Or at least if they did fix some bugs, they don't document it in the release notes.

Broadcom needs to do a much better job of listening to this forum and responding to people that have problems with their desktop products. Simply dumping it for free and saying essentially "good luck with it" isn't the best way to get people to use their products. The community forums can only go so far to help ourselves -- and we can't fix bugs.  

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Jose Albarran]

Hi, Paul (et al)

I do not now if you/somebody has already solved this issue. I have a VM that:

• Always ask for upgrade the encryption
• Normally, when I select "Don't" Fusion crashes (

  Professional Version 13.6.3 (24585314))

• When I try, retry and retry, sometimes it starts
• I'm not able to see the menu to decrypt the machine (suggested by AI)

I will thank a lot any comment (the other suggestion by AI is editing the .vmx file to remove the encryption.enabled = "TRUE" but I'm not so brave!

[Technogeezer]

Don't make any manual changes to the virtual machine's .vmx file yet. There needs to be more troubleshooting to try and determine what exactly is going on. That'll give us a better idea on next steps.

What I would do is to make a copy of this VM to an external disk to preserve its current state. 

Can you be more specific about what happens when "Fusion crashes"?  Is it really Fusion that's crashing or the virtual machine?

Can you collect and post a quick support bundle? (from the Fusion menu bar, click Help > Collect Support Information > Quick).

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Jose Albarran]

Really thank you for answering so quick!

When I say that "Fusion crashes", I mean that it ends totally (full application) with no further message, after I click "Do not upgrade".

I have found a way to start my VM (it's weird and crazy).

• I start another VM already upgraded
• Then, I start the VM with problems. In this moment, the pop-up windows appears on top of window. I click "Do not upgrade" and the VM start.
• If I do not start the other VM, the message appears on top of Fusion control window (instead of VM) and crashed when I answer
• If I do not shutdown the windows (and leave Fusion suspending the VM), I can return to VM without problem.

Moderator edit: Link to external source removed as it is unable to be downloaded.

[Technogeezer]

The better way to share the support bundle is to attach it in a reply to this thread.

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Technogeezer]

I'm getting errors when trying to use the link you;ve posted. Please attach the support bundle to a reply to your next post.

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

[Jose Albarran]

Hi, Paul

I have uploaded the file. I do not why, but in my previous interaction, no "ATTACH" link was visible.

Thank you very much again for your support!!!

Attachment(s)

VMware Fusion Quick Problem Report 2025-05-29 at 19.57.31...57   1.10 MB 1 version

[Jason McClellan]

@Jose Albarran -  There is a bug with the view attachment.  We are working with the vendor to fix.   thx @Jason McClellan, Platform Mgr.

------------------------------
Thank you
Jason
Broadcom Community Platform Admin, IT
------------------------------

[Jose Albarran]

Hi, Paul

I feel stupid or either blind, but I do not find a “Attach” button in on-line fórum.

Trying to attach to an e-mail answer. Let me know if you receive.

And again, really thank you!!!



Jose M. Albarrán
Tlfo: [phone]
e-Mail: [e-mail]<mailto:[e-mail]>
LinkedIn: https://es.linkedin.com/in/jmalbarran
Also available in Telegram, Signal, Skype (jmalbarran). I don't use WhatsApp.

Attachment(s)

VMware Fusion Quick Problem Report 2025-05-29 at 19.57.31...57   1.10 MB 1 version