You already know the basics. Right‑click the executable, hit Run as administrator, and hope the game stops being stubborn. That trick works for half the launch failures out there. But if you are here because it did not work, you are dealing with a different class of problem.
Running a game as admin is not a magic wand. It is a permission elevation that bypasses User Account Control (UAC) restrictions, gives the process write access to protected folders like %ProgramData%codecodecodecode and C:Program Filescodecodecodecode, and unlocks registry keys the game might need to create on first launch. Death Stranding 2, like many Kojima Productions titles, tries to write configuration files, save data, and shader caches into locations that a standard user token cannot touch. When that write fails, the game simply exits before a window appears.
But the real trouble starts when admin elevation alone still leaves you staring at a black screen or a silent process in Task Manager. That is where the non‑obvious culprits live.
Why “Run as Administrator” Actually Works — And When It Doesn’t
UAC creates a split‑token environment. Without admin rights, the game runs with a filtered access mask. It cannot write to its own installation folder unless the folder permissions were explicitly changed during installation. Most Steam titles are installed under C:Program Files (x86)Steamsteamappscommoncodecodecodecode, a directory that is read‑only for standard users. When Death Stranding 2 tries to cache shaders or update its config files there, the write fails silently. The game then assumes a critical corruption and terminates.
Elevating to admin gives the process the original unfiltered token. Writes succeed. The game launches.
Still, many users report that admin mode does nothing. Three reasons explain that failure:
- The game is already being blocked by another component before it even checks permissions. Your antivirus, Windows Defender real‑time scanning, or a firewall rule can intercept the process during its initial handshake with Steam or the anti‑cheat system. Admin rights do not override these blocks.
- Corrupted Visual C++ or DirectX runtimes. Admin elevation cannot fix a missing
VCRUNTIME140.dllcodecodecodecode or a broken DirectX state. The game will crash just as fast. - The anti‑cheat or DRM layer is the one failing. Denuvo, or whatever protection Kojima Productions uses, might require elevated privileges to install its kernel‑level driver. But if that driver is blocked by Windows Defender Application Guard or Core Isolation, admin mode will not help.
So admin rights are a prerequisite, not a solution. If you have already set the executable to run as admin and the game still refuses to open, you must look deeper.
The Hidden Failures That Keep the Game Closed
Start with Event Viewer. That is the single most underused tool for diagnosing launch crashes. Press Win + R, type eventvwr.msccodecodecodecode, and navigate to Windows Logs > Application. Look for Error events with source “Application Error” or “.NET Runtime” that time‑stamp with your launch attempt. The Faulting module path tells you what actually broke — a missing DLL, an outdated GPU driver, or an overlay injector.
Process Monitor (ProcMon) from Sysinternals is even more surgical. Filter by the game’s executable name, launch it, and watch which registry keys or files return ACCESS DENIEDcodecodecodecode. You will often see the game trying to write to HKLMSoftwareKojima Productionscodecodecodecode or C:ProgramDataDeath Stranding 2codecodecodecode. If those writes fail despite admin rights, you have a permission inheritance problem from a prior installation or a security policy.
Another silent killer: fullscreen optimizations. Windows 10 and 11 apply them by default. They can cause the game to hang during the swapchain creation. Disabling them is straightforward, but doing it through the compatibility tab alongside admin mode can create a conflict. Instead of ticking both boxes, try only disabling fullscreen optimizations without admin. Or the reverse. Some engines handle the combination badly.
GPU driver state is another blind spot. If you recently updated drivers without a clean install, leftover shader caches or registry entries from the previous version can corrupt the initialization of Death Stranding 2. Use DDU (Display Driver Uninstaller) in Safe Mode, then install the latest driver fresh. Then try launching with admin rights.
Steam overlay, GeForce Experience overlay, Discord overlay — all of these inject DLLs into the game process. Admin mode does not grant those injectors any additional rights, but if an overlay crashes during injection, it can bring the game down with it. Disable all overlays temporarily. Test with admin. Re‑enable one at a time.
Advanced Diagnostics: Tools Beyond the Basic Checklist
You have already verified integrity of game files, updated Windows, disabled startup apps via msconfigcodecodecodecode, and run the SFC scan. Fine. Now try the things the tutorials skip.
Dependency Walker is a classic tool for finding missing DLLs. Open the game’s .execodecodecodecode with it and look for red‑marked modules. A missing d3dx9_43.dllcodecodecodecode or xinput1_3.dllcodecodecodecode can be fixed by reinstalling DirectX runtime from Microsoft’s web installer. Do not rely on Windows Update for this.
Graphics preference override for laptop users with dual GPUs is often set incorrectly. Even after forcing high‑performance mode in Windows Graphics Settings, the game might still try to launch on the integrated GPU. That can cause an immediate exit because Death Stranding 2’s shader compiler expects a discrete GPU. To verify, open Task Manager’s Performance tab while launching – if GPU 0 (Intel) spikes and GPU 1 (NVIDIA/AMD) stays idle, the override failed. Use NVIDIA Control Panel or AMD Software to set the game manually.
Virtual memory starvation is another overlooked cause. Death Stranding 2’s open world streams massive amounts of data. If your pagefile is too small or on a nearly full drive, the allocation fails and the process crashes before the main menu appears. Set a custom pagefile size to 1.5× your RAM on the fastest SSD you have. Reboot. Test with admin.
The Security Trade‑Off
You already know that running a game as administrator permanently is a bad idea. If a remote code execution exploit hits the game, the attacker gets system‑level access. But for a launch fix, you can set it temporarily, then remove the flag once the game runs.
What many experienced users miss: leaving the “Run as administrator” checkbox enabled can actually cause problems later. Some games that write logs or save files to AppDataLocalcodecodecodecode will change ownership of those folders to the administrator account. When you later launch without admin, the game cannot read its own saves. Sudden “Save corrupted” errors appear. The fix is to take ownership of the game’s save folder and grant Everyonecodecodecodecode full control.
Also, Windows 11’s Memory Integrity (Core Isolation) blocks kernel‑level drivers from loading. Denuvo and other anti‑tamper software sometimes rely on such drivers. If the game fails to start with admin rights and you see a “Secure Boot” or “Driver not signed” error in Event Viewer, you might need to disable Memory Integrity temporarily. That is a security downgrade, so do it only for testing.
The Last Resort
One edge case that the general guides ignore: the game might be crashing because of a race condition with Steam’s login process. If you have two‑factor authentication or Steam Guard enabled, Steam itself might not be fully ready when the game calls SteamAPI_Init()codecodecodecode. Running the game as admin does not speed up Steam. Try launching Steam as admin first, then the game. Or disable Steam overlay completely — it has been known to block the game from initializing the Steamworks API.
If nothing else works, move the entire game installation to a different drive. Permissions can get locked at the partition level due to BitLocker or NTFS encryption. Fresh install on a non‑system drive often bypasses weird permission inheritance.
Eventually, a title update from Kojima Productions might fix the root cause. Until then, the admin flag is your first step, not your last. The real fix is in the diagnostics you run after it fails.
