Apple Releases macOS Big Sur 11.5.2 With Bug Fixes

[Johnny Santiago]

I just updated with this 11.5.2, same problem. Nothing is fixed. After installation, immediately mbp16 2019 crash, kernel panic. After using for about 15 minutes, it crashed again. Thunderbolt power on failed. I really did not enjoy using this machine at this rate. So i will stick on windows 10 (bootcamp). I just hope i can still used it for a longer time at least i can have return of investment at least under windows 10. Can not even sell this machine of good faith. How can you sell a machine that always restart.

 

[Fortran-man]

Does 11.5.x fix the dreaded second monitor problems that plague both intel and m1 minis?

my second screen blinks out every 30 minutes or so with 11.4…. Apple had this fixed at 10.14.6, but the problems resurfaced with every version of 11.x to date through 11.4.x. No amount of cable switching solves this. The monitor connected via hdmi is most problematic

worse…. External hard drives connected via thunderbolt are not mounted upon wake from sleep.

the mini and 11.x is a nightmare if you have 2 monitors and/ or external hd

 

[Johnny Santiago]

Nothing was fixed in my case, from catalina up to this date 11.5.2. I ended up selling my external monitor, due to kernel panic, attached an external ssd (samsung t2) for sure it will restart, thunderbolt power on failed. Even without any device now attached, it will restart. This mbp16 2019 using intel gone wild. Every update i am hoping this will be fixed, only consolation now is windows 10 on bootcamp, at least i can have my work done until this machine is totally down as i can not sell it knowing it's problematic, by then i hope i have already return of investment for this 3k dollar unreliable machine.

Does 11.5.x fix the dreaded second monitor problems that plague both intel and m1 minis?

my second screen blinks out every 30 minutes or so with 11.4…. Apple had this fixed at 10.14.6, but the problems resurfaced with every version of 11.x to date through 11.4.x. No amount of cable switching solves this. The monitor connected via hdmi is most problematic

worse…. External hard drives connected via thunderbolt are not mounted upon wake from sleep.

the mini and 11.x is a nightmare if you have 2 monitors and/ or external hd

 

[philosopherdog]

The only way of reliably connecting 2 displays still after upteen updates is to prevent sleep using amphetamine and unplug before sleeping the machine. Pretty rediculous. The Mac is so neglected.

 

[johto]

I just updated with this 11.5.2, same problem. Nothing is fixed. After installation, immediately mbp16 2019 crash, kernel panic. After using for about 15 minutes, it crashed again. Thunderbolt power on failed. I really did not enjoy using this machine at this rate. So i will stick on windows 10 (bootcamp). I just hope i can still used it for a longer time at least i can have return of investment at least under windows 10. Can not even sell this machine of good faith. How can you sell a machine that always restart.

sounds like you have a hardware faulty or you should do a clean install of MacOS

 

[Jonas07]

Big Sur is a disgrace for intel macs when is about performance kinda ironic since one year ago was fine with Catalina.

 

[Johnny Santiago]

sounds like you have a hardware faulty or you should do a clean install of MacOS

Since day 1 after purchase, already have this kernel panic thunderbolt power on failed. Run diagnostic, no problem/hardware faulty noted, all is clear. Perhaps, i might agree if using windows it will restart, but it didn't. Something is wrong with this machine and mac os Apple knows or not know, the thing is why it is released to production. If this is a car, so many accidents already if engine is running then suddenly panicked and restart.

 

[PBG4 Dude]

Big Sur is a disgrace for intel macs when is about performance kinda ironic since one year ago was fine with Catalina.

With the continuing issues on my 2020 iMac in Big Sur, I may roll back to Catalina. I am not impressed with this release, and I’m worried about moving forward to Monterey.

 

[Larsvonhier]

Nothing was fixed in my case, from catalina up to this date 11.5.2. I ended up selling my external monitor, due to kernel panic, attached an external ssd (samsung t2) for sure it will restart, thunderbolt power on failed. Even without any device now attached, it will restart. This mbp16 2019 using intel gone wild. Every update i am hoping this will be fixed, only consolation now is windows 10 on bootcamp, at least i can have my work done until this machine is totally down as i can not sell it knowing it's problematic, by then i hope i have already return of investment for this 3k dollar unreliable machine.

This really sounds like a mad hardware problem, not to be really fixed by updates. Why dontcha make an Apple repair appointment in a store?

 

[benwiggy]

What's the build number?

 

[Larsvonhier]

Big Sur is a disgrace for intel macs when is about performance kinda ironic since one year ago was fine with Catalina.

Cannot second that: I have a couple of C2D, i5 and XEON Macs (Macbooks, Macbook Pros and Mac Pros) running here with Big Sur and Monterey. Even unsupported as they are officially. Running as good and stable as on Mojave and Catalina. Cannot complain at all!

 

[PBG4 Dude]

Cannot second that: I have a couple of C2D, i5 and XEON Macs (Macbooks, Macbook Pros and Mac Pros) running here with Big Sur and Monterey. Even unsupported as they are officially. Running as good and stable as on Mojave and Catalina. Cannot complain at all!

