Skip to content

Allow the Windows VM window to move to secondary/external displays (and add multi-monitor full screen like Parallels) #145

Open

Description

@casthuntsville1

Description

I can’t move a Windows 11 VM window off the main display in Window mode. When I drag the window toward a secondary display, it stops at the edge of the main display and won’t cross over. That means I can only use the VM on my main screen. I’d like to be able to drag the VM window to any connected display, and also to run full screen on a chosen display or on all displays.

Environment
Mac: MacBook Pro 16-inch, Apple M5 Max, 64 GB memory
macOS (host): macOS 27.2.1 (Golden Gate)
VMPal version: 0.118 (build 118)
Guest: Windows 11 (ARM64), running on HVPal (VMPal’s own engine on Apple’s Hypervisor framework)
Displays (3 total):
Built-in Liquid Retina XDR display: main display, ProMotion, Apple XDR Display (P3-1600 nits) preset
Sceptre E24 (1): external, to the right of the built-in display
Sceptre E24 (2): external, to the left of the built-in display
Mission Control > “Displays have separate Spaces”: On
Other Mission Control settings: “Automatically rearrange Spaces based on most recent use” On; “When switching to an application, switch to a Space with open windows for the application” On

Steps to reproduce
Connect one or more external displays to the Mac.
Start the Windows 11 VM in Window mode (not full screen).
Grab the VM window by its title bar and drag it toward the secondary display.

Expected behavior

The window moves across the display boundary and can be placed fully on the secondary display, the same as any native macOS window. Once it’s there:

The guest display output (dynamic resolution) should adjust to the new display’s size and backing scale factor. For example, switch from 2× Retina to the external display’s 1× or 2× scale, and request a new guest resolution if the display has resize-with-window enabled.
Full screen (green button / View > Enter Full Screen) should open on the display the window is currently on, not jump back to the main display.

Actual behavior

The window stops at the edge of the main display and won’t move past it. It acts as if its frame is being clamped to the main screen’s visibleFrame, which looks like a constrainFrameRect(_:to:) override or a frame-clamping rule in the VM window controller. It could also be a minimum or fixed content size that’s larger than the target screen. Releasing the mouse leaves the window snapped against the edge of the main display. Other macOS apps’ windows move between the same displays normally, so the display arrangement itself works.

Feature request (beyond the bug)

Parallels Desktop is the reference implementation here, and it’s a big reason people stay with it:

Free window movement across displays. In Parallels Window mode, you can drag the VM window to any display. Then you click the Full Screen icon and the VM goes full screen on that display only, while macOS keeps the other displays. VMPal should allow at least this much.
“Use All Displays in Full Screen.” Parallels has an option, under the View menu and in the VM’s Options > Full Screen settings, that extends the Windows guest across all connected displays when you enter full screen. Each Mac display becomes a separate monitor in the guest, and the guest’s monitor arrangement matches the macOS display arrangement from System Settings > Displays. Parallels also has a companion option, “Show and hide spaces on all displays simultaneously,” so switching into or out of the VM switches every display at once.
Per-display selection (improves on Parallels). Parallels only lets you use one display or all of them. Its users have asked for years for an option like “Use selected displays in full screen.” For example, Windows full screen on two external monitors while the MacBook’s built-in screen stays on macOS. A checklist of displays in VMPal’s display settings, or a prompt when entering full screen, would put VMPal ahead of Parallels on this.
Technical notes / suggestions
The guest needs a virtual display (or multiple virtual display heads, for the multi-monitor case) whose resolution and DPI follow the host NSScreen the window is on. Listen for NSWindow.didChangeScreenNotification and didChangeBackingPropertiesNotification and re-negotiate the guest resolution and scale when they fire.
For multi-monitor full screen, attach one guest display per selected NSScreen, map their positions from NSScreen.frame to keep the arrangement, and create one full-screen window (and Space) per display.
Handle both settings of “Displays have separate Spaces.” With it on, macOS won’t let a window span displays, so a window that’s more than half on another display should be handed off to that display cleanly instead of being clamped.
Handle hot-plugging: when a display is disconnected or reconnected, move the VM window to a remaining display and reconfigure the guest displays without needing a VM restart.
Why this matters

Running Excel and other Office apps in a Windows VM on a large external monitor, while keeping macOS apps on the laptop screen, is a core use case for Mac virtualization. Right now VMPal limits the VM to the main display, which is the biggest gap I’ve found compared with Parallels.

Multi-monitor support is a basic expectation for desktop virtualization on the Mac, and right now it’s the biggest gap between VMPal and Parallels.

My workflow: I use the Windows VM mostly for Microsoft Excel (including large Data Model / Power Pivot workbooks) and for building Windows installers for apps I develop on the Mac. Those are wide, data-heavy windows. My setup is a 16-inch MacBook Pro with two 24-inch external monitors, one on each side. I want Windows on one of the external monitors and macOS apps on the built-in display and the other monitor. Since the VM is stuck on the built-in display, I can’t do that. I’m left with the smallest screen, while two larger monitors sit unused for the work I most need them for.

Why it matters for VMPal generally:

Basic macOS window behavior. Users expect every window to move freely between displays. When the VM window stops at the screen edge, it feels like a bug rather than a missing feature.
Common setup. Most people who run a Windows VM on a Mac for work have at least one external monitor, and the VM usually goes there so it can run side by side with macOS apps.
Parallels has had it for years. Parallels lets you drag the VM to any display, go full screen on a chosen display, or extend Windows across all displays with “Use All Displays in Full Screen.” Users comparing the two will see this gap right away, and it could keep them on Parallels.
An opening to do better than Parallels. Parallels still only offers one display or all of them in full screen. Its users have asked for years to pick specific monitors, for example Windows on the externals and macOS on the laptop screen. If VMPal adds per-display selection, it beats Parallels on this.
Work and productivity users. Excel, Visual Studio, and other line-of-business Windows apps are why many people buy a VM license. Those users depend most on screen space, and they’re the most likely to pay for a perpetual license.

Activity

  1. casthuntsville1 commented on Nov 20, 2026

    @casthuntsville1
    Author

    Here is a video showing the issue

    VMPal-Bug-Windows-VM-Window-Stuck-at-Display-Edge.mp4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions