MacBook Pro M4 Pro HDMI External Display Problems

I have an external display (Acer CBA272) which works perfectly with an older MacBook Pro M1 and used to work perfectly with my newer MacBook Pro with an M4 Pro chip (all fully updated on the OS front).


Suddenly, a few months ago, the MacBook Pro M4 Pro stopped detecting the external monitor when plugged in via HDMI directly and via HDMI using a USB-C adaptor (the external display does not have a Thunderbolt connection).


Strangest of all though is that, when connected, the monitor recognises that it is plugged into the computer (just not the other way around) and there is also a work around that will allow the MacBook Pro to detect the monitor. If I connect an iPad as an external display first, then close the lid on the MacBook Pro M4 Pro, I will get a signal to the external monitor and it can be set up as the main display. I can then disconnect the iPad and use the external monitor as normal. Clearly though, this is an annoying work around and only works when I have the iPad around. But it does show that there is no problem with the cable or the monitor, just the process of macOS recognising it.


Apple Support have checked the device and they have confirmed that there is no hardware issue with the MacBook Pro M4 Pro. I have used multiple HDMI cables including the Apple recommended Ultra HD Belkin cable, plus the MacBook Pro M4 Pro works fine over any HDMI cable to my television.


My sense is, therefore, that something is wrong at a software level and, although I can't find exactly similar views online, it looks like others have had problems with Sonoma, MacBook Pro M4 Pro models and external displays. It feels terrible that such an expensive Pro-level device should require such an annoying workaround for what should be a very straightforward task. I'm looking, therefore, to see if others are facing a similar problem and whether you might have found any solutions.

Posted on Aug 21, 2025 3:57 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 25, 2025 1:02 PM

if you have met the other recommendations such as cable lengths:

For MacOS 12 Monetary nd some later versions, some users got relief by deleting two preferences files, then Restarting:


Library/Preferences/com.apple.windowserver

~/Library/Preferences/com.apple.windowserver.<UUID>.plist -OR-

~/Library/Preferences/ByHost/com.apple.windowserver.<UUID>.plist


-- where [~] tilde is an active abbreviation for "current user"

-- and <UUID> is a string of hexadecimal numbers unique to your system, grouped as 8-4-4-4-8 hexadecimal digits


Restart REQUIRED after these deletions.

Similar questions

11 replies
Question marked as Top-ranking reply

Aug 25, 2025 1:02 PM in response to JC_JC

if you have met the other recommendations such as cable lengths:

For MacOS 12 Monetary nd some later versions, some users got relief by deleting two preferences files, then Restarting:


Library/Preferences/com.apple.windowserver

~/Library/Preferences/com.apple.windowserver.<UUID>.plist -OR-

~/Library/Preferences/ByHost/com.apple.windowserver.<UUID>.plist


-- where [~] tilde is an active abbreviation for "current user"

-- and <UUID> is a string of hexadecimal numbers unique to your system, grouped as 8-4-4-4-8 hexadecimal digits


Restart REQUIRED after these deletions.

Sep 9, 2025 4:20 AM in response to hta48

I would recommend trying Grant Bennet-Alder's advice from above, which has worked for me!


Please note that you must delete the relevant .plist files in both the Library File on Macintosh HD and in your User Library (which you may need to reveal in the Finder by going to "Show View Options"). The ~/Library/Preferences/ByHost/com.apple.windowserver.<UUID>.plist file was the culprit for me.


Grant Bennet-Alder

Aug 25, 2025 01:02 PM in response to JC_JC

if you have met the other recommendations such as cable lengths:

For MacOS 12 Monetary nd some later versions, some users got relief by deleting two preferences files, then Restarting:


Library/Preferences/com.apple.windowserver

~/Library/Preferences/com.apple.windowserver.<UUID>.plist -OR-

~/Library/Preferences/ByHost/com.apple.windowserver.<UUID>.plist


-- where [~] tilde is an active abbreviation for "current user"

-- and <UUID> is a string of hexadecimal numbers unique to your system, grouped as 8-4-4-4-8 hexadecimal digits


Restart REQUIRED after these deletions.

Aug 21, 2025 7:16 AM in response to JC_JC

The Mac does not rely on Windows-like side-loaded "Drivers" which are actually packages of resolutions and settings for a specific display. Instead, it goes straight to the immutable source -- it asks the display itself.


