Failed to create a bootable disk image file for this version of macOS.

Discussion in 'Installation and Configuration' started by DaveP10, Dec 6, 2021.

  1. DaveP10

    DaveP10 Bit Poster

    Messages:
    1
    Hello all,

    Any ideas on why I keep getting this message? I am running out of ideas and cannot get any answers from support.
    I had to rebuilt my mac system from scratch and reinstalled + re-added the license. I am on macOS Monterey 12.01 and trying to create a new Big Sur instance on 11.6.1. The .app installer is sitting in /Applications and I've downloaded directly from Apple, so I can confirm that it is clean. Yet, I am still getting this error within the Installation Assistant right after I select the .app and click Continue.

    Any ideas would be very helpful on how to resolve.

    Thank you!
     
  2. DougD

    DougD Bit Poster

    Messages:
    1
    Stuck in same boat. Did you ever figure this out?
     
  3. CloudDude

    CloudDude Bit Poster

    Messages:
    3
    I had the same issue. In my case, the error occurred when trying to directly create a macOS VM whose OS version is not natively supported on my physical underlying Mac hardware. For example trying to directly create/install macOS Monterey on a Mac Pro 2010 produced this error.'

    I figured out I could instead first (1) Create a macOS VM using the last version natively supported by the underlying hardware then (2) upgrade the OS within the VM thereafter. Using the same example, first created a macOS Mojave VM, then upgraded the OS within the VM to Monterey 12.3.1.
     
  4. CloudDude

    CloudDude Bit Poster

    Messages:
    3
    Additional note about this in-place OS upgrade process. From my experience, upgrading the VM from macOS Mojave to Monterey went fine, but at one point during the upgrade it displayed an icon of a circle with a slash going through it with a link about macOS startup. But after some time it rebooted and continued the upgrade process. My suspicion was that page was related to attempted firmware upgrades which weren't needed.
     
  5. DebasmitaM@Parallels

    DebasmitaM@Parallels Staff Member

    Messages:
    1,141
    Hello, please let us know if the issue is resolved. If not, kindly help us with the screenshot of the error.
     
  6. veeceeoh

    veeceeoh Bit Poster

    Messages:
    2
    @DebasmitaM@Parallels - I am having the same issue of the error message "Failed to create bootable image file for this version of macOS" when I select the macOS Monterey 12.3 installer .app in the Applications folder, as downloaded directly from Apple's server. I also see the same error when I select the macOS 13 Ventura beta installer .app as well. Both of these installer apps are for the respective Intel version of macOS.

    The host system is a 27" 2017 iMac with 4.2GHz Quad-Core Intel Core i7, running macOS Monterey 12.4 as the host OS. I am 100% sure that the host Mac is able to natively install and run macOS Monterey 12.3, so the error message must be due to another reason.

    Here are screenshots:

    [​IMG]
    [​IMG]
    [​IMG]
     
  7. DebasmitaM@Parallels

    DebasmitaM@Parallels Staff Member

    Messages:
    1,141
    Hello, which Parallels Desktop version you are using?
     
  8. veeceeoh

    veeceeoh Bit Poster

    Messages:
    2
    I'm using Parallels Desktop for Mac version 17.1.4.
     
  9. BenS28

    BenS28 Bit Poster

    Messages:
    1
    Any updates on this? Other users (i.e. me) are having this issue as well, so please don't DM individuals or if you do, please update this thread as well.
     
  10. SuF

    SuF Bit Poster

    Messages:
    1
    I can confirm that I am having the same issue on the same exact hardware 27" 2017 iMac with 4.2GHz Quad-Core Intel Core i7, running macOS Monterey 12.4 as the host OS and Parallels Desktop for Mac version 17.1.4.
     
  11. Grllle

    Grllle Bit Poster

    Messages:
    1
    Same problem for me trying to install a Mojave 10.14.6 VM
     
  12. YoonK

    YoonK

    Messages:
    1
    The same issue, anyone knows where to get an Image File for older versions? I am planning to upgrade a Big Sur VM to Monterey inside the VM but cant seem to find a working download link for Big Sur Image
     
  13. Aries@PF

    Aries@PF Kilo Poster

    Messages:
    164
    I'm having the same issue. 2019 MBP on the latest v17 Parallels. I've gone so far as to completely remove all of the hidden components of parallels as well as redownload the latest Full installers for the OSes that I was having trouble with. I'm kind of glad I'm seeing this post because that means that my issues likely aren't my system, but have something to do with Parallels itself as this system is pretty OEM when it comes to software. I've even managed to use the Host OS to create installer IMG files using the terminal just fine (using the same installers parallels refuses to use).
     
  14. Aries@PF

    Aries@PF Kilo Poster

    Messages:
    164
    Note: I can drag/drop these Same installers onto a cloned VM, install the OS, and then basically rename that to the new OS. So it's NOT the installers.
     
  15. Aries@PF

    Aries@PF Kilo Poster

    Messages:
    164
    I keep older versions for personal use and that's Not the issue as they give the same result. I thought at first it had something to do with the 11.6.7 I had used to baseline the latest VMs I'd created (via internal upgrade), but nope.
     
  16. Enrico5

    Enrico5 Bit Poster

    Messages:
    2
    Same issue here. Mac Pro 7.1 Intel with Monterey 12.4.

    I make a video proof

     
  17. Asish@Parallels

    Asish@Parallels Staff Member

    Messages:
    140
    Hello @Enrico5 , Kindly let us know the processor of your Host Mac (Intel/ M1).
     
  18. Enrico5

    Enrico5 Bit Poster

    Messages:
    2
    Intel Xeon W 28 cores
     
  19. Aries@PF

    Aries@PF Kilo Poster

    Messages:
    164
    They're clearly using Intel as they have incompatible VMs for M1 in their list.
     
  20. DebasmitaM@Parallels

    DebasmitaM@Parallels Staff Member

    Messages:
    1,141
    Hello, we would request you to create a support ticket so that we can check the issue internally.
     

Share This Page