Mac

Mission Control or Spaces broken after macOS 27

After macOS 27, Mission Control stalls, windows land on the wrong Space, or a detected external display goes black. Collect evidence, try user-reported workarounds, file feedback.

Start here: Confirm detection

Displays settings and `system_profiler SPDisplaysDataType`.

Problem summary

I'm here because, since macOS 27, Mission Control or Exposé stalls, a window jumps to the wrong Space, switching between full-screen apps lags, or an external display goes black after I move a window or desktop to it — yet the display is still detected. Many users report the same thing on 27.0 and 27.0.1, and some report it on the 27.2 betas. Apple has not named a fix, and its 27.0.1 notes say only that the update provides bug fixes. This page confirms you have this problem and not a display that has dropped out, records the evidence Apple needs, walks through the workarounds users report, and shows how to file feedback. None of the workarounds is an Apple-confirmed fix.

Operator snapshotEvidence first

First proof

Run `system_profiler SPDisplaysDataType` while the screen is black.

Screen to open

sw_vers

Expected signal

The black display is listed with `Online: Yes`.

Stop boundary

Don't erase or reinstall macOS for this.

Layer path

1Mission Control, Spaces, full-screen apps and Stage Manager all sit above the display layer. The Mac can detect and drive a monitor correctly while the window system draws the wrong Space on it, draws nothing, or stalls while switching. That is why this page starts by confirming the display is still detected: a missing display and a black but detected display need different fixes.

2After macOS 27.0, many users reported stalls when opening Mission Control, windows opening on the wrong Space, laggy full-screen switching and external displays going black after moving a window or desktop between displays. Reports continue on 27.0.1 and on 27.2 betas. Apple has not published a cause or a fix; its 27.0.1 notes say only that the update provides bug fixes.

3Apple's 27.2 beta 4 notes list a separate known issue (188643179): display settings might not be restored and the arrangement might change with an external display connected. It can move windows to unexpected places, but it is beta-only and does not prove that every report has one cause. The useful work is evidence: exact build, display topology, Stage Manager and Spaces settings, and whether a fresh user account reproduces it.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Confirm detection

Check: Displays settings and `the "Check the display is still detected" command below`.

Expected result: Black display listed and `Online: Yes`.

If not: If missing, use the display-not-detected runbook.

Record the setup

Check: `the "Record the macOS build" command below`, display layout, Stage Manager and Spaces settings.

Expected result: All written down.

If not: Update 27.0 to 27.0.1 if behind.

Bring back the black display

Check: Add a desktop on it in Mission Control, switch to it, delete it.

Expected result: Display draws again (user-reported).

If not: Log out and back in, or restart.

Safe stop: Don't erase or reinstall macOS for this.

Check arrangement

Check: Displays → Arrange and main display.

Expected result: Layout matches the desk.

If not: Fix it and note it in feedback.

Test a new user

Check: Create a Standard test account and reproduce.

Expected result: Same result shows a system-level problem.

If not: If it is clean, check your own utilities and login items.

Test separate Spaces off

Check: Turn off "Displays have separate Spaces" and log out.

Expected result: You see whether the symptom changes.

If not: Turn it back on if nothing changes or you need Stage Manager.

Safe stop: Don't install a beta on a production Mac.

File feedback

Check: Feedback Assistant or apple.com/feedback/macos.html with the evidence.

Expected result: Report filed with build, layout, settings and steps.

If not: Keep the evidence files in case Apple asks.

Did this solve your problem?

Your answer helps us improve this page.

No account or personal details. We store the page, answer, optional reason and day with a 90-day retention period. A random reference in this browser prevents repeat votes. Feedback privacy

Decision tree

If: The display is missing from Displays settings and `system_profiler`.

Then: Display detection problem, not Mission Control.

Action: Follow the external display not detected runbook.

If: The display is detected but went black after moving a window or desktop to it.

Then: Window and Space drawing fault reported by many users on macOS 27.

