Some Windows 98-era games run on Windows 10 with a few compatibility settings. Others are DOS programs, 16-bit Windows software, CD-dependent releases, or 3D games built for hardware that Windows 10 no longer emulates. Identify the game’s technology first, then escalate from native compatibility mode to DOSBox-X, WineVDM, a virtual machine, or period-hardware emulation.
Identify what you actually have
“Windows 98 game” describes several different program types. The executable and installer—not the box date—determine the right solution.
| Game type | What to look for | Best first method |
|---|---|---|
| Pure DOS | Manual lists MS-DOS; game starts from a DOS prompt | DOSBox-X |
| Windows 3.x/Win16 | 16-bit Windows executable or installer | WineVDM/OTVDM, a 32-bit guest, or a legacy environment |
| 32-bit Windows 95/98 | Ordinary Win32 executable | Windows 10 compatibility settings |
| DirectDraw, Direct3D, or Glide | Requires period-specific graphics APIs or 3dfx hardware | Native testing, then DOSBox-X, 86Box, or period hardware |
| Mixed DOS/Windows release | Separate DOS and Windows launchers | Test each executable separately |
| 32-bit game with 16-bit installer | Installer fails before the game can be tested | Legitimate replacement installer, patch, or legacy environment |
On 64-bit Windows 10, ordinary 16-bit x86 applications and 16-bit Windows installers do not run directly. Microsoft documents NTVDM only for 32-bit x86 Windows, not x64 or ARM: NTVDM and 16-bit app support and 64-bit Windows and 16-bit programs. A failed installer therefore does not prove that the game itself is 16-bit.
Protect the original before changing anything
- Back up save files and configuration files.
- Keep the original disc, serial number, or legally purchased digital installer.
- Use official patches, publisher fixes, or a verified community patch for that title.
- Avoid random “no-CD” executables, cracked files, and unverified ISO downloads.
- If an official re-release exists, compare its features with the original before deciding which version you want to preserve.
Method 1: Try the game directly on Windows 10
This is the quickest route for a self-contained 32-bit Windows game. Microsoft’s current guidance is to install updates, run the Program Compatibility Troubleshooter, and update device drivers: Microsoft’s older-app compatibility guidance.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Find the real executable. Right-click the shortcut, choose Properties, and use Open File Location when available. Apply settings to the game’s .exe, not only to the installer.
- Open compatibility properties. Right-click the executable, choose Properties > Compatibility, and test one change at a time.
- Test an older Windows mode. Try Windows 95, Windows 98/Me, or Windows XP mode, depending on the title.
- Test display options. Try reduced color mode, 640×480 resolution, and Disable fullscreen optimizations when that checkbox is offered. Windowed mode can help if the game supports it.
- Use administrator rights only when needed. Test Run this program as an administrator if installation or saving fails, but do not treat it as a universal fix.
- Run the troubleshooter. On current Windows 10 instructions, use Start > Settings > System > Troubleshoot > Other troubleshooters > Program Compatibility Troubleshooter > Run. Older releases used Update & Security > Troubleshoot > Additional troubleshooters, so labels vary.
- Update graphics and sound drivers. This can address instability, but it cannot recreate a missing 16-bit subsystem or obsolete hardware.
Compatibility mode changes selected behavior; it does not turn Windows 10 into Windows 98. Stop repeating checkbox combinations when the program still has broken timing, sound, colors, CD access, copy protection, or 3D initialization.
Method 2: Enable DirectPlay only when a game needs it
DirectPlay is a legacy networking component, not a general old-game mode. It may help a title that explicitly requests an old DirectX networking feature, but it will not fix a 16-bit executable, renderer, installer, or disc-protection driver.
- Press Windows key + R.
- Enter
optionalfeaturesand press Enter. - Expand Legacy Components.
- Select DirectPlay, confirm, and restart if Windows asks.
Availability and wording vary by Windows 10 edition and build. Microsoft describes DirectPlay as an optional legacy component installed on demand: Windows components installed on demand.
Rank #2
- up to four players with multi-player split screen
- nine unique new worlds
- 3-D graphics and cool music
- Competer over LAN, modem to modem or Internet
- dozens of challenging new levels
Method 3: Use DOSBox-X for DOS and Windows 9x software
DOSBox-X is the practical first emulator for DOS games and supports DOS-based Windows versions, including Windows 3.x and Windows 9x. Its documentation covers Windows 98 RTM and Windows 98 Second Edition (SE), CD and hard-disk images, sound, networking, and optional 3dfx Voodoo emulation. Individual games still need title-specific settings.
When DOSBox-X is the right move
- The game launches from DOS or lists MS-DOS requirements.
- It needs DOS memory managers, Sound Blaster settings, or CPU timing.
- It is a Windows 9x title that depends on DOS-era storage or CD behavior.
- You need a contained Windows 98 environment without replacing the host installation.
Prerequisites
- A legally obtained Windows 98 or Windows 98SE disc or image.
- A legally obtained game disc, installer, or image.
- A current DOSBox-X build from the official site.
- A dedicated folder for disk images, configuration files, and backups.
The DOSBox-X guide recommends Windows 98SE when you do not know which edition to install. Its documented guide covers retail and OEM full editions, not upgrade editions: Installing Microsoft Windows 98 in DOSBox-X.
Starting configuration
Use the guide’s values as a starting point, not a universal profile:
[sdl]
autolock=true
[dosbox]
title=Windows 98
memsize=128
vmemsize=8
vesa modelist width limit=0
vesa modelist height limit=0
[dos]
ver=7.1
[cpu]
cputype=pentium_mmx
core=normal
[sblaster]
sbtype=sb16vibra
Preserve a working configuration before changing CPU, sound, video, or memory values. Maintain a separate configuration for each troublesome game rather than forcing one global setting.
Install Windows 98 from an image
The documented image-mounting method uses:
IMGMOUNT C hdd.img
IMGMOUNT D Win98.iso
XCOPY D:WIN98 C:WIN98 /I /E
C:
CD WIN98
SETUP
Copying the WIN98 directory to the virtual hard disk reduces later requests for the installation CD. The guide estimates about 174 MB for a complete Windows 98SE directory, or about 120 MB without the OLS and TOUR directories.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Mount a game CD
IMGMOUNT D game_cd.iso
If Windows 98 does not detect the disc, the image may need an IDE assignment:
Rank #4
IMGMOUNT D game_cd.iso -ide 2m
Use the drive letter and image format appropriate to your setup. Attach CD and floppy devices before booting Windows 98; DOSBox-X notes that adding them after boot may require a reboot. Its virtual internal Z: drive is normal and contains DOSBox-X commands.
Graphics, sound, and 3D
Re-run the game’s sound setup and start with Sound Blaster 16-compatible settings. Match the game’s IRQ, DMA, and port choices to the emulated device. For Glide titles, DOSBox-X includes Voodoo emulation and Glide support, but that does not guarantee every game will work. DirectDraw, Direct3D, and Glide have different failure modes.
Method 4: Use WineVDM for selected Win16 programs
WineVDM/OTVDM is a third-party open-source compatibility project for Windows 1.x–3.x-era 16-bit applications on 64-bit Windows. It is relevant when the executable itself is Win16, or when a 16-bit installer is the immediate obstacle.
- Download it only from the project’s official repository or a verifiable release.
- Use its
otvdm.exeorotvdmw.exepath as documented by the project. - Do not expect it to emulate Windows 98, DOS memory management, CD checks, sound cards, Direct3D, or Glide.
- For software that genuinely requires a complete 16-bit or Windows 98 system, use a 32-bit guest or full legacy environment instead.
Method 5: Virtual machines and period-hardware emulation
Virtual machine
A virtual machine can isolate Windows 98 and reproduce its APIs, registry behavior, and old installer environment. VirtualBox and VMware are possible tools, but neither guarantees usable Windows 98 graphics or sound acceleration.
- Advantages: isolation, snapshots, and a familiar guest operating system.
- Limitations: awkward Windows 98 drivers, difficult USB/CD/audio setup, and major 3D-acceleration constraints.
86Box and similar emulators
Specialist period-hardware emulation is appropriate when CPU timing, unusual sound cards, video cards, or 3dfx-era hardware behavior matters. It is an advanced route, not the default for a casual installation. A real period-compatible PC can be more reliable for a particularly demanding title, but that decision is game-specific.
Choose the method from the symptom
| Symptom | Likely cause | Next step |
|---|---|---|
| “This app can’t run on your PC” | 16-bit program, damaged file, wrong architecture, or blocked protection driver | Identify whether installer or game fails; use WineVDM for Win16 or a legacy environment |
| Black screen | DirectDraw, fullscreen, color depth, video adapter, or intro codec | Try windowed mode, reduced colors, 640×480, fullscreen-optimization changes, then a title-specific patch or emulator |
| Crashes after the intro | Video codec, renderer, or copy protection | Patch the title legitimately; test another renderer or legacy environment |
| Game runs too fast | Modern CPU speed or busy-wait timing | Lower DOSBox-X CPU speed; test core=normal and use a per-game configuration |
| No sound | Wrong Sound Blaster model, IRQ, DMA, port, driver, or MIDI device | Run sound setup and match settings to the emulated hardware |
| CD not found | Wrong drive letter, late mounting, missing IDE assignment, or disc check | Mount before boot, try the documented -ide option, or use a legitimate patch/re-release |
| Missing DLL | Obsolete runtime or incomplete installation | Use the publisher’s patch or a verified re-release; avoid random DLL sites |
| Saves fail | Protected folder, expected directory, or read-only mount | Install outside Program Files, inspect the save path, and back up saves |
| Wrong colors or flicker | Palette handling or DirectDraw behavior | Try reduced color mode, windowed play, and a game-specific compatibility fix |
| Multiplayer fails | Missing DirectPlay or obsolete network protocol/service | Enable DirectPlay only if required; do not assume the original online service still exists |
| Copy-protection error | Obsolete disc driver blocked by modern Windows | Use an official re-release or legitimate patch, not an unverified executable replacement |
Legacy applications may also expect to write inside protected directories. Microsoft explains the relevant file and registry virtualization limits in User Account Control for game developers.
When to stop trying compatibility mode
- The installer is reported as an unsupported 16-bit application.
- The game requires Windows 3.x, DOS components, or Windows 98 registry behavior.
- It expects a specific CD-ROM drive, DOS memory manager, or sound-card configuration.
- It uses Glide or crashes during 3D initialization.
- Timing, sound, input, colors, or CD access remain broken after focused tests.
- Obsolete copy protection is the blocker.
- Repeated checkbox changes produce no meaningful change.
Should you use an official re-release?
A legitimate modern edition is usually the lowest-friction option when convenience matters. It may include a fixed installer, DOSBox configuration, controller support, widescreen options, or removal of obsolete protection. It may also change music, multiplayer, video, or other original behavior. Check the specific listing rather than assuming every re-release is identical or permanently available. A starting point for classic releases is GOG’s classics catalog.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
The shortest recommendation
- For a normal 32-bit Windows 95/98 game, try the executable’s compatibility properties and Microsoft’s troubleshooter.
- For DOS software or a DOS-based Windows 9x title, use DOSBox-X.
- For a Win16 executable, try WineVDM/OTVDM; move to a 32-bit or Windows 98 guest if it needs more than Win16 support.
- For Windows 98 APIs, registry behavior, CD checks, or period 3D hardware, use DOSBox-X’s Windows 98 setup, a carefully configured VM, 86Box, or real period hardware.
- Choose an official re-release when reliable installation is more important than preserving the original executable and behavior.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




