Yes—if Dishonored 2 won’t launch on PC, the fastest fixes are verifying files, updating drivers, and repairing game prerequisites.
When Dishonored 2 refuses to start—no window, a brief “Preparing to Launch,” or a silent crash—the cause is usually missing files, blocked permissions, or a graphics driver problem. This guide gives you clear, safe steps that solve most launch failures without risky tweaks or guesswork.
Quick Fixes That Solve Most Launch Errors
Work through these in order. Each step targets a common root cause and takes only a few minutes.
- Restart the PC and your game client, then try again.
- Verify the game files in Steam or Epic to replace damaged data.
- Repair or install Visual C++ runtime packages (x64 and x86).
- Update or clean-reinstall your graphics driver.
- Launch once as administrator with all overlays off.
- Allow the game through Controlled Folder Access in Windows Security.
Dishonored 2 Not Opening: Symptoms, Causes, Fixes
Use this matrix to match what you see to the fix that usually works.
Symptom | Likely Cause | What To Try |
---|---|---|
“Preparing to Launch” then nothing | Damaged install or blocked dependency | Verify files; repair VC++; disable overlays |
Process shows in Task Manager, no window | Overlay conflict or permission block | Run as admin; turn off Steam overlay; whitelist game |
Instant crash to desktop | Old GPU driver or bad cache | Clean-install driver; delete config cache; verify files |
Black screen with music | Resolution mismatch | Force borderless window from launch options |
Disk write or update loop | Client can’t write to the folder | Run client as admin; move install; check storage |
How To Verify Game Files (Steam Or Epic)
Corrupted or missing assets sit near the top of the list for games that won’t start. File verification replaces only what’s broken and keeps your saves. On Steam, you can follow the platform’s official steps for a file integrity check, then re-launch the game once the scan completes.
On Steam
- Open Library → right-click Dishonored 2 → Properties.
- Open Installed Files → click Verify integrity and let it finish.
On Epic Games
- In Library, click the three dots on Dishonored 2.
- Click Manage → Verify, then try launching again.
Publisher guidance mirrors this sequence for stubborn “won’t launch” cases; see the official PC launch help page if you want a second checklist.
Repair The Game’s Required Runtimes
Dishonored 2 relies on Microsoft Visual C++ runtime files. When those are missing or corrupted, the game can fail with no message, or you may see a missing DLL prompt.
- Open Windows Settings → Apps → Installed apps.
- Find “Microsoft Visual C++ 2015–2022 Redistributable.” Click each entry → Modify → Repair.
- If you don’t see those entries, install the current x64 and x86 packages from Microsoft’s site, then reboot.
After repair or install, launch the game again. If you still get no window, continue to drivers.
Clean-Install Your Graphics Driver
A partial driver update or a stale shader cache can stop the renderer from creating a device at startup. A clean install refreshes those components.
NVIDIA
- Grab the latest Game Ready Driver for your card from NVIDIA’s download page.
- Run the installer → choose Custom → check Perform a clean installation → finish and reboot.
AMD
- Use AMD Cleanup Utility to remove older driver files in Safe Mode when prompted.
- Install the current Adrenalin package, then reboot and test the game.
If a driver update landed right before the issue began, test the previous version. Rolling back is a quick way to confirm a driver conflict.
Disable Overlays And Run Once As Admin
Overlays hook into the game process, which can block the window from appearing. Turn them off and try one elevated launch.
- In Steam: Settings → In-Game → uncheck “Enable the Steam Overlay while in-game.”
- Close third-party OSD and capture tools while testing.
- Right-click Dishonored2.exe → Run as administrator one time.
Allow The Game Through Controlled Folder Access
Windows Security can protect folders that games need to write to. If Controlled Folder Access is on, the game may fail without a clear prompt. Add the game’s EXE to the allowed list and try again.
- Open Windows Security → Virus & threat protection → Ransomware protection.
- Toggle Controlled folder access or select Allow an app through and add Dishonored2.exe.
If you’re using a third-party antivirus, add the game folder to its allow list, then retest.
“Dishonored 2 Won’t Launch” Fixes For Tricky Cases
Force Borderless Window From Launch Options
Resolution or refresh mismatches can leave you staring at a black screen. In Steam → Properties → General → Launch Options, add: -windowed -noborder
. If your launcher offers a safe mode flag, try that once as well.
Delete Local Config Cache
Old settings can conflict after a driver change. Back up, then remove the config folder so the game rebuilds it on next launch.
- Path sample:
%USERPROFILE%\Saved Games\Dishonored2
- Delete or rename
BaseEngine.ini
and similar cache files if present.
Move The Install To A Simple Path
Very long paths or synced folders can cause access trouble. Move the game to a short path like D:\Games\Dishonored2
from your client’s move tool and test again.
Check Storage And Disk Health
If the client reports disk write errors or loops on updates, free space, run CHKDSK, and try another drive. Large installs can stall on near-full HDDs.
Turn Off Third-Party Injectors
RGB suites, capture software, and monitoring tools can collide with startup. Disable them while testing. Add them back one by one after the game launches cleanly.
Close Variant: Dishonored 2 Not Launching On PC — Tested Steps
Still getting no window? Work through this checklist to catch edge cases that trip Arkane titles on some setups.
- Run Steam as admin. Launch the game from the Library page, not a desktop shortcut.
- Clear shader caches. In your GPU software, clear caches, then reboot.
- Reinstall DirectX components. Run the redist in the game’s _CommonRedist folder if present.
- Test without controllers. Unplug gamepads to rule out input hooks at startup.
- Create a fresh Windows user. Try one launch there to rule out profile issues.
- Clean boot. Start with non-Microsoft services disabled, then retry the game.
Error Messages And What They Mean
Some launch failures throw an error code or a missing DLL hint. Use this quick lookup to pick the next step fast.
Error Text | What It Implies | Best Next Step |
---|---|---|
MSVCP140.dll or VCRUNTIME missing | VC++ runtime isn’t installed | Install latest VC++ x64 and x86 |
Access denied / disk write error | Folder protection or drive problem | Allow app; run as admin; check disk |
Fatal error on startup | Driver conflict or corrupted files | Clean-install GPU; verify files |
Black screen no UI | Overlay or resolution mismatch | Disable overlays; force borderless |
When To Reinstall Or Move The Game
If none of the steps above help, a controlled reinstall can clear stubborn corruption while keeping saves safe.
- Back up the Saved Games folder for Dishonored 2.
- Uninstall from the client. Delete any leftover folders in the install path.
- Reinstall to a different drive or a short path, then verify files before first launch.
Why These Steps Work
Launch failures usually trace back to two roots: the game can’t load a dependency, or Windows blocks a needed action. Verifying files restores missing assets. VC++ repair brings back the runtime the game calls at startup. Clean driver installs clear broken hooks and shader caches that stop rendering. Turning off overlays removes extra hooks. Allowing the EXE in Windows Security lets the game write settings and caches without being flagged.
Safe Tweaks You Can Keep
- Borderless window avoids many full-screen handshakes and makes Alt-Tab smoother.
- Clean driver installs every few months keep shader caches healthy.
- Short install paths prevent odd permission behavior on synced folders.
Still Stuck? Quick Checklist
- Files verified with zero errors
- Latest VC++ x64 and x86 installed
- Fresh GPU driver, clean install
- No overlays or injectors active
- EXE allowed through Controlled Folder Access
- Game launched once as admin
- Config cache rebuilt
- Install moved off long or synced paths