Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Same here, this bug exists on 11.0.1. I made sure to update right after taking the computer out of the box. However, an hour later I ran into a situation where it just made more sense to wipe the thing and start fresh and I figured since I had updated I shouldn't run into this issue... wrong. Luckily I bought two M1 MBAs at the same time, so I quickly restored using Apple Configurator 2 from the second one via the included USB-C-to-USB-C charge cable in less than 15mins. Didn't have any issue getting into DFU mode, the whole restore worked perfectly on the first try.
how did you get into DFU mode? I can't get it to work.....
 
Interesting update. I got a call from Apple today with an engineer that wanted to follow-up with my case. He wanted to know about if I got my solution resolved and I referenced the article to use terminal commands in recovery to restore since when I called that article didn't exist. I did explain the article did work but that I had 11.0.1 when I had the issue which he confirmed with me and my build number.

Interesting they followed up. He did explain they have received a large number of calls with my same issue so they must be trying to follow up with folks.
 
Clearly Apple is experiencing a Big Sur’ge of issues with their new Macs
lol

The name that fits.. Finally.

Why would anyone ever need to restore or do a clean installation in a less than one week old machine? Apple even haven’t released any major OS update yet nor the prior version of OS works.

More likely to happen on Windows, muck 30-day trial that gets bundled with OEM systems. But its not like Apple get off the hook here either.... We all get screwed over by "never touching the Macintosh HD disk" *ever*, yet clearly some apps that install in root folder /var folder (hidden) and /usr, no one knows that files exsist because no "how to uninstall" apps/tools or instructions never tell you that

And for good reason...
 
Last edited:
Hopefully Apple updates the shipping OS to 11.0.1 ASAP. But at least there’s a fix for those who thought their machines were “bricked”.
True! However, I just ran into the same issue although I had already updated to 11.0.1 before resetting the machine...

Edit: I just noticed that I am not alone with this. Sorry, did not read the thread thoroughly!
 
Oof I’m okay with those instructions since I like terminal but I can only imagine someone who doesn’t have technical acumen freaking out doing those steps.
But, most users wouldn't do this regardless. I mean they ship with Big Sur, so the only people screwing around with needing to reinstall are techies who tinkered. Not the home user. There's no reason to reinstall the OS on a new Mac unless they're completely incompetent of following the setup when the first booted it. This is certainly more for people who have tried a developer release update (There IS a developer update to 11.0.1... it's 11.1) and for whatever reason had to "roll back" to 11.0.1 which is what they all shipped with.
 
But, most users wouldn't do this regardless. I mean they all (M1 Macs) ship with Big Sur, so the only people screwing around with needing to reinstall using recovery are techies who tinkered. Not the home user. There's no reason to reinstall the OS on a new Mac unless they're completely incompetent of following the setup when the first booted it. This is certainly directed more for people who have tried a developer release update probably (There IS a developer update to 11.0.1... it's 11.1) and for whatever reason had to "roll back" to 11.0.1 which is what they all shipped with.
 
  • Like
Reactions: macbookfan
It is an easy fix....reboot your computer, when it asks for the password don’t enter, left upper corner erase your disk....then choose to install macOS again, you will be asked for your network connection, and just works after that
 
Unsure what to call it but machine didn’t load up to OS. I can use another term if needed.

I didn’t bash Apple but outline a major issue I experienced. I have 3 other Macbooks, 4 iPads, 5 iPhones, 3 Apple TVs, 2 Homepods, 4 Airpods and other Apple stuff at home. So I do not wait for bad news. Why would anyone do that?

However Apple is not teflon. Like any other manufacturer they may have issues which should be identified and communicated. They should have tested the OS under various algorithms to see if clean restore actually works.
That is what we have comments sections in Macrumors. Cheers.
Pre-release OSes go through an incredible amount of testing. Bugs still slip through. It’s been that way for 50+ years.

Figure out a way to fix this and you’ll be a billionaire.
 
Last edited:
The forum is a hit and miss. Quite a lot of ‘Appleogists’ here, who seem to be threatened by any reasonable criticism of Apple.
Good to see you finally got one upvote!

There are probably 100 active trolls per Apple fan in these news discussion forums. Everyone knows that, even the trolls lol.
 
Last edited:
  • Like
Reactions: m2m2k
That’s not particularly relevant, is it? There are reasons, and it should work but it doesn’t.
Actually it is relevant as Apple released a fix for it in one of the first updates and these people could have had the fix if they just turned on the computer and ran the update. The new Macs coming from the factory will have that fix, but you cant load laptops with a patch in transit. I don't believe there is any "relevant reason" to wipe a brand new apple computer. I have seen many reasons proposed and none pass scrutiny.
 
