Fallout New Vegas Won’t Launch | Quick Fix Guide

Few things sting like clicking “Play” and getting nothing. If the launcher closes, a black screen hangs, or the game bounces back to desktop, you can fix it with a short, methodical run-through. This guide walks you through fast checks first, then deeper steps that solve most start-up failures on Windows 10 and Windows 11. The fixes apply whether you use Steam, GOG Galaxy, or a manual install.

Triage Steps That Save Time

Work in order. After each step, try to launch the game. If it starts, stop there and play.

Symptom	Likely Cause	Fast Fix
Nothing happens after “Play”	Corrupted or missing game files	Run a file verification in your client
Instant crash with missing DLL message	Old Visual C++ or DirectX components	Install VC++ 2010 (x86) and the legacy DirectX package
Black screen, then desktop	Bad INI or wrong GPU/display pick	Delete FalloutNV INIs; relaunch to regenerate
Launcher opens, game never does	Overlay or antivirus interference	Disable overlays; add exceptions; run the EXE as admin
Hangs after Bethesda logo	Mod loader or ENB conflict	Launch the vanilla EXE; move d3d9/dxgi files out
Crashes only on first boot	INI cache or codec hiccup	Reboot Windows; delete INIs; try borderless window

Troubleshooting When New Vegas Fails To Launch On PC

Start with clean, reversible actions. These don’t touch saves and fix the bulk of cases.

1) Verify Game Files

File verifications replace damaged or missing assets and reset a surprising number of launch stalls. In Steam, open the game’s Properties > Installed Files and run the integrity check. In GOG Galaxy, use Manage Installation > Verify/Repair. This process takes a few minutes on HDDs and less on SSDs.

Link for Steam users: verify integrity of game files.

2) Refresh The Configuration Files

Bad INIs block launch more often than you’d think—especially after driver swaps, display changes, or mod toggles. Close your client. Go to Documents\My Games\FalloutNV\ and delete Fallout.ini and FalloutPrefs.ini. Don’t touch your saves. Relaunch to generate new ones. If you use a laptop or multi-monitor setup, open the launcher’s Options and confirm the right GPU and resolution before hitting Play.

3) Install Required Runtimes

The game was built against older Microsoft libraries. A modern PC may be missing them after a fresh Windows install.

• Install Visual C++ 2010 (x86)—this resolves common MSVCP100.dll and MSVCR100.dll errors.
• Install the legacy DirectX runtime (June 2010)—adds D3DX and XAudio components many classics depend on.

Grab VC++ here: Visual C++ 2010 SP1 Redistributable. For DirectX, run the offline “June 2010” package if you still see D3DX or XInput errors after VC++ is in place.

4) Run The Game As Administrator And Tweak Compatibility

Right-click FalloutNV.exe in the install folder, then Properties > Compatibility. Check “Run this program as an administrator.” If launch still fails, try “Disable fullscreen optimizations.” Use a compatibility mode only if nothing else moves the needle; the title runs fine on current Windows without it once prerequisites are set.

5) Turn Off Overlays And Capture Hooks

Steam, GeForce Experience, Radeon Software, Discord, MSI Afterburner, and FPS counters can hook DirectX at launch. Turn them off for a test. If the game starts, re-enable only what you need.

6) Reboot, Then Try Windowed Or Borderless

A simple reboot clears driver restarts and pending updates. If the game still balks, set the launcher to Windowed, choose a native resolution, and enable borderless through your mod manager or a small helper tool. Windowed + borderless avoids many alt-tab and multi-monitor quirks.

Fixes For Steam And GOG Installs

Different storefronts lay down files a bit differently. Here’s what moves the needle for each.

Steam-Specific Checks

• Confirm the install path isn’t inside a protected Windows folder. Default SteamLibrary paths are fine.
• Clear Steam’s download cache, then relaunch the client and re-run the file check.
• If you see “disk write” prompts during updates, change the game’s install drive, or repair the library folder in Steam’s Settings.

GOG Galaxy Tips

• Use Manage Installation > Verify/Repair to fix a missing registry key that sometimes blocks launch.
• If you installed the standalone (offline) installer, re-run the setup and pick “Repair.”

Driver, Audio, And Display Gotchas

New drivers bring better stability, but a mid-install hiccup can leave stale components that a reboot and a clean reinstall resolve.

Graphics Drivers

Update to the current WHQL driver from NVIDIA, AMD, or Intel. If launch problems appeared right after a driver update, use the previous known-good version. A clean install option removes leftovers that can break older DirectX paths.

Audio Stack

If you use USB DACs, VR headsets, or virtual audio tools, set your default device to standard speakers, then launch the game. Once it loads, you can switch back.

High-DPI And Multi-Monitor

On very high DPI displays, Windows can scale the window oddly. In the EXE’s Compatibility settings, try “High DPI scaling override” with Application selected. If you have two GPUs (common on some laptops), force the dedicated GPU for the game in your graphics control panel.

When Mods, ENBs, And Script Extenders Are In The Mix

Mod loaders and ENBs add a layer that’s great for stability once tuned, but they can also stop the game from launching if a file goes missing or the load order breaks.

