In other cases, some monitors are completely blacked-out or not charging the MacBook Pro connected by Thunderbolt or USB-C cables. In the worst cases, some Mac users have found that the external display is not recognized by Ventura or Monterey when connected via USB-C or Thunderbolt.
The problem has affected all brands of monitor including LG, Dell, BenQ, Asus, Acer, Xiaomi and even Apple’s own Studio Display. Many users have found that after upgrading to Ventura, Monterey and even Big Sur, one or more of the external monitors they were using suddenly stopped working with their MacBook Pro, Mac Studio or Mac Mini. If your screen still isn't working, you'll want to give Appel Support a call, and they should be able to get you back on track.If you’ve have problems with external monitors not working on your Mac after upgrading to macOS Ventura, macOS Monterey or after buying an Apple Silicon M1/M2 Mac, here we show you how to get them working again. Unfortunately, if you've tried all the tips above, it may be time to call in the big guns. Go System Preferences > Displays and then try connecting your external monitor to your Mac with that Displays menu open. I know this sounds a little odd, but ultimately, it's how I got my external display to work with my iMac (2021). Connect your monitor with display settings open If that doesn't work, try rebooting your Mac, but plug in your external display before you power on your Mac again. I would actually suggest trying two different types of reboots.įirst, reboot your Mac and then plug in your external display once your Mac is powered on and you're logged in.
Rebooting your Mac is a great way to shock the system and fix any niggling problems you might be experiencing. Plus, if you're connecting your monitor via a USB-C hub, you'll want to try hooking that USB-C hub to a different port as well. Specifically, on the M1 iMac and the M1 Mac mini, you should be using a Thunderbolt port to connect to any monitor.
If you're using a USB-C connection for your monitor, try a different port to see if that resolves the issue.
0 kommentar(er)
