Video: Remove Displays From Desktop - Max Performance

Last updated 6 August 2026

Steps

An output that Windows owns is an output Windows can interrupt. Notifications, update prompts, the odd dialog that opens on the wrong screen — all of them can land on a projector mid-show. And driving the desktop across every output costs performance that the playback engine would rather have.

Removing the outputs from the Windows desktop hands them to Backstage exclusively. It is the recommended final state for a production server.

Before you start

  • Do this last. Settle EDID emulation, output format and any mosaic grids first — see the callout below for why.

  • Keep one display on the desktop for operating the machine locally, or be certain remote access is working.

  • Sign in as Admin. The remove and return buttons are hidden for everyone else.

1. Open the Desktop page

In the Hub, select the server and click System Management.

Go to Configure → GPU and choose the Desktop tab.

2. Check what is currently on the desktop

Outputs on the Windows desktop lists every output with its Resolution and whether it is On desktop. On an unconfigured server they all are.

A mosaic grid appears as a single entry, not as its members. Removing or returning it acts on the whole grid — you cannot take half a mosaic off the desktop, and there is no reason to want to.

3. Remove them

Use the per-row action to remove one output, or Remove all from desktop to clear them in one go. Return all to desktop is the way back.

A removed output disappears from Windows entirely — and from the NVIDIA Control Panel too. Display Settings will not list it, and neither will the driver's own tool. That is expected, not a fault: Backstage still renders to it. Do not go looking for the output in Windows to confirm it works — confirm it in Backstage.

Removed outputs are locked against EDID and mosaic changes. The EDID page says so directly: outputs removed from the desktop, or part of a mosaic, cannot be reassigned until they are returned. This is why the order matters — EDID first, mosaic second, remove from desktop last. Getting it backwards means undoing this step to change anything else.

4. If the change does not take

Removing or returning a display can get stuck inside the GPU driver. The page recognises this itself: when the result is anything other than a clean success, it reveals a banner saying a server restart often clears that state, with a Restart server button beside it.

If that banner appears, take it at face value rather than retrying the button — the driver state is what is blocking the change.

Done when

The outputs you removed read as no longer on the desktop, and Windows shows a desktop spanning only the displays you deliberately left behind. The projectors and walls are now driven exclusively by Backstage, with no operating system surface on them at all.

What this depends on

Depends on

Why

EDID and mosaic already settled

Removed outputs are locked against both.

Remote access or a remaining desktop display

You still need a way to operate the machine.

A restart, sometimes

The GPU driver can wedge mid-change; a restart clears it.

Admin role

The remove and return controls are admin-only.