How to Use DxWnd with Steam Games: Windowed Mode for Classics

You can use DxWnd with Steam games — and for classic re-releases that are locked to fullscreen, it is often the difference between playable and unplayable. DxWnd is a free, open-source program that forces fullscreen-era games to run in a window. Many beloved titles on Steam are the original DirectDraw or early Direct3D builds wrapped for modern sale: they still demand exclusive fullscreen, still switch your display to a tiny resolution, and still fall apart when you alt-tab. DxWnd fixes that by hooking the game itself. The catch is that Steam sits between you and the game, so the setup has a few specific steps — this guide covers them, plus the caveats that actually matter.

When DxWnd Helps a Steam Game (and When It Doesn’t)

DxWnd is worth setting up when a Steam game is a legacy title that forces fullscreen, changes your desktop resolution, shows broken colours, or crashes on alt-tab. It is not needed when the game already offers a proper windowed or borderless mode in its own settings — check the game’s options first, because a native setting always beats a hook. And it must not be used with multiplayer games protected by VAC or another anti-cheat: hooking a game’s process can be treated as cheating, with account consequences. Everything below assumes a single-player classic.

Step 1: Find the Real Game Executable

DxWnd needs to hook the game, not the Steam client. Your Steam library lives under the Steam installation folder, in steamapps\common\<Game Name>\ — for example C:\Program Files (x86)\Steam\steamapps\common\ followed by the game’s folder. Inside, find the game’s actual .exe: usually the file the game itself runs, often named after the game. In Steam you can also right-click the game > Manage > Browse local files to open the folder directly.

Watch out for one common trap: some games ship a small launcher executable that then starts the real game. If you point DxWnd at the launcher, the hook may not carry over to the game that actually opens. If a profile “does nothing,” suspect this first and look inside the game folder for the main game binary.

Step 2: Add the Game to DxWnd

Run DxWnd as administrator, choose Edit > Add, and set the Main tab’s Path to the game executable you found in Step 1 — under steamapps\common, not to steam.exe and not to a Steam shortcut (Steam shortcuts are URLs, not programs, and DxWnd cannot hook them). Leave Run in Window enabled, set a sensible window size for the game’s era, and click OK. Our full DxWnd tutorial explains each of these fields if this is your first profile.

Step 3: Launch It the Right Way

Two things have to be true at launch time:

• Steam must be running and signed in. Steam games check in with the client for DRM. If you launch the game through DxWnd while Steam is open, that check passes normally, exactly as if Steam had started the game itself.
• Launch from inside DxWnd. Double-click the profile in DxWnd’s window. Starting the game from Steam’s Play button instead skips the hook, and you will get plain fullscreen again.

If the combination of Steam overlay and DxWnd causes flicker, a black window, or input weirdness, turn the overlay off for that one game: in Steam, right-click the game > Properties > General, and disable Enable the Steam Overlay while in-game. The overlay injects its own code into the game, and two injectors in one process do not always get along. This is a per-game setting, so your other games keep their overlay.

About “Application Load Error”

Search for DxWnd plus Steam for long and you will meet the Application Load Error family — Steam-side launch failures with codes such as 5:0000065434 that appear when a game is started outside Steam’s usual path, which is exactly what launching through any external tool does. It does not mean DxWnd broke your game; it generally means Steam’s launch checks were not satisfied in that attempt. Sensible first checks, in order:

• Make sure Steam is fully open and signed in before you launch from DxWnd — not still updating or restarting.
• Be consistent about administrator rights: running the game elevated while Steam is not (or the reverse) is a classic trigger. Pick one arrangement — most players do best with Steam in its normal mode and DxWnd as administrator, and if errors persist, try matching them.
• Verify the game files in Steam (right-click the game > Properties > Installed Files > Verify integrity) so you know the installation itself is sound.
• Restart Steam once and try again; a stale client state causes more of these errors than any setting does.

No honest guide can promise a single guaranteed fix, because the error is a family with several causes — but the checks above resolve the common ones. We also keep a dedicated guide to the Application Load Error and its standard Steam checks.

A Quick Pre-Flight Checklist

When a Steam game ignores DxWnd or opens misbehaving, run down this list before changing random settings — in practice, one of these five is almost always the cause:

1. Steam is open and signed in (not mid-update, not restarting).
2. The profile’s Path points at the game’s real executable inside steamapps\common — not the Steam shortcut, not steam.exe, and not a launcher stub.
3. DxWnd is running as administrator, and the game was launched by double-clicking its profile inside DxWnd.
4. The Steam overlay is disabled for this specific game, so only one injector is active in the process.
5. The game’s own display options have been checked — if it has a native windowed mode, that setting and DxWnd should not fight over the same window; use one or the other.

Notice what is not on the list: reinstalling Steam, moving your whole library, or editing the registry. The Steam-plus-DxWnd combination fails for mundane reasons — a wrong path, a closed client, an overlay conflict — and the fix is correspondingly mundane. Methodically confirming the basics beats folklore tweaks every time, and it keeps your Steam installation exactly as Valve expects it, which matters the next time the client updates.

Steam-Specific Caveats Worth Knowing

• Which executable is “the game” varies. Remasters sometimes run through a wrapper or a configuration tool first. Browse the local files and identify the binary that actually renders the game.
• Cloud saves and achievements keep working as long as Steam is running, because those are Steam client services — launching through DxWnd does not disconnect the game from Steam.
• Keep DxWnd current. Steam’s client updates regularly, and DxWnd is actively maintained; if a combination that worked stops working, check the latest DxWnd version before you start changing settings.
• Windows 11 players should also apply the per-game “Disable fullscreen optimizations” property described in our DxWnd on Windows 11 guide — it removes one more layer that can fight DxWnd’s windowing.

Get DxWnd itself from the download page (official SourceForge file, hashes published for verification), and keep the golden rule in view: Steam running, game launched through DxWnd, overlay off if it misbehaves. That trio handles the great majority of classic Steam titles.