Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
So, maybe the problem is your monitor or your hub/cable or anything between.

I've tried with three brands of hubs, two brands of TB3 cables and two brands of monitors ...

This was and IS working fine on my 2019 Intel MBP. And it was working okay with my 2021 Apple Silicon MBP in a sense - had to disconnect and connect the TB3 cable, a pain but I thought Apple would *fix* the issue not make it worse. Now with MacOS 13 - after the MBP goes to sleep - it can never wake up extrernally connected monitors.
 
Mac: Mac Book Pro M1, on Mac os 13.1
Monitor: LG 27UL550-W UHD 4K IPS Monitor

I had the same issue. I was using a type-C HDMI adapter to connect my Mac to my monitor.
I removed the adaptor and connected my mac directly to my monitor using the HDMI cable only (no adaptor, no type-c connector), and everything was back to normal.

Hope this helps someone.
 
My MacStudio, running 12.6, never had problem with external monitor, direct HDMI to HDMI, via HDMI to DP adapter, or a TB3 to HDMI 2.1 adapter (from Sabrent). So, maybe the problem is your monitor or your hub/cable or anything between.
And I will never trust USB3.x for connecting a high resolution monitor.
This problem has been going on for years.

 
Different problem here. I was using an Anker 555 hub with HDMI from hub to monitor’s HDMI. Worked fine. Tried using USB-C from monitor to PD USB-C on 555 hub to power it and the MacBook Air M1 from the Samsung LS27A800UNNXZA monitor’s power. I had to adjust the monitor’s settings to use USB-C and accept the device in Ventura, but monitor worked well. But whenever it went to sleep I got constant notices that my ext. drives had been incorrectly disconnected. They were still connected though and worked fine. I switched to using the monitor with USB-C cable plugged directly into TB3 port on MacBook Air M1. Still had the erroneous notices popping up in great numbers. Unplugged the power to the 555 hub since it wasn’t needed to power the MacBook Air M1, and that helped, but still getting a few erroneous notices. The MacBook Air M1 is charging from the monitor’s power. Perhaps having two power sources connected to the MacBook Air M1 TB3 ports is overkill and caused a huge number of notices about drive disconnects. With just a single power source I get only one round of notices rather than dozens.

Maybe Apple should replace their idiot programmers with the ones Musk fired from Twitter! Everything works now, but getting tired of clearing those damn notices. For some reason I couldn’t clear all the notices at once and was forced to manually clear dozens of the little turds…
 
  • Like
Reactions: albabe
The problem also exists with external GPU-s. After the update when the display was finally working, after several forced restarts, then it was getting sluggish (like a 30Hz display... and it was set to 60Hz). Finally I found this topic on apple discussions, about usb-c external monitors not detected.

Ventura 13.0.1 update results in USB-C monitor no longer being detected

One of the posts suggested to remove the logged in user's old Window Server config file(s), and restart your mac because all of this problems related to WindowServer process. ( ~/Library/Preferences/ByHost/com.apple.windowserver.{guid}.plist).

In my case after removing the files and restarting my mac the problem disappeared. (for now... :))

Hope it helps out some of you!
 
Hey! I'm new to mac os so may be you can advice me something. I've just bought this usb c hub for my macbook air m1. My os version is 13.0.1. I've connected it to my monitor via hdmi-dp cable but macbook just doesn't see the monitor at all. I've tried every solution I've seen online: power cycling, safe mode, changing resolution etc. But still have no result. What shuold I do to make it work?


ade97b46be1c365c2793d6ee8caa07b8.jpg
 
Hi All,

