Plenty of Windows machines run their whole lives without a monitor. A server in a rack, a mini PC tucked behind a digital sign, a build machine in a closet, a tower that lost its screen to another desk years ago. They all work fine, right up until you try to remote into one and get nothing.
That nothing is not a HopToDesk limitation, and it is not a network problem. When Windows detects no display output at all, it simply stops producing a desktop image. There is no screen to capture, so there is nothing any remote desktop tool can show you. For years the standard fix was a small HDMI dummy plug that tricks the machine into thinking a monitor is attached.
HopToDesk now fixes this in software. The client includes our own virtual display driver, called HtdVDD, and it makes a headless machine behave exactly like one with a real screen.
What happens when you connect
You do not have to set up anything in advance. When you connect to a HopToDesk host that has no active display, the client notices and plugs in a virtual monitor on the spot. Windows builds a normal desktop on it, HopToDesk captures it, and your session opens like any other. You get a real resolution, a real cursor, and full control.
When the last remote session ends, the virtual monitor is unplugged again and the machine goes back to exactly the state it was in before. Nothing is left running, and nothing changes for a machine that already has a screen. If a display is present, the driver never activates at all.
Built by us, signed by us
Virtual display drivers are not new, but the way they usually reach your machine is a problem. Most remote tools either bundle a third-party driver from another company or ask you to install one yourself, and each of those adds someone else's software and someone else's update schedule to a machine you have to trust.
HtdVDD is our own driver. We build it, we sign it with our own publisher certificate, and it ships inside the regular HopToDesk client. It installs on machines with Secure Boot enabled, with no test mode and no security settings to loosen.
It is also a user-mode driver. That is a technical distinction with a practical meaning: it runs in the same protected way as a normal application, not inside the core of the operating system. A fault in a user-mode driver ends the driver, not the machine. It cannot blue-screen the server it runs on.
Where this helps
Some places this changes the day-to-day:
- Rack servers and lab machines that never had monitors, where a session used to require a walk to the server room with a screen under your arm.
- Virtual machines, which have no physical port to put a dummy plug into. VMs whose console output is missing or awkward now get a full desktop over HopToDesk.
- Digital signage and kiosk controllers, where the machine drives a display that is not a normal desktop monitor.
- The unattended fleet. Combined with unattended access, a headless machine becomes reachable at any time, from anywhere, with nobody on site.
Requirements and the fallback
The virtual display driver needs Windows 10 version 2004 or newer, which covers current Windows 10, all of Windows 11, and recent Windows Server releases.
For machines older than that, the classic answer still works: a dummy plug that costs about ten dollars. One tip from our support desk if you go that route: buy one that reports 1080p or better. Some very cheap plugs only claim a small 1024x768 screen, and a desktop that tiny is barely usable over a remote session.
Try it
There is nothing to enable. Update HopToDesk on the headless machine to the current version, make sure it is set up for unattended access, and connect. The screen that was never there will be waiting for you.
Download the latest client at www.hoptodesk.com/download, and manage all of your unattended machines from the HopToDesk Dashboard.
Fast, secure remote desktop for individuals and IT teams, with a dashboard to manage every device in one place.