I wouldn’t want to work from home. So nice try. Lol. Love my job.Sounds like you're someone who can't work from home trying to insult people that do.
I wouldn’t want to work from home. So nice try. Lol. Love my job.Sounds like you're someone who can't work from home trying to insult people that do.
Yeah like Catalina had NO issues right? I was getting on average 3 kernel panics a day in Catalina. Apple confirmed it was the OS and not my computer. And was fixed after a later update.This is what happens to product quality when you let lazy morons "work from home"...
No the article has 10 people that posted. Said nothing about how many total people this affects.It's literally the source for the article. LOL.
Windows still has printing issues going on.Sorry Windows, you are not so bad after all!
Mac is just the same, just different.
Free worthless update, gladly will pay for something that works. No need yearly new marginal incremental versions that break my older ios devices sync.
When you work from home this is what happens. Bug after bug after bug.
Companies just moved to Windows 10 when Windows 7 was EOL. I know some companies still on Windows 10 1809. Which is 2018 build of Windows 10!Waiting until the .3 or .4 version of a new OS hac been SOP since computers came into general use back in the mid 90’s. Everyone knows that while the company does extensive testing, many many circumstances crop up that never came in the beta testing. This is simply how it works.
Additionally, if Apple or any Microsoft waited until 99.99 of all the problems were found in bet testing it would take 3 years before any new system could be brought to fruition.
Yes, assuming you have the original Flash Drive/SSD installed. It seems like the firmware update only goes through if the original Apple-disk is installed.
For me, using the OWC Aurora X2, the workaround (thanks to this post by akro) was to update with the original disk then go through the same process one more time with the OWC disk. My guess is that the firmware update then will be skipped as it's already finished. Ridiculous but works, and so far without further issues.
I just love these comments. Work from home is not to be blamed for EVERYTHING. I had major issues with Catalina. That was before work from home was a thing. Plus Apple has always had work from home, I applied for one and I’m not even in California.Which is related to work at home. ?
I run BigSur On My mac mini. Late 2012. Flawlesly for nearly a year now. I can’t understand they made it unsupported performance wise. Marketing wise i Can see the picture.I installed it on my unsupported Mac and it's been running great. Maybe they focused more on trying to prevent it running on unsupported Macs than on supported Macs?
NEVER EVER do updates on battery. And if possible, do it at 100% while still charged. That way (as someone mentioned) if USB ports go bad you have 100% battery backupPretty much this, Millions of macs have installed without an issue. This is just a few on twitter and we all know that everyone on twitter gives the entire story.
How do we know that the person updating their mac wasn't connected to power and it shut off midway through an update because the person failed to connect to power?
For mine, You cannot turn the machine on. Interestingly, the ports seem to power up because the blue light on my hub connected to the TB port went on and I could hear the connected Time Machine drive start spinning. But no other responses.Can someone clarify for me. I see the reports “don’t turn on” and people saying “brick”. So the update actually caused power to no longer work? Can they boot into internet recovery? Boot from USB? Or is it truly “bricked”?
I wouldn’t want to work from home. So nice try. Lol. Love my job.
Too many people in this thread need to get their terminology straight. Your machine is not "bricked" if it turns on and can be rebooted. "Bricked" means dead - no power up - like a doorstop.I don't know if this is the same or a related problem. I got a new M1 MBP and decided to get rid of my old 2014 MBP (can not upgrade it to Monterey). I erased the data drive while in Disk Utility (I believe this may have been a mistake). the computer would not boot from a USB install disk for BigSur. After trying it would appear to be bricked. I repowered, cleared PRAM or NVRAM or whatever it is, and did an internet recovery.
This worked fine (except, ugh, I forgot how Mavericks looked), I downloaded the Big Sur OS from App Store. Went into recovery mode, selected Disk Utility, erased the entire drive and formatted with APFS, quit drive utility and installed Big Sur. All went normally thereafter.
It is worth a try. Especially if the installer is getting lost in some quagmire. Not saying this should happen, but what clued me in was reference to older machines Who knows what they were running. If they don't meet minimum Monterey specs, that is on the person installing. Go back to Big Sur.
sometimes it just to weird , for me just now . boot cannot repair only boot to bootcamp. if cannot boot to bootcamp or repair it totally confuse what happening.Too many people in this thread need to get their terminology straight. Your machine is not "bricked" if it turns on and can be rebooted. "Bricked" means dead - no power up - like a doorstop.
safe . the only not suggested is external boot.I got an M1 MBP (2020) and I was wondering if it’s safe to upgrade. Any suggestions?
I have the exact same policy.As much of an Apple evangelist I am, I have never upgraded the OS until the second or third update. If you depend on your Mac for school or to run your business (as I do) you can't take any chances. I don't know how Apple can cover all the bases, but they really need to do better.
Makes sense to support their bottom line. ?Well yea, you’re supposed to buy a new MacBook Pro with Monterey pre-installed.
I wouldn't mind waiting for more than a year, though three might be a bit much. Delivering an OS (or any software for that matter) on a schedule is generally a bad idea. I wouldn't mind if the point releases were only bug-fix releases and not releases for sneaking in more features. At least I'd have more confidence, since whenever you add a feature there's a high chance of adding bugs.Waiting until the .3 or .4 version of a new OS hac been SOP since computers came into general use back in the mid 90’s. Everyone knows that while the company does extensive testing, many many circumstances crop up that never came in the beta testing. This is simply how it works.
Additionally, if Apple or any Microsoft waited until 99.99 of all the problems were found in bet testing it would take 3 years before any new system could be brought to fruition.
I just did 4 Monterey upgrades (including one from High Sierra, no Mac newer than 2019) and they went smoothly.I work at an AASP and the most amount of MacOS reinstalls we ever did in a month was MacOS Big Sur (11.1-11.3) Probably did over 100 in a single month.
I have not seen a single Monterey boot loop yet. Probably just unlucky or very rare.