To get a Mac display to become active, you need the Mac to query the display, and the display to answer with its name and capabilities. Otherwise, the display will not be shown as present, and no data will be sent to the display. "No signal detected" is generated by the DISPLAY, not by the Mac.

 

This query is only sent at certain times:

• at startup

• at wake from sleep — so momentarily sleeping and waking your Mac may work

• at insertion of the Mac-end of the display-cable, provided everything on that cable is ready-to-go

• hold the Option key while you click on the (Detect Display) button that will appear in Displays preferences (from another display)


so try doing some of those things and see if the display comes alive.


Modern Displays with multiple ports are sometimes busy scanning the other ports, looking for an input, and miss the query from the Mac. They need to pay attention to the port you are actually using, or they will miss the query.


Some displays have On-Screen Display settings that can be used to tell the display a computer is attached on a certain port, or a certain port should be highest priority. Changing those may make your display more responsive.


Some displays include their own private "sleep" settings for the display alone. This can allow the display to enter its own sleep mode, on top of the Mac's not sending it data. A display that is sleeping on its own can generally not respond to the Mac's query, and will stay dark.


Aug 21, 2025 9:05 AM in response to JC_JC

HDMI cables you want for HDMI-only Displays (higher resolutions than 720p TV sets) are marked as Certified with an anti-counterfeiting tag and are labeled:


"PREMIUM High Speed HDMI cable" or that + "with Ethernet" (up to 4K at 30Hz) --OR--

ULTRA High Speed HDMI cable" or that + "48G" (supports higher resolutions and backward-compatible)


Cables with No Certification tags are good for your standard 720p TV set, and not much more.


HDMI was invented for HD TV sets. it works great at its original resolution of 720i or 720p. At higher resolutions, it quickly develops issues that are complex to solve, and the cables and adapters required to solve are NOT intuitive.


Remember that using a random different HDMI cable is a check against cables that are BROKEN. It does not necessarily correct for cables arhat are not high enough specs.

Aug 21, 2025 8:15 AM in response to Grant Bennet-Alder

Thanks so much for this reply and detailed explanation, which is really helpful and adds to my understanding of the situation.


Unfortunately, I've tried each of these things (startup, waking from sleep, insertion of the cable, and holding the Option key while clicking Detect Display in System Settings) and none of them will get the display and Mac to speak to each other. I've also switched off the "auto-detect input" on the display to ensure that it's only scanning the HDMI port. I'm pretty sure that there are no configurable sleep settings on the display.


The only way that I can get the M4 Pro MacBook Pro to see the Acer CBA272 is by first screen sharing to an old iPad Pro, then closing the lid on my MacBook Pro. It will then recognise the Acer CBA272 as a connected display alongside the iPad. If I then stop sharing to the iPad, the Acer CBA272 will continue to function as normal, until it is disconnected. If it is disconnected, I have to go through the process again.


The thing that is confusing me is that the Acer CBA272 display works every time with an old M1 MacBook Pro running the same operating system. It's just the new M4 Pro MacBook Pro that is having problems and, as far as I can tell, only with this Acer CBA272 display. It worked fine with an Apple Display that I tried in the Apple Store and also is recognised by my television over HDMI.


Anyway thanks for your help. I really appreciate it. If you or anybody else have any other suggestions, then they would be gratefully received!

Aug 21, 2025 11:57 AM in response to Grant Bennet-Alder

Thanks. Again, this is all very useful. Unfortunately though, I have been consistently using two HDMI cables labelled with "PREMIUM High Speed HDMI cable with Ethernet" and have also now purchased a Belkin “ULTRA High Speed HDMI cable" from the Apple Store to try. Unfortunately, the HDMI cable upgrade has made no difference to my problem. Thanks again though for the suggestions!

Aug 25, 2025 11:53 AM in response to hta48

Great to have your input! And really useful to know that it's happening with other brands of external monitor too (Acer, LG etc.). Would be great to hear from others who having this problem too. Many thanks! Let's hope that we can find a solution or that Apple will provide some sort of fix at some point. I feel pretty certain that it is a problem at a software level, rather than something with the monitor (which works fine with other devices) or the cables.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

MacBook Pro M4 Pro HDMI External Display Problems

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.