Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apple Releases macOS Sonoma 14.4.1 With Fix for USB Hub Bug

MacBird said:
1.15 GB for a 'minor' update. :)
Click to expand...
The minor change files are doubtless packaged up in a much larger collection of files that are subsequently signed, for security reasons. It certainly used to be the case that Apple would replace a whole system volume for significant updates.
 
Universal Control works better as before. But not as good as it was before Sonoma.

Still some disconnections. Far less than before, but still happens. Sooo annoying.
 
metabotschafter said:
And again, after the update the Mac came back with an "updated" Filevault Recovery key. Same like with the 14.4 update.
Click to expand...

If you were given a new Recovery Key, you might want to try validating it via Terminal.

I’ve noticed posters on some other Mac sites reporting that the new keys they were given fail, while their existing ones remain valid.
 
  • Like
Reactions: Pummers and metabotschafter
Darth Tulhu said:
Nope, still on Ventura and will stay there until I actually can't.

Historically, moving away from the OS my device came with has been detrimental. Every. Time.
Click to expand...
I'm on Monterey (2020 iMac) and plan to stay here as long as possible. No desire to upgrade and certainly not based on the horror show I've been reading about since Ventura.
 
  • Like
Reactions: uploaded
Jordan Klein said:
I'm on Monterey (2020 iMac) and plan to stay here as long as possible. No desire to upgrade and certainly not based on the horror show I've been reading about since Ventura.
Click to expand...

I've also read about the horror show and so I was late to the Ventura party, but version .4 (or was it .5?) was rock solid for me. Also Sonoma (I started at .3) gave me absolutely no trouble. Mac Studio and M1 Air here.
 
  • Like
Reactions: vjl323
dspdoc said:
Care to be more specific? What plug-ins?
Click to expand...
Kontakt and HALion. It didn't happen in 12.3 and earlier, for the same software; nor did it occur in the seed testing: only in the release. The problem has been widely reported and is entirely repeatable.

User-level software shouldn't cause a panic - at worst it should just crash the application. Panics are only caused by kernel extensions, drivers, and other low-down stuff.
 
Not sure about printer related fixes some were asking, but updating from 14.4 to 14.4.1 removed existing printer queues.
 
  • Like
Reactions: vjl323
I'm concerned about the one thing, did apple patch the GoFetch Flaw with this update?:

- if apple patched it what is the performance hit on M1, M2 & M3 chips?
 
****ing great update.
Now when I install some pkg or do a system update my installd memory leaks to 40GB and does a lot of swap 12+ GB.

Well done apple, now I have to wait for another release...
 
benwiggy said:
Kontakt and HALion. It didn't happen in 12.3 and earlier, for the same software; nor did it occur in the seed testing: only in the release. The problem has been widely reported and is entirely repeatable.

User-level software shouldn't cause a panic - at worst it should just crash the application. Panics are only caused by kernel extensions, drivers, and other low-down stuff.
Click to expand...
I have never seen or heard of this occurring.
 
For anyone who might be interested, 14.4.1 didn't fix everything. If you have a KVM in the mix, keyboards and mice are still not being recognized, at least not for me. I have two docking stations and a desktop PC plugged into a 4-system KVM. The KVM shares the monitor, keyboard, mouse, and sound output with 4 systems (a couple of macs and a couple of PCs). All PCs work fine with all peripherals. The macs get video and sound, but not keyboard or mouse. I really hate to say this, but my Windows 11 machines have been far more stable and reliable than my macs over the last couple of years (and it used to be the exact opposite for decades). I'm on my systems 10 hours a day minimum so I don't say this lightly.
 
  • Like
  • Wow
Reactions: osplo, Chuckeee, vjl323 and 1 other person
HobeSoundDarryl said:
I have researched it to death... and tested it with a wide variety of new and old enclosures with and without powered & unpowered hubs myself and am nearly completely confident this IS a macOS bug and not all of the redirects that tend to get slung when this topics comes up (firmware, cable, hubs, user error, settings, etc). Too many people, with too much differing equipment, etc are suffering the problem (but not everyone of course). The most telling in all of the research was with many people upgrading from pre-Big Sur to a newer version of macOS, crashing into the problem with their enclosure(s), then- needing the stable enclosure more than the update- downgrading and the enclosure works fine again. To me that screams where this problem lies because everything else remains the same.

I've got an important RAID enclosure forced retired because it can't keep its connection... unless I take it to any older Mac and then it is as stable as it can be. It is very frustrating that the "just works" company can't resolve this bug over now nearly 4 generations of macOS.
Click to expand...
Yep. This is essentially why I upgraded to 25Gb networking and set up high speed NAS. I effectively get 3 GB/s speeds. Good enough for any form of external access.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back