[go: up one dir, main page]

Mac mini (M4) — Windows move to one screen after sleep with dual display setup

Hi everyone,


I’m using a Mac mini (M4) with two monitors connected. Every time the Mac goes to sleep or when I log out and back in, all open windows move to one of the screens instead of staying where they were.


It’s pretty annoying because I have to rearrange everything each time I wake the Mac up.


Both monitors are connected directly (no dock), and I’ve already tried changing the “Displays have separate Spaces” option, but the issue remains.


Has anyone else experienced this or found a fix? Any advice would be appreciated! 🙏


Thanks in advance!


—José

Mac mini, macOS 26.0

Posted on Oct 7, 2025 5:52 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 8, 2025 8:12 AM

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.


16 replies
Question marked as Top-ranking reply

Oct 8, 2025 8:12 AM in response to ToDoApp

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.


Oct 8, 2025 8:11 AM in response to ToDoApp

<< all open windows move to one of the screens instead of staying where they were. >>


That specific symptom occurs when the second display comes ready so late, the Mac decides it is no longer available.


In that moment, all the windows on the [assumed dead] display are moved to the nearest edge of the [still working] display, so that they will not be lost forever and inaccessible.



Oct 13, 2025 12:18 PM in response to ToDoApp

On an Intel system, the System Management Controller (SMC) runs stuff like fan speeds, clock rates, sleeping, waking, and charging.


On an Apple-silicon Mac, one of the efficiency processors stays slightly awake at all times doing similar work. So the concept of "asleep" makes far less sense, since it is never fully asleep.


Consider Never sleeping your Mac.

Oct 8, 2025 9:00 AM in response to ToDoApp

<< That’s why I think this isn’t really a “display not responding” situation. >>


This happens in only a few milliseconds at system startup, or when an App goes to draw in its window.


When a more complex App that have a lot of processing to do are ready to draw their windows, the display may be ready to go, so some Apps windows will appear where you expected.


<< using a DisplayPort-to-HDMI adapter, plus another HDMI-to-DVI adapter at the end. >>


In general. "stacking" adapters is a losing proposition. You should generally convert from computer output to desired display input in at most ONE adapter.


Which display is the slow one?

if you swap adapter stacks, does the problem follow the adapters?

Does the problem follow the displays?

Oct 8, 2025 8:47 AM in response to Grant Bennet-Alder

Hello Grant!


Thanks for your reply.


I’m using two identical (and very old) Samsung monitors that only have VGA and DVI inputs. They used to work perfectly with my old MacBook Pro 2013.

Right now, one of them is connected through HDMI with a DVI adapter on the monitor side, and the other one is using a DisplayPort-to-HDMI adapter, plus another HDMI-to-DVI adapter at the end. They actually work fine overall — both monitors stay active all the time and never lose signal.


That’s why I think this isn’t really a “display not responding” situation. The weird part is that some apps (like Firefox and Outlook) get moved to the other screen after wake, while others like Photoshop stay exactly where they were.


So yeah, I totally understand what you mean about macOS querying the display, but in this case it feels like the Mac is just... getting a bit overprotective?


It seems more like a software quirk or some timing bug than an actual signal loss.


Thanks a lot for your help!


—José

Oct 8, 2025 11:02 AM in response to Grant Bennet-Alder

Hello Grant,


That actually makes a lot of sense —especially the part about the few milliseconds window during wake-up. It might explain why Photoshop (which takes longer to initialize) keeps its position, while lighter apps like Firefox and Outlook move to the other screen.


Regarding the adapters, you’re right: I’m aware that stacking two isn’t ideal. Unfortunately, with these old monitors (DVI only) and the limited outputs on the Mac mini, it’s currently my only option.


Do you know if there’s any way to make macOS wait a little longer before rearranging the windows —or to recheck displays after a short delay? Maybe a command, script, or some plist tweak that forces the system to “redetect” displays a few seconds after wake?


Thanks again for the insight —your explanation helped me understand what’s really going on here.


Thanks again!


—José

Oct 9, 2025 5:17 AM in response to Grant Bennet-Alder

Thanks, Grant!


Yeah, I’m aware of those adapters — unfortunately, here in Argentina the options are way more limited (and definitely not $10).

Still, your explanation about the timing makes total sense. Do you happen to know if there’s any way to tell macOS to “wait a bit longer” before deciding a display is gone?


It feels like adding just a short delay before the window relocation would completely solve this issue.


One more time, thanks!


—José

Oct 16, 2025 8:07 AM in response to Grant Bennet-Alder

Thanks, Grant — seriously, you seem to be the only one in this so-called "official" Apple Community who actually replies.


I have to say, I’m honestly disappointed. Is everyone else just pretending not to see the thread, or is that part of Apple’s new “seamless user experience”?


And really… so the mighty Mac — the paragon of “it just works” — can’t even handle something as simple as turning its monitors on and off properly? That’s quite the feature.


Maybe I should take it to the Genius Bar… though judging by the name, I’d probably get more caffeine than answers.

Oct 16, 2025 8:18 AM in response to ToDoApp

The folks who answer queries here are other users like you, who have decided to volunteer their time to help other users. Apple employees are generally prohibited from posting here, except for clearly-identified Apple Support Community Specialists who may post to be sure your query does not go un-answered after days.


Readers contribute when they have something to ADD to the discussion that has not already been said, or when something already said is not quite right and needs to be adjusted, or when they can elaborate on something stated, but not in enough detail. Occasionally a reader will post a summary of what has been noted to drive home the most important points.


when the answers provided are already the "best available", other readers may not have anything to add.

However, you can see how many times the post has been viewed on the 'My subscriptions" page.



Oct 16, 2025 10:32 AM in response to ToDoApp

ToDoApp wrote:

Thanks, Grant — seriously, you seem to be the only one in this so-called "official" Apple Community who actually replies.

I have to say, I’m honestly disappointed. Is everyone else just pretending not to see the thread, or is that part of Apple’s new “seamless user experience”?

@Grant Bennet-Alder is the contributor who is most familiar with how the external displays work with Apple's computers. Plus @Grant is able to provide those important technical details in a very clear & concise way. I have not seen any other current forum contributor post so such information on this forum regarding external displays. If I see a discussion regarding external displays where @Grant is not involved I will try to get his attention to assist since I am unable to provide the assistance even after reading so many of @Grant's posts (nor do I have the time necessary to assist which such a thread requires).


You are working with the best & most knowledgable contributor already regarding issues with external displays. You are in great hands here. Even Apple techs don't provide the level of assistance that @Grant does.

Oct 16, 2025 2:08 PM in response to HWTech

Thanks, I really appreciate your reply and I absolutely respect Grant’s knowledge — he’s clearly the go-to person when it comes to external display issues.


That said, I have to be honest: it doesn’t really feel like a solution if the best we can do is to keep the Mac from sleeping altogether. I mean, I’m not trying to be disrespectful or waste anyone’s time — I just find it hard to accept that something as basic as proper monitor wake control can’t be addressed more directly.


I’m still hoping there’s a simpler, more elegant answer out there… because it really seems like the kind of thing macOS should handle without all these workarounds.

Mac mini (M4) — Windows move to one screen after sleep with dual display setup

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