Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
You never have been able to go back to a lower version than a mac has initially being shipped with. Intel or M1, no difference.
And the posters comments still ring true. On a intel mac you CAN downgrade the OS. This is assuming you realize they are talking about updates. If an update is dog **** you can revert back. An update is not something that ships with the mac but something you take after receiving the mac therefore making it eligible to be downgraded.

Which on iPadOS you can.. downgrade as long as the signing server is still accepting the previous version.

on mac m1 you can't at all. Its whatever is live on the server that it will be restored to.
 
  • Disagree
Reactions: jdb8167
My MacBook Air Late 2013 also demonstrates this issue after the latest Big Sur updates. Apple messed up big time.

This issue is not just in Monterey!
 
Last edited:
My USBs connected to Thunderbolt monitor (DELL UP2720Q) disconnect every day after update to M1 Pro. No problems with previous Intel Macbook.

Maybe it´s time to split Intel and AS version of MacOS again, these universal craps just do not work on any platform. I remember the same problems when Apple moved to Intel from PowerPC.
 
  • Like
Reactions: Jochheim
Apple Silicon Mac itself have some what compatibility issue with many monitors. It keep crashing with a pink screen.
 
Since I've owned my m1 Mac mini I've had to unplug the monitor from HDMI at least once every week because when the computer wakes from sleep all I see is colored static. Unplugging and plugging the cable back in has always fixed this, fortunately.

Same here. Two HDMI / USB-C to HDMI connected HP monitors on my launch day M1 Mac Mini has had this wake from sleep problem randomly on both monitors. They work fine on any other Mac / PC other than the M1.
 
  • Like
Reactions: rebelrogue42
My USBs connected to Thunderbolt monitor (DELL UP2720Q) disconnect every day after update to M1 Pro. No problems with previous Intel Macbook.

Maybe it´s time to split Intel and AS version of MacOS again, these universal craps just do not work on any platform. I remember the same problems when Apple moved to Intel from PowerPC.

I don't think that's potentially the DELLs issue. My brand new Studio Ultra cannot maintain a link to an external hard drive connected directly to its USB ports. If Studio sleeps, external disconnects "unexpectedly." On wake I get the warning about needing to eject the drive like I pulled the cable without first ejecting it. Sometimes while it is awake it will randomly disconnect too. I have not been able to deduce why this is happening "at random."

Prior Intel Macs did not do this. The very same drive using the very same cable remained readily attached for years without unexpected ejections. I've already tried changing cables, changing ports and even putting a powered hub in the middle. Nothing works. Searches reveal that this seems to be a very common issue with Monterey and maybe Big Sur before it too. It's very frustrating to spend $6K on a brand new super Mac and have one of the most basic of functions be wonky... then discover that it's a common issue for many going back to perhaps the prior version of macOS too.

What's on that external drive? My media library to feed AppleTVs throughout the house. When it unexpectedly disconnects, no AppleTVs have access to that media. Working solution (that isn't 100% effective)? Prevent Mac from sleeping... but that wasn't necessary with Intel Macs... even some upwards of 10 years old.

I'm thinking Apple needs a Snow Leopard-like dev year (or two) and an even better bug-reporting model to give them a clear list of things to fix. I can't believe disc drives connected via USB jacks in 2022 are not ridiculously reliable in terms of staying connected.
 
Last edited:
  • Like
Reactions: Jochheim
I don't think that's potentially the DELLs issue. My brand new Studio Ultra cannot maintain a link to an external drive connected directly to its USB ports. If Studio sleeps, external disconnects. On wake I get the warning about needing to eject the drive like I pulled the cable without first ejecting it. Sometimes while it is awake it will randomly disconnect.

Prior Intel Macs did not do this. The very same drive using the very same cable remained readily attached for years without unexpected ejections. I've already tried changing cables, changing ports and even putting a powered hub in the middle. Nothing works. Searches reveal that this seems to be a very common issue with Monterey and maybe Big Sur before it too. It's very frustrating to spend $6K on a brand new super Mac and have one of the most basic of functions be wonky... then discover that it's a common issue for many going back to perhaps the prior version of macOS too.

What's on that external drive? My media library to feed AppleTVs throughout the house. When it unexpectedly disconnects, no AppleTVs have access to that media. Working solution? Prevent Mac from sleeping... but that wasn't necessary with Intel Macs... even some upwards of 10 years old.

I'm thinking Apple needs a Snow Leopard-like dev year (or two) and an even better bug-reporting model to give them a clear list of things to fix. I can't believe disc drives connected via USB jacks in 2022 are not ridiculously reliable in terms of staying connected.
I don't blame Dell, as I wrote I didn't have these issues with previous Intel Mac so it has to be something with M1.

