Apple Releases macOS Catalina 10.15.6 Supplemental Update With Virtualization Bug Fix

[MacRumors]

Apple today released a supplemental update for macOS Catalina 10.15.6, with the update coming a month after the original launch of macOS Catalina 10.15.6.

The ‌‌macOS Catalina‌‌ 10.15.6 Supplemental Update can be downloaded from the Mac App Store using the Update feature in the System Preferences app.

According to Apple's release notes, the update fixes a problem that could cause virtualization apps like VMware to crash. It also fixes an issue that could cause the 2020 iMac to appear washed out after waking from sleep. Apple's full release notes are below:

macOS Catalina 10.15.6 supplemental update includes bug fixes for your Mac.

- Fixes a stability issue that could occur when running virtualization apps
- Resolves an issue where an iMac (Retina 5K, 27-inch, 2020) may appear washed out after waking from sleep

macOS Catalina 10.15.6 will likely be the last update to the macOS Catalina operating system as Apple transitions to macOS Big Sur, the newest version of macOS set to be released in the fall.

Article Link: Apple Releases macOS Catalina 10.15.6 Supplemental Update With Virtualization Bug Fix

 

[Apple Macintosh 128K]

Always nice to see that quick turn around.

 

[djphat2000]

oh thank Cook!

 

[mb335]

YES! Glad this came out. Experienced the virtualization issue since updating to 10.15.6, which the workaround was to do frequent rebooting to avoid the issue.

 

[chucker23n1]

So, about two and a half weeks between VMware narrowing it down to a sandbox issue, reporting it to Apple, and Apple releasing a fix. That's not so bad.

 

[CJ Dorschel]

I've been a Mac user for almost 20 years yet this is the first time I have never updated my systems to the latest OS. I've held off on 10.15 but am considering updating as Apple has begun to drop support for certain aspects of 10.14 (security updates, etc will continue of course). I've been experiencing issues on two Mac Pro's that haven't been resolved with weeks of online research, clean installs, and Apple tech leading me to consider updating to 10.15.

My biggest concern is access to root as Apple continues to extend SIP. I've always disabled SIP and Gatekeeper as I require read/write access for development and third party apps. Certainly this it not something everyone should do and doing so is always with risk yet is a necessity for my personal needs and I utilize other precautions, etc.

That stated, my biggest concern is read/write access to root as Apple created two volumes for Applications - User and System. I've created a script that mounts the drive for read/write, assigns the necessary permissions, then deletes it. I've used this on my MacBook Pro for development work which is now running Big Sur.

My concerns with 10.15:

- Will this be necessary in case my system needs to be restarted? (I rarely do so unless necessary)
- Has Apple locked the ability to mount and change root permissions with incremental 10.15.x updates?

Don't even get me started on Big Sur. Running it on my MacBook Pro for development and struggling to adjust to the UI in addition to SSV. I completely understand Apple's focus on security especially for novices/everyday users, yet their focus on locking the system down further with each release makes it difficult for third party developers to maintain their apps which is most likely Apple's true intentions as they want to force developers to utilize the Mac App Store. Given there are ways to easily bypass Apple's security measures - granted they've made the processes more difficult - and users have already found backdoors in Big Sur, I wonder if there are better methods for security measures than what Apple has been implementing since SIP and Gatekeeper were introduced.

 

[TheYayAreaLiving 🎗️]

It’s an update day today

 

[Populus]

Yes!! I can finally perform a clean install of the latest Catalina versión with the virtualization bug solved!! Until I finally install macOS Big Sur in the fall

 

[dogslobber]

So, about two and a half weeks between VMware narrowing it down to a sandbox issue, reporting it to Apple, and Apple releasing a fix. That's not so bad.

It's total incompetence that such a stopper got into the field. Some useless developer doesn't know how to unit test their code change properly and the Apple QA process is sorely lacking. This is a total joke.

 

[adamw]

At least they fixed the Virtualization apps issue. Probably right about being the last version of Catalina to be released.

 

[Belle Pomme]

My MacBook Pro also has that washed-out problem too, so I hope it helps.

 

[Realityck]

Always nice to see that quick turn around.

It been an issue since the 10.15.6 PB 2 so no they did not get onto this as quick as we all reported as well as publicly released this. I encountered this crashing my iMac enough to think that it had suddenly went bad.

 

[digitalrampage]

I had started to get the washed out issue on my 16” 2019. Weird...

 

[MauiPa]

I've been a Mac user for almost 20 years yet this is the first time I have never updated my systems to the latest OS. I've held off on 10.15 but am considering updating as Apple has begun to drop support for certain aspects of 10.14 (security updates, etc will continue of course). I've been experiencing issues on two Mac Pro's that haven't been resolved with weeks of online research, clean installs, and Apple tech leading me to consider updating to 10.15.

