That message is a game launcher reporting that your PC couldn't initialize the DirectX 12 renderer, so the game quit before the first frame. The fix is one of three things: your GPU lacks DirectX 12 hardware support, your copy of Windows is too old, or the game's own launch options are forcing DX12 when your hardware can only run DX11. The "-dx12" and "-d3d12" arguments are extra command-line flags a launcher passes to the game executable, and if a game or a reinstalled launcher has one saved, every launch fails the same way until you remove it.
The message rarely means DirectX 12 is missing from Windows. DirectX 12 ships with Windows 10 and Windows 11 as a system component, so the error surfaces when the game's hardware check fails or the renderer call is refused. Read the exact wording: games built with Unreal Engine, Unity, or custom renderers word the check differently, and the phrasing usually tells you which of the three causes you're facing.
Before touching anything, identify the GPU and the Windows build. Press Win+R, type dxdiag, hit Enter, and look at the System tab for the OS build and the Display tab for the chip name. Any GPU newer than roughly 2012 from Nvidia, AMD, or Intel generally exposes DirectX 12 hardware support, though support on paper and support in a specific game are different tests.
Which of the Three Causes Actually Applies to Your PC
The first cause is hardware. DirectX 12 requires a GPU with a feature level of 11_0 or higher, and cards from before roughly the GTX 600 series or Radeon HD 7000 series can fall short. If dxdiag reports "Feature Levels: 11_0" or lower on a modern-looking system, the GPU is the limit, not the software.
The second cause is the operating system. Windows 8.1 and earlier do not include DirectX 12 at all, and even on Windows 10 the DirectX 12 components depend on a build that has received the platform updates Microsoft pushed through Windows Update. A machine that hasn't been updated in years can report a build too old for the game's renderer to initialize.
The third cause is a launch option. This is the most common one for players who see the exact error text with the "-dx12 or -d3d12" wording, because that phrasing is the game telling you it tried the flagged renderer and failed. Removing the flag is the fix; hunting for driver updates first wastes time on the wrong problem.
| Symptom | Most Likely Cause | First Check |
|---|---|---|
| Game worked, then broke after a patch or reinstall | Saved launch option | Steam/Epic/launcher properties for -dx12 |
| Error on a pre-2012 GPU or Windows 7/8.1 PC | Hardware or OS limit | dxdiag feature level and OS build |
| Error on a modern GPU with current Windows | Driver or renderer mismatch | GPU driver version and game patch notes |
| Error only in one game, others run fine | That game's default renderer | Game's graphics settings file |
The table is a starting map, not a diagnosis. Run dxdiag first, then decide which row you're in; the steps that follow assume you've done that.
Clearing -dx12 and -d3d12 from Steam, Epic, and Desktop Shortcuts
Steam is the most common home for a stray launch argument. Open your Library, right-click the game, choose Properties, and look at the Launch Options field at the bottom of the General tab. If it contains -dx12, -d3d12, or a string like "-dx12 -high", delete the whole entry and close the window. Relaunch the game; Steam re-reads the field on every start.
Epic Games Store works differently. Click the three dots next to the game in your Library, choose Manage, and check whether a launch argument was added under the game's settings. Epic doesn't expose a single obvious field the way Steam does, so if you can't find one, the argument may be baked into a desktop shortcut instead.
Desktop shortcuts are the hidden path. Right-click the shortcut, choose Properties, and read the Target field. A shortcut that ends in something like "Game.exe" -dx12 is passing the flag directly to the executable, and the launcher never sees it. Delete everything after the closing quote, keep the quoted path intact, and click Apply.
For games launched outside a store, check the game's own config files. Unreal Engine titles often store renderer settings in a GameUserSettings.ini under Documents, and some store a default renderer in the engine ini. Search the game's install folder and Documents folder for the string "dx12" before assuming the launcher is at fault.
Removing the Argument from a Shortcut or Config File When the Launcher Isn't Involved
Some games don't use Steam or Epic at all. GOG Galaxy, EA App, Ubisoft Connect, and standalone installers each keep launch options somewhere different, and a few games read a command-line string from a text file next to the executable. If the error appears with no store client open, the flag lives in one of those places.
Start with the shortcut on your desktop and in the Start menu. Properties, then Target, is the fastest place to catch a flag that a store client never touched. If the Target field is clean, open the game's install directory and look for a file named something like launch.bat, run.bat, or a .url shortcut that wraps the executable.
Config files are the next layer. Games built on Unreal Engine 4 and 5 read DefaultEngine.ini and GameUserSettings.ini, and a line under a rendering section can force the DX12 RHI. Delete the line rather than editing it to DX11 unless you know the game accepts a DX11 value; some builds only recognize "Default" or leave the setting absent.
If you find nothing, the flag may be in a registry entry a launcher wrote. That's rare and risky to edit by hand. The safer route is to uninstall the launcher's per-game settings by removing and re-adding the game to the library, which resets the saved launch configuration without touching your save files, provided the saves live in the game's Documents folder rather than the install directory.
Checking GPU Feature Level and Windows Build in dxdiag
Press Win+R, type dxdiag, and press Enter. The DirectX Diagnostic Tool opens on the System tab, which lists the operating system, the processor, and the DirectX version. Write down the Windows build number and the DirectX version string; a DirectX 12-capable system typically reports DirectX 12 in that field even though the renderer is what games actually call.
Switch to the Display tab and read the Feature Levels line. A card listed with 12_1, 12_0, or 11_1 supports DirectX 12 at those feature levels. A card listed with only 11_0 or 10_1 can still run DirectX 11 games but will fail a DirectX 12 renderer call, which is exactly the error you're seeing.
Check the driver version on the same tab. An ancient driver on a DirectX 12-capable card can still fail the game's check, because the driver supplies the interface the game queries. Update through the GPU maker's own tool: Nvidia App or GeForce Experience for Nvidia cards, AMD Software: Adrenalin Edition for Radeon, and Intel Arc Control or the Intel Driver & Support Assistant for Intel graphics.
If dxdiag shows a feature level below 11_0, stop here. No launch option, driver, or Windows update will add DirectX 12 support to that hardware, and the game's own system requirements page will confirm the minimum GPU. Running without the flag isn't an option for a game that only ships a DirectX 12 renderer; you need different hardware.
Updating Windows When the DirectX 12 Component Is Missing or Outdated
Windows 10 and 11 deliver DirectX 12 as part of the operating system, and the pieces that games query are updated through Windows Update rather than a standalone installer. Microsoft's DirectX End-User Runtime package, still distributed for older titles, installs DirectX 9, 10, and 11 libraries and does not add DirectX 12 support. Downloading it won't fix this error.
Open Settings, then Windows Update, and install every pending update, including optional ones. Restart when prompted. On Windows 10, the DirectX 12 platform updates arrived through cumulative updates, so a machine that paused updates for a year or more can be several DirectX component versions behind even though the OS looks current.
Confirm the build after updating. Press Win+R, type winver, and note the version and build. Then re-run dxdiag and check that the DirectX version line reflects a current build. If Windows Update reports no updates but the build is old, the machine may be pinned to a release that's out of support; Microsoft's Windows lifecycle documentation lists which builds still receive updates.
After updating, relaunch the game without any launch flags. If the error persists on a DirectX 12-capable GPU with a current build and current driver, the problem is likely the game's own renderer or a corrupted install, not Windows. That's the point to verify the game files rather than keep patching the OS.
When the Game Only Has a DX12 Renderer and No DX11 Fallback
Some games ship with DirectX 12 as the only renderer. If that's the case, "try running without the -dx12 or -d3d12 argument" is advice that won't help, because the argument isn't what's failing; the hardware or the driver is. The game's store page and its system requirements list the API, and a requirements page that names DirectX 12 as the minimum tells you the fallback doesn't exist.
Check the game's official support page or patch notes. Developers sometimes add a DirectX 11 mode in a later patch, and a few add a compatibility flag that forces the older renderer. If the notes don't mention one, the community forums for that specific title are the next stop, but treat user-posted flags with caution; a flag that works in one build can break the next.
Verify the game files before concluding the renderer is the problem. Steam's Verify Integrity of Game Files and Epic's Verify option both rebuild missing or corrupted files, and a broken renderer DLL inside the install produces the same error as a hardware limit. The verification takes a few minutes on most connections.
If verification passes and the hardware is DirectX 12-capable, file a support ticket with the dxdiag report attached. The developer needs the feature level, driver version, and build number to tell whether the failure is on their side or yours, and a ticket with those three facts gets a useful answer faster than a general "game won't launch" report.
Edge Cases: Laptops with Dual GPUs, Windows on ARM, and Virtual Machines
Laptops with both integrated and discrete graphics are a frequent source of this error. The game may launch on the integrated GPU, which can have a lower feature level than the discrete chip, even though the discrete chip supports DirectX 12. Windows' graphics settings let you assign a specific GPU to a specific app: Settings, System, Display, Graphics, then browse to the game executable and set it to High Performance.
Windows on ARM machines run x86 games through emulation, and emulation doesn't always expose the full DirectX 12 feature set. Some games launch, some fail the check, and the outcome depends on the emulation layer and the game's own detection code. Microsoft's documentation on Arm emulation doesn't promise DirectX 12 parity, so treat any ARM result as a per-game variable rather than a fixed rule.
Virtual machines are the other edge case. A VM's virtual GPU typically exposes an older feature level unless GPU passthrough is configured, and most consumer VM software doesn't pass a physical GPU through to the guest by default. Running the game on the host OS, outside the VM, is the reliable path if the host hardware supports DirectX 12.
Cloud gaming and remote-play setups can also trip the check, because the streaming client's virtual display adapter is what the game sees. If the error appears only when streaming, test the same game locally to separate a streaming-layer problem from a game-layer one.
Settings That Revert After Every Restart and Other Failure Modes
A launch option you deleted can come back if the launcher re-syncs settings from the cloud. Steam Cloud syncs some per-game configuration, and Epic's cloud saves can restore a settings file that contains the flag. If the option reappears after every restart, disable cloud sync for that one game, delete the flag, and test a launch before re-enabling sync.
Games that write their own config on exit can also undo your fix. Some titles rewrite the renderer line in GameUserSettings.ini every time they close, and if the game itself defaults to DirectX 12 on a machine that fails the check, it will rewrite the flag on the next launch. In that case, edit the config while the game is closed, set the file to read-only in its properties, and test; a read-only config stops the game from overwriting your change.
Antivirus and anti-cheat software occasionally interfere with the renderer initialization. If the error appears only after a security update, check the game's support page for known conflicts and add the game folder to the security software's exclusion list as a test. Remove the exclusion if it doesn't change the outcome.
The failure case worth naming: a player with a DirectX 12-capable GPU, current Windows, and current drivers who deletes the flag and still sees the error. At that point the flag was never the cause, and the next diagnostic step is the game's own log file, usually in the game's install folder or Documents, which records which renderer call failed and why.
FAQ
Does reinstalling DirectX 12 fix this error?
No, because DirectX 12 isn't a separate download you can reinstall on Windows 10 or 11; it's a system component delivered through Windows Update. Microsoft's DirectX End-User Runtime package installs DirectX 9, 10, and 11 libraries for older games and does not add DirectX 12. The correct action is to install pending Windows updates and confirm the build number with winver, then re-check dxdiag.
Why does the error mention a command-line argument I never added?
The launcher or a shortcut is passing the flag on your behalf, often after a game update or a reinstall that restored a saved setting. Steam stores it in the per-game Launch Options field, and desktop shortcuts store it in the Target field. Check both before assuming the game itself is forcing DX12, because the flag's location determines which fix applies.
Can a DirectX 11-only GPU run a game that requires DirectX 12?
No. A GPU whose highest feature level is 11_0 cannot initialize a DirectX 12 renderer, and no flag, driver, or Windows update changes that hardware limit. The game's system requirements page names the minimum GPU, and comparing that against your dxdiag Display tab settles the question in under a minute.
Does the -dx11 flag work as a replacement?
Sometimes, but only in games that ship a DirectX 11 renderer and recognize the flag. Adding -dx11 to a game that only has a DirectX 12 path does nothing, and in some builds an unrecognized flag prevents launch entirely. Check the game's own documentation for the exact flag it accepts before adding one.
Is this error caused by a corrupted game install?
It can be. A broken renderer DLL inside the install produces the same message as a hardware limit, which is why verifying game files is a sensible step after the launch options are clean. Steam's Verify Integrity of Game Files and Epic's Verify option both rebuild missing files, and the check takes a few minutes on most connections.
Do dual-GPU laptops fail this check more often?
Yes, when the game launches on the integrated GPU instead of the discrete one. Windows' Graphics settings let you assign the game executable to High Performance, which routes it to the discrete chip and its higher feature level. Assign the specific executable rather than the launcher to avoid the launcher's own GPU choice overriding yours.
Can I run a DirectX 12 game in a virtual machine?
Usually not without GPU passthrough, because a VM's virtual display adapter typically exposes an older feature level than the host GPU. Consumer VM software doesn't pass a physical GPU through by default, so the game's DirectX 12 check fails inside the guest even when the host hardware supports it. Running the game on the host OS is the reliable path.
What if the error still appears after removing every flag?
Then the flag wasn't the cause, and the next step is the game's own log file plus a support ticket with the dxdiag report attached. Include the feature level, driver version, and Windows build number; those three facts let the developer tell whether the failure is in their renderer or your configuration. Without them, support can only offer generic troubleshooting.