Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Sonoma 14.4: Reasons Not to Update
- Thread starter MacRumors
- Start date
- Sort by reaction score
It also broke Docker https://github.com/docker/for-mac/issues/7220
I suppose my 15 year old Macbook Pro is deemed not update worthy by Apple themselves... any reason after that, I'll lightly consider. Until then, I have something to print.
I must be incredibly lucky. Encountered no issues whatsoever.
That said, there's no way a group of a few thousand beta testers can anticipate everything that hundreds of millions of endusers may be doing with their Macs. For good or ill, these updates are necessary because Apple has detected exploits affecting the previous OS, and wants to protect its customers. Which is more important, you think, quickly releasing security fixes that may prevent a long term catastrophe, or waiting to fix it until Apple is SURE nothing unanticipated is going to happen with each and every piece of hardware and software that everyone in the world may be using at any given time?
That said, there's no way a group of a few thousand beta testers can anticipate everything that hundreds of millions of endusers may be doing with their Macs. For good or ill, these updates are necessary because Apple has detected exploits affecting the previous OS, and wants to protect its customers. Which is more important, you think, quickly releasing security fixes that may prevent a long term catastrophe, or waiting to fix it until Apple is SURE nothing unanticipated is going to happen with each and every piece of hardware and software that everyone in the world may be using at any given time?
Since Apple unveiled macOS Sonoma 14.4 on March 7, the transition to the latest software update has not been entirely smooth for everyone, and a number of issues have been reported by users that significantly impact their daily workflow.
This article lists the most prominent challenges users have faced since updating to macOS Sonoma 14.4, and offers potential solutions where available.
USB Hub and Monitor Ports
Lost Connectivity
Some users have experienced connectivity issues with USB hubs and monitors with USB ports since updating to macOS 14.4, with several reports of mice, keyboards, and other peripherals no longer being detected. While Apple works on a fix, a handful of users have had some success by changing the setting "Allow accessories to connect" to "Ask for new accessories" under the Security section of System Settings ➝ Privacy & Security.
Java Processes
Unexpected Terminations
Oracle last week warned that the macOS 14.4 update can cause Java processes to "terminate unexpectedly" on Macs. The issue affects all Java versions from Java 8 to the early access builds of JDK 22, and there is no workaround available. Affected users might be unable to return to a stable configuration unless they have a complete backup of their systems prior to the OS update.
Printer Operation
Removed or Corrupted Drivers
The update may remove or corrupt printer drivers. Specifically, the core CUPS software for printing operations over a network seems to be removed. HP printers in particular appear to be affected, but the exact commonalities between the reports, such as the use of Microsoft Defender or JAMF mobile device management software, are not entirely clear. Some users have found a workaround by granting Full Disk Access to certain processes in System Settings ➝ Privacy & Security. Despite these attempts, a comprehensive solution has not yet been found.
PACE/iLok Protections
Audio Unit Plugins Crash
There have been reports of compatibility issues with PACE products, including the iLok License Manager, connected to Apple silicon Macs running macOS 14.4. The problem specifically impacts plugins from various manufacturers that are safeguarded by PACE/iLok, including those made by Universal Audio, when used with host DAWs such as Logic Pro. Temporarily setting a DAW and the iLok License Manager application to run in Rosetta mode appears to circumvent the issue.
Consider Not Updating
If you anticipate that any of these problems could significantly impact your daily operations or productivity, it may be prudent to delay updating to the latest version of macOS Sonoma until Apple addresses these concerns with a subsequent fix. Have you identified any other issues since updating? Let us know in the comments and we might include them here if they turn out to be commonplace.
Article Link: macOS Sonoma 14.4: Reasons Not to Update
Almost nothing works for me well with my Apple products these days. It's so sad. Had a nightmare upgrading from my iPhone 14 Pro with the latest system to an iPhone 15 Pro with the latest system. You would think that would be easy, but nothing worked and I had to try and re-pair them multiple times and it never worked and ultimately it still broke my watch connection and now I can't stop the stream of "Enable Wi-Fi Calling?" messages which appeared by the hundreds on all my devices and no change in setting fixes. APPLE GET YOUR SH*T WORKING - OR YOU ARE GOING TO LOSE EVERYTHING.
Tim Cook needs to order a 1-year bug-fixing hiatus from new features.
Just tested this. Sure enough, you're right. The Speaking Rate slider resets back to default after quitting System Settings. Wow... stuff like this would take literally 5 minutes to fix.
Have you submitted this feedback by Feedback Assistant?
If not, I just did.
I gave a down-vote, because surely it can't be _that_ bad, can it? Hundreds of your devices? Are you a corporate IT whiz?
I was referring to updates such as “17.4.1” which are the ones that usually fix what they broke with the more major update.
I remember this kind of thing from my IBM Mac days— updates forced upon unsuspecting workers 😄
They need to take the approach of Ubuntu, release a new version but also maintain a LTS version. 
I don't think there has been a release of the MacOS software (mid release) where there has been an advisory NOT TO UPDATE IT!
Apple totally dropped the ball on communicating WHAT was being done in this release to prepare people for the adverse affects of this patch. put on 14.4.1 already to correct these critical things. I am waiting for the iLOK fix that doesn't require me to dumb down my software with Rosetta.
Apple totally dropped the ball on communicating WHAT was being done in this release to prepare people for the adverse affects of this patch. put on 14.4.1 already to correct these critical things. I am waiting for the iLOK fix that doesn't require me to dumb down my software with Rosetta.
Unfortunately, I did this update as soon as it was offered, under the assumption that using a newer "M" series processor, there were still plenty of things Apple was probably patching/improving related to the relatively new architecture. So figured it was best to move to whatever their latest (presumably beta-tested) release offered.
Now, I'm regretting that because I do, in fact, have one audio app that uses that (terrible) iLok product. (I knew as soon as I saw it wanting to load iLok that it would give me grief. I hate, hate, hate these software copy protection schemes.)
I'm also regularly seeing disconnects/reconnects of an external USB hard drive I have on a hub, attached to my Macbook Pro 16" M1 -- and didn't associate it with this update until now. But makes sense that's my culprit.
The Java issue is kind of a non-issue for me, since I'm not a developer and retired my apps that needed Oracle's JRE for them to run. But it's a pretty big issue, overall, for Apple. A large percentage of people who chose a Mac as their primary machine are software devs.
Now, I'm regretting that because I do, in fact, have one audio app that uses that (terrible) iLok product. (I knew as soon as I saw it wanting to load iLok that it would give me grief. I hate, hate, hate these software copy protection schemes.)
I'm also regularly seeing disconnects/reconnects of an external USB hard drive I have on a hub, attached to my Macbook Pro 16" M1 -- and didn't associate it with this update until now. But makes sense that's my culprit.
The Java issue is kind of a non-issue for me, since I'm not a developer and retired my apps that needed Oracle's JRE for them to run. But it's a pretty big issue, overall, for Apple. A large percentage of people who chose a Mac as their primary machine are software devs.
First I have heard of anyone connecting that to the update or complaining the update has caused similar problems for them.
Do you normally reinstall your printers after minor OS updates? I thought not.
Recently upgraded from Intel to a M2, Mojave to Sonoma, most of the transition went well but none of the email passwords came across and had to be re-entered and of course none of my 32-bit apps work anymore.
Now I’m thinking maybe I should start again with Ventura.
Apple makes things difficult for upgraders.
Now I’m thinking maybe I should start again with Ventura.
Apple makes things difficult for upgraders.