Here to report that I'm also having issues with my external display on Ventura...here's my situation:
  • 2020 MacBook Air M1 + 32" LG UltraFine 4K Ergo (32un880-b)
  • Primarily connect USB-C > USB-C single cable / passthrough (the cable that came with the display)
  • Just upgraded to Ventura maybe 2 weeks ago, no display issues / working fine this entire time
  • Came home last night, plugged in USB-C, LG monitor starts to flicker (along with MBA), charging no longer works, monitor is not detected whatsoever by MBA / Settings > Display Settings
  • I'm getting either "No Signal" from the LG, or an intermittent blinking of the USB-C connection dialog:
  • IMG_5473 Large.jpeg
  • HDMI still working (both ports) — however when connecting to my MBA via HDMI / hub, passthrough charging no longer works and causes the monitor and MBA to flicker
  • Tried all of the common troubleshoot points (monitor power cycle, unplug, reboot, etc.) I even upgraded to Ventura 13.0.1 to see if that would solve it, no dice
At this point, I have no idea if it's the USB-C port on the monitor, USB-C cable, or the MBA. Seeing how I'm having issues with the hub and passthrough charging while connected via HDMI, I'd like to think this is a software issue, but can’t say with total certainty. MBA also charges perfectly fine through USB-C from the wall charger.

I've ordered a DisplayPort > USB-C cable just for my own troubleshooting sanity, though that still doesn't solve the USB-C single cable solution that I love with the LG.

Any insights would be appreciated!
 
Last edited:
Kind of the same problem here.
I'm on Ventura with 14"MBP & Apple Studio Display.
When I plug in the TB cable from the Studio Display the display turn on/off every 3 seconds.

To resolve it temporarly I have to reboot my MBP with the TB cable attached to the MBP.
 
Different problem here. I was using an Anker 555 hub with HDMI from hub to monitor’s HDMI. Worked fine. Tried using USB-C from monitor to PD USB-C on 555 hub to power it and the MacBook Air M1 from the Samsung LS27A800UNNXZA monitor’s power. I had to adjust the monitor’s settings to use USB-C and accept the device in Ventura, but monitor worked well. But whenever it went to sleep I got constant notices that my ext. drives had been incorrectly disconnected. They were still connected though and worked fine. I switched to using the monitor with USB-C cable plugged directly into TB3 port on MacBook Air M1. Still had the erroneous notices popping up in great numbers. Unplugged the power to the 555 hub since it wasn’t needed to power the MacBook Air M1, and that helped, but still getting a few erroneous notices. The MacBook Air M1 is charging from the monitor’s power. Perhaps having two power sources connected to the MacBook Air M1 TB3 ports is overkill and caused a huge number of notices about drive disconnects. With just a single power source I get only one round of notices rather than dozens.

Maybe Apple should replace their idiot programmers with the ones Musk fired from Twitter! Everything works now, but getting tired of clearing those damn notices. For some reason I couldn’t clear all the notices at once and was forced to manually clear dozens of the little turds…
I finally got my ext. monitor to work with my MacBook Air M1 via USB-C cable. I plugged the USB-C cable into the monitor and directly into one of the MacBook Air M1 TB3 ports. It doesn't consistently work if I plug it into a PD port on a powered hub. When it goes through a hub, the monitor isn't always seen, no power is passed through the hub (tried several different hubs), and the ext. SSD and HDDs attached to the hub kept spitting out errors about improper ejections.

However, with the USB-C cable plugged into the monitor and directly into one of the MacBook Air M1 TB3 ports, and with the hub connected to the other MacBook Air M1 TB3 port without a power cable plugged in, then the monitor, SSD, and HDD all work well. What a colossal PITA! If I plug a power cable into the hub's PD port it goes bad. The monitor powers/charges the MacBook Air M1, so the hub really doesn't need power or power passthrough, so I just leave it without power.

In my case, I think the issues were related to Apple not being able to get the TB3 ports to work correctly with hubs that have power passthrough.
 
So I think I have the same issue as the OP. I've attached pictures which show the issue.