Actually it is relevant as Apple released a fix for it in one of the first updates and these people could have had the fix if they just turned on the computer and ran the update. The new Macs coming from the factory will have that fix, but you cant load laptops with a patch in transit. I don't believe there is any "relevant reason" to wipe a brand new apple computer. I have seen many reasons proposed and none pass scrutiny.
Messed up time machine restore and there you are.
 
  • Like
Reactions: PickUrPoison
Actually it is relevant as Apple released a fix for it in one of the first updates and these people could have had the fix if they just turned on the computer and ran the update. The new Macs coming from the factory will have that fix, but you cant load laptops with a patch in transit. I don't believe there is any "relevant reason" to wipe a brand new apple computer. I have seen many reasons proposed and none pass scrutiny.
"None pass scrutiny" based on what measurable criteria? Let me give you one and PLEASE tell me why this reason does not pass scrutiny:

Enterprise customers (who buy Macs in the 100s/1000s) have a program called Automated Device Enrollment that ensure computers they deploy are under management. ADE requires the computer to have a fresh O/S to work. So, when companies started receiving their first M1 Macs, they needed to test their deployment processes and make sure they work. That means multiple test runs, especially if anything failed. So, the IT team would need to restore the O/S between each test run. How do you do that if Apple does not provide a solution?

(And, let me stop you if you answer is Enterprises should not be buying M1 Macs until they are ready. Apple does not necessarily give customers that options. When Apple replaces a model line, they happily replace any outstanding orders with the upgraded model. As a result, many enterprise customers found themselves with M1 MacBooks Air regardless if they were ready or not. While that is great for Apple, it is not always the best situation for the customers.)
 
Well wanted to format the air I am not keeping to return to apple and needless to say it is now stuffed. I tried the terminal method and usb bootable installer and it didn't work. I couldn't be bothered trying configurator as it is going back to apple anyway, they can deal with it. I hope I don't have to clean install the air I am keeping anytime soon. And yes it was updated to 11.0.1, didn't make a difference. Really hope apple fix this soon, shouldn't be this difficult.
 
"None pass scrutiny" based on what measurable criteria? Let me give you one and PLEASE tell me why this reason does not pass scrutiny:

Enterprise customers (who buy Macs in the 100s/1000s) have a program called Automated Device Enrollment that ensure computers they deploy are under management. ADE requires the computer to have a fresh O/S to work. So, when companies started receiving their first M1 Macs, they needed to test their deployment processes and make sure they work. That means multiple test runs, especially if anything failed. So, the IT team would need to restore the O/S between each test run. How do you do that if Apple does not provide a solution?

(And, let me stop you if you answer is Enterprises should not be buying M1 Macs until they are ready. Apple does not necessarily give customers that options. When Apple replaces a model line, they happily replace any outstanding orders with the upgraded model. As a result, many enterprise customers found themselves with M1 MacBooks Air regardless if they were ready or not. While that is great for Apple, it is not always the best situation for the customers.)
This is the first reply that actually might have a valid reason for needing to format a new machine. I wouldn’t know as I have very limited experience with MDM myself.

that being said the IT staff at a company can get that terminal open if need be to get the machine restored.

is it ideal? No. Should it work without the extra steps? Yes! But the average consumer has no valid reason to wipe a new machine. The situation you are describing is not the average consumer.
 
Actually it is relevant as Apple released a fix for it in one of the first updates and these people could have had the fix if they just turned on the computer and ran the update. The new Macs coming from the factory will have that fix, but you cant load laptops with a patch in transit. I don't believe there is any "relevant reason" to wipe a brand new apple computer. I have seen many reasons proposed and none pass scrutiny.
The fix that was released apparently doesn’t work. Now what?
 
Follow the support article using terminal. Or call Apple for help if you are that rare people who is smart enough to wipe a computer but dumb enough to not use google.
Yeah, doesn’t work. Apple says send it back. 4 week wait on replacement 🙁

Now what? Still think the software doesn’t need to work?
 
In the OS world, they do the same, though much of it is automated. It could have been a regression or a new bug.

somethings make me feel stupid...obviously having a computer do random things automated will be much easier to find a bug than a real human sitting there trying to test everything. Why didn't I think of that....?
 
Tried a dozen times to install 11.0.1 on an external drive. Get error: “An error occurred while extending ownership to this volume.”

Why do I install on external? So I can use a boot drive with multiple machines. Carries my apps and preferences and data stored on the system volume with me to all machines I work on. I have external data volumes as well, but some apps INSIST on storing their data on the system drive, like iTunes backups of my phones.

I am willing to replace all my machines with M1 Macs because I know sharing the boot drive will require that, but I can’t even get it to work on the first M1 Mini I bought. Tried installing from a boot flash drive, from Restore, no go.
 
It is an easy fix....reboot your computer, when it asks for the password don’t enter, left upper corner erase your disk....then choose to install macOS again, you will be asked for your network connection, and just works after that
YOU ARE THE MAN! Worked like a charm! Why didn´t Apple come up with this? Amazing! (I just registered just to thank you!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.