Civ VI graphics-device error?Check the Steam shortcut first

If Civilization VI reports "No compatible graphics device found" on Windows, try launching it from your Steam library with DirectX 11 selected before changing drivers or buying a graphics card. 2K identifies a specific trap: a Steam desktop shortcut launches the DX12 version even when you have chosen DX11 as your preference. If DX11 also fails from inside Steam, collect the diagnostic information 2K requests rather than treating that shortcut behaviour as the whole diagnosis.

Start from Steam, then choose DX11

Open Steam's Library, select Civilization VI and press Play. Choose the DirectX 11 option in the launch menu. If Steam starts the game without showing that choice, right-click Civilization VI in the library, open Properties and select General. 2K says this is where you can change the preferred launch version. This procedure applies to the Windows Steam edition; it is not a console or native Linux instruction.

For this check, use the library Play button again, rather than your desktop shortcut. The publisher says shortcuts take the default option at the top of Steam's launch list, which is DX12 for Civ VI. Remembering DX11 does not change that shortcut's behaviour. If the game now reaches its main menu, the immediate launch test has succeeded. Keep using Steam to start the DX11 version and check that your usual game session also works.

Separate the launcher change from hardware support

The old 2K Launcher is no longer the place to select the graphics version. PC Gamer reported its removal from Civ VI's Steam edition in August 2024 and noted that the choice had moved into Steam. That change explains why instructions telling you to find a DX11 button in the old launcher are no longer the right route. Reinstalling that launcher is not part of 2K's current graphics-device troubleshooting.

DX11 is still a compatibility requirement, not a way to make every graphics card suitable. The Windows Steam listing specifies DirectX 11, and 2K's error guidance distinguishes a GPU lacking DX11 support from an attempt to use DX12 without compatible hardware. Switching the launch choice can address the latter situation; it does not add missing hardware capabilities. Nor does a successful launch prove that DX11 will give you a higher frame rate than DX12.

Record the result when DX11 still fails

If the same message appears after launching DX11 inside Steam, record that result along with the exact error text. The shortcut explanation no longer accounts for the whole problem. 2K's next step for this error is a support ticket with DxDiag and MSInfo reports. Give support the distinction that matters: whether only the desktop shortcut failed, whether DX12 failed from the library, or whether both library choices failed.

Microsoft's DirectX Diagnostic Tool can collect the PC's sound and video information. Search Windows for dxdiag and open it, then use the System tab to read the DirectX version under System Information. If it asks to check whether drivers are digitally signed, Microsoft recommends choosing Yes. The Windows DirectX version is useful information to supply, but 2K separately requires suitable graphics hardware. Do not turn that one number into a guaranteed compatibility verdict.

Send the reports, keeping your launch choice reversible

In dxdiag, wait for information collection to finish and choose Save All Information. Save the text file somewhere easy to find. Then press Windows and R, enter msinfo32 and open System Information. Choose File, then Export, and save that report too. 2K asks that "search selected category only" and "search category names only" are unchecked. Wait for the export to finish before closing the tool.

Attach both reports to the support ticket using Add File, with your launch-test results and a screenshot of the error if available. Keep any further changes separate so you can describe what affected the result. To revisit the graphics choice, return to Civilization VI's Properties and General page in Steam. Changing that preference is reversible; deleting saves, replacing DLLs or forcing software rendering is not needed for this documented first check.