MDS Imagr "Bad CPU type in executable"

Hi everyone,

Probably an issue others are running into, apologies if it was answered in another thread…

I understand that startosinstall does not work with M1 processors, per the article below… however, the article also explains that the workaround is to “Use Apple configurator or MDM to wipe Macs, then run an MDS workflow to install non-OS install packages.”

I configured my workflow to not wipe or install MacOS… but I still receive the CPU error when trying to run the workflow:

How can i run the workflow to just install my packages/profiles/scripts?

Target mac is Macbook Air 10, M1, 13", MacOS 11.0.1. Deploying MDS from a web server.

Thanks for the help

that is correct. MDS doesn’t currently work on M1 Macs. I am waiting to see if Apple support restoring from the recovery.


Got it, thanks for confirming.

Does MDS support running from within the OS itself or does it have to run within Recovery?

For example, if an M1 Mac set itself up using Automated Device Enrollment via ASM/ABM and an MDM server, then login to the local admin account and call the MDS workflow via terminal.

The thought would be it would allow the non-OS packages, scripts, and profiles of the workflow to run and take advantage of the Rosetta emulation platform.

There are many issues around the M1 and Big Sur. They are outlined here:


Any updates on this issue?

Yes, i am working on a SiMac version now and it looks like you will be able to install packages and scripts from recovery and it will run after next boot on a SiMac.



This is fantastic news. Will we still be able to preset workflows on this new version?

that is the plan. Follow me on twitter if you want to see progress as it happens :slight_smile:

Thank you @tperfitt! What’s the process to make this public? I apologize if this is a basic question, just learning how to deploy using MDS.

All builds are posted here:


1 Like