Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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've done it in the past once when I had problems with Migration Assistant while setting up a new mac. I don't recall what exactly went wrong as it was some years ago but it was sufficiently screwy that I decided to just do erase and install and migrate stuff by hand.
 
  • Like
Reactions: PickUrPoison
  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.
I guess this is not really a proces for regular people, but more for corporate IT and developers which try out if their software works. To reduce risk of incompabilties between different softwares and components you restore to clean state once in a while. And in that case: Bang - there your are.
 
I decided I am going to wait until next year to upgrade and stick it out with Mojave on my early 2015 13 in MBP. It has nothing to do with it being a first gen product or this issue in particular. Its just right now, with the pandemic, the commerce experience with Apple and many other retailers has been less than stellar. When things are back to normal and I can interact with the products before I make my purchase, then I will part with cash.
 
It’s absolutely nothing like that.
What it’s really like is taking a .0 release of an OS that shipped on a .0 release of hardware—on day one of a once in a decade (or two) architecture transition—and doing something relatively uncommon, assuming everything will be fine.

Should it work? Sure! Will it? Who knows?
 
Last edited:
  • Like
Reactions: deeddawg and lip008
People having problems: "we should be able to clean install our brand new Mac. We are power users"
Apple provides instruction using command lines
The same people: "boo hiss no normal people can do this. It's supposed to just work. Applr sucks. This is too difficult."

Am I getting the vibes right based on the comments here? :D
 
What should they look for?
All OS Updates? A USB Install media? I’ve owned Macs since the IIsi 5/80, owned Mac Clones from power and Umax, created a frankenmac by moving my powermac into a PC case for more internal drive bays, overclocked my clamshell ibooks with soldering irons, and I wouldn’t do what these people have done.
 
  • Like
Reactions: Zance
Why 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?
While that is certainly a valid point, I would certainly be hesitant with a completely new product like this. Especially knowing they released an OS update right around the time people were receiving them. Meaning it would certainly seem like a good idea to update first. Which in this case would have prevented the problem.
 
I’ve not read it but does it say “We, trillion dollar Apple, have launched faulty software. It’s your job to fix it” or does it say “We’re really sorry, there will be an update in the next 24 hours to fix this for you. So sorry for our failure, we’ve credited your iTunes account as a gesture of goodwill” 🤔
 
Another failure in quality from the company that convinced us to believe their high msrps were justified because, well, quality, and then suggesting buyers not buy new tech because of bugs is a paradox.

Um, there was an obscure bug with an OS fresh out of the release candidate cycle. And the OS is free. Does your Windows do that? *rolls eyes*
 
Don't you remember when you could just buy a few new memory sticks and future-proof your computer yourself?

And they say progress is always better.. yup
Progress is better, faster, lower latency on chip unified memory is one reason why this new cpu flies.
 
  • Like
Reactions: fahlman
Problems with the M1 Mac? Oh, tell me it isn't so! :rolleyes: Kidding aside, I'm so used to software issues with Apple over the past 9-months; nothing surprises me. Fortunately, unscrewing the macOS with little consequence is a breeze compared to iOS 14 🐞 🐛
 
Last edited:
No it’s not. Apple Apps you just drag them to the trash can. It’s not like windows with a registry or uninstall program
When I uninstall an app there are usually all manner of files relating to it in /Library/Application Support, /Library/Preferences and in various other places, including the corresponding folders in ~/Library. Sometimes things are still running as a service when I have removed the Application. I'm not keen on my computer having these orphaned files. Do Apple apps not do this then?
 
One snippet from the docs that I hate:

  • Your Mac will begin activating, which requires an internet connection. When your Mac is activated, click Exit to Recovery Utilities.
For those of us who provision Macs, this is going to be a pain in the backside.
 
Apple Support was clueless. I did it via Apple Configurator 2 on my own. Fire them!
 
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. Like I said it’s just how I am I like to tinker . Learn. Do things I’m not supposed to 😁 . I’m not sure why people get so angry at people for wanting to clean install there devices lol.
 
Article is not accurate.
Issue happens even if you update Big Sur to latest version.

-As soon as I received my M1 Air, I updated the Sur.
-i then migrated from timemachine backup however backup was very messy.
-so, I decided to do factory reset.
-there is a new algorithm to do clean install. You need to press power button while powering up the machine then you can go into restore options.
- however clean install option fails. It failed 4 times with me.
-eventually i had to use disk utility to delete a volume per high level support person’s institutions and retry reinstall OS option. Yet I still failed.
-after that action my machine was a brick.
-i had to return the machine to Apple store for full refund and then buy another one.
Update doesn’t fix the issue folks.

55ED3FAD-91F8-41E9-98B5-FA8BC41A69B8.jpeg
 
Can anyone explain why you would wipe a brand new computer?
This is mostly for IT Departments and developers for testing software. Based on your tests and the results you want to start new in a clear state. So you wipe your machine and try maybe with a modified version.

It is specific usecase, not for most people. But these certainly do exist.
 
  • Like
Reactions: Zance and haddy
“These issues” should never brick a machine.
they used the word bricked. but bricked is non working. doesn't power on useless. is this actually what happened? or was the upgrade just botched. if so that's not bricked.. I haven't actually looked anything up regarding this

ok just looked it up see it did do it :eek:

this why I never "upgrade" major OS installs. clean installs only. I wonder if this was the case with clean installs or just upgrades
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.