Sorry to hear that similar problems are even on the brand new Apple device. But actually it gives me some hope that Apple will, at least, put some attention to it. As you wrote, these problems are here since the first M1 mac.

I definitely agree on another year for macOS just for fixing bugs if it helps.
 
Maybe they should charging for macOS updates again…

Would be better for all of us if they had to earn the upgrade money.
 
I have an M1 Mac mini connected to two 4K LG displays, one through USB-C and another through HDMI, without any issues whatsoever. This is one of those cases where anecdotal evidence is not proof of a widespread (or, at the very least, universal) issue.
 
Last edited:
I have an M1 Mac mini connected to two 4K LG displays, one through USB-C and another through HDMI, without any issues whatsoever. This is one of those cases where anecdotal evidence is not proof of a widespread (or, at the very least, universal (issue).
Since reversing the way I plug the USB-C connectors in at both ends fixed things for me, it's indeed quite possible/likely that many people will never see this problem. Interesting that the orientation was working fine with 12.2 but 12.3 required the reversal. (I think the advice originally came from someone at LG.)
 
  • Like
Reactions: Mainyehc
just give the updates a few months to shake out.

So basically just keep surfing from one update the next, hoping for the best? That’s an untenable position for those who absolutely rely on their Mac to earn a living and pay Apple very handsomely for the privilege of using their computers to do so. I get that sometimes stuff just happens, but it’s becoming a regular occurrence at New Apple and for every bug they fix they seem to add two more, so waiting for updates to drop is hardly a great solution.
 
Monitor support on MacOS has been bad for some time. I have an LG monitor where macOS won't boot up if its connected to DisplayPort, but if it goes to sleep on HDMI it won't wake back up. It will wake up if I hook it up to DisplayPort after its booted. The same monitor works fine with the same machine in Windows and Linux. This has been a problem since I first bought it back when Mojave was released.
 
  • Like
Reactions: turbineseaplane
Does anyone know if there is a tech equivalent to the auto industry's "Lemon Law"? I get that software is extremely complex given the infinite combinations of hardware & software, but there has to be some point where there is some level of accountability. These are all real issues that affect people's livelihoods.
 
How did Apple become so bad at external monitor support? Back in the day, Windows users used to envy Mac users for this reason but now it’s the other way around. And the dock that Steve introduced over 10 years ago hasn’t evolved at all... It’s as dumb as ever in adapting to a multiple monitor environment.
Part of the problem is the increasing complexity of the technology and lowered tolerances as a result. The other part is Apple don’t care to test anything beyond the lowest common denominator. It used to be that this was helped by just not offering lots of features but complexity with Apple product has grown to stupid complexity too.
 
  • Disagree
Reactions: lysingur
I keep thinking I need to upgrade to Monterey, and Apple keeps giving me reasons not to.

My strategy is to just keep three generations of support, meaning that if a new macOS is likely to be released this June, projecting ahead and staying at Big Sur is the ideal choice, after all, theoretically most apps have at least three generations of OS support.

Of course, if start with the Monterey model, they have to sing "Danny Boy".
 
  • Like
Reactions: TechRunner
My strategy is to just keep three generations of support, meaning that if a new macOS is likely to be released this June, projecting ahead and staying at Big Sur is the ideal choice, after all, theoretically most apps have at least three generations of OS support.

Of course, if start with the Monterey model, they have to sing "Danny Boy".
Yeah... this is my problem... those of us who ordered the Mac Studio and didn't cave in and the Studio Display are in a difficult position. They'll all come with Monterey....Seriously like what i am supposed to do (other than hope)....???
 
  • Like
Reactions: ddhhddhh2
12.3 Actually fixed my USB-C display issues with my Philips Brilliance 279P. It's been a wild ride. It worked with the original version of Monterey. Then it totally stopped working over USB-C in 12.1 and 12.2. Now 12.3 has fixed it. I hope they don't regress it back fixing the others!
 
Starting with 12.3? Hah. Our imac that controls streaming and does titling at my church accidentally got upgraded to Monterey in November. Since then, our usb c/thunderbird > hdmi > SDI > video mixer board has not worked. I tried everything short of downgrading back to the previous os x. Apple was no help.
I solved it temporarily by getting a thunderbird > SDI box. Note if you're in the same boat: that's not a monitor adapter, it's an output stream (?) adapter. Basically, your software has to implement "stream" access. Luckily, mine did.
The fine tech support at Black Box told me that the problem was that in monterey they removed support for a number of resolutions. In my case, I needed 1080i/60.
Long term solution is to get rid of the mac and replace it with a PC running OBS of some flavor, and it can handle titling, adapters, streaming, camera control, etc. all in one. We have the mac, a camera control box, a video switcher, a usb recorder box, and a streaming box. Plenty fine for a 1080 stream for hundreds less.
I'd love to have a mac, but can't afford a similar solution running on a mac.
 
  • Like
Reactions: alien3dx
Starting with 12.3? Hah. Our imac that controls streaming and does titling at my church accidentally got upgraded to Monterey in November. Since then, our usb c/thunderbird > hdmi > SDI > video mixer board has not worked. I tried everything short of downgrading back to the previous os x. Apple was no help.
I solved it temporarily by getting a thunderbird > SDI box.

Relative to the external hard drive research, some online forum posts about Monterey and "unexpected ejections" have suggested similar workarounds. For example, I've seen a few posts about using thunderbolt 3 to thunderbolt 2 (adapter) to firewire adapter and then using firewire drives. Apparently that works. If you work through 2 adapters to be able to use an ancient interface, you (may) have a consistently-attached external drive... exactly as how the same drive + cable would behave with the former Intel Mac minus the dongles and having to use Firewire.

I haven't opted to try that yet mostly because I don't really want to dig out a firewire drive... but also because I almost don't want that to be an actual solution on a brand new $6K Mac. But it sure is frustrating to see the notification that my external drive has unexpectedly ejected over and over again- at least daily. And I know from accidentally doing that at times in the past, that can easily lead to having to reformat the drive and reload it with the files to get it back in use again.

Bring on the Snow Leopard "behind the scenes" bug fixes macOS year or two.
 
  • Like
Reactions: lysingur
Yes they can. They could do whatever and be fine. They’re flush with cash. You’re talking about Wall Street BS. The only winning move in THAT game is to not play it. The stock market is poison to everything.
Except they do play in it because I can buy AAPL shares right as we speak.

And honestly, when all their competitors (Google, Microsoft, Amazon, Samsung, etc...) are adding new software features every year, they just don't have the opportunity to take a whole year to release a major version that's basically just bug fixes. No matter if they're at Wall Street or not. Because that release will get review bombed by all the reviewers and consumers will realize there's nothing new. People are already saying there's nothing new even when there actually is.

It really sucks and I really hate to say that, trust me... but stability is not sexy (anymore).
New features are always sexy.

It's a huge dilemma, because Apple really do have a major problem with the quality of their software now. What I see them doing with iOS is they release a mid-major-update release (iOS 15.4 contained a lot of features). They kinda did it with Universal Control, but they should commit to that a little more with macOS.
 
According to one user on the MacRumors Forums, the issue stems from macOS not recognizing a DisplayPort protocol version, which meant they had to change the version to an earlier one with poorer quality output.

While Apple is updating support for DisplayPort protocols, how about they get around to finally supporting DisplayPort MST (which has been part for the DisplayPort standard for many years now) for daisy chaining and multi monitor hubs. Lack of MST support is not a hardware issue because the same Intel Mac booted into Windows supports MST just fine.
 


Following the latest macOS Monterey 12.3 update, users are reporting several problems when using external monitors, ranging from Macs not detecting displays at all to inaccurate screen output, according to posts on the Apple Support and MacRumors forums.

24-inch-imac-and-macbook-monterey.jpeg

In the ten days since the update became available to the public, users have already reported issues with the update bricking Macs that have had logic board replacements and problems with using game controllers. Adding to the list of issues, users are now reporting that the update is causing problems with external monitors.

According to users on the Apple Support and MacRumors forums, some external displays connected over USB-C are no longer detected by Macs after updating to the latest macOS update. As one user on Apple Support reports:
Other users have shared similar experiences. While many also report issues with USB-C displays, others also say that HDMI connections to the Mac are not being recognized. Some users have been able to crowdsource potential workarounds in the meantime. According to one user on the MacRumors Forums, the issue stems from macOS not recognizing a DisplayPort protocol version, which meant they had to change the version to an earlier one with poorer quality output.
Another short-term fix floated on both the Apple Support and MacRumors forums is to unplug the external display for a short time, plug it back into the Mac, and then plug the display back into a power outlet, after which it should work. Some users have also reported problems when using two external monitors with their Mac.

The issue of only one external display being recognized when two are connected to a Mac seems to have been present throughout the beta testing period for macOS 12.3. Even after release, however, the issue remains. As one user on the Apple Support forums relates:

The online reports suggest that these issues are not arising when using Apple's new Studio Display, but instead with third-party monitors, such as those offered by BenQ and LG.

macOS 12.3 is Monterey's largest point-update since launch, bringing with it Universal Control along with several other new feature additions. MacRumors earlier this week reached out to Apple for comment on the issues users are experiencing so far with the latest macOS update. We'll update this post if we receive a response.

Article Link: Users Report External Monitor Issues After Updating to macOS Monterey 12.3
I have the same issue, mac mini not detecting third monitor USBC.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.