You launch a game through DxWnd and instead of a window you get a Windows error: “Error 740: The requested operation requires elevation.” The good news is that this is one of the most clearly understood DxWnd problems. Error 740 is not a DxWnd malfunction and not a damaged game — it is Windows User Account Control (UAC) refusing a launch because the programs involved disagree about administrator rights. Once the elevation levels in the chain match, the error goes away. This guide explains what the error means, when it appears, and the fixes in the order you should try them.
What Error 740 Actually Means
740 is the Windows system error code ERROR_ELEVATION_REQUIRED. Since Windows Vista, every program runs at a privilege level: standard or elevated (administrator). A process running at the standard level cannot silently start a program that demands elevation, and Windows blocks the attempt with this error instead of guessing what you wanted. Classic games complicate this because many of them — and especially their installers and launchers — were written for Windows 95/98/XP, where everything ran with full rights. Their executable files often carry a request for administrator privileges baked in, so on a modern system they demand elevation every single time they start.
DxWnd sits in the middle of this. DxWnd has to start the game itself in order to hook it, so when the game demands elevation and DxWnd is running without it (or the reverse mismatch occurs), Windows stops the launch and you see error 740. Nothing has crashed; the launch was simply never allowed to begin.
When This Error Typically Appears
- DxWnd is running normally, the game demands admin rights. The most common case: an old game executable that always triggers a UAC prompt when you start it directly.
- The game was manually set to “Run as administrator.” Someone ticked that box in the game’s Compatibility properties in the past, and now the game insists on elevation while DxWnd runs unelevated.
- A launcher or installer is in the way. Setup programs and launcher stubs habitually demand elevation even when the game itself does not.
- Steam is in the chain. Steam, DxWnd and the game at three different privilege levels is a reliable way to produce launch errors, of which 740 is one.
The Fixes, in Order
1. Run DxWnd as Administrator
Close DxWnd, right-click dxwnd.exe, and choose Run as administrator, then launch the game from inside DxWnd as usual. This single step resolves the majority of error 740 cases, because DxWnd’s own getting-started documentation assumes it runs elevated — hooking games that themselves request elevation requires DxWnd to be at least at their level. If it works and you play this game often, many users make the change permanent by opening dxwnd.exe’s Properties > Compatibility tab and ticking Run this program as an administrator, accepting the UAC prompt at each DxWnd start as the price.
2. Launch the Game from Inside DxWnd
DxWnd can only hook a game it starts. If you double-click the game’s own icon, the game starts on its own terms — elevation prompt and all — and DxWnd is not involved. Add the game with Edit > Add if you have not already, and start it by double-clicking its entry in DxWnd’s window. Our step-by-step guide to using DxWnd covers profile setup in full.
3. Match the Elevation Levels
Think of the chain — DxWnd, any launcher, the game, and Steam if present — as needing one consistent level. If the game’s Compatibility properties have “Run this program as an administrator” ticked, either untick it (if the game runs fine without it) or run DxWnd elevated to match. What you must avoid is the mixed state: an elevated game trying to be started by an unelevated DxWnd, or an elevated DxWnd profile manipulated by tools running at different levels. Consistency, not maximum elevation, is the goal.
4. Point DxWnd at the Real Game, Not the Launcher
If error 740 appears only for one specific title, check what the profile’s Path field actually points at. Launcher and setup executables frequently demand elevation out of habit. Browse the game’s folder, find the main game binary (usually the largest executable, named after the game), and repoint the profile at it. This also improves hooking reliability generally, because launchers hand off to child processes that DxWnd may not follow.
5. For Steam Games, Align Steam Too
If the game lives in Steam, make sure Steam itself is fully open and signed in before launching, and keep Steam and DxWnd at compatible levels — the arrangement most players settle on is Steam in its normal mode and DxWnd as administrator, with the game launched from DxWnd. Our guide to using DxWnd with Steam games walks through the launch order, and the related Application Load Error guide covers the other classic Steam launch failure.
What Not to Do
Do not disable UAC to make error 740 go away. UAC is a core Windows protection, the error is doing its job correctly, and turning it off exposes every program you run — including old games of unknown provenance — to silent full-system access. Likewise, do not download a “pre-elevated” or patched dxwnd.exe from a random site: the genuine program is free from SourceForge, and a modified hooking tool is precisely the kind of file you should never trust. The fixes above are boring because the problem is boring — a permissions mismatch, not damage.
Still Seeing Error 740?
If the error persists after matching elevation everywhere, work through our general DxWnd not working checklist — a wrong Path or an antivirus quietly removing dxwnd.dll can masquerade as an elevation problem. The DxWnd troubleshooting hub collects all of our fix guides in one place, and for genuinely game-specific cases the project’s SourceForge forum is where the developer and community work through individual titles.
Frequently Asked Questions
What is error 740?
Error 740 is the Windows error ERROR_ELEVATION_REQUIRED. It means a program tried to start another program that requires administrator privileges, and Windows blocked the launch because the first program did not have those privileges itself.
Why does error 740 appear with DxWnd?
Because DxWnd starts the game in order to hook it. If the game demands elevation (as many classic games and launchers do) while DxWnd runs without administrator rights — or the levels otherwise mismatch — Windows refuses the launch with error 740.
Do I always need to run DxWnd as administrator?
Not for every game, but it is the recommended default: DxWnd’s own documentation assumes it, and any game that requests elevation can only be launched by an elevated DxWnd. Running DxWnd as administrator is the first fix for error 740.
Why does error 740 happen with only one of my games?
Because elevation demands are per-program. One game (or its launcher) requests administrator rights while your others do not. Check that game’s executable and Compatibility settings, and make sure the profile points at the real game binary rather than a launcher.