Based on severity? More than in the past? Or fewer?There are a lot of those oops scenarios nowadays with Apple.
Hmmm. Well I’m open to being convinced, anyway...
Based on severity? More than in the past? Or fewer?There are a lot of those oops scenarios nowadays with Apple.
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.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 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.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?
- Buys a brand new M1-based Mac with Big Sur installed.
- Proceeds to re-install Big Sur.
- Problems occur.
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.
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.It’s absolutely nothing like that.
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.What should they look for?
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.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?
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.
Progress is better, faster, lower latency on chip unified memory is one reason why this new cpu flies.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
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?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
This would be a silly overreaction to this story at any time, but to be taking this line while Apple are busy demolishing Intel and sending Mac performance into the stratosphere is really something.What a mess this company has turned into
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.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
I always end up wiping a brand new computer, because I install lots of software like games etc to test the computer the first days, and then I think it's better to start fresh and reinstall only the software I need.Can anyone explain why you would wipe a brand new computer?
“These issues” should never brick a machine.It's understandable that these issues happen but also a good reason to wait a few weeks after the release of any major new line of hardware or software to let problems like this get sorted out.
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.Can anyone explain why you would wipe a brand new computer?
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“These issues” should never brick a machine.