My biggest concern is access to root as Apple continues to extend SIP. I've always disabled SIP and Gatekeeper as I require read/write access for development. Certainly this it not something everyone should do and doing so is always with risk yet is a necessity for my personal needs and I utilize other precautions, etc.

That stated, my biggest concern is read/write access to root as Apple created two volumes for Applications - User and System. I've created a script that mounts the drive for read/write, assigns the necessary permissions, then deletes it. I've used this on my MacBook Pro for development work which is now running Big Sur.

My concerns with 10.15:

- Will this be necessary in case my system needs to be restarted? (I rarely do so unless necessary)
- Has Apple locked the ability to mount and change root permissions with incremental 10.15.x updates?

Don't even get me started on Big Sur. Running it on my MacBook Pro for development and struggling to adjust to the UI in addition to SSV. I completely understand Apple's focus on security especially for novices/everyday users, yet their focus on locking the system down further with each release makes it difficult for third party developers to maintain their apps which is most likely Apple's true intentions as they want to force developers to utilize the Mac App Store. Given there are ways to easily bypass Apple's security measures - granted they've made the processes more difficult - and users have already found backdoors in Big Sur, I wonder if there are better methods for security measures than what Apple has been implementing since SIP and Gatekeeper were introduced.

Seriously? Mac development works fine giving your apps and Xcode appropriate permissions and Apple is not trying to lock down developers

are you sure you aren’t in one of those intellectual traps where you are creating your own imagined problems? Time to rethink?

Of course if you were specific, maybe I could see your point

 

[Realityck]

So, about two and a half weeks between VMware narrowing it down to a sandbox issue, reporting it to Apple, and Apple releasing a fix. That's not so bad.

While the VM observations certainly helped, Apple didn't respond to any reports or submitting feedback of kernel crashes with just using the computers with Mac applications, no VM. For me turning off BlueTooth seemed to make it a lot more stable, but still it happened occasionally. I went to Big Sur PB instead of sticking with 10.15.6, anything was better then a OS with kernel panics.

 

[chucker23n1]

It's total incompetence that such a stopper got into the field. Some useless developer doesn't know how to unit test their code change properly and the Apple QA process is sorely lacking. This is a total joke.

How do you check for a memory leak in a unit test?

 

[dogslobber]

How do you check for a memory leak in a unit test?

Memory profile tools.

 

[nt5672]

How do you check for a memory leak in a unit test?

I think the meaning was "test" and you use Instruments development tool called Leaks. So the simple test is that you run your unit tests while monitoring with Leaks. Even better design your unit tests to test for leaks.

 

[jprmercado]

Will this release eventually be integrated into a combo update?

 

[nikhsub1]

I downgraded to 10.15.5 because of this problem! Updating back now...

 

[CJ Dorschel]

Seriously? Mac development works fine giving your apps and Xcode appropriate permissions and Apple is not trying to lock down developers

are you sure you aren’t in one of those intellectual traps where you are creating your own imagined problems? Time to rethink?

Of course if you were specific, maybe I could see your point

Thank you for the kind assistance. My question was simple and I'm not in an "intellectual trap". If you have nothing productive to add to a discussion, perhaps it's best to be an adult and refrain from unnecessary slights.

As for an "example", many third party apps require access to specific area's. TotalSpaces is one example of an app I've used since Apple removed Exposé's "grids". Yet this has nothing to do with my questions. Perhaps this old thread regarding this particular "example" may be informative although it is from 2016. Third party app developers have had to struggle with Apple's changes since El Capitan and many of us refuse to use the App Store for many reasons yet - again - none of this has to do with my question(s). I've noticed you tend to talk down to people often on this site without actually helping. That's a shame. I hope you grow out of that phase soon.

https://www.reddit.com/r/osx/comments/3qq89p

 

[noraa]

I actually experienced the virtualization bug for the first time today, so the timing here is perfect.

 

[The Mercurian]

My MacBook Pro also has that washed-out problem too, so I hope it helps.

I had started to get the washed out issue on my 16” 2019. Weird...

That makes 3 of us then. Usually if I adjust the brightness it snaps back to normal but sometimes i have to close the lid and reopen.

 

[chucker23n1]

Memory profile tools.

So, not with a unit test at all.

 

[chucker23n1]

I think the meaning was "test" and you use Instruments development tool called Leaks. So the simple test is that you run your unit tests while monitoring with Leaks. Even better design your unit tests to test for leaks.

They should absolutely test for leaks, but… that seems antithetical to a unit test.