Well, it’d be hard for you to see the continuing Big Sur graphics glitches if you don’t have a 2020 iMac with a 5500/5700XT GPU.

 

[Johnny Santiago]

This really sounds like a mad hardware problem, not to be really fixed by updates. Why dontcha make an Apple repair appointment in a store?

Machine is stable on windows(bootcamp). did not have the chance to visit apple store due to pandemic. If it restart on windows, i might agree this is hardware problem. Run diagnostic on mac os, no problem noted. Mbp16 2019 + mac os catalina/big sur = unstable ( thunderbolt power on failed, countless restart). Mbp16 2019 + windows 10 = ok, very stable ( can do my job all day long).

 

[Jupeman]

I just updated with this 11.5.2, same problem. Nothing is fixed. After installation, immediately mbp16 2019 crash, kernel panic. After using for about 15 minutes, it crashed again. Thunderbolt power on failed. I really did not enjoy using this machine at this rate. So i will stick on windows 10 (bootcamp). I just hope i can still used it for a longer time at least i can have return of investment at least under windows 10. Can not even sell this machine of good faith. How can you sell a machine that always restart.

I have been fighting kernel panics under Big Sur for months, also. Have you talked with Apple tech support? It is a laborious time consuming process, but they are likely to get you to a Tier 2 agent with a direct path to engineering. I'm waiting to see if my watchdog kernel panics end with 11.5.2 (very skeptical), but I continue to have dialog with Apple every day.

 

[Johnny Santiago]

I have been fighting kernel panics under Big Sur for months, also. Have you talked with Apple tech support? It is a laborious time consuming process, but they are likely to get you to a Tier 2 agent with a direct path to engineering. I'm waiting to see if my watchdog kernel panics end with 11.5.2 (very skeptical), but I continue to have dialog with Apple every day.

I have updated to 11.5.2 a while ago, and immediately restart after updated. After 15 minutes, it restart again. Yes i have called apple support, countless smc and nvram reset. Nothing fix the problem including updates from catalina up to this date. The only thing this machine is usable is to use windows 10 on it. Otherwise, infinite loop - panic and restart.

 

[dannys1]

Interesting that you mention that. Expect things like that to get worse and worse... eventually your Intel Mac will be rendered virtually useless towards the remaining updates for it. Then you will HAVE to get an M1 Mac. I've suspected this was the case for a loooooong while. And, same thing for the M1 Macs (and all Apple devices). That's how they make their money. They eventually render what you have as unusable, if you refuse to stay onboard their profit boat... they push you overboard, then haul you back in when you buy their latest technology.

Just because I'm happy to own an M1 Mac, doesn't mean I'm not aware of their practices. It's better you know the devil's tactics when you choose to play with the devil. Apple... Microsoft... same devil... different suit and tie.

Completely disproven nonsense.

 

[UltimoInfierno]

With something the size of macOS, it's either going to be one or two bugs or several hundred. Apple isn't going to want to release a huge fix list like that.

Since when is truth a problem?

You can decide to skim or completely ignore the bug resolved and added features document. Others may actually NEED the information in order to decide, whether an update warrants the work involved (company computers, multi computer/device owners).

I'd even value a "reported bugs, not yet fixed" document maintained on a regular basis (that would probably beat the above mentioned in size by up to several degrees). That would at least show, that a reported bug is actually acknowledged, and whether it pays to check, if it has been solved (currently the only way - often just confirms a still-not-solved state).

It would be nice to know, if Apple has fixed a bug - let's say in handling sparseimage on NAS SMB shares, if you've just discovered, that your backup access is "unreadable" or downright "inaccessible" since 11.3, but ONLY if stored on a NAS SMB Share. If you copy - for instance - the 349 GB sparseimage file to the local internal or external SSD, no problem exists for features previously working for years and years. This is no long term solution. Stopping backing up personal data to encrypted container is not an option either in our modern world.

Also, if something works, I'd probably postpone any update, if Apple specifies, that they have fixed that, specific bug ;-) At least until someone else has confirmed, that the fix did not alter existing functionality.

I don't mind working through a long list of potential fixes and updates. It's standard in other OS'es, and it saves a loooot of time trouble-shooting newly introduced "fixes" to working features, like the sparseimage example above ;-)

Regards

 

[fhall1]

You guys aren't making me feel real good....

I'm still at Mojave 10.14.6. My usual process for the past few years is to go to the previous major OS version when the new one drops in Sep/Oct. So I went from 10.13.6 to 10.14.6 when 10.15.0 was released. Usually that means most/all 3rd party software/hardware issues are pretty much fixed since the OS is now a year old. So last fall I should have migrated to 10.15.5 (or was it 6) when 11.0 was released.

However, I saw tons of complaints about Catalina still having a terrible amount of bugs when Big Sur was released and people were saying the early releases of 11.x were way better than the last release of Catalina. So I stayed on Mojave and figured I'd wait until THIS fall and go directly to Big Sur 11.5 or 11.6, whichever is last released.

