You can't use an M1 Mac to create bootable pre-BigSur macOS installers

[segers909]

I repair Macs, and thus I often need a bootable installer for various macOS versions. I just upgraded to an M1 Macbook Air, and it appears I'm no longer able to use the "createinstallmedia" command line app: it errors out on "Killed: 9":

sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USB

Password:

Killed: 9

The same is also true for El Capitan, Sierra, High Sierra, and Mojave. It does work for Big Sur.

I did some googling and "Killed: 9" refers to the program nog having a valid code signature. This can probably be circumvented by disabling the Mac's SIP, but doing so would stop iOS apps from working on the Mac in question.

I figured perhaps I have to re-download the installers, that Apple has updated the app signature. However, trying to do so results in the message "update cannot be found". I also tried it in Terminal:

softwareupdate --fetch-full-installer --full-installer-version 10.13.6

Scanning for 10.13.6 installer

Install failed with error: Update not found

On my wife's 2015, downloading 10.13.6 works immediately, as does createinstallmedia. I copied the installer from her computer to mine, and the same "Killed: 9" error remains.

 

[Wildkraut]

Try to download it over the AppStore, search there for Big Sur.

 

[Stephen.R]

I wouldn't be surprised if you need to use the same arch to create the bootable installer: i.e. use an Intel Mac to create an intel bootable installer, use an Arm Mac to create an arm bootable installer.

 

[Wildkraut]

I wouldn't be surprised if you need to use the same arch to create the bootable installer: i.e. use an Intel Mac to create an intel bootable installer, use an Arm Mac to create an arm bootable installer.

Yep and there isn't a 10.13.6 version for the M1, all the can try is Big Sur upwards.

 

[Superhai]

Does it also SIGKILL if you put ‘arch -x86_64’ in front of the createInstallMedia command?

 

[Mike Boreham]

I repair Macs, and thus I often need a bootable installer for various macOS versions. I just upgraded to an M1 Macbook Air, and it appears I'm no longer able to use the "createinstallmedia" command line app: it errors out on "Killed: 9":


The same is also true for El Capitan, Sierra, High Sierra, and Mojave. It does work for Big Sur.

I did some googling and "Killed: 9" refers to the program nog having a valid code signature. This can probably be circumvented by disabling the Mac's SIP, but doing so would stop iOS apps from working on the Mac in question.

I figured perhaps I have to re-download the installers, that Apple has updated the app signature. However, trying to do so results in the message "update cannot be found". I also tried it in Terminal:


On my wife's 2015, downloading 10.13.6 works immediately, as does createinstallmedia. I copied the installer from her computer to mine, and the same "Killed: 9" error remains.

I have made many bootable USB installers on my M1 MacBook Air using createinstallmedia, using installers downloaded from the App Store and with the Python script.

I have also just recently tried the free MDS app by Two Canoes which gives access to all the Apple Software Update Catalogs and creates bootable USBs (using creatinstallmedia) without needing the Terminal.

 

[segers909]

Does it also SIGKILL if you put ‘arch -x86_64’ in front of the createInstallMedia command?

Yes.

sudo arch -x86_64 /Applications/Install\ macOS\ High\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB

Password:

Killed: 9

 

[segers909]

I have made many bootable USB installers on my M1 MacBook Air using createinstallmedia, using installers downloaded from the App Store and with the Python script.

I have also just recently tried the free MDS app by Two Canoes which gives access to all the Apple Software Update Catalogs and creates bootable USBs (using creatinstallmedia) without needing the Terminal.

Well.. Then why can't I get it to work! Even the MDS app doesn't work: when I use it to download macOS, it just gets stuck on "Busy, Please Wait". I'm guessing it's getting the exact same error as I do when I use Terminal.

 

[Mike Boreham]

I wouldn't be surprised if you need to use the same arch to create the bootable installer: i.e. use an Intel Mac to create an intel bootable installer, use an Arm Mac to create an arm bootable installer.

Bootable USB installers made on either Intel or Mac will boot the other OK. Unlike actual macOS installations which will only boot either M1 or Intel, depending which machine type installed it.

 

[Mike Boreham]

Well.. Then why can't I get it to work! Even the MDS app doesn't work: when I use it to download macOS, it just gets stuck on "Busy, Please Wait". I'm guessing it's getting the exact same error as I do when I use Terminal.

Wish I could help.

It is not necessary to disable SIP or change Startup Security Utility.

 

[Mike Boreham]

Well.. Then why can't I get it to work! Even the MDS app doesn't work: when I use it to download macOS, it just gets stuck on "Busy, Please Wait". I'm guessing it's getting the exact same error as I do when I use Terminal.

Rereading thread I see you were trying to create a Catalina USB installer in the OP, and that failed, but Big Sur worked.

I should have made clear that I have only made Big Sur installers on my M1 MacBook Air. I have never tried to download or make an installer for anything except Big Sur.

