Having difficulties creating bootable Ventura USB installer for M2 Mac Studio

[tk_mac]

Has anyone here created a bootable USB installer for Ventura that works with the latest M2 Macs, and if so, how did you do it?

The following is what I tried and its not working. I am trying to create a bootable installer for M2 Mac Studio with the latest Mac OS (13.4.1). First, I realize there are two builds for this OS, as indicated at https://mrmacintosh.com/macos-ventura-13-full-installer-database-download-directly-from-apple/

I downloaded the correct build 22F2083 from his page, the one indicated "for New WWDC Macs Only". I run the resulting pkg file and it installs the "Install macOS Ventura" app into /Applications. I then use the terminal command

sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --volume /Volumes/InstallVentura

to try to make my thumb drive named "InstallVentura" into a bootable installer. The issue is that I get the error

Making disk bootable...
Failed to extract AssetData/boot/Firmware/Manifests/InstallerBoot/* from update bundle
The bless of the installer disk failed.

I tried this both on the Mac Studio and on another Mac and I get the same result. How do I fix this? Is there something wrong with this build that it will not convert into a USB installer?

Thanks

 

[Mike Boreham]

Not a Terminal expert so can’t see what’s wrong. Dumb Q was it formatted HFS+?

I use Mist or MDS apps, either of which can both download the installer and create the bootable installer. I have used MDS for past few years but version 5 is no longer free. You can still download v 4.4 from the link and it works fine in Ventura. Mist is newer, and free so I have much less experience with it.

PS Is it possible that that special build for WWDC M2 Macs has something about it which prevents installers? These special build for latest macs situations dont last long as the “specialness” gets rolled into the next release…might have to wait for 13.4.2 if this is the case?

 

[kitKAC]

I downloaded the standard 13.4.1 installer the other week and created multiple boot sticks for work using the Terminal command, each one was fine.

It's probably an issue with that specific build.

 

[tk_mac]

....was it formatted HFS+?

I use Mist or MDS apps, either of which can both download the installer and create the bootable installer.....

PS Is it possible that that special build for WWDC M2 Macs has something about it which prevents installers?....

Yes it was formatted HFS+. I normally download systems with MDS which produces .dmg files, but the build 22F2083 was not on the list of system images offered, so I downloaded a .pkg through the Apple link supplied by mrmacintosh. Then I installed that .pkg to put the system installer into the /Applications folder and then ran the terminal command. I don't know if there is supposed to be something special about that build to not create installer thumbdrives or not.

I downloaded the standard 13.4.1 installer the other week and created multiple boot sticks for work using the Terminal command, each one was fine.

It's probably an issue with that specific build.

Did you do standard 13.4.1 from a .pkg or a .dmg download? Exactly what procedure did you follow. Can you try the 22F2083 build just to see if you have the same issue as I? Thanks

 

[kitKAC]

Did you do standard 13.4.1 from a .pkg or a .dmg download? Exactly what procedure did you follow. Can you try the 22F2083 build just to see if you have the same issue as I? Thanks

I use the links on MrMacintosh to download the .pkg files direct from Apple, install the file to Applications and then use the correct command line from here:

https://support.apple.com/en-gb/HT201372

Tried that build (22F2083), and I get the same error as you. Maybe it's deliberate as the build isn't universal.

 

[Mike Boreham]

Double clicking the pkg file will install the Install Assistant app which is what createinstallmedia needs, not .pkg or dmg.

https://osxdaily.com/where-download-macos-installers/

 

[AppleM0]

I'm having the same issue trying to create a bootable USB installer for 13.4.1. `Install macOS Ventura.app` was downloaded directly from the App Store link through Software Update, following the guide linked to below. However, the machine that I am using the create the bootable USB installer is running the latest Sonoma beta as of writing this.

Apple support article/guide: https://support.apple.com/en-us/HT201372

% sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled

Password:

Ready to start.

To continue we need to erase the volume at /Volumes/Untitled.

If you wish to continue type (Y) then press return: Y

Erasing disk: 0%... 10%... 20%... 30%... 100%

Copying essential files...

Copying the macOS RecoveryOS...

Making disk bootable...

Failed to extract AssetData/boot/Firmware/Manifests/InstallerBoot/* from update bundle

The bless of the installer disk failed.

 

[bogdanw]

Try with --downloadassets

sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --downloadassets --volume /Volumes/MyVolume

 

[AppleM0]

Try with --downloadassets

sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --downloadassets --volume /Volumes/MyVolume

Still no luck

 

[MnSteve]

FWIW, I am having the same issue, tried the suggestions above, and continue to not be blessed.

I saw a similar thread that suggested granting full disk access to the Terminal app, which I have done.

 

[bogdanw]

I saw a similar thread that suggested granting full disk access to the Terminal app, which I have done.

You could try to give createinstallmedia Full Disk Access.

 

[MnSteve]

You could try to give createinstallmedia Full Disk Access.

I cannot find anything named "createinstallmedia" to which to grant access. I granted access to the downloaded "Install macOS Ventura" app but it made no difference. Still no blessing.

 

[bogdanw]

Has anyone tried the 22F82 installer with downloadassets?
If 22F82 is for all Macs, the downloadassets option should download the additional necessary files for M2, hopefully making a valid USB installer.
22F82 InstallAssistant.pkg https://swcdn.apple.com/content/dow...8l8vhu6ria5aqk7edd262orj/InstallAssistant.pkg

sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --downloadassets --volume /Volumes/MyVolume

 

[MnSteve]

The terminal command references a file named Ventrua.app, but the web link points to InstallAssistant.pkg. Sorry, I'm confused.

 

[bogdanw]

The terminal command references a file named Ventrua.app, but the web link points to InstallAssistant.pkg. Sorry, I'm confused.

Delete Install macOS Ventura app from Applications, download InstallAssistant.pkg, make sure you have enough free space on the drive and install it. It will put Install macOS Ventura app in Applications.

Then use the Terminal command, with downloadassets, to create a bootable installer.

 

[MnSteve]

$ sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --downloadassets --volume /Volumes/VenturaUSB

Ready to start.
To continue we need to erase the volume at /Volumes/VenturaUSB.
If you wish to continue type (Y) then press return: Y
Erasing disk: 0%... 10%... 20%... 30%... 100%
Copying essential files...
Copying the macOS RecoveryOS...
Making disk bootable...
Failed to extract AssetData/boot/Firmware/Manifests/InstallerBoot/* from update bundle
The bless of the installer disk failed.

 

[bogdanw]

Another potential solution: create a bootable dmg and write the dmg on the USB.
To create a bootable Ventura dmg:

hdiutil create ~/Desktop/13.dmg -size 20g -layout SPUD -fs HFS+J
hdiutil attach ~/Desktop/13.dmg -noverify -nobrowse -mountpoint /Volumes/InstallVentura
sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --volume /Volumes/InstallVentura
hdiutil detach /Volumes/Install\ macOS\ Ventura
hdiutil resize -sectors min ~/Desktop/13.dmg

If successful, "Restore a disk image to a disk using Disk Utility on Mac" https://support.apple.com/guide/disk-utility/restore-a-disk-image-to-a-disk-dskutl14078/mac

 

[Yebubbleman]

Has anyone here created a bootable USB installer for Ventura that works with the latest M2 Macs, and if so, how did you do it?

The following is what I tried and its not working. I am trying to create a bootable installer for M2 Mac Studio with the latest Mac OS (13.4.1). First, I realize there are two builds for this OS, as indicated at https://mrmacintosh.com/macos-ventura-13-full-installer-database-download-directly-from-apple/

I downloaded the correct build 22F2083 from his page, the one indicated "for New WWDC Macs Only". I run the resulting pkg file and it installs the "Install macOS Ventura" app into /Applications. I then use the terminal command

sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --volume /Volumes/InstallVentura

to try to make my thumb drive named "InstallVentura" into a bootable installer. The issue is that I get the error

Making disk bootable...
Failed to extract AssetData/boot/Firmware/Manifests/InstallerBoot/* from update bundle
The bless of the installer disk failed.

I tried this both on the Mac Studio and on another Mac and I get the same result. How do I fix this? Is there something wrong with this build that it will not convert into a USB installer?

Thanks

What is the end goal here?

If you're trying to wipe that Mac Studio, my recommendation is to put it into DFU mode and just use another Mac with Apple Configurator 2. That way, it's pretty much guaranteed to download and restore the correct OS version for that particular Mac model.

If the goal is to make a bootable OS drive to have handy for just-in-case scenarios, it'll be easier to do when you're dealing with a common build that isn't machine-specific.

Has anyone tried the 22F82 installer with downloadassets?
If 22F82 is for all Macs, the downloadassets option should download the additional necessary files for M2, hopefully making a valid USB installer.
22F82 InstallAssistant.pkg https://swcdn.apple.com/content/dow...8l8vhu6ria5aqk7edd262orj/InstallAssistant.pkg

sudo /Applications/Install\ macOS\ Ventura.app/Contents/Resources/createinstallmedia --downloadassets --volume /Volumes/MyVolume

I don't believe that's correct. The --downloadassets flag in that command was used mainly for bridgeOS updates for the T2. Apple Silicon Macs do not have a separate device on-board running a separate Apple OS that needs to be factored in the way that the Intel Macs with the T2 did.

 

[bogdanw]

I don't believe that's correct. The --downloadassets flag in that command was used mainly for bridgeOS updates for the T2.

As Apple never explains, we have to presume based on the little information provided
"Usage: createinstallmedia --volume <path to volume to convert>
Arguments
--volume, A path to a volume that can be unmounted and erased to create the install media.
--nointeraction, Erase the disk pointed to by volume without prompting for confirmation.
--downloadassets, Download on-demand assets that may be required for installation.
Example: createinstallmedia --volume /Volumes/Untitled
This tool must be run as root."

 

[MnSteve]

I believe I have tried every suggestion in this thread, and all of them end with


Failed to extract AssetData/boot/Firmware/Manifests/InstallerBoot/* from update bundle

The bless of the installer disk failed.

 

[Yebubbleman]

As Apple never explains, we have to presume based on the little information provided
"Usage: createinstallmedia --volume <path to volume to convert>
Arguments
--volume, A path to a volume that can be unmounted and erased to create the install media.
--nointeraction, Erase the disk pointed to by volume without prompting for confirmation.
--downloadassets, Download on-demand assets that may be required for installation.
Example: createinstallmedia --volume /Volumes/Untitled
This tool must be run as root."

I'm telling you, as someone that uses that command regularly, that's what it does. It's bridgeOS firmware for the T2 and UEFI updates for any Intel Mac that is so old that it doesn't know how to boot that particular macOS release. It doesn't have any bearing on iBoot firmware whatsoever.

 

[bogdanw]

I'm telling you

Apple is telling us:
“Apple silicon
A bootable installer doesn't download macOS from the internet, but it does require an internet connection to get firmware and other information specific to the Mac model.”
https://support.apple.com/en-us/HT201372
Anyway, this is off-topic. There is another thread “A "full installer" no longer is.”https://forums.macrumors.com/threads/a-full-installer-no-longer-is.2319226/

@MnSteve I doubt they will work, as they probably use createinstallmedia as well, but you can try:
Disk Drill https://www.cleverfiles.com/boot-mac-from-usb.html
Install Disk Creator https://macdaddy.io/install-disk-creator/
TINU “open tool to create bootable macOS installers” https://github.com/ITzTravelInTime/TINU
MIST - macOS Installer Super Tool https://github.com/ninxsoft/Mist

 

[MnSteve]

@bogdanw Thanks. I've invested as much time in creating a bootable USB as is justified, for me. I have built a bootable USB for every release of MacOS but I've never actually had to use it in the heat of battle. Kind of the mentality of "If you have it you won't need it." I hope the converse is not true.

 

[Yebubbleman]

Apple is telling us:

Again, their documentation is different at the consumer level from IT level and it's often the case that Apple shares details in the IT community that it doesn't as often share in the public-facing documentation of their own command.

That all being said --downloadassets is only necessary if (a) you are contending with an Intel Mac with the T2 Security chip (and do not have a recent version of bridgeOS already installed for that T2 Security Chip) or (b) You are on an Intel Mac that is WAY behind on its UEFI updates from Apple. It does not fetch anything for an Apple Silicon Mac that isn't already a part of the OS (as firmware on an Apple Silicon Mac resides in a part of the drive that is adjacent to the OS).

 

[Nixiiao]

tried this both on the Mac Studio and on another Mac and I get the same result. How do I fix this? Is there something wrong with this build that it will not convert into a USB installer?

The only way I was able to create a new bootable installer for 13.4.1 is using an Intel Mac. At the meantime, I tried multiple methods mentioned above and from other websites, non of them worked for Apple silicon based Macs (tried on M1 and M2 models).