Most 32-bit games from the Windows 95, 98, and XP era can run on Windows 11 after you install the libraries they expect and adjust a small number of compatibility settings. DOS games and 16-bit Windows games are different: 64-bit Windows 11 cannot execute 16-bit programs directly, and Compatibility Mode cannot add that missing support. Those games need DOSBox, another suitable emulator, or an older/32-bit Windows virtual machine.
The reliable approach is to identify the game’s execution model first, install it outside protected system folders, use Windows’ compatibility tools one change at a time, then add only the specific legacy components named by the error. The steps below cover installation, DirectX, DirectPlay, Visual C++, DOSBox, save failures, graphics problems, and installers that will not start.
What kind of old game are you trying to run?
Start with the game’s executable and original system requirements. The distinction between 32-bit, 16-bit, and DOS determines whether Windows settings can solve the problem or whether you need an emulation layer.
| Game type | What Windows 11 can do | What you should use |
|---|---|---|
| 32-bit Windows game | Usually runs on 64-bit Windows 11, sometimes after compatibility settings or legacy runtime installation. | Native Windows execution with the troubleshooting steps below. |
| 16-bit Windows game or 16-bit installer | 64-bit Windows 11 cannot run 16-bit applications, processes, or components directly. Compatibility Mode does not change that. | A suitable emulator or virtual machine, or a newer installer supplied by the publisher. |
| DOS game | Not a native 16-bit Windows application environment. | DOSBox or another DOS-compatible emulator. |
Microsoft documents the 16-bit limitation for 64-bit Windows in its 64-bit Windows guidance and explains the historical NTVDM support in its NTVDM documentation. If the game is DOS-based, use DOSBox rather than repeatedly trying Windows compatibility options.
What should I do before changing compatibility settings?
Prepare a clean, writable installation before diagnosing a crash. This avoids confusing a permissions problem with a graphics or runtime problem.
- Use legitimate media or an official installer. Install from the original disc, a legitimate store client, or the publisher’s current installer.
- Run the game’s own redistributable installers. If the installer includes DirectX, Visual C++, or another runtime, install it before adding components manually.
- Update Windows and your graphics driver. Microsoft’s current Windows 11 release table lists versions 26H1, 25H2, and 24H2. Version 26H1 is intended for new devices; it is not an in-place feature update for existing 24H2 or 25H2 systems. Check the Windows 11 release information page for your device’s servicing status.
- Install to a user-writable path. A folder such as
C:GamesGameNameis a better first choice thanC:Program Filesfor software that writes saves or configuration files beside its executable.
Legacy programs that write to protected locations can trigger User Account Control (UAC), file virtualization, or per-user save locations. Microsoft describes those behaviors in its UAC overview, UAC virtualization guidance, and UAC advice for game developers. Moving the game is generally preferable to granting administrator rights immediately.
How do I run Windows’ compatibility troubleshooter?
Use the built-in troubleshooter before making manual changes. It tests common settings for older programs and lets you try a proposed fix.
- Open Start > Settings > System > Troubleshoot > Other troubleshooters.
- Find Program Compatibility Troubleshooter and select Run.
- Choose the game, follow the prompts, and test it after each suggested setting.
Microsoft recommends this tool for older applications that no longer receive updates. The current instructions are in Make older apps or programs compatible with the latest version of Windows. If the troubleshooter cannot identify the executable, locate the game’s actual .exe yourself and use the manual method.
Which compatibility settings should I test manually?
Apply one setting at a time so you know which change helped. Do not enable every checkbox by default; combinations can create new display or permission problems.
- Find the game’s real executable. For a shortcut, right-click it and choose Open file location.
- Right-click the executable, choose Properties, and open the Compatibility tab.
- Check Run this program in compatibility mode for: and test an appropriate older Windows version, commonly Windows 7 or Windows XP.
- Test Disable fullscreen optimizations if fullscreen produces a black screen, flicker, or an immediate crash.
- Test Reduced color mode or Run in 640 × 480 screen resolution only when the game’s display mode requires it.
- Use Run this program as an administrator only when the game genuinely needs elevated access.
- Select Apply, then OK, and launch the game.
If the controls are unavailable or greyed out, select Change settings for all users first. Microsoft’s compatibility-mode instructions are available at Windows program compatibility mode. Administrator mode is an access change, not a general compatibility cure; it can weaken the normal UAC boundary, so reserve it for a demonstrated need.
How do I fix missing DirectX files on Windows 11?
Install Microsoft’s legacy side-by-side libraries when an older game reports files such as d3dx9_*.dll, XAudio 2.7, XInput 1.3, XACT, or Managed DirectX. Having DirectX 12, or another current system DirectX version, does not guarantee that these optional components are present.
Install the June 2010 DirectX runtime
Use the official DirectX End-User Runtimes (June 2010). Microsoft’s current Download Center listing identifies version 9.29.1974.1, published July 15, 2024. The package adds legacy libraries side by side; it does not downgrade or replace the DirectX version built into Windows.
- Offline package:
directx_Jun2010_redist.exe. Choose this when the web installer fails, the computer is offline, or you need to install on several machines. - Web installer:
dxwebsetup.exe. Use Microsoft’s DirectX End-User Runtime Web Installer when an online installation is convenient.
Run the installer, allow it to extract or install its files, then retry the game. Never download an individual DLL from an unofficial DLL site. A missing library should be supplied by Microsoft’s runtime or the game’s legitimate redistributable.
When does a game need DirectPlay, and how do I enable it?
DirectPlay is a separate legacy networking component, not another name for DirectX 9. Enable it only when the game explicitly requires it or reports a DirectPlay-related failure.
Enable DirectPlay in Control Panel
- Open Control Panel.
- Select Programs, then under Programs and Features choose Turn Windows features on or off.
- Expand Legacy Components.
- Check DirectPlay, select OK, and restart if Windows requests it.
Windows may also display an on-demand prompt the first time a game calls DirectPlay. That installation requires elevation and can suspend the game until the feature is installed. Microsoft explains optional components in Windows components installed on demand; the graphical DirectPlay path is also described in Microsoft Q&A.
Use DISM when the graphical option is missing
Open Terminal (Admin) or Command Prompt (Admin) and run:
DISM /Online /Enable-Feature /FeatureName:DirectPlay /AllRestart Windows afterward. This command works only when the Windows image exposes an optional feature named DirectPlay. If DISM returns 0x800f080c (“feature name was not recognized”), do not guess another feature name. Check whether Legacy Components appears in Windows Features, install pending Windows updates, and repair the Windows installation if the component store is damaged. See Microsoft’s guidance on DirectPlay feature-name failures.
Which Visual C++ Redistributable does an old game need?
Match the redistributable to the game’s architecture and build generation when errors mention MSVCR*.dll, MSVCP*.dll, or VCRUNTIME*.dll.
| Game or build condition | Redistributable to install |
|---|---|
| 32-bit game on 64-bit Windows | x86 redistributable |
| 64-bit game | x64 redistributable |
| Game built with an older Visual Studio generation | The corresponding older package, such as 2010, 2012, or 2013, when the game requires it |
| Application built with Visual Studio 2017 through 2026 | The current shared v14 redistributable family |
A newer package does not replace every older runtime, and installing x64 alone does not satisfy a 32-bit executable. Use Microsoft’s Latest supported Visual C++ Redistributable downloads table rather than a third-party DLL website. If the game’s installer includes a redistributable, run that package first; otherwise use the version and architecture indicated by the error or the game’s documentation.
How do I run a DOS game with DOSBox?
DOSBox supplies the DOS environment that 64-bit Windows 11 lacks for DOS software. Install DOSBox, place the game in a dedicated folder, mount that folder as a virtual DOS drive, and start the executable from inside DOSBox.
Mount a folder and launch the game
For a game stored in C:DOSGAMESGAME, enter:
MOUNT C C:DOSGAMES
C:
CD GAME
GAME.EXEReplace the folder, directory, and executable names with the actual values on your computer. DOSBox’s Usage, MOUNT command, and Basic setup and installation pages explain the command syntax.
Launch directly from Windows
You can pass the executable to DOSBox and close the emulator after the game exits:
dosbox C:DOSGAMESGAMEGAME.EXE -exitIf any directory contains spaces, quote the complete path:
dosbox "C:DOS GamesGAMEGAME.EXE" -exitDOSBox also supports dragging a DOS executable onto the DOSBox program. In the classic DOSBox interface, Alt+Enter toggles fullscreen. Keep the game files inside the mounted directory; DOSBox maps the Windows folder to a virtual drive rather than exposing your entire Windows file system.
Why does an old game start but fail to save?
A game that launches but cannot create or update saves is usually blocked from writing where it expects, redirected to a per-user location, or running under a different account from the one that owns the existing saves.
- Protected installation folder: Games under
C:Program Filesmay be unable to write beside their executable. - UAC virtualization: Windows may redirect legacy writes to a per-user location, producing saves that are hard to find or inconsistent between accounts.
- Controlled folder access: Windows Security can block writes to Documents, Desktop, or another protected folder.
- Different Windows account: A save created by one account may not be visible to another account running the game.
Move the game and test a fresh save
- Exit the game completely.
- Copy or reinstall it to a writable location such as
C:GamesGameName. - Run it once and create a new save.
- If the new location works, copy existing saves into the location the game actually uses, keeping a backup first.
Allow a blocked executable without disabling protection
If Windows Security reports App is blocked, open the notification and select Add an allowed app, then browse to the game’s actual executable. You can also open Windows Security > Virus & threat protection > Manage ransomware protection > Allow an app through Controlled folder access and add that executable.
Allow only the specific game file you trust. Do not turn off all ransomware protection to solve one save problem. Microsoft’s instructions are in Virus and threat protection in Windows Security and Configure Controlled Folder Access.
How do I fix black screens, crashes, and wrong graphics?
Work from the least invasive change to the most game-specific one. A newer DirectX number alone does not prove that the old game’s optional libraries or rendering path are available.
- Update the graphics driver. Use Windows Update or the GPU manufacturer’s current driver.
- Open the executable’s Compatibility tab. Test one older Windows mode at a time.
- Disable fullscreen optimizations. This is a useful test for black screens, flicker, or crashes during the transition to fullscreen.
- Try windowed mode. Use the game’s own configuration option if it provides one.
- Use administrator mode only when needed. It can address a genuine access requirement but is not a universal graphics fix.
- Install the official June 2010 DirectX runtime. Do this when the error names D3DX, XAudio, XInput, XACT, or another legacy DirectX library.
- Use a maintained, game-specific compatibility wrapper or community port. If the title depends on a very old 3D API that modern drivers no longer expose correctly, a reputable project designed for that game is safer than randomly replacing system DLLs.
Do not copy replacement DLLs from download sites into the Windows system directory. Keep any wrapper or port confined to the game’s documented installation and preserve the original files so you can undo the change.
What if the game’s installer will not run?
Separate an installer failure from a game failure. A modern Windows executable may launch while an old setup program does not, especially when the setup program is 16-bit.
- Check whether the publisher offers a current installer or patch and use that version when available.
- Right-click the installer, choose Properties > Compatibility, test a suitable compatibility mode, and run it as administrator only if the installer requires elevation.
- If the installer is 16-bit, stop trying compatibility combinations: 64-bit Windows 11 cannot execute it directly.
- Obtain a newer installer, or install the game inside a 32-bit/older Windows environment, suitable emulator, or virtual machine.
Some 16-bit installers can be recognized and substituted by 64-bit Windows for specific supported installer formats. That narrow behavior does not mean arbitrary 16-bit installers or games are supported. Microsoft distinguishes these cases in Application installation on 64-bit systems and its 16-bit program guidance.
Which fix should I try for each symptom?
| Symptom | First targeted action | Next step if it remains |
|---|---|---|
| “This application cannot run” or an installer exits immediately | Determine whether the executable or installer is 16-bit. | Use a newer installer, emulator, or older/32-bit Windows environment. |
Missing d3dx9_*.dll, XAudio, XInput, or XACT file |
Install the official June 2010 DirectX End-User Runtime. | Run the game’s bundled redistributable and retest. |
Missing MSVCR, MSVCP, or VCRUNTIME file |
Install the matching Visual C++ generation and architecture. | For a 32-bit game, verify that the x86 package is installed even on 64-bit Windows. |
| Multiplayer or startup error names DirectPlay | Enable Legacy Components > DirectPlay. | Use the DISM command if the graphical option is unavailable, then restart. |
| Game starts but cannot save | Move it to C:GamesGameName and create a new save. |
Allow only the game executable through Controlled folder access if Windows Security blocked it. |
| Black screen or fullscreen crash | Test Disable fullscreen optimizations and windowed mode. | Update the graphics driver, install required legacy DirectX libraries, or use a maintained game-specific wrapper. |
Change one variable between launches and record what happened. That simple discipline prevents a working setting from being hidden by three simultaneous changes.
Which common old-game advice is wrong?
“Install DirectX 12.”
Windows already includes its current system DirectX runtime. Older games may instead need optional libraries from the June 2010 End-User Runtime; installing a newer DirectX number does not add every historical component. See Microsoft’s DirectX End-User Runtime listing.
“Compatibility Mode runs 16-bit games.”
It does not. Compatibility settings alter selected behaviors of a supported Windows executable; they cannot provide the 16-bit execution environment absent from 64-bit Windows 11. Use DOSBox, another emulator, or an appropriate virtual machine for that class of software.
“DirectPlay is DirectX 9.”
DirectPlay is an optional Windows feature under Legacy Components. It must be enabled separately when a game requires it.
“The latest Visual C++ package fixes every MSVCR error.”
Not necessarily. The game may need the x86 package or an older Visual C++ generation, such as 2010, 2012, or 2013.
“Run every old game as administrator.”
Administrator mode can weaken the security boundary and does not solve missing libraries or unsupported CPU environments. A writable installation folder is the better first test for old write behavior.
“Download the missing DLL from a DLL website.”
A random DLL may be the wrong version or unsafe. Install the official Microsoft runtime or the game’s legitimate redistributable instead.
Frequently Asked Questions
Will upgrading an existing Windows 11 PC to 26H1 make old games work?
Not by itself. Microsoft describes 26H1 as intended for new devices rather than an in-place feature update for existing 24H2 or 25H2 installations, and no Windows release guarantees support for a particular legacy title. Treat the game’s architecture and required runtimes as the deciding factors.
Can I install a 32-bit game on 64-bit Windows 11 without a virtual machine?
Usually yes. Most 32-bit Windows games run natively on 64-bit Windows 11; the virtual-machine or emulator requirement applies to 16-bit Windows software and DOS environments that need their own execution layer.
Why did my save disappear after I changed Windows accounts?
Legacy games can write to per-user locations through UAC virtualization or protected-folder rules. A save created under one Windows account may therefore be invisible to another; test the game from the account that created the save and keep backups before moving files.
Should I install both x86 and x64 Visual C++ packages?
Install the architecture the executable needs: x86 for a 32-bit game and x64 for a 64-bit game. A 64-bit operating system does not make the x64 package a substitute for the x86 runtime.