Fallout New Vegas Won’t Load | Quick Fixes Guide

Troubleshooting / By

For Fallout: New Vegas not launching, restart the client, verify files, update drivers, and add the 2010 DirectX and VC++ runtimes.

When the Mojave refuses to boot, the fix is usually a short chain of checks. Start with the client, then the install, then the system. Most players get back in by verifying files, cleaning launch flags, and restoring the legacy graphics runtimes the game expects. The steps below move from fastest to deeper fixes, with clear cues for Steam, GOG, Epic, and Windows.

Why New Vegas Won’t Launch On PC (And Fast Checks)

The game targets older APIs and file layouts. A missing DirectX 9 component, a blocked executable, or a corrupt shader cache can stop the splash screen cold. Mods and script extenders add another layer: a broken plugin or load order will stall the executable before a window appears. Use this table to map the symptom you see to the first action that saves you time.

Quick Map Of Symptoms To Fixes

Symptom Likely Cause First Fix To Try
Play button flips to “Running,” then back Corrupt files or missing redistributables Run Verify integrity of game files in the client
No window; brief hourglass Blocked executable or overlay conflict Run the .exe as admin; disable overlays; whitelist in AV
Logo shows, then crash to desktop DirectX 9 or VC++ runtime missing Install June 2010 DX9 and VC++ redistributables
Modded build hangs at start Broken plugin, wrong load order, or script extender mismatch Launch vanilla; test NVSE; isolate by halves
“Disk write” or update error Client cache or drive permissions Clear client download cache; check drive and folder ACLs
Black screen with audio Windowed/fullscreen mode or GPU driver Toggle to borderless/windowed; update drivers; reset ini

Start With The Client: Steam, GOG, And Epic Steps

Kill any stuck processes first. Close the launcher, end leftover tasks, and reboot the PC to clear handles and overlays. Then fix the install from the client you use.

Steam

  1. Right-click the title in Library → Properties → Installed Files → Verify integrity of game files. This replaces missing or altered data and redownloads the executable if needed. You can also use Steam’s “Installed Files” tab to move the install to a healthy drive.
  2. In Properties → General, remove launch options you no longer want. Unload overlays (Steam, GPU, capture, Discord) for a clean test.
  3. Run Steam as admin for one launch cycle if the folder sits on a protected path or network share.

GOG Galaxy

  1. Manage Installation → Verify / Repair. GOG will scan and re-fetch damaged data.
  2. Disable Overlay in Galaxy for a test run.

Epic Games Launcher

  1. Library → three dots next to the game → Manage → Verify.
  2. Unplug controllers for a test boot; some users see input hooks stall the first frame. Add the launcher and the game folder to AV exclusions, then try again.

Tip: One or two files may “fail to verify” on a healthy setup because the client rewrites config at launch. That message alone isn’t proof of damage; retest before chasing ghosts.

Repair The Install: Redistributables And DirectX 9

This title was built for DirectX 9 and uses runtime files that aren’t bundled with modern Windows. You need two things on many fresh systems: the June 2010 DX9 package and the Visual C++ redistributables. Install both, then reboot.

Install Legacy Graphics Files

  • DirectX End-User Runtimes (June 2010) — installs the D3DX and XAudio bits many older games call.
  • Visual C++ redistributables — install the 2010, 2012, 2013, and the latest supported package. The modern roll-up lives on Microsoft’s docs hub.

Reset Game Config And Render Mode

  1. Delete or rename the Fallout.ini and FalloutPrefs.ini under Documents\My Games\FalloutNV\. The game will rebuild clean files on next launch.
  2. Force a first boot in windowed or borderless mode via the launcher, then switch to your preferred fullscreen after a stable run.
  3. If you use multiple monitors, set the main display as primary, run once, then restore your layout.

Fix Permissions, Paths, And Overlays

Executable blocks and overlays are repeat offenders. Clear them methodically.

  • Run as admin: Right-click FalloutNV.exe → Properties → Compatibility → check Run this program as an administrator.
  • Unblock: If Windows flagged the file after a move, Properties → General → Unblock.
  • Folder ACLs: Avoid Program Files for modded setups. If needed, give your user Modify rights on the game folder.
  • Disable overlays: Turn off Steam, Xbox Game Bar, GeForce/Adrenalin overlay, and recording tools for a test launch.
  • Antivirus: Add the game folder and client to the allowlist. Some scanners sandbox new executables until they “learn” them.

Drivers, Codecs, And GPU Settings

Out-of-date drivers and forced control-panel flags can trip this engine. Update, then trim down overrides.

  1. GPU drivers: Install the latest stable driver from NVIDIA, AMD, or Intel. Choose a clean install to wipe old profiles.
  2. Control panel: Remove per-app overrides like forced anti-aliasing, shader cache off, or strange V-Sync rules. Start with defaults.
  3. Codecs: If a third-party codec pack is installed, disable it for a test run. Bink videos can hang on bad decoders.

Modded Builds: NVSE, Load Orders, And 4GB Memory