Action: Add, switch to and delete a desktop on that display; if that fails, log out or restart.

Safe stop: Don't erase the Mac or reinstall macOS for this.

If: Mission Control and full-screen switching lag, but nothing goes black.

Then: Same reported macOS 27 behaviour; background indexing after the upgrade can add to it.

Action: Check the whole Mac is not slow first. As reversible tests, the OS X Daily author reported Reduce Transparency helped; note the result in feedback.

If: Windows open on the wrong display or the layout changed.

Then: Arrangement or main display changed; on 27.2 beta, Apple's known issue 188643179.

Action: Fix the layout in Displays → Arrange and set the main display.

Safe stop: Don't install a beta on a production Mac to chase this.

If: It only happens in your own account, not a new test user.

Then: Something in your account is involved.

Action: Quit window-management utilities and login items one at a time.

If: It happens in a fresh account with the same displays.

Then: System-level behaviour.

Action: Collect the evidence and file feedback with Apple.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
External display goes black after moving a window to it.	Display still in Displays settings; `Online: Yes`; pointer moves onto it.	Spaces and window drawing.	Add and delete a desktop on it, then log out or restart.
Mission Control opens slowly or stutters.	`sw_vers`; Stage Manager setting; WindowServer log saved right after it happens.	Window management on macOS 27.	Try reversible display settings; file feedback.
Windows open on the wrong Space or display.	Displays → Arrange layout; main display; Spaces setting.	Arrangement or Spaces assignment.	Fix the arrangement; note it in feedback.
Mac freezes or logs out when opening Mission Control.	WindowServer or Dock reports in DiagnosticReports.	WindowServer crash or hang.	Back up, then attach the reports to feedback.

Reference

Commands and settings paths

Record the macOS build

sw_vers

Where: Terminal on the Mac.

Expected: Prints ProductName, ProductVersion and BuildVersion (27.0.1 and 26A434 on current stable).

Failure means: 27.0 and 26A428 mean the Mac is one update behind.

Safe next step: Install 27.0.1 from Software Update and keep the output for feedback.

Check the display is still detected

system_profiler SPDisplaysDataType

Where: Terminal on the Mac, while the display is black.

Expected: Each connected display is listed; one shows `Main Display: Yes`, and each external shows `Online: Yes`.

Failure means: A display missing from the list is a detection problem.

Safe next step: Use the display-not-detected runbook.

Read the Stage Manager setting

defaults read com.apple.WindowManager GloballyEnabled

Where: Terminal on the Mac. Read-only.

Expected: Prints 0 when Stage Manager is off.

Failure means: An error saying the key does not exist gives no answer here.

Safe next step: Check Stage Manager in Control Center instead.

Save recent WindowServer log lines

/usr/bin/log show --last 15m --predicate 'process == "WindowServer"' --style compact > ~/Desktop/windowserver-log.txt

Where: Terminal on the Mac, right after the problem happens. The full path avoids zsh's built-in `log` command.

Expected: A text file of time-stamped WindowServer lines on the Desktop.

Failure means: WindowServer logs errors during normal use; one error line does not prove the cause.

Safe next step: Attach the file to your feedback report.

Look for WindowServer or Dock crash reports

ls /Library/Logs/DiagnosticReports ~/Library/Logs/DiagnosticReports | grep -i -E 'WindowServer|Dock'

Where: Terminal on the Mac.

Expected: No output means no WindowServer or Dock reports were saved.

Failure means: Listed files mean a crash or hang was recorded.

Safe next step: Attach the matching files to feedback.

Hardware boundary

Hardware and platform boundary

Change only when

No purchase fixes this while the display is still detected — reports span many Apple silicon Macs and monitors.
Buy a cable or dock only after the display-not-detected runbook proves one has failed.

Evidence that matters

Your chip's external display limit, if you are adding another screen.
A direct connection test before blaming a dock.

Evidence that does not matter

