You set up the profile, launched the game — and it took over the whole screen anyway, exactly as if DxWnd were not there. “Still fullscreen” is the most common DxWnd disappointment, and it is nearly always a checklist problem rather than a compatibility verdict: one of a handful of specific things is preventing the window from forming. This guide is that checklist, in the order the causes actually occur.
Check 1: You Launched from Inside DxWnd
DxWnd forces windowed mode by hooking the game as it starts it. If you launched the game from its desktop shortcut, the Start menu, or a store client’s Play button, DxWnd never got its chance, and fullscreen is simply the game’s default behaviour continuing undisturbed. The launch must happen by double-clicking the game’s entry inside DxWnd’s own window. This sounds obvious, and it remains the single most frequent cause — if you take one thing from this page, take the habit of launching from DxWnd every time. Our not working checklist covers the same ground from the hooking angle.
Check 2: Run in Window Is Enabled on the Right Profile
Open the profile you are actually using — right-click the entry > Modify — and look at the Main tab: Run in Window must be enabled. Two failure shapes hide here. The option was unticked during earlier experiments and never restored. Or you have two entries for the same game — an old one and a new one, pointing at the same or slightly different paths — and you have been editing one while launching the other. Delete duplicates so there is exactly one profile per game, and confirm its Path names the executable you really run.
Check 3: The Hook Actually Engaged
A profile can be correct and still not hook, in which case window settings are irrelevant. Launch the game from DxWnd and read DxWnd’s window: the target’s status and log show whether the game registered as hooked. If it never registers, you are not in “still fullscreen” territory at all — work the general not working checklist (administrator rights first, then the real-exe path, then antivirus interference). If it does register as hooked yet still covers the screen, continue below.
Check 4: The Game’s Own Fullscreen Setting
Plenty of classic games keep their own display preference: a fullscreen checkbox in the options menu, a configuration utility, or a line in an .ini file in the game folder. When a game is determined to open in exclusive fullscreen by its own setting, it can fight DxWnd’s window — typically by reasserting fullscreen after the window forms, or by opening fullscreen on a second attempt. Where the game offers a windowed or borderless mode of its own, set it there and let DxWnd manage placement and size; where it offers only fullscreen, leave the game setting alone and rely on the hook, but know that this specific combination is the stubborn one. For Steam games, a game-side alternative also exists: Steam’s per-game launch options accept flags such as -windowed (support varies by title), which asks the game itself to start windowed before DxWnd is even involved — see our Steam games guide for the surrounding workflow.
Check 5: Is It Actually Fullscreen? (Borderless vs Exclusive)
Before concluding failure, verify what you are looking at. A window sized exactly to your monitor, without a border, is visually identical to fullscreen — but it is a window: Alt+Tab switches away instantly, the taskbar can appear over it, and other windows can sit on top. Exclusive fullscreen, by contrast, makes the display mode switch (often with a flicker or a second of black) and Alt+Tab is slow and disruptive. If your “fullscreen” game Alt+Tabs instantly and lets you park a chat window over it, DxWnd has already succeeded — you have a borderless-style window, which for most players is the ideal outcome rather than a problem.
A Note on Resolution Switching
A related sighting: the game starts and your whole desktop changes resolution — icons grow, everything shifts — before the game appears. That mode switch is the game asking Windows for a fullscreen display mode, and it means the game got far enough to impose its display before DxWnd’s window contained it. It is worth one specific profile check: make sure the window size fields in the profile are filled in explicitly rather than left to follow the game. A profile with concrete window geometry gives DxWnd something definite to hold the game to; a profile left entirely on “game decides” has less to push back with on titles that open by switching modes. If the desktop still resizes after that, you are back in Check 3/Check 4 territory — hook state first, then the game’s own fullscreen insistence.
Check 6: The Environment Basics
Finally, the dull causes that break windowing along with everything else: DxWnd not running as administrator (so the hook degrades silently), an old DxWnd build missing a fix for this title — the current release is v2.06.16 — or dxwnd.dll missing because an antivirus quarantined it, which our false positive guide explains how to recover safely. Correct whichever applies, then retest from Check 1.
If It Still Will Not Window
A small number of games use rendering paths that a generic profile cannot window, and they need game-specific settings or support in a newer build. At that point the productive move is the project’s SourceForge forum: name the game, your DxWnd version, and what the hook status showed, and check whether a community .dxw profile exists for the title. The troubleshooting hub collects all of our fix guides, and our step-by-step tutorial recaps the profile basics these checks assume.