The Problem Nobody Warns You About
An exhibition PC is installed in a rack or behind a panel with no monitor attached. Everything works — until you connect remotely to fix something and find one of these:
- The remote session opens at 640×480 or some other useless resolution
- The screen is black with a working mouse cursor
- The desktop is there but the projector output has stopped since the PC rebooted
- Windows has rearranged all your windows onto a display that no longer exists
The cause is the same in every case: without a display connected, the GPU has no EDID, so Windows has no display to render to. It either falls back to a basic mode or renders nothing at all. Remote desktop software then either mirrors that useless mode or has nothing to mirror.
This is not a fault. It is how PCs work. But it is a recurring headache in exhibition and signage installations where the media PC legitimately has no monitor of its own.
When You Actually Have This Problem
It is worth being precise, because half of "headless" cases are not really headless:
| Situation | Headless? |
|---|---|
| PC drives a projector that is switched off at night | Yes — the EDID disappears when the projector powers down |
| PC drives a display through a matrix or extender that drops the signal | Yes — same effect |
| PC drives a display that stays powered | No — the display provides EDID |
| PC has genuinely nothing plugged into the GPU | Yes |
The second row is the one people miss. A media PC connected through an HDBaseT extender or a matrix can lose its EDID when the far end powers off, which is why a system works during the day and comes up wrong the next morning. The PC is effectively headless overnight.
Three Solutions
1. HDMI/DisplayPort dummy plug (EDID emulator)
A small hardware dongle that plugs into the GPU and presents a fake EDID. The GPU believes a monitor is attached and renders normally.
Advantages: works before Windows loads, survives driver updates, requires no software, and cannot be broken by a Windows update. It is active at the BIOS level, which matters if you ever need to see POST or change firmware settings remotely.
Disadvantages: costs a few dollars per machine, occupies a physical port, and the resolution it advertises is fixed by the dongle. Cheap ones advertise a resolution you may not want.
This is the right default for a permanent installation. Hardware that cannot be un-configured is worth a lot in a system nobody will maintain.
2. Virtual display driver (software)
A driver that creates a display device in software with no hardware attached. Virtual Display Driver and Parsec's VDD are the common open-source options.
Advantages: free, no hardware, and you can define custom resolutions — including resolutions no real monitor offers, which is useful for unusual video-wall geometries.
Disadvantages: it is a driver, so it loads after Windows boots (no BIOS/POST visibility), and a Windows update can break or unsign it. Some builds also require disabling driver signature enforcement, which is not something you want on an unattended production machine.
Note on searching for these: most of the discussion online is about game streaming (Sunshine, Moonlight), not AV. The software is the same; the advice about latency and HDR mostly is not relevant to signage.
3. Keep a display permanently powered
Sometimes the simplest answer: leave a small monitor connected in the rack, or configure the projector/display to stay powered with the input muted rather than fully off.
Advantages: no extra parts, no software.
Disadvantages: power consumption, and on projectors it consumes lamp/laser life. Muting the shutter is better than leaving an image on — see Panasonic's OSH shutter command.
Which to Choose
| Requirement | Use |
|---|---|
| Permanent unattended install | Dummy plug |
| Need BIOS/POST access remotely | Dummy plug (drivers load too late) |
| Need a non-standard resolution | Virtual driver |
| Video wall with unusual geometry | Virtual driver |
| Temporary or lab machine | Either |
| Machine that already drives a permanently-on display | Nothing needed |
A practical combination for exhibition work: a dummy plug for reliability, plus the display or projector on the real output. The dummy plug guarantees a desktop exists even when the projector is off overnight, and your content still goes to the projector during the day.
The Remote Desktop Angle
headless display adapter anydesk is one of the most common searches on this topic, and for good reason: remote desktop tools are where the symptom shows up.
Different tools behave differently:
- RDP creates its own virtual session and generally works headless — but that session is not the console session, so it will not show you what the projector is showing. For AV work this is usually wrong: you need to see the actual output.
- VNC, AnyDesk, TeamViewer and similar mirror the physical console, which is what you want — and which is exactly what fails without a display.
So the rule for AV: use a console-mirroring tool (VNC/AnyDesk), and give the machine a display to render to. Using RDP to dodge the problem means you are looking at a different desktop than the one on the wall.
There is a related quirk worth knowing: VNC can be blocked when spanning multiple displays in NVIDIA Surround configurations, and some tools need a mouse present to show a cursor at all.
Setup Checklist
- Dummy plug fitted on each headless machine, or a virtual driver installed and confirmed to survive a reboot
- Resolution set explicitly to the output resolution you actually need, not left to auto
- Verified after a full power cycle — not just after a reboot. See the commissioning checklist
- Verified with the projector powered off, since that is the state it will be in overnight
- Remote access tested in that state — connect remotely with the projector off and confirm you get a usable desktop
- Windows display scaling checked — a fake EDID advertising a small display can trigger scaling that makes your content the wrong size
The fourth and fifth items are the ones that catch people. Testing with the projector on proves nothing, because the projector was providing the EDID.
With SoftControl
This is a Windows configuration issue rather than a control-protocol one, but it intersects with control work in a specific way: if your control system powers displays off at night, it is also removing the EDID from every PC connected to them.
SoftControl runs the media PCs and the displays from one interface, so the closing sequence that powers down projectors is the same sequence that creates the headless condition. Worth designing for deliberately: fit dummy plugs, or use display mute/shutter instead of full power-off where the projector supports it.
See also Wake-on-LAN not working for the related overnight-power problem, and the commissioning checklist for the full unattended-operation list.