You’ll get this screen: New VM dialog with macOS Catalina installer dropped on itĬlick Continue Select the default macOS guest OS for it, for now Now go back to Finder and drag your installer on top of the above dialog and drop it there. Then the steps to install your new macOS Catalina VM are as follows.įirst select File New from within VMware Fusion: Install a new VM dialog You can however drag & drop the installer bundle from your VM to your host OS, or copy it out using a network share via AFP (not samba). If you want to get that 6.4GB “Install macOS 10.15 Beta.app” installer out of the VM then you cannot use the VMware Fusion shared folders feature. But as it involves a few more steps, not all of them obvious, I figured to write it out for you. As it turns out, the main trick is to start from a new VM, not upgrade an existing one. I tried that, but my VM no longer booted. Then user bogdam reported he could get passed this by changing the virtual machine hardware to Windows 10. If you then try to reboot it in verbose mode, so that you can see what happens, you’ll get the following screen. Basically if you run the upgrade then your VM will hang on reboot.

This thread describes the problems you bump into if you try to upgrade a macOS Mojave VM to the new beta macOS Catalina. Credit for figuring out how-to do this goes to vmtn users Bogdam and intel008 as they are the ones who posted the resolution in the following thread at VMTN: macOS Catalina VMs do not run in VMware Fusion 11.1.0 Here’s a quick note on how-to setup a macOS catalina VM on VMware Fusion 11. Should you experience a noticeable drop in free space, simply run DaisyDisk and you can quickly and easily identify areas which can be cleaned up.ĮDIT: Reminder, be sure to create a boot disk volume of at least 120 GB, which you can resize via Disk Utility > Boot Disk > Partition during the initial setup for Mountain Lion.Update: This is no longer an issue with Fusion 11.5 This is one of the many areas where Mac OS reigns supreme over Windows, you can perform multiple upgrades without a ton of junk files, wasted space, and unwanted files. Anyway, since it is in a VMware Fusion environment, it also means I can take a number of snapshots along the way should anything go wrong. Sure, it was install on top of install on top of install, though none of the methods I tried online seemed to work for creating an.

So, I copied over the Mavericks installer, updated in place, then I finally ran the Big Sur Public Beta installer tool. When I tried to install the beta on top of 10.8.5, it said the minimum requirement was Mac OS 10.9. So, I created a new, clean, VM based off 10.8.5, then ran the MacOSPublicBetaAccessUtiility.pkg which can be found here. dmg installer was 10.8.5 (Mountain Lion). For a variety of reasons, I have hung on to all of the original full installers for Mac OS going all the way back to 10.7.5 (Lion).

Vmware fusion 8.5 catalina black screen