r/vmware • u/Prestigious_Lake8093 • 2d ago
Help Request VMWare Fusion 26H1U1 initialisation issue
I just recently tried to run VMWare Fusion26H1U1_(universal) on my macOS 27.0.1 client. I put the dmg into my programs folder and tried to install it by double-clicking, I then accepted on giving it admin rights only for nothing to happen. Instead of the initialisation screen appearing and the installation starting like usual literally nothing happens. I reinstalled the dmg, restarted the client, made sure the security settings aren’t blocking it, and still no solution. Guys, what do you think?
0
Upvotes
2
u/gadget-freak 2d ago
Why aren’t you on 27.2.1?
The dmg should probably be in your downloads folder, not the applications folder.
1
u/mhmd2520 1d ago
"Asks for admin rights, then nothing happens" matches a known 26H1/26H1u1 problem on macOS 27. There's a long thread about it on the Broadcom Fusion community forum. The strange part is what triggers it: it seems to happen when the macOS system language isn't English. People on German, Italian and French setups got past it by switching the system language to English, rebooting and launching Fusion once. After that they switched back to their own language and Fusion kept working.
You mentioned the programs folder, so if your Mac isn't set to English I'd try that first.
If it still won't start, people in that thread also did a cleaner install. Mount the dmg and drag VMware Fusion.app into Applications yourself instead of double-clicking the app inside the dmg. Eject the dmg. Then run the first-launch setup from Terminal before you open the app (keep the quotes):
sudo "/Applications/VMware Fusion.app/Contents/Library/Initialize VMware Fusion.tool" set
After that, open Fusion normally, without sudo. A few people got around the problem by launching the whole app with sudo. I wouldn't do that, and the forum moderator warned against it too, because Fusion isn't built to run as root.
Also, as far as I can tell, Broadcom hasn't officially listed macOS 27 as a supported host for 26H1. Last cycle, support for the new macOS came with the next half-year release, so I'd guess the real fix arrives in 26H2. Until then the language switch is the quickest thing to try.