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

MacRumors

macrumors bot
Original poster
Apr 12, 2001
68,108
38,862


Apple today released macOS Monterey 12.3.1, a minor update to the macOS Monterey operating system that launched in October. macOS Monterey 12.3.1 comes two weeks after the launch of macOS Monterey 12.3, an update that brought Universal Control.

macOS-Monterey-2.jpg

The ‌‌‌‌‌macOS Monterey‌‌ 12.3‌‌.1 update can be downloaded on all eligible Macs using the Software Update section of System Preferences.

According to Apple's release notes, macOS Monterey 12.3.1 introduces a fix that could cause Bluetooth controllers like game controllers to disconnect from the Mac after playing audio through some Beats headphones. It also addresses a bug that could cause USB-C or Thunderbolt external displays to not turn on when connected to the 2018 Mac mini as a secondary display.
This update fixes the following issues:
- USB-C or Thunderbolt external display does not turn on when connected to Mac mini (2018) as a second display
- Bluetooth devices, such as game controllers, may disconnect from your Mac after playing audio through some Beats headphones
macOS Monterey 12.3.1 also addresses two vulnerabilities, including an AppleAVD issue that could allow an application to execute arbitrary code with kernel privileges and an Intel Graphics Driver issue that could allow an application to read kernel memory.

Apple says these exploits may have been actively exploited, so it is a good idea for all users to update as soon as possible.

Today's macOS Monterey update was also accompanied by iOS 15.4.1, iPadOS 15.4.1, tvOS 15.4.1, watchOS 8.5.1, and new 15.4.1 software for the HomePod.

Article Link: Apple Releases macOS Monterey 12.3.1 With Bluetooth and Display Fixes
 
Last edited:
I hope this also fixes the issue with Quick Previews. After a while, hitting the space bar only shows a tiny thumbnail instead of previewing the file as it should. The only way to fix this is to restart Finder which is frustrating since it will usually close all Finder windows.
 
At this point, can anyone tell me if there are still any memory leaks in Monterey? Or have been fixed all of them?

Any other major bug on Monterey? Or is this a safe release to jump from Big Sur?
An operating system contains millions of lines of code. It will never be perfect and there will always be some memory leak somewhere. But the major ones seem to be under control.
I work in software Quality Assurance and I can guarantee you that perfect software does not exist!
 
At this point, can anyone tell me if there are still any memory leaks in Monterey? Or have been fixed all of them?

Any other major bug on Monterey? Or is this a safe release to jump from Big Sur?
12.2 fixed the major memory leak issue, I have been on 12.3 on two machines on a full time basis for work with zero issues.
 
Bit alarming that the external display bug is referenced purely as a Mac mini 2018 issue, rather than on iMacs and MBPs too - either they haven't fixed the issue for all, or they don't know fully understand what the issue was.

Still, nearly download on my iMac 2017 with dual, borked external displays so will soon find out.

Edit: Yes, it fixed it.
 
Last edited:
An operating system contains millions of lines of code. It will never be perfect and there will always be some memory leak somewhere. But the major ones seem to be under control.
I work in software Quality Assurance and I can guarantee you that perfect software does not exist!
I know, I know, but I think we can all agree that an early release in october is not like a late relase in june with just refinements and bug/stability fixes. And on that scale, I just wanted to know if we’re closer to the later than to the former

Thank you anyway, I think it is time to install Monterey.
 
Bit alarming that the external display bug is referenced purely as a Mac mini 2018 issue, rather than on iMacs and MBPs too - either they haven't fixed the issue for all, or they don't know fully understand what the issue was.

Still, nearly download on my iMac 2017 with dual, borked external displays so will soon find out.
You had this issue as well? I didn’t know iMacs could have external displays attached!
Let us know if you still have this issue. Thank you!
 
At this point, can anyone tell me if there are still any memory leaks in Monterey? Or have been fixed all of them?

Any other major bug on Monterey? Or is this a safe release to jump from Big Sur?
The systemstats process has been going nuts on both my iMac and Macbook Air on 12.3. Woke up my Macbook Air today and the process was using 64GB of memory according to Activity Monitor.

I'm really hoping this update fixes it.
 
You had this issue as well? I didn’t know iMacs could have external displays attached!
Let us know if you still have this issue. Thank you!
I did... and of course they can! Not HDMI but USB-C/Thunderbolt (plus iPads/iPhone as well via Sidecar). Which of course is better anyway as it's just a single cable for video/audio/power.

I have 2x USB-C monitors, one plugged into one TB3 port, and the second daisy chained into the back of a TB3 external drive that's using the Mac's second port.

And I shall report back, though the download has got pretty slow.

Edit: It fixed it.
 
Last edited:
An operating system contains millions of lines of code. It will never be perfect and there will always be some memory leak somewhere. But the major ones seem to be under control.
I work in software Quality Assurance and I can guarantee you that perfect software does not exist!
Before any problem can be fixed, the company first has to admit that there is a problem, not ignore it or claim ”it’s a feature, not a bug”.
 
At this point, can anyone tell me if there are still any memory leaks in Monterey? Or have been fixed all of them?

Any other major bug on Monterey? Or is this a safe release to jump from Big Sur?
If you are a tap-to-click user, check out this thread


Basically, tap-to-click when pressing CMD, like to open up links in a new tab in browsers, fails around 20-60% of times, making it seem like the trackpad was broken. This bug seems to have been around since Monterey of beta days, and issue seems to be barely acknowledged by Apple.

It happens on all of the new 14" and 16" MBP's as well (led me to return mine). But if you aren't a tap-to-click user, you may be good.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.