Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
i never seem to have all the issues of people who "upgrade" its like rolling fresh paint over a surface
I have never clean-installed MacOS in my life, and I'm on my 4th MacBook. Always simply installing the updates, and when buying a new mac I always restore a backup from the previous one.
 
I feel like the comments are more full of vitriol this year, I’d like to think that it due to COVID driving people nuts. But sadly people like to condemn since it’s the easiest thing to do rather than create something of their own.
 
  • Like
Reactions: rodriguise
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.
I think people wanted to remove some of the pre-installed software such as iMove, Pages etc.
 
  • Like
Reactions: JosephAW and IG88
Some of us brick our Macs on purpose for educational purposes in business. I went and got one today, reproduced the error, learned how to DFU on an M1 and Restored successfully (Apple's article gave me the same error). Now I can teach my team how to resolve this and leveled up my Apple knowledge at the same time. ;)
 
Oh snap I went through this today, my MBA was really laggy on safari and felt a little off. So I wanted to do a clean install, wiped everything on the drive tried to install Big Sur and got that dumb error, tried resetpassword told me no user and still was getting that error

so I went to Find My app on my iPhone and found my MBA and clicked 'erase device', after a couple minutes my computer restarted and I had to boot into recovery, also got a welcome screen to select a language and enter my network (which I didn't have to do when I first went into recovery), also had to mount Macintosh HD.

But sure enough it worked and installed, also I feel that the computer is faster too, no more laggy scrolling in safari. I suspect a bad update maybe? When I first got the computer I had to install 11.0.1, 5 times as it didn't like it my guess
 
  • Like
Reactions: IowaLynn
Why the screenshot looks so pixelated like it's not a retina display mac?
 
  1. Buys a brand new M1-based Mac with Big Sur installed.
  2. Proceeds to re-install Big Sur.
  3. Problems occur.
While it's great to hear there's a recovery process available, it puzzles me why anyone would be doing this? Surely it could not have been that may people? Or was it that they are trying to restore from a Time Machine backup to get their system matching a former non-M1 machine?

Let's hope that Apple further expands their testing procedures to catch issues like this. Seems like one more of those "oops, we forgot to test that scenario" type of thing.
 
  • Like
Reactions: Val-kyrie
Some of us brick our Macs on purpose for educational purposes in business. I went and got one today, reproduced the error, learned how to DFU on an M1 and Restored successfully (Apple's article gave me the same error). Now I can teach my team how to resolve this and leveled up my Apple knowledge at the same time. ;)
If you can resolve it, it's not really "bricked" is it?
 
i like doing clean installs. espcially major OS versions. i never seem to have all the issues of people who "upgrade" its like rolling fresh paint over a surface with saw dust all over it :p but this is just me.
That is probably the most perfect way of doing things, but if you have a lot of third party software and customized your experience in a lot of small ways, that is a huge pain in the ass
 
True, though I don't think we see a "copy these terminal commands" instruction from Apple very often.

View attachment 1677227

People who are doing the steps that cause this bug to be an issue in the first place are more likely to be the sorts of folks who can copy some shell commands into terminal.

The first thing the average Mac buyer does is certainly not erasing the hard drive for no particular reason.
 
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.
Can anyone explain why you would wipe a brand new computer?
Why would anyone expect doing a clean install to be a problem?
Why would being new have anything to do with doing a clean install?
Why would a person not be able to expect to do a clean install on a brand new computer?
 
Last edited:
Oh boy, someone is yet to find out about the Application Support dir(s) :cool:
Yep, App Support Files can be scattered all over the Mac and they don’t get moved to the recycling bin with the App. You can manually locate them with Spotlight or use a program like Nektony AppCleaner to find the dozen files and Launch items.
 
This reminds me of the issue I had after upgrading to the Catalina Beta and then trying to delete the disk container and reinstall High Sierra. Internet Recovery failed even in the Apple Store and they installed a new Logic Board for me. It had something to do with the new T2 chips back then I believe.
 
  1. Buys a brand new M1-based Mac with Big Sur installed.
  2. Proceeds to re-install Big Sur.
  3. Problems occur.
While it's great to hear there's a recovery process available, it puzzles me why anyone would be doing this? Surely it could not have been that may people? Or was it that they are trying to restore from a Time Machine backup to get their system matching a former non-M1 machine?

Let's hope that Apple further expands their testing procedures to catch issues like this. Seems like one more of those "oops, we forgot to test that scenario" type of thing.
There are a lot of those oops scenarios nowadays with Apple.
 
I really thought thats what they do in the beta phase, test the software for possible malfunctions.
In the videogame world, they hire people to play a game and intentionally try to cause a bug or an error
 
  • Like
Reactions: IowaLynn
I really thought thats what they do in the beta phase, test the software for possible malfunctions.
In the videogame world, they hire people to play a game and intentionally try to cause a bug or an error
In the OS world, they do the same, though much of it is automated. It could have been a regression or a new bug.
 
This scenario is more like:

You had a brand new house built, and a room that was professionally painted in that new house. Although the paint was perfect, you came in "just because" and decided it needed another coat, and are mad because the existing coat wasn't prepped for you slopping another coat on it and it came out looking terrible.

Definitely the builder's fault.
It’s absolutely nothing like that.
 
  • Like
Reactions: IG88
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.