![]() Since then I've been upgrading them from within the client. I did my initial client installations of macOS 11 using the Beta 6 (build 20A5364e) "Install macOS Big Sur Beta" app. I assume macOS 11 has changed how the recovery partition works, and Fusion hasn't yet caught up with these changes. So I know this isn't a bug in macOS 11 itself, or not only a bug in macOS 11. Cmd-R does boot into the recovery partition when used from a macOS 11 beta installation on actual hardware. This bug happens with both kinds of client. I've installed macOS 11 beta clients both as an upgrade from macOS 10.15.7 and directly (by dragging the "Install macOS Big Sur Beta" app onto the "Select the Installation Method" window). I'm sure I can't be the only one who's seen this, but so far I haven't seen any bug reports. Create Recovery Partition Installer for Mac lies within System Tools, more precisely File Managers. This free app can be installed on Mac OS X 10.7.0 or later. ![]() The most popular version among the application users is 1.1. ![]() When I let the keys go, I get a "normal" boot. This Mac download was scanned by our antivirus and was rated as virus free. But then I see a series of aborted attempts to launch the recovery app that lasts as long as I hold the Cmd-R keys. I follow the standard procedure (press Cmd-R as the virtual machine is restarting). But in none of them have I ever been able to boot into the recovery partition. I've installed macOS 11 beta clients on a VMware Fusion 12.0.0 host (running on the latest macOS 10.15.7) in a couple of different ways.
0 Comments
Leave a Reply. |