To “force windowed mode” means making a game run inside a desktop window even though the game itself offers no windowed option — by intercepting or redirecting the calls it uses to take over the screen. It is the standard rescue for fullscreen-only classics, and there is no single technique: launch flags, API hooking, API wrapping and virtual machines each attack a different layer, and the right choice depends on the game’s era. DxWnd, the tool this site documents, is the hooking approach, and usually the deepest one for DirectX-era titles.
Why Some Games Have No Windowed Option
Exclusive fullscreen was the default assumption of 1990s and early-2000s game development. A game set the display mode itself, drew straight to the screen, and treated windowed mode as an afterthought or an impossibility — menus and cutscenes were hard-coded to resolutions like 640×480 or 800×600, and the engine often had no code path for “share the screen with a desktop”. Some later games added a windowed toggle; many never did. When a game lacks the option, nothing inside the game can be persuaded to provide it — the window has to be imposed from outside.
Method 1: The Game’s Own Switches
The cheapest solution is the one the developers left behind. Many games accept launch arguments such as -windowed, -window or -w, hide a setting in a configuration file, or respond to Alt+Enter at runtime. Try these first: they cost two minutes and, when supported, give the most native result. Their weakness is coverage — the fullscreen-only games that send people searching for this page are usually the ones that ignore every flag, which is why our guide to games that stay fullscreen even under DxWnd exists for the next layer down as well.
Method 2: API Hooking (DxWnd)
Hooking inserts a mediator between the game and Windows. DxWnd loads alongside the game and intercepts the display-mode and window calls the game makes: when the game demands exclusive fullscreen, DxWnd lets it believe the demand was met, while actually giving it a window of the size and position set in its profile. Because the interception happens at the Windows-behaviour layer, the same profiles can also carry fixes for game speed, palettes, CD audio and locales. This is the method purpose-built for fullscreen-only DirectDraw and early Direct3D games, and our step-by-step DxWnd tutorial walks through the whole flow, while the settings guide explains the profile options you will meet.
Hooking has one structural advantage over everything else on this page: it is per-game. The flag a game ignores and the wrapper it dislikes can be replaced by a profile tuned to that one title — one game gets its window at its native resolution in the corner of a second monitor, the next gets stretched time and palette emulation, and neither configuration touches the other. That is why the hooking tools accumulated the compatibility databases and forum threads: windowed mode for old games is rarely one problem, and a per-game answer key beats a global switch.
Method 3: API Wrapping (dgVoodoo2)
A wrapper replaces the graphics API itself. dgVoodoo2 substitutes modern Direct3D for Glide and early DirectX calls, and a program that renders through a modern API can generally be presented in a window as a side effect. Wrapping is the definitive fix when the rendering is what is broken — obsolete APIs modern drivers handle badly — but window control is not its headline feature, and it does nothing for behaviour problems like speed or CD audio. The layers compose rather than compete; our DxWnd vs dgVoodoo2 comparison maps exactly where each one wins and how players stack them.
Method 4: A Virtual Machine
The heavyweight option: run a real period Windows inside a VM and let the game have its fullscreen inside that. It sidesteps every compatibility question except the VM’s own weak spots — 3D acceleration, input latency and sheer setup effort. For DOS games the equivalent heavyweight is DOSBox, an actual emulator. A VM is the last resort for games whose copy protection or drivers refuse modern Windows outright, not the first tool for a game that merely wants a window.
Which Method for Which Era
- Game has flags or a config setting: use them. Native beats forced.
- Windows 95–XP era, fullscreen-only, DirectDraw/early Direct3D: DxWnd first — it was built for exactly this.
- Glide or early DirectX game that renders wrongly: dgVoodoo2, alone or under DxWnd’s window.
- Game needs period Windows itself (drivers, 16-bit installers, disc checks): virtual machine.
- Modern game: it almost certainly has a borderless option already; dedicated tools like Borderless Gaming polish that case.
Windowed, Borderless and “Fake Fullscreen” Are Different Things
Terminology causes real confusion here, because three different presentations all get called “windowed”. A true window is a framed, resizable rectangle that shares the desktop — what forcing tools produce. Borderless fullscreen (or borderless windowed) is a modern game’s own mode: a window with no frame, sized to exactly cover one monitor, which looks like fullscreen but alt-tabs like a window. Fake fullscreen is the retro-tool approximation of the second: a true window deliberately sized and positioned to fill the screen. The distinction matters when choosing tools — Borderless Gaming and its kin polish games that can already window themselves into the borderless presentation, while DxWnd’s job is the prior step: manufacturing a window at all for games that refuse. A DxWnd profile can size its window to the screen when you want the borderless look from a game that predates the concept.
Honest Limits
Forcing a window is not magic. A small number of engines detect and resist hooking; some games render correctly but trap the mouse or misplace the cursor until their profile is tuned; and a true window is not the same as the borderless-fullscreen presentation modern games offer — a forced window has a real frame and a real resolution, which is precisely what makes it useful for streaming, multi-monitor play and taming ancient resolutions. And the standing rule applies: hooking tools and anti-cheat do not mix, so keep forced windowed mode for single-player games.