But seeing how 11.5.2 is still pretty sucky - I'm on the horns of a dilemma. I really don't want to fall behind three versions and lose security fixes, etc. I guess I'm looking for suggestions from the group?

 

[ds10]

Since 11.5 came out, my M1 MBP has been crashing nightly. Wake up in the morning to the machine asking for a password as it starts to boot. The 11.5.1 didn't change this. After loading 11.5.2 yesterday, my MBP was still running and hadn't had a kernel panic overnight. Hopefully they addressed the kernel panic. It was getting rather annoying.

Since when is truth a problem?

You can decide to skim or completely ignore the bug resolved and added features document. Others may actually NEED the information in order to decide, whether an update warrants the work involved (company computers, multi computer/device owners).

I'd even value a "reported bugs, not yet fixed" document maintained on a regular basis (that would probably beat the above mentioned in size by up to several degrees). That would at least show, that a reported bug is actually acknowledged, and whether it pays to check, if it has been solved (currently the only way - often just confirms a still-not-solved state).

It would be nice to know, if Apple has fixed a bug - let's say in handling sparseimage on NAS SMB shares, if you've just discovered, that your backup access is "unreadable" or downright "inaccessible" since 11.3, but ONLY if stored on a NAS SMB Share. If you copy - for instance - the 349 GB sparseimage file to the local internal or external SSD, no problem exists for features previously working for years and years. This is no long term solution. Stopping backing up personal data to encrypted container is not an option either in our modern world.

Also, if something works, I'd probably postpone any update, if Apple specifies, that they have fixed that, specific bug ;-) At least until someone else has confirmed, that the fix did not alter existing functionality.

I don't mind working through a long list of potential fixes and updates. It's standard in other OS'es, and it saves a loooot of time trouble-shooting newly introduced "fixes" to working features, like the sparseimage example above ;-)

Regards

Better, IMO, that they get the kernel panic fixed than spend the time to put out a detailed statement about the bug that was causing said kernel panic. At least in my case, my M1 MBP was hitting a kernel panic nightly.

 

[DSL Steve]

No problems on a late 2013 MBP or a M1 Mac mini.

 

[KaplanMike]

Interesting that you mention that. Expect things like that to get worse and worse... eventually your Intel Mac will be rendered virtually useless towards the remaining updates for it. Then you will HAVE to get an M1 Mac. I've suspected this was the case for a loooooong while. And, same thing for the M1 Macs (and all Apple devices). That's how they make their money. They eventually render what you have as unusable, if you refuse to stay onboard their profit boat... they push you overboard, then haul you back in when you buy their latest technology.

Just because I'm happy to own an M1 Mac, doesn't mean I'm not aware of their practices. It's better you know the devil's tactics when you choose to play with the devil. Apple... Microsoft... same devil... different suit and tie.

If this really WAS the case, how am I able to run an graphic office shop that's populated with Macs that date to 2012 and 2013 (along with newer machines, of course)? Yes, these nine-year-old iMacs can't run the current OS, but they're still capable of running all the software we need to get the work done.

 

[UltimoInfierno]

You guys aren't making me feel real good....

I'm still at Mojave 10.14.6. My usual process for the past few years is to go to the previous major OS version when the new one drops in Sep/Oct. So I went from 10.13.6 to 10.14.6 when 10.15.0 was released. Usually that means most/all 3rd party software/hardware issues are pretty much fixed since the OS is now a year old. So last fall I should have migrated to 10.15.5 (or was it 6) when 11.0 was released.

However, I saw tons of complaints about Catalina still having a terrible amount of bugs when Big Sur was released and people were saying the early releases of 11.x were way better than the last release of Catalina. So I stayed on Mojave and figured I'd wait until THIS fall and go directly to Big Sur 11.5 or 11.6, whichever is last released.

But seeing how 11.5.2 is still pretty sucky - I'm on the horns of a dilemma. I really don't want to fall behind three versions and lose security fixes, etc. I guess I'm looking for suggestions from the group?

I really have no good advice for you. Only you can decide, if risks are worth any potential gains. Best of luck, whatever you decide.

 

[N1noodle]

Id say, if you dont have any issues and update doesnt does anything you specific, its always smart to w8 a week or 2 before updating.

 

[jazz1]

Well my dual HomePod minis are still "wonky" after OS update. I was hoping I wouldn't have to re-boot the M1 Mac mini to switch from my AirPod Max to the two minis in stereo. I also noted that while using the headphones the HomePod minis were lit up like they were in use. I have not yet seen my original issue of having videos not synching with dialog. A reboot fixed that temporarily. But I was hoping the OS update would make the HomePod Minis work as expected?

 

[Blowback]

Zero problems on 2017 MBPro. Updated (after reviewing this and other sites!!!) yesterday evening and did my usual: Restart --->Run awhile/open apps/ use Safari--->Shutdown--->Start again. Been using all since yesterday with not even a hiccup. Installation of 'phase 1' of 'Backdoor' complete......

Fixed (?) delay in ejecting/ and auto eject of external CCC SSD backup drive. Did todays backup and hit 'eject' and it ejected without asking 'eject Both?' and did it immediately.