Apologies if I have misled you. I will have a go at Catalina and report back.

 

[Stephen.R]

Bootable USB installers made on either Intel or Mac will boot the other OK. Unlike actual macOS installations which will only boot either M1 or Intel, depending which machine type installed it.

That's good to know, thanks.

 

[Mike Boreham]

Even the MDS app doesn't work: when I use it to download macOS, it just gets stuck on "Busy, Please Wait". I'm guessing it's getting the exact same error as I do when I use Terminal.

MDS is actually downloading while it saying "Busy please wait". I am currently downloading have successfully downloaded Catalina build 19H2 on my My M1 MBA using MDS.

 

[Mike Boreham]

MDS is actually downloading while it saying "Busy please wait". I am currently downloading have successfully downloaded Catalina build 19H2 on my My M1 MBA using MDS.

However I can't make a bootable Catalina USB with either creatinstallmedia or MDS. MDS gives this:

As far as I can see there are no read or write protect issues.


And createinstallmedia gives this:

Last login: Sat Feb 6 14:33:00 on console
michaelb@MBA16 ~ % sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled
Password:
zsh: killed sudo --volume /Volumes/Untitled

I am not fluent with Terminal but have used creatinstallmedia many times.

It looks possible that M1 Macs will only create Big Sur USB installers, (though they will download others).

 

[Apple_Robert]

Thanks for mentioning the MDS app. I just used it to create 2 Big Sur installers. It downloads the OS file a lot quicker than the App Store, and I think it may be a few minutes faster with the creation process as well.

 

[Fishrrman]

Will utilities such as "Diskmaker X" and "Install Disk Creator" run on the m1 Macs?
(I don't have an m1 Mac).

 

[segers909]

Will utilities such as "Diskmaker X" and "Install Disk Creator" run on the m1 Macs?
(I don't have an m1 Mac).

Install Disk creator errors out on

An error occurred.

Try ejecting the destination disk and reinserting it, or rebooting. It probably couldn't be unmounted to erase it.

And Diskmaker X specifically mentions on its website that it won't be updated for Big Sur.

 

[chrfr]

Install Disk creator errors out on


And Diskmaker X specifically mentions on its website that it won't be updated for Big Sur.

Ultimately, you need to be building your installer disks on machines which are compatible with the operating system that's going onto the installer disk. This is an issue with Intel Macs as well, although the createinstallmedia command is a bit more widely compatible.

 

[bsunarjo]

Is this really just a problem with the code signature? And no easier workaround than disabling SIP for the whole system? For a moment I thought this essentially meant I had bricked my MacBook Pro by removing its harddrive, but then I managed to find an old Catalina time machine backup from which to boot. This seriously sucks, I can’t believe I can’t use my new M1 mac to fix older machines.

 

[AppleTO]

Yeah, I tend to repair a lot of older Macs for people as well, and I’m having the exact same issues as everyone else in this thread.

I don’t know of any other way to create bootable installers other than ‘createinstallmedia’ (it seems most ‘disk maker’ apps with GUIs are really just doing this).

You used to be able to create bootable installers in Disk Utility just by restoring disk images, but I’m assuming that doesn’t work anymore either.

Quite annoying really.

 

[Apple_Robert]

Yeah, I tend to repair a lot of older Macs for people as well, and I’m having the exact same issues as everyone else in this thread.

I don’t know of any other way to create bootable installers other than ‘createinstallmedia’ (it seems most ‘disk maker’ apps with GUIs are really just doing this).

You used to be able to create bootable installers in Disk Utility just by restoring disk images, but I’m assuming that doesn’t work anymore either.

Quite annoying really.

The app MDS can download the OS as well as make a USB installer. It is very good app.

MDS – Twocanoes Software

twocanoes.com

 

[AppleTO]

The app MDS can download the OS as well as make a USB installer. It is very good app.

MDS – Twocanoes Software

twocanoes.com

I just tried that actually. No issues downloading but it’s not able to create the USB. Same results as the posts above.

 

[Apple_Robert]

I just tried that actually. No issues downloading but it’s not able to create the USB. Same results as the posts above.

That is odd. I used it a few days ago to make 2 BS installers for my M1 MBA.

 

[DeanL]

I wouldn't be surprised if you need to use the same arch to create the bootable installer: i.e. use an Intel Mac to create an intel bootable installer, use an Arm Mac to create an arm bootable installer.

That's incorrect: Big Sur is universal (i.e. there isn't two separate installers).
It's probably not working simply because he is trying to create installers on an M1 Mac for an OS that is only available in x86_64.

 

[AppleTO]

That is odd. I used it a few days ago to make 2 BS installers for my M1 MBA.

Ah, I have no issues with Big Sur installers. My issues were with trying to make Catalina bootable USBs. (Still have some 2013 iMacs at work). My apologies, I should have been clearer.