[How To Fix MacOS Catalina 10.15 Stuck On Apple Logo On VMware Fusion
Clotilde Wilks
yeah same thing here. Installed mojave, installed the beta, downloaded the update, installed, rebooted and now it's just hanging at the black screen/apple logo. Probably due to vmware fusion not knowing what else to do...
These seem to be two distict issues (or at least the fix in the other thread didn't work for me). I mounted the VMDK and removed the extensions from /Library/Extensions, but still am stuck on an Apple logo when I try to boot the VM in Fusion 11.1
How to Fix macOS Catalina 10.15 Stuck on Apple Logo on VMware Fusion
Download Zip https://t.co/wz7Kb4WD3z
Here we go again with a new version of macOS and so far I haven't been able to get it booted in VMware Workstation, just curious if anyone else has either. Same old instructions to create a working bootable ISO function (same as Mojave but change the name of the installer app obviously). It won't boot past the Apple logo, can't boot into safe mode, or recovery either. Made several attempts so far to upgrade a clean Mojave VM using the Catalina installer app, still no joy on the reboot, it just hangs on the Apple logo with zero activity (no hard drive, network, nothing at all).
First, you need working virtual machine with previous version of macOS. I used 10.13.6. Install macOSDeveloperBetaAccessUtility.dmg. Then download Catalina installer from AppStore, then run it. After preparing computer will be rebooted. And can't booted, you will see only apple logo, no disk activity, no processor activity. It's kernel panic. Just shutdown virtual machine, change type to Windows 10 x64 and start it again. Installation will continue. After next reboot virtual machine can not boot. Ok, shutdown it, change it type to macOS 10.14 back and start machine again. Installation will continue. That's all.
So I gave several attempts to this process as explained above by serezha and had no luck, even when I alter the machine type to Windows 10 x64 there's no activity once that kernel panic happens, no way apparently to get past it. I suppose we'll figure it out at some point, ain't in that much of a major hurry to get it working.
VMware will likely need to fix something or it's an issue with the beta. I wouldn't expect proper support until Catalina is released which is usually when VMware release a new version of Fusion/Workstation. September timeframe.
Link to procedure with ISO installer here (can clean install or upgrade over the top of your existing VM). No need to use an unknown third party vmdk image from the internet - use the vanilla Apple Installer app to create the Installer ISO.
1. If you have another OSX virtual machine eg High Sierra or Mojave, temporarily attach the vmdk undergoing the upgrade process to it as a secondary drive (so now have 2 disks attached to this VM - High Sierra or Mojave.vmdk, and the stalled Catalina.vmdk disk. Don't detach the original High Sierra/Mojave drive)
3. Next, run the "ShowAllFiles.app" to show the hidden "Locked Files" folder. Note it is located inside the /macOS Install Data folder (on the "--Data" volume if upgrading from an earlier Catalina build eg DP1 to DP2)
4. Next, we need to take ownership of the "Locked Files" folder. Right click the "Locked Files" folder, click "Get Info", click the arrow next to Sharing & Permissions, click the lock icon and provide your admin password, click the plus button to add yourself to the list of owners and then select "Read & Write" to have custom read/write access privilege
If the script fails to find the target volume with the "macOS Install Data" folder, terminate it by pressing the and keys on your keyboard simultaneously. Manually copy the provided prelinkedkernel to /macOS Install Data/Locked Files/Boot Files folder with Finder as described in the following post...
VMware 15 presently cannot boot the native prelinkedkernel found in macOS Catalina's BaseSystem/installation media without panicking. Temporarily changing the guest OS type from macOS to Windows 10 X64 can bypass this panic and enable the second installation phase to complete. Paradoxically, once the prelinkedkernel is rebuilt on a completed installation (at the end of the install process), the VM is able to boot with guest setting back to macOS! My script replaces the Target Partition/macOS Install Data/Locked Files/Boot Files/prelinkedkernel with the plk from a completed install.
Just updated another virtual machine to Catalina without any problems. I am use unlocked Vmware workstation 15.1 on windows 7 x64 host. I started update with 10.13.6, virtual hardware version 15, guest OS type is macOS 10.13. First I removed vmware tools. It is only precausion, but vmware tools may contain incompatible kexts. I installed beta profile, then downloaded Catalina installer from AppStore. The I started installation. After first reboot was kernel panic (apple logo without any disk and processor activity). I shutdowned virtual machine, change it type to Windows 10 x64 and started it again. Installation was continued automatically. After next reboot virtual machine can not boot, I saw boot manager from EFI. I shutdowned it, changed type to macOS 10.14 and started it again. Installation was continued and finished without any problems.
If you have any problems with first reboot: use compatible host hardware (intel's ivy bridge and higher), use vmware workstation 15, use virtual hardware version 15, try to upgrade from high sierra (I do not tried to upgrade from Mojave, may not works), try to uninstall vmware tools before upgrade.
I finally had the time to try macOS Catalina Beta these last few days. (Could not do it before due to other more important tasks & also going on sea vacation for 1 week. One task was get the iOS 13 Simulator working, via Xcode Beta)
Using VMware Workstation 15.0.3 - cannot update to 15.1.0 at this point, as it is hard to do on this PC due to bugs in the VMware installer/updater so please do not suggest that. (I am using latest 15.1.0 on my laptop however.)
Restarting or power off/on does not help any. Then I remembered I installed VMware Tools, and that I should not install VMware Tools until fully updated, so I went back to my snapshot I took, and uninstalled VMware Tools (then restarted).
Any ideas how to fix/work around this, please? (Again, please do not suggest update to VMware Workstation 15.1.0, as I cannot do it for now. And I think it is not necessary, and all my other VMs work fine.)
Turn off VM, switch to Windows 10 64-bit. Looked OK, then around 50% in the process, Minutes XX remaining text (was around 47-45 minutes at some point) went away and was replaced with "Estimating time remaining.." (notice lack of any concrete number) and has been sitting there for 10 mins now..
Did you uninstall VMware Tools from the old VM before trying the upgrade, or kept it, please?
What CPU do you use?
I tried TWO ways:
One of my Catalina Beta VMs has Hardware Level 10.x (this is coming from an older VM, which works fine). I dare not change this hardware level on the older VM, as it has failed many times when I do that, and also it works well set that way.
However, when I added the Rescue Disk to the VM as suggested this caused 3 disk drives to show somehow - Disk 1 with regular name, plus Disk 1 with "- Data" added after the name, and the 3rd, rescue disk.
EDIT: Is there any way to modify the files that need a change without booting into a 2nd VM?
Such as boot into some Boot Loader as Clover, or maybe boot into a Rescue Disk (this works in Windows, unsure how it works in macOS, I guess it is very different).
@Naki, for some reason, the automated script is not seeing the hidden and locked "macOS Install Data/Locked Files/Boot Files" folder (probably a problem with Catalina's new "firmlinks", specific to updating Catalina physical disk partitions containing "--Data" volume).
The extra "Data" volume you are seeing when booted into High Sierra or Mojave with Catalina vmdk attached is normal since Catalina splits its System Volume (read only) from its User's Data volume. When booted into Catalina, this Data volume is hidden from the user (but can be seen from terminal with diskutil list command).
I have downloaded the full "Install macOS Catalina Beta.app" from Apple's software catalog with @crazybirdy's downloader script (keep a copy safe eg on 16GB USB drive). The app is directly run while booted into DP2_19A487l and I have chosen to install over the top of the existing macOS_apfs volume (note diskutil list output shows the existence of macOS_apfs--Data volume)...
On the first reboot into the second phase install, we are actually booting into the install files which have been placed by the installer in the macOS_apfs--Data volume @/macOS Install Data/Locked Files/Boot Files. This is more clearly seen if you have Clover ---> can see the following verbose screens...
Next, I have attached the Catalina vmdk to my Mojave virtual machine as an extra HD. I have booted into Mojave to "rescue" the Catalina install. I have run the "ShowAllFiles.app" to show the hidden "Locked Files" folder. Note it is located inside the "macOS Install Data" folder on the macOS_apfs--Data volume.
In order to replace the prelinkedkernel, we need to take ownership of the "Locked Files" folder. Right click the "Locked Files" folder, click "Get Info", click the arrow next to Sharing & Permissions, click the lock icon and provide your admin password, click the plus button to add yourself to the list of owners and then select "Read & Write" to have custom read/write access privilege...