hoakley March 31, 2022 Macs, Technology

Apple has released Monterey 12.3.1 update

Apple has just released the update to macOS Monterey 12.3.1.

It claims to address two issues: for Mac mini 2018 systems, it ensures that a USB-C or Thunderbolt display used as a second display turns on properly, and it fixes an incompatibility between some Beats headphones and other Bluetooth devices such as game controllers, which may disconnect after playing audio through the headphones.

There are two security fixes included in this update, detailed here. One affects AppleAVD, the other Intel Graphics Drivers. Apple remarks that it’s aware of reports that both vulnerabilities have been actively exploited. These make this an urgent update for all Monterey users.

This update does bring firmware updates for T2 and M1 Macs.

This update is around 1.83 GB on Intel Macs and 2.22 GB for M1 models, and is now available in Europe as well as North America.

There’s no sign of any accompanying security updates to Big Sur or Catalina.

I will shortly be posting my analysis of the changes this update brings.

Thanks to Mr. Macintosh for alerting us to this update.
Last updated 2125 GMT 31 March 2022.

19Comments

Add yours

1

Bob Wiggins on March 31, 2022 at 6:22 pm

I wonder if this addresses the bricking issue on some Mac’s with Logic Board replacements.

Although my M1 MacBook Pro is all original and not one of the later M1s, I decided to wait and see before upgrading as I don’t have another recent Mac to perform a restore with in case of trouble.

LikeLiked by 1 person
- 2
  
  Javier Gallardo on March 31, 2022 at 6:53 pm
  
  I do have a second mac to do the Configurator thing, but I’m going to do same as you. Catastrophic corruption has happened in some update, but quickly detected. The postponing can’t be too long, as important security updates are included. We need some brave, equipped, tech-savvy users to go as advance party.
  
  LikeLiked by 1 person
  - 3
    
    hoakley on March 31, 2022 at 10:38 pm
    
    I don’t understand how you can get “catastrophic corruption” in a Big Sur or Monterey update. Before the updated system is handed over, it has to be shown that it perfectly matches that expected, down to the last bit.
    Howard.
    
    LikeLike
    - 4
      
      Javier Gallardo on April 1, 2022 at 8:16 am
      
      I neither do understand it:
      https://appleinsider.com/articles/22/03/17/macos-monterey-123-reportedly-bricking-macs-with-replacement-logic-boards
      
      LikeLiked by 1 person
    - 5
      
      hoakley on April 1, 2022 at 8:46 am
      
      Thank you.
      I try here to bring not vague rumours, but to cast light. That report doesn’t attempt to resolve any information which could be useful, other than problems were being reported in unspecified Mac models which had had replacement logic boards, and that they seemed to be fixed by performing a ‘revive’ using Apple Configurator 2.
      The truth behind that seems to be that some MacBook Pro 2012 (M1) Macs which had been given replacement logic boards had problems with the 12.3 update. Most appear to have been unable to install it at all, but a few did have problems with ‘firmware’ update failure. That isn’t catastrophic corruption, nor does it brick that Mac. It does require another Mac to be connected to it to perform either a firmware refresh or a full restore. Users who can’t or won’t do this themselves can get that performed by any Apple store, or service provider, in the normal way, and free of charge.
      So this applied to a very small number of Macs of a specific and recent model, which had already required major warranty repair. Recovery was straightforward, and could be performed by some if not many of those users, using readily available free tools and a well-documented procedure.
      Compared to the often widespread broken installs that used to happen before Big Sur, that’s a huge improvement, and definitely no cause for alarm, particularly if you don’t have a 2021 MacBook Pro which has required a replacement logic board.
      From rumour comes forth light.
      Howard.
      
      LikeLike
- 6
  
  hoakley on March 31, 2022 at 10:36 pm
  
  I’m sorry, I don’t know. Only Apple does, and it ain’t telling.
  Howard.
  
  LikeLiked by 1 person
  - 7
    
    hoakley on April 1, 2022 at 7:27 am
    
    Update: this update apparently addresses the issue of some MacBook Pro 2021 Macs not being updated to 12.3.
    Howard.
    
    LikeLike
8

ericrfmwp on March 31, 2022 at 7:12 pm

I just checked, using Software Update and SilentKnight, and not only is there no 12.3.1 listed, but also no 12.3 (I’m on 12.2.1). It’s probably just a short window, but I thought it was interesting to note, especially if something odd happens like they decide to yank 12.3.1 because of a Fatal Flaw™

LikeLiked by 1 person
- 9
  
  hoakley on March 31, 2022 at 10:39 pm
  
  Thank you.
  This update did seem to roll out slowly and across different parts of the world at different times. But I think it should be available now worldwide.
  Howard.
  
  LikeLike
10

prehensileblog on March 31, 2022 at 9:12 pm

It appears that 12.3.1 fixes this bug:
https://forum.keyboardmaestro.com/t/open-with-finder-applescript-bug-in-macos-12-3/26971/12?u=lantro

LikeLiked by 1 person
- 11
  
  hoakley on March 31, 2022 at 10:44 pm
  
  Thank you. That’s fascinating, as I can’t see anything changed in /System/Library which could account for that.
  Howard.
  
  LikeLike
12

dhausman on March 31, 2022 at 9:31 pm

My 2017 intel macbook pro updated, but my m1 macbook pro says 12.3 is current. Usually I can update right away, this is kind of strange. Even tried a softwareupdate -l

LikeLiked by 2 people
- 13
  
  hoakley on March 31, 2022 at 10:46 pm
  
  I’m sorry to hear that. SilentKnight can trigger the update’s availability, although in this case there seems to have been some sort of geographical limitation.
  Howard.
  
  LikeLike
  - 14
    
    dhausman on March 31, 2022 at 11:31 pm
    
    Tried SilentKnight, it reported iBoot needed updated. I did reboot my M1 and then it showed the update. Not sure why I would need to reboot. Has be concerned that my users will get a nudge and not be able to update.
    
    LikeLiked by 1 person
    - 15
      
      hoakley on April 1, 2022 at 7:28 am
      
      Thank you.
      Sometimes softwareupdated seems to freeze and updates cease becoming available. In my experience, that’s extremely unusual, but cured by a restart. Or it may just be coincidence, of course.
      Howard.
      
      LikeLike
16

Paul Durack on April 1, 2022 at 1:11 am

This is really interesting, no 12.3.1 available for me either – I’m on the west coast USA, so would assume I am first in the queue – on a MacBook Air 2020 (M1, MacBookAir10,1)

LikeLiked by 1 person
- 17
  
  hoakley on April 1, 2022 at 7:29 am
  
  I’m sorry to hear that. Have you tried restarting, then running SilentKnight once everything has settled down again?
  That often triggers update availability.
  Howard.
  
  LikeLike
  - 18
    
    Paul Durack on April 4, 2022 at 7:03 pm
    
    Yep, tried to do that a couple of times, even updating silentknight to 1.18. I must admit that I have the beta profile installed, which is likely holding me back for the beta of 12.4 to land, at some stage in the distant future
    
    LikeLiked by 1 person
    - 19
      
      hoakley on April 4, 2022 at 8:22 pm
      
      I don’t test betas outside the summer period (WWDC to next major release), but still use SilentKnight throughout to keep up to date with security data updates, and have never had a problem. So I’m afraid I’m baffled.
      Howard.
      
      LikeLike