A newer monitor or faster dock — the display already works; the reported fault is in window management.

Avoid

Buying hardware to fix a black Space on a detected display.
Third-party utilities sold as a Mission Control fix.
Installing macOS betas on a Mac you rely on.

Last reviewed

2026-10-17 · Reviewed by HomeTechOps. Written 2026-10-17 against macOS 27.0.1 (26A434). Apple's 27.0.1 notes and 27.2 beta 4 release notes were read that day; neither names a Mission Control fix, and the beta notes list known issue 188643179 for display arrangement. The symptoms and workarounds come from user reports (Apple Community, MacRumors, r/MacOS, OS X Daily, The Mac Observer) and are labelled as such. The `sw_vers`, `system_profiler`, `defaults read`, `log show` and DiagnosticReports commands were run on a macOS 27.0.1 Mac. No fix is claimed.

Sources/assumptions

Assumes an Apple silicon Mac on macOS 27. Current stable is 27.0.1 (26A434, 28 September 2026); 27.0 was 26A428 (14 September 2026). There is no 27.1 for Macs; 27.2 is in beta (beta 4, 26B5112a, 13 October 2026).
Apple's 27.0.1 notes say only "This update provides bug fixes for your Mac" and do not mention Mission Control or Spaces (read 2026-10-17).
The symptom reports come from users: an Apple Community thread started 15 September 2026 that showed about 489 "Me too" on 17 October 2026, a MacRumors thread, r/MacOS, OS X Daily (30 September 2026) and The Mac Observer. They report it on 27.0, 27.0.1 and 27.2 betas. Apple has not confirmed a cause or a fix.
Apple's 27.2 beta 4 release notes list known issue 188643179 (display settings might not be restored; arrangement might change). That is a separate, beta-only issue, not proof that every symptom here has one cause.
The add-and-delete-desktop, log out or restart, and turn off separate Spaces steps are user-reported workarounds. The commands were run on a macOS 27.0.1 Mac on 2026-10-17.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Avoid unsafe electrical or data-loss steps.
4. Stop when the evidence says the risk moved.

FAQ

Does macOS 27.0.1 fix Mission Control?

Apple has not said so. Its 27.0.1 notes say only that the update provides bug fixes. Users on Apple Community, MacRumors and OS X Daily report that the stalls and black screens continue on 27.0.1, and some report them on 27.2 betas. Install 27.0.1 because it is the current stable build, but don't expect it to fix this.

My external display went black after I moved a window to it. Is the monitor broken?

Probably not, if it is still listed in System Settings → Displays and shows `Online: Yes` in `system_profiler SPDisplaysDataType`. Users report the display comes back after adding a desktop on it in Mission Control, switching to it, then deleting it, or after logging out or restarting. If the display is missing from Displays settings, follow the display not detected runbook.

Should I turn off "Displays have separate Spaces"?

Only as a test you can undo. It takes effect after you log out. Apple says that with it off the Dock appears only on the main display, and Stage Manager and Split View on other displays need it on. If it makes no difference, turn it back on.

Is this the 27.2 beta display arrangement bug?

Not necessarily. Apple's 27.2 beta 4 notes list known issue 188643179: with an external display connected, display settings might not be restored and the arrangement might change. The Mission Control reports started on 27.0, before that beta. If you are on stable 27.0.1, don't install a beta to test this.

How do I report this to Apple?

Use Feedback Assistant, which is built into macOS and collects diagnostics with your permission, or Apple's macOS feedback form. Include `sw_vers`, your display layout, the Stage Manager and Spaces settings, whether a new test user shows the problem, and the exact steps. Apple asks people to report issues even when others have reported them already.

Get the deal & firmware alerts

Home Stack Field Notes: NAS deals, firmware changes worth acting on, restore-test reminders, and new decision guides — plus the capacity & backup sizing cheatsheets from our calculators. Unsubscribe anytime.

Subscribe on beehiiv