Start Vanilla, Then Add Layers Back

1. Temporarily move d3d9.dll, dxgi.dll, ENB files, and ReShade files out of the game folder.
2. Launch the base EXE from the install directory. If it starts, you’ve isolated the conflict.
3. Restore tools one at a time. Launch after each addition to spot the blocker.

Script Extender Checks

If you use a script extender, match its version to the game’s build and your runtime libraries. Missing VC++ files stop the extender from loading, which looks like a silent crash. Reinstall the extender last, after VC++ and DirectX are in place.

Resetting The Launcher And INIs Properly

Here’s a clean reset that avoids collateral damage to saves and mods.

1. Back up Documents\My Games\FalloutNV\Saves\.
2. Delete Fallout.ini and FalloutPrefs.ini in the same folder.
3. Empty the game’s Video cache in AppData\Local\FalloutNV if present.
4. Launch the launcher, open Options, confirm your GPU, pick a native resolution, and click OK before hitting Play.

Deeper Repair Steps When The Basics Don’t Work

If you’ve made it here, set aside ten minutes for a tidy rebuild. It’s still quick and fixes stubborn cases.

Repair The Install Folder

• Uninstall the game from your client.
• Manually delete the leftover game folder to remove stray files from prior mods or reshade tools.
• Reinstall to a simple path such as SteamLibrary\steamapps\common\Fallout New Vegas.

Install Legacy Runtimes In This Order

1. Visual C++ 2010 x86 (SP1 build).
2. Legacy DirectX “June 2010” package.

Reboot Windows after both. Then try the vanilla EXE directly from the folder before you open your client. If the EXE starts but the client button still fails, the client overlay or a command-line parameter is the blocker.

Check For File Locks

Security tools can quarantine the EXE or block write access to the install directory. Add the game folder and your client folder to the allow list. If the game launches once those exceptions are in place, you’ve found the culprit.

Create A Fresh Windows User Profile (If Needed)

Rarely, profile-level permissions or shell extensions trip the launcher. Creating a new local user and testing the game there is a quick way to confirm. If it works on the new profile, migrate your documents and keep playing.

Clean Reinstall Checklist

Use this when you want a near-fresh slate without touching saves.

Step	What To Do	Why It Helps
1	Back up saves from Documents\My Games\FalloutNV\Saves	Prevents data loss during cleanup
2	Uninstall from Steam or GOG	Removes registered files and entries
3	Delete leftover game folder	Clears mod hooks and stray DLLs
4	Reboot Windows	Releases file handles and drivers
5	Install VC++ 2010 x86, then legacy DirectX	Restores classic dependencies
6	Reinstall the game to a simple path	Avoids permission issues
7	Launch the EXE once as admin	Builds new INIs with correct GPU
8	Re-enable overlays one by one	Identifies hook conflicts

Common Edge Cases And Quick Wins

Wrong Monitor Or Resolution

On multi-display rigs, the launcher sometimes picks the wrong screen. Open Options on the launcher, select the right monitor, and set a supported resolution. If you go above native, the game may stall during creation of the swap chain.

32-Bit Limitations

This is a 32-bit title. Keep background RAM use in check while testing (web browsers with dozens of tabs, video editors, and VMs eat headroom). A lean desktop session often turns a crash-on-start into a normal boot.

Saves Load But New Game Crashes

That points to a scripted mod or a codec pack. Try a new game with mods disabled. If a new game works, your load order needs a pass or a missing extender file.

Prevent Launch Problems Going Forward

• Keep a copy of clean INIs that launch correctly; stash them in a “Good INIs” folder and swap them back if needed.
• Update graphics drivers on a steady cadence; skip optional betas unless you’re testing a fix.
• Change one thing at a time when adding mods; launch between additions so you always know what broke.
• Use borderless windowed when streaming or using multiple overlays to avoid hook clashes.

When You Should Reinstall Windows Components

If the game still refuses to start after the steps above, reinstalling core runtimes is worth it. Install VC++ 2010 x86 again, then the legacy DirectX package, and reboot. These two packages solve a high share of stubborn DLL errors tied to older games. If you also run new releases, adding the current “VS 2015–2022” VC++ redist is safe and can improve compatibility across your library.

Steam And GOG Repair Links You’ll Use Often

You already saw the Steam integrity page above. Keep that handy. If you use GOG, open Galaxy, click the game, then the Customize or Manage button, and run Verify/Repair. Both tools save hours of manual hunting when a file goes missing after a crash or power cut.

Wrap-Up: Order Of Operations That Works

1. Verify files in your client.
2. Delete the two INIs in Documents\My Games\FalloutNV.
3. Install VC++ 2010 x86, then legacy DirectX; reboot.
4. Run FalloutNV.exe as admin; pick the right GPU and resolution in the launcher.
5. Disable overlays and antivirus hooks; try borderless windowed.
6. Remove ENB/ReShade files; reintroduce mods one at a time.
7. Do a clean reinstall only if all else fails.

If you follow that list in order, you’ll almost always get from a dead click to the Mojave in one sitting.