I have 2 MacBook Pros - a personal 2017 13 inch, and a work 2019 15 inch.
The work MacBook works fine on my Samsung CRG9 monitor. (5k ultra wide display)
The personal one always used to, but since upgrading to Ventura no longer does.

  • When the CRG9 is plugged in, it becomes garbled. Screenshooting the screen shows MacOS thinks it is displaying perfectly.
  • If I set the built in display to scaled (as opposed to Default) it too becomes garbled when the CRG9 is plugged in, but is fine otherwise.
  • I use a USBC to DisplayPort cable, which worked perfectly before and works on my other MacBook and windows laptops ok.
  • It works fine in safe mode. (but clearly I can't just use my computer in safe mode all the time)
  • Bootcamp windows on the same MacBook 13 works fine.

I have tried:
  • Resetting NVRAM etc.
  • Completely reinstalling MacOS, so this is a vanilla install with no additional application installed
  • Changing the display port version to 1.1 and 1.2
  • Reseating the cables
  • Setting all the possible resolutions and profiles for the external monitor
When plugged into 2017 MBP 13: (I used an extended display to the iPad otherwise I could't try changing resolutions!)
IMG_8389.jpeg


When plugged into the 2019 MBP 15 using the same cable
IMG_8387.jpeg
 
  • Like
Reactions: Bee_Lu
On MacOS 13.0 and 13.0.1, I had 2 displays hooked up to my 2021 MBP 14" (M1 Pro) via an Anker Thunderbolt 4 Mini Dock. It worked, mostly... on boot or wake-up from sleep, I had to power-cycle the dock to make the displays work, which is easy, since has a power button.

Once I upgraded to 13.1, only one display would work at a time. After trying nearly everything I could think of and/or read in this thread, I swapped the cord running from the hub to the laptop to one from CalDigit that is explicitly marked as Thunderbolt 4. Now everything works, without even having to power-cycle the dock.

Lessons learned:
  1. It could be the wire(s).
  2. If you suspect (1.), go with something brand-name and verified to be what it says it is.
 
I'm about to endeavor down this path with MBA M1 2020 so I've been researching what I'm in for once I begin.

I haven't read everyone's post accord 3 pages so this may have already been mentioned... I've read a few of comments elsewhere relating to TB3/4 female to male extenders to a hub, suggests trying:
  • flipping the female end over
  • flipping the male end over at the MB
  • the other TB port on the MB, and then again flipping the female
For those using an external hub, without an extender but with power supply, try:
  • unplugging TB cable after shutdown, ensure hub is powered up, boot MB, and then plug in TB cable
  • unplugging TB cable before shutdown, then as above
Essentially they were suggesting that let's the hub 'boot up' so MB can everything connected when it starts...
 
MacBookPro M1 Max + Apple Pro Display XDR
When I close the lid the Pro Display XDR becomes black and not usable.
It seams to be a super premium, very expansive "duo" with a "beginners" operating system.
 
Last edited:
  • Like
Reactions: CyberNomad
This thread popped up in my researching of a similar issue and all things are pointing to Ventura. I have a MBP 2015 16GB mem, 1TB HD, and previously had my Samsung Odyssey G9 curved 49" connected using DisplayLink Adapter with HDMI-HDMI for port 1, DP to DP for port 2 and running the monitor in Picture in Picture so essentially I had 3 screens (MBP, 1/2 the galaxy as screen1, 1/2 galaxy as screen 2). All worked fine until ventura upgrade. It seems now Display port is being recognized by the monitor as having a connection, but the MBP doesn't see it and that 1/2 of the screen is black.

I just received my CalDigit TS4 doc and tried the same with it and outcome is the same. I have tried all the steps in this thread, including running the kill command.

I then went and pulled a work MBP 2017 (close to the same spec) other than it is not running Ventura as the upgrade has not been approved yet by the IT team. Tried both the DisplayLink doc and the Caldigit and presto I get what I used to get on my MBP 2015.

Note that I have tried on the CalDigit doing both the DP of monitor to DP of dock and no luck. I have tried DP of monitor to Thunderbolt (these are new high-end cables) and have used both Caldigit's TB 4. cable to the MBP and and Apple TB 3 cable.


I have also updated the G9 firmware to the latest version hoping it was a Samsung issue, but no luck. Also reading this thread I see others are using a variety of monitors and thus this keeps pointing back to Apple.

So my take at the moment is this has something to do with either TB or DP. The HDMI side of the monitor shows a screen without issue. Problem is the monitor only offers 1 HDMI and 2 DP, as otherwise I would just go the HDMI route, but this DP issue with Ventura is really frustrating.

UPDATE: I can further confirm it is Ventura in that the office offered push of Ventura this morning. I just completed that upgrade and low and behold I am not experiencing the same issues with the DisplayPort on this MBP. Noting as above, I had no issues with it previously. Really seems quite odd as I cannot imagine what they would have done to allow this to happen or even make it through testing.
 
Last edited:
Well after spending hours today researching and trying new cables and a bunch of other suggestions, I finally gave up on the Samsung G9. I grabbed 2 Dell U3417W monitors which gives me curvature and double screens. I plugged those first into the CalDigit TS4 and ugghh nothing, the monitors were not detecting the signals. So then I used a DisplayLink4K Pluggable which has 2 inputs (HDMI and DP) for 2 sources. So I tried HDMI on one and DP on the second. Still no signal. But then I ran the DisplayLink Manager App and PRESTO!!!! Success. They are only running at 3440x1440 with a 60 MHz refresh but they freaking work!!

So the questions I am now trying to figure out is why CalDigit is not working to push the displays signal. CalDigit hub is working to show my 2 SSD drives I have added, it powers other devices plugged in, but won't handle the screens. DisplayLink is doing something here and apparently these monitors which, granted are older - work when the Samsung would not handle the DP, though it did handle HDMI. Sucks that I can't make use of either CalDigit or the Samsung, but I at least have what I need.

Anyone have any thoughts on this - is it Ventura causing this with newer Gaming monitors and DP or is it something else?
 
Anyone got a fix for the monitor setup? I'm always losing the left/right side monitor configuration every time I hooked it up to my Mac
 
So I think I have the same issue as the OP. I've attached pictures which show the issue.

I have 2 MacBook Pros - a personal 2017 13 inch, and a work 2019 15 inch.
The work MacBook works fine on my Samsung CRG9 monitor. (5k ultra wide display)
The personal one always used to, but since upgrading to Ventura no longer does.

  • When the CRG9 is plugged in, it becomes garbled. Screenshooting the screen shows MacOS thinks it is displaying perfectly.
  • If I set the built in display to scaled (as opposed to Default) it too becomes garbled when the CRG9 is plugged in, but is fine otherwise.
  • I use a USBC to DisplayPort cable, which worked perfectly before and works on my other MacBook and windows laptops ok.
  • It works fine in safe mode. (but clearly I can't just use my computer in safe mode all the time)
  • Bootcamp windows on the same MacBook 13 works fine.

I have tried:
  • Resetting NVRAM etc.
  • Completely reinstalling MacOS, so this is a vanilla install with no additional application installed
  • Changing the display port version to 1.1 and 1.2
  • Reseating the cables
  • Setting all the possible resolutions and profiles for the external monitor
When plugged into 2017 MBP 13: (I used an extended display to the iPad otherwise I could't try changing resolutions!)
View attachment 2128298

When plugged into the 2019 MBP 15 using the same cable
View attachment 2128299
Hi, I have exactly the same issue with the Philips 499P9H, I found a fix on another forum.

Without the external display plugged in, open terminal and paste in:

sudo sleep 20 ; sudo kill -9 $(pgrep WindowServer)

Then enter.

Then type your password when requested and enter.

Plug your monitor in and bingo after a few seconds it should work.

My issue is that I don't want to do this all the time, especially as my laptop crashes and restarts after being left closed for a few hours and I need to repeat the process.

I can't believe the apple have not sorted this with an update, very disappointing. I think I am going to reinstall the previous OS.

Francis
 
  • Like
Reactions: allanz85
Hi, I have exactly the same issue with the Philips 499P9H, I found a fix on another forum.

Without the external display plugged in, open terminal and paste in:

sudo sleep 20 ; sudo kill -9 $(pgrep WindowServer)

Then enter.

Then type your password when requested and enter.

Plug your monitor in and bingo after a few seconds it should work.

My issue is that I don't want to do this all the time, especially as my laptop crashes and restarts after being left closed for a few hours and I need to repeat the process.

I can't believe the apple have not sorted this with an update, very disappointing. I think I am going to reinstall the previous OS.

Francis

Does not work for me. I have this issue with the monitors connected via TB3. Once the MBP goes into sleep mode and wakes up - it will NOT connect to the displays, whether I connect them directly or via the TB3 dock. Running the script above kills WindowServer and forces a logout, which means one has to log back in. Reconnecting the TB3 cable or the displays via USB-C has no effect. The ONLY thing that works is a reboot. I've used Apple products for a long time but this is the first time I am seeing such horrendous behavior.
 
So I think I have the same issue as the OP. I've attached pictures which show the issue.

I have 2 MacBook Pros - a personal 2017 13 inch, and a work 2019 15 inch.
The work MacBook works fine on my Samsung CRG9 monitor. (5k ultra wide display)
The personal one always used to, but since upgrading to Ventura no longer does.

  • When the CRG9 is plugged in, it becomes garbled. Screenshooting the screen shows MacOS thinks it is displaying perfectly.
  • If I set the built in display to scaled (as opposed to Default) it too becomes garbled when the CRG9 is plugged in, but is fine otherwise.
  • I use a USBC to DisplayPort cable, which worked perfectly before and works on my other MacBook and windows laptops ok.
  • It works fine in safe mode. (but clearly I can't just use my computer in safe mode all the time)
  • Bootcamp windows on the same MacBook 13 works fine.

I have tried:
  • Resetting NVRAM etc.
  • Completely reinstalling MacOS, so this is a vanilla install with no additional application installed
  • Changing the display port version to 1.1 and 1.2
  • Reseating the cables
  • Setting all the possible resolutions and profiles for the external monitor
When plugged into 2017 MBP 13: (I used an extended display to the iPad otherwise I could't try changing resolutions!)
View attachment 2128298

When plugged into the 2019 MBP 15 using the same cable
View attachment 2128299

I've just signed-up here because I'm having exactly the same issue with a MBP 2019 13"-inch and a Samsung Odyssey G9 49" monitor via Thunderbolt-to-DP Cable since upgrading to Ventura last November. Killing the WindowServer process helps as a workaround, but has to be repeated every time the Mac is restarted. I've reported the bug to Apple already a couple of times but nothing happened so far. I haven't even received a response or acknowledgement to my reports from them yet.

I'm very frustrated with Apple's recent decrease in quality & user experience.
 
Last edited:
Good news

I have spoken several times with Apple Support and they have confirmed that the macOS developers are working on solving this problem. The answer is "It is expected that it will be fixed in the next update" that means that in 13.2 it should be fixed. He has also told me that this is what is expected although he cannot confirm that it is fixed in 13.2 and he has to wait for 13.3.

But what is confirmed by Apple Support is that they are working on fixing this problem.

Also a User in the Apple forum, assures that the support of Apple Germany has also told him two days ago that they are already working to solve it.
 
Good news

I have spoken several times with Apple Support and they have confirmed that the macOS developers are working on solving this problem. The answer is "It is expected that it will be fixed in the next update" that means that in 13.2 it should be fixed. He has also told me that this is what is expected although he cannot confirm that it is fixed in 13.2 and he has to wait for 13.3.

But what is confirmed by Apple Support is that they are working on fixing this problem.

Also a User in the Apple forum, assures that the support of Apple Germany has also told him two days ago that they are already working to solve it.
Hope this also fixes the multi arrange between monitors.. It's such a mess right now for my current setup with dual Mateview...

1673392776810.png

If I put an iPad via Sidecar it gets even more crazy....
 
I can confirm my situation is the same. Panasonic TV doesn't work with 13.1 and 13.2. I did a clean install before testing it. So I will revert to Monterey for the time being.

Luckily, it's just my Macbook. That I just use for presentations. LG OLED, Dell, Sony LCD/OLED and BenQ work.

Very frustrating.
 
13.2 fixed the problem for:

Dell U4919DW 49" 32:9 Curved IPS Monitor​

All the best!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.