Grand Theft Auto 2 (1999, DMA Design, published by Rockstar) is the last of the top-down GTAs: one city, three districts, and a respect system that lets you play rival gangs against each other. Its DxWnd story, documented across several threads in the project’s forum, has one rule that decides everything: DxWnd must hook the game’s manager program, not the game itself. Hook gta2.exe directly and the game crashes; hook it through the manager and it runs. This guide follows those threads, including where the results honestly differ between versions.
Why the manager is the target
GTA 2 does not start at gta2.exe in the way most games do — it is launched by a front-end program, the gta2 manager (gta2 manager.exe), which handles settings and then starts the game. Community testers in the forum established the behaviour the hard way: a profile pointed at gta2.exe produces crashes, while the manager-targeted profiles are the ones people report working — in mixed mode in one long test thread, and, in ghotik’s own later release notes, with the extended hook applied through the manager application (“GTA2 runs when extended hooked through the manager application”). The manager is also where you will find the game’s own options, including its 3D sound toggle, so it has to be part of the launch chain anyway.
Setup
- Add a profile in DxWnd as in how to use DxWnd, but set the target path to gta2 manager.exe in your GTA 2 folder — not gta2.exe.
- Keep the resolution fixed. The profile ghotik shared in the forum thread locks the game to 640×480, and there is a reason beyond tidiness (see the sound note below): the fewer mode switches between the manager, menus and the game, the better GTA 2 behaves under DxWnd.
- Launch the manager from DxWnd and start the game from it as normal. Working community profiles exist for both the CD install and later re-releases; if you import one, how profiles work explains the import and path-correction steps — the stored path will be the author’s, not yours.
- If the game starts but the DxWnd window never appears around it, ghotik’s suggestion in the thread is to switch the profile’s hook start method to Hook → Inject suspended process and try again.
If it still fails: a short checklist from the threads
- Crash the moment the game starts? Check the profile target first. Every thread diagnosis of an instant crash ends at the same place: the profile was pointing at gta2.exe. Point it at the manager and retry before changing anything else.
- Manager opens, game window never appears? That is the case ghotik’s Inject suspended process suggestion addresses — the hook has to be in place before the manager hands over to the game.
- Window appears, then the game takes the whole screen anyway? Work through still fullscreen — the general causes (wrong executable, hook timing, another overlay interfering) apply here too, on top of this game’s own quirks.
- It worked on Windows 10 but not after an upgrade? You are in the honestly-mixed territory described below — check the forum threads for your exact build before assuming your profile is wrong.
Set your options in the manager, not in the game
Because the manager is the launch point, it is also where your display and sound choices should be made before DxWnd enters the picture. The manager carries GTA 2’s configuration — screen mode and resolution choices, and the 3D sound option testers mention toggling when audio misbehaves. The workflow the threads converge on is: configure the game once in the manager, keep those choices stable (that is the fixed-resolution discipline again), and let the DxWnd profile do only the windowing. Changing video options inside the game afterwards reintroduces exactly the mode-switching the setup is designed to avoid. If you import a shared profile, remember it may assume the manager’s defaults — set the manager to match the profile, not the other way round.
The sound-loop glitch, and why fixed resolution matters
A sound fault is documented twice in the forum, in independent threads: under DxWnd the game’s audio can begin looping when you move between the menu and gameplay. The testers’ explanation is that the loop is triggered by the resolution changing between those screens — and, tellingly, the same looping was observed natively, without DxWnd, whenever the game changed resolution. GTA 2 likes to switch modes between its shell and the game proper, so the practical countermeasure is the fixed-resolution profile above: no mode switch, no trigger. If a launch fails outright instead — the process simply never gets going — work through DxWnd not working for the general causes before assuming it is this game.
Known issues — results genuinely vary
This is the point where honesty matters more than a tidy guide. Testers report that the edition of the game matters: one forum member found DxWnd would not cooperate with the old Rockstar Classics free release while the CD version worked. Windows version matters too — in a later release-candidate thread, ghotik noted that on Windows 11 GTA 2 was refusing to run even with an older DxWnd release and its original profile at the time of testing. Neither statement cancels the other out; together they mean your mileage will vary by build, and the forum threads (linked below) are the current state of knowledge. What is consistent across every report is the manager rule: whichever edition you have, gta2.exe is the wrong target.
Where to get GTA 2 legally
GTA 2 is not currently on sale digitally. It was sold on Steam for years but has since been delisted, and Rockstar’s own free download of the classics — offered in the 2000s — was withdrawn long ago. If you bought it on Steam before the delisting, it remains in your library and still downloads; otherwise, the original CD is the legitimate route.
More game-specific setups live on the DxWnd games hub. Sources: the DxWnd forum threads on the GTA 2 sound fault and window behaviour, and ghotik’s v2.06.10 and v2.06.12 release notes, all on SourceForge.