Mod frameworks add stability and features, but the launch chain must match.

  • Baseline test: Move the Data folder mods out temporarily (or toggle your mod manager off) and launch the base game. If it starts, add mods back in halves until the hang returns.
  • Script extender: Ensure your NVSE version matches the game’s executable. Launch through the NVSE loader when required; launching the base .exe can crash script-dependent builds.
  • Large-address aware: A 4GB-aware executable lets the game use more memory on 64-bit Windows, which reduces boot crashes on heavy mod lists.
  • Load order: Use your mod manager’s sorter, then scan for missing masters. One missing dependency will stop the game before a window opens.

Clean Up Launch Flags And INI Edits

Old tweaks stick around and break new setups. Remove them and re-add only what you need.

  1. Clear custom flags in the client’s launch options. The engine can reject odd combos like forced -d3d9ex with certain overlays.
  2. Avoid editing Fallout_default.ini inside the install. Keep changes in the user folder copies that regenerate safely.
  3. Keep refresh rate and resolution sane for the first boot. After a stable run, match your monitor’s native settings.

Common Windows Issues That Block A Launch

If the game won’t start on a clean install, the OS may be the gatekeeper. These fixes target the usual suspects.

Safe Mode Checks

  • Clean boot: Use msconfig to disable non-Microsoft services and startup apps, then test. Add back in batches to find the stopper.
  • SFC and DISM: Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated terminal to repair system files.
  • Updates: Install pending Windows updates, then reboot twice.

Storage And Path Health

  • Free space: Keep at least 15–20 GB free on the game drive to let shaders and caches breathe.
  • Drive errors: Run chkdsk /f or your SSD’s vendor tool if the client reports write errors.
  • Short path: Avoid extremely long mod paths; some tools balk at deep directories.

When The Client Says “Running” But Nothing Appears

This pattern points to a silent crash on initialization. Work the chain top to bottom:

  1. Kill all overlays and RGB/monitor utilities.
  2. Install the June 2010 DX9 package and the VC++ runtimes, then reboot.
  3. Delete the My Games\FalloutNV config files to regenerate defaults.
  4. Verify files in your client to replace any bad assets.
  5. Launch the executable directly from the install folder as admin. If that works, the client hook is the problem; reinstall the client or clear its cache.

Targeted Fixes For Frequent Error Patterns

Not every system throws a clear code, so match what you see here and apply the direct fix. These address the highest-volume launch stoppers.

DirectX And VC++ Missing Or Corrupt

Install the DX9 June 2010 package and the Visual C++ redistributables, then restart. If you saw msvcr or msvcp file names in a crash log, this step often resolves it.

Overlay Hook Conflict

Disable Steam Overlay, Xbox Game Bar, GeForce Experience/Adrenalin overlays, Discord, MSI Afterburner/RivaTuner, ReShade, and any capture tools. Retest after each toggle so you can keep the ones that behave.

Ini Settings Causing A Black Screen

Switch to windowed or borderless mode in the launcher, set the resolution to 1280×720 for the first boot, and let the game reach the main menu. After that, set your native resolution and preferred mode.

Second Table: Fix Paths You’re Likely To Need

These locations help you reset configs, run the executable directly, or add allowlist entries in your antivirus. Keep them handy.

Item Typical Path What To Do There
User configs Documents\My Games\FalloutNV\ Delete Fallout.ini and FalloutPrefs.ini to rebuild
Steam install Steam\steamapps\common\Fallout New Vegas\ Run FalloutNV.exe as admin; check file presence
Client cache Steam: Steam\userdata\<id>\config; Epic/GOG in AppData Clear download cache; restart the launcher

Linux And Steam Deck Notes

On Proton, pick a stable Proton version in Steam’s Compatibility menu, then retest. If you use community DirectX wrappers, keep them one-per-game to avoid mixed d3d9 layers. For Deck, set the title to borderless/windowed first to sidestep resolution handoffs during the opening video.

When You Should Reinstall

Reinstall only after you’ve verified files and repaired the runtimes. If you do need a fresh install:

  1. Back up your saves from Documents\My Games\FalloutNV\Saves.
  2. Uninstall from the client, then delete any leftover files in the install folder to flush mods and stray DLLs.
  3. Install to a short path like D:\Games\FNV\ if you mod often.
  4. Run once unmodded to main menu, quit, then add tools and mods in small batches.

Final Pass: Clean Boot And Fresh Config

If nothing above moves the needle, strip the system to basics for one run: clean boot, overlays off, fresh configs, runtimes reinstalled, and the client launched as admin. Most launch failures clear in that state. From there, re-enable services in groups until the blocker shows itself.

Helpful Official References

Two official resources you’ll use during these steps:

Checklist You Can Work Top To Bottom

  1. Reboot the PC and close all overlays.
  2. Verify files in your client.
  3. Install June 2010 DX9 and the VC++ redistributables; reboot.
  4. Delete the user .ini files to regenerate clean configs.
  5. Run the executable as admin from the install folder.
  6. Update GPU drivers and reset control-panel overrides.
  7. Test vanilla; then add mods back in halves if you use them.
  8. Clean boot Windows and try again if the client still shows “Running.”