COD Vanguard Not Launching on PC Fix: A Complete Troubleshooting Guide

COD Vanguard not launching on PC? Here’s how to get back into the game when clicking Play leaves you staring at your desktop.

You click Play, and nothing happens. Or the Battle.net or Steam window flickers, a black screen shows up for a second, and then you’re staring at your desktop again like nothing ever tried to open. Maybe the game does launch, gets as far as a loading screen or the campaign difficulty select, and then crashes without warning.

If any of that sounds familiar, you’re dealing with one of the more stubborn PC issues Call of Duty: Vanguard has had since launch, and it hasn’t fully gone away even years later. It shows up on both Steam and Battle.net, and it doesn’t always have a single obvious cause. The usual suspects include:

Corrupted or missing game files
An outdated graphics driver
A Windows update that changed something in the background
A conflicting background app or overlay
Hardware that isn’t compatible with what Vanguard requires

This guide combines Activision’s own official PC troubleshooting guidance with community-reported workarounds from Steam and Reddit threads, clearly separating the two so you know what’s confirmed and what’s still trial and error.

Quick answer: Start with these four things — run Vanguard as administrator, verify your game files through Steam or Battle.net, install a clean GPU driver, and disable the background apps Activision specifically flags as known conflicts (NZXT CAM, MSI Afterburner, and Razer Cortex). That combination covers Activision’s own recommended first steps. If it doesn’t fix yours, the rest of this guide gets more specific.

What’s Actually Going On When Vanguard Won’t Launch

Before jumping into fixes, it helps to understand what “not launching” can actually mean, because the cause is often different depending on exactly what you’re seeing.

Nothing happens at all when you click Play (no window, no process in Task Manager) — usually a permissions issue, a corrupted launcher configuration, or antivirus software blocking the executable before it even starts.
The game opens briefly, then crashes to desktop — more often tied to corrupted or missing game files, a driver conflict, or a background app interfering with the process.
A black screen with audio playing — the game is running, but it’s stuck on a fullscreen or shader-loading step that isn’t displaying correctly. This is a different problem from a hard crash, with its own fix path (see below).
The game launches fine but disconnects or throws a specific error code partway through — usually either a corrupted file, a known bug tied to something specific, or a server connection issue rather than a launch problem at all.

Keeping this distinction in mind will save you time, since a fix aimed at one symptom won’t necessarily do anything for another.

Start With These Checks Before Anything Else

These are the checks Activision’s own official PC troubleshooting article for Vanguard leads with, so they’re worth doing first regardless of your specific symptom.

Confirm Your PC Actually Meets Vanguard’s Requirements

This sounds obvious, but it trips up more people than you’d expect, because Vanguard has one requirement that isn’t just about raw performance.

Call of Duty: Vanguard only supports CPUs with the AVX (Advanced Vector Extensions) instruction set, according to Activision’s official system requirements page. This isn’t a speed or performance threshold — it’s a hardware compatibility requirement built directly into how the game engine runs. Your CPU either supports AVX or it doesn’t, and if it doesn’t, there’s no setting, patch, or workaround that will change that.

Here’s where it gets confusing: AVX support doesn’t line up neatly with how new or powerful a CPU is. Some genuinely strong processors — certain Intel Core i7 chips from around 2011–2012, like the i7-970 or i7-930 — don’t support AVX, even though they can comfortably run other Call of Duty titles like Warzone. Players with CPUs like this have reported getting a message that their processor doesn’t meet the minimum specification, even though the CPU seems more than capable on paper.

You can check by searching your exact CPU model plus “AVX support,” or by downloading CPU-Z from CPUID, the tool’s official developer. It’s free, and it lists every instruction set your processor supports under its CPU tab.

Here’s the full official spec sheet, straight from Activision Support:

	Minimum	Recommended (60 FPS)
OS	Windows 10 64-bit	Windows 10 or 11 64-bit
CPU	Intel Core i3-4340 or AMD FX-6300	Intel Core i5-2500K or AMD Ryzen 5 1600X
RAM	8 GB	12 GB
GPU	NVIDIA GTX 960 or AMD Radeon RX 470	NVIDIA GTX 1060 or AMD Radeon RX 580
VRAM	2 GB	4 GB
Storage	36 GB (Multiplayer/Zombies only) up to 177 GB (all modes)	Same
DirectX	DirectX 12 required	DirectX 12 required

Two details worth knowing:

The full 177 GB install covers Campaign, Multiplayer, and Zombies together — you can get away with 36 GB if you only install Multiplayer and Zombies.
Vanguard has an optional Hi-Rez Asset Cache (up to 32 GB) used for streaming higher-resolution textures, which you can turn off in settings if storage is tight.

Running low on free disk space — separately from the install size itself — is also a fairly common trigger for launch failures, so it’s worth confirming you have breathing room beyond the minimum install.

Activision’s official guidance also confirms that Vanguard requires DirectX 12, and specifically notes that Windows 8 does not support DirectX 12 — so Windows 8 users won’t be able to run the game at all, regardless of other specs. Activision recommends keeping Windows 10 fully updated through the standard Windows Update process, and has a dedicated Windows 10 compatibility article for Vanguard if you want to check your build against their recommendations. Windows 11 is also officially supported per Activision’s recommended and competitive spec tiers.

Run Vanguard as Administrator

Vanguard occasionally needs elevated permissions to access certain files on startup, and running without them can cause the game to fail silently. This is a quick, safe check that costs you nothing to try, and it’s commonly cited across community troubleshooting resources as an early step.

Right-click the Call of Duty: Vanguard .exe file (or its desktop shortcut).
Select Properties.
Open the Compatibility tab.
Check Run this program as an administrator.
Click Apply, then OK.
Repeat this for your Battle.net or Steam client, since the launcher itself sometimes needs the same permission.

Try launching the game again. If it opens normally now, that was likely your whole problem. If not, move on.

Verify Your Game Files

Corrupted or partially downloaded files are a documented cause of crash-on-launch issues, and Activision’s own troubleshooting guide points players to each platform’s built-in repair tool for exactly this.

On Steam, Activision links directly to Steam’s official guide on verifying game files:

Right-click Call of Duty: Vanguard in your Library.
Choose Properties → Installed Files.
Click Verify integrity of game files.
Let Steam scan and redownload anything it flags.

Activision also recommends checking Steam’s guide on programs that may interfere with Steam if verification alone doesn’t help.

On Battle.net, Activision points to Blizzard’s own Repairing Blizzard Games article for the Scan and Repair process:

Open the Battle.net client and select Vanguard.
Click the gear icon next to the Play button.
Choose Scan and Repair.
Click Begin Scan and wait for it to finish.

This process can take a while depending on your connection and how much data needs to be re-downloaded, so don’t assume it’s stuck if it takes several minutes.

Tip: Verify your game files before reinstalling the entire game. A damaged or missing file can often be repaired without downloading the full installation again.

Reinstall Your Graphics Driver — Properly

An outdated GPU driver is a frequent cause of both crash-on-launch issues and general instability once you’re in a match. Activision maintains its own general guide to updating video card drivers alongside the manufacturer sites. A regular driver update through GeForce Experience or AMD’s software often does the job, but if you’re still having trouble afterward, a clean install clears out anything the old driver left behind.

Download the latest driver directly from NVIDIA’s official driver page or AMD’s support site for your specific card.
Choose the Custom install option instead of Express.
Check the box for Perform a clean installation (NVIDIA) or the equivalent clean-install option in AMD’s installer.
Restart your PC once it’s done.

Tip: If you’re not sure whether your current driver is actually current, check the version number against what’s listed on the manufacturer’s download page rather than trusting GeForce Experience’s “up to date” message at face value — it occasionally lags behind.

The Game Opens and Immediately Closes or Crashes to Desktop

If Vanguard flashes open for a second and then dumps you back to the desktop, that’s a different troubleshooting path than a game that never opens at all — it usually means something is actively interrupting the process after it starts.

Check Whether Your Antivirus Is the Culprit

This is one of the few fixes here that’s directly recommended by Activision itself, not just a community workaround. Activision’s official troubleshooting guide states: “if you are running antivirus software, we recommend adding the entire Call of Duty: Vanguard game folder to your antivirus exception list.”

Open your antivirus software and find its Exclusions or Exceptions settings.
Add Vanguard’s entire install folder (not just the .exe) to the exclusion list.
Run a scan-and-repair through Steam or Battle.net afterward, in case a file was already altered or quarantined before you added the exclusion.

Activision’s guide even calls out specific antivirus products with their own quirks: Comodo users are told to go to Settings → Advanced Protection → Miscellaneous → Detect Shell Code Injections and add the game folder there, while BullGuard users need to go to Settings → Main and uncheck Self Protection.

Rather than disabling your antivirus completely, which isn’t something we’d recommend even temporarily, this targeted exclusion approach keeps your protection active everywhere else while ruling out interference with the game specifically.

Delete the Battle.net Cache

This is a widely documented Battle.net troubleshooting step for clearing out corrupted cache data linked to crashes and repeated repair loops.

Press Windows key + R to open Run.
Type %ProgramData% and press Enter.
Find the Blizzard Entertainment folder.
Delete it.
Reopen Battle.net — it will rebuild the cache automatically the next time it loads.

This only clears temporary data. It won’t touch your account, your save data, or the game files themselves.

Activision’s official guide also separately recommends checking Blizzard’s own article on closing background applications that might interfere with Battle.net games generally.

Disable Known Conflicting Background Apps

Activision’s own troubleshooting article specifically names three programs known to conflict with Vanguard: NZXT CAM, MSI Afterburner, and Razer Cortex. These are worth disabling first since they’re officially flagged, not just community suspects.

NZXT CAM, MSI Afterburner, and Razer Cortex — close these entirely, or at minimum disable their overlay/monitoring features, before launching.
If you use Razer Synapse, Activision’s guide specifically recommends making sure it’s updated to the latest driver version if issues persist.

Beyond Activision’s own list, players troubleshooting Call of Duty titles more broadly have also reported conflicts with these overlays, so they’re worth disabling too as a community-reported step if the official list above doesn’t resolve things:

GeForce Experience overlay: Settings → General → toggle off In-Game Overlay.
Discord overlay: User Settings → Activity Settings → Game Overlay → toggle off Enable in-game overlay.
Xbox Game Bar: Windows Settings → Gaming → Xbox Game Bar → toggle off.

If disabling all of these fixes the crash, you can re-enable them one at a time afterward to figure out which one was actually responsible, if you want to keep using it selectively.

Try a Clean Boot

This is another step directly recommended by Activision’s official troubleshooting guide, not just a general Windows fix borrowed for this article. A clean boot temporarily strips out non-essential background programs and services so you can see whether something unrelated to Vanguard is interfering. Activision links to Microsoft’s own clean boot guide as the reference for the process.

Press Windows key + R, type msconfig, and hit Enter.
On the Services tab, check Hide all Microsoft services, then click Disable all.
On the Startup tab, click Open Task Manager and disable each item listed there.
Restart your PC and try launching Vanguard again.

If it launches cleanly this way, re-enable your services and startup items in small batches to narrow down the specific conflict, then restore everything else once you’re done.

One more official detail worth knowing: Activision’s guide also notes that if the game doesn’t start and you’ve previously disabled ASLR (Address Space Layout Randomization, a Windows security feature) on your system, you should re-enable it — a disabled ASLR setting can itself prevent Vanguard from starting.

Don’t Skip Shader Preloading on First Launch

This is an official detail from Activision that’s easy to miss and can look like a crash or freeze when it isn’t one. On your very first boot, Vanguard runs a Shader Preloading process, and the game specifically warns you in-game to let it finish before jumping into any game mode. Navigating out of the Main Menu before preloading completes doesn’t necessarily crash the game outright, but Activision’s own guidance confirms it can lead to performance issues afterward. If you’re having trouble shortly after a fresh install or a major update, letting this process run to completion untouched is worth trying before assuming something’s actually broken.

The Black Screen: Why It’s a Different Problem

A black screen after launch — especially one with sound playing in the background — usually isn’t a crash at all. The game is running; it’s just not displaying anything, which typically points to a fullscreen conflict, a hang during shader loading, or an unrelated system-level crash rather than a corrupted file.

Try forcing windowed mode. If you can’t see anything to click, press Alt+Enter to toggle out of fullscreen, or Alt+Tab out to the desktop and adjust display settings from there.
Disable fullscreen optimizations. Right-click the Vanguard .exe → Properties → Compatibility tab → check Disable fullscreen optimizations. This is a general Windows compatibility setting that resolves fullscreen rendering conflicts across a range of games, not just this one.
Cap your FPS to match your monitor’s refresh rate. A mismatch between the two has been reported by some players as a trigger for this exact issue — if you’re on a 60Hz display, cap the game at 60 FPS; for 144Hz, cap it there instead.

Community-reported tip: Some players have specifically found that combining windowed mode with a refresh-rate-matched FPS cap cut down how often this happened, even when nothing else worked. This is a community-reported workaround rather than an officially confirmed fix, but it costs nothing to test and doesn’t touch any settings you can’t easily undo.

COD Vanguard Not Launching on Steam vs. Battle.net

The general fixes above apply to both platforms, but each launcher has its own quirks worth knowing about specifically.

If You’re Launching Through Steam

Verify integrity of game files if you haven’t already (steps above).
Turn off the Steam Overlay: Steam → Settings → In-Game → uncheck Enable the Steam Overlay while in-game.
Check Steam’s own guide to programs that can interfere with Steam, which Activision’s troubleshooting page also links to directly.
As a diagnostic step, try launching the game’s .exe directly from its install folder instead of through Steam. If it opens that way but not through Steam itself, the problem is likely with Steam’s overlay or launch process rather than the game files.

If You’re Launching Through Battle.net

Run Scan and Repair using Blizzard’s official repair guide (steps above).
Clear the Battle.net cache (steps above).
Check Blizzard’s guide on closing background applications that might be interfering.
Check for a stuck background update — Battle.net will sometimes show “Play” as available while a patch is still quietly downloading in the background, which can cause the game to fail or crash almost immediately when you try to launch it.

Stuck in a “Scan and Repair” Loop

This specific variant deserves its own callout because it’s especially frustrating: you run the repair, it completes, and the game immediately asks you to run it again — sometimes indefinitely. This particular loop isn’t addressed directly in Activision’s official troubleshooting article, so the following are community-reported approaches:

Run the scan-and-repair process as administrator.
Temporarily disable your antivirus specifically during the repair (and re-enable it right after), since some antivirus software interferes with the repair tool writing files to disk.
Double-check you actually have enough free disk space — an interrupted repair due to low storage can cause this exact loop.
If none of that breaks the cycle, a full uninstall and reinstall is the next step.

Some players have reported this loop persisting even after a clean reinstall, so treat it as something worth trying rather than a guaranteed fix.

Fixing Specific COD Vanguard Error Codes

If you’re getting a specific numbered error, that usually narrows things down considerably.

A quick note before we get into these: only a handful of Vanguard’s launch-related fixes are directly documented by Activision (antivirus exclusions, clean boot, disabling NZXT CAM/MSI Afterburner/Razer Cortex, and the Steam/Battle.net repair tools, all covered above). The error-code-specific fixes below come largely from player reports on Steam Community, Reddit, and gaming outlets rather than Activision’s own documentation, so we’ve labeled them accordingly. A workaround that helped some players isn’t the same thing as a confirmed fix.

Error 6068

Gaming outlets and player reports describe Dev Error 6068 as a PC-specific crash with no officially confirmed root cause. The fixes below are community-reported, gathered from player troubleshooting rather than an Activision statement:

Run the game as administrator.
Some players have added -d3d11 to Battle.net’s additional command-line arguments (Options → Game Settings) as a workaround. This is a community-reported workaround, not an officially confirmed fix — Vanguard runs on DirectX 12 by default, so forcing DirectX 11 isn’t a supported configuration, and results vary.
Disable the GeForce Experience overlay and Xbox Game Bar.
Turn off MSI Afterburner if it’s running.
Match your FPS cap to your monitor’s refresh rate.
If your GPU is overclocked, revert it to stock clocks — you can restore your previous overclock afterward if this doesn’t help.
Some players have reported success setting the game’s process priority to High in Task Manager (Details tab → right-click the Vanguard process → Set priority → High). This only applies for the current session and resets automatically when you close the game, so there’s no lasting change to worry about.
As a further step, capping your max FPS lower than usual reduces CPU and GPU load and has helped some players avoid this crash. Finding a stable number takes some trial and error, and it’s not guaranteed, but it’s low-risk to test.

Error -1338 / 0x00001338

Player reports on Steam Community and Reddit describe an unusual pattern tied to this error code:

Go to your Documents folder → Call of Duty Vanguard folder → delete the Players folder. It regenerates automatically the next time you launch.
If ray tracing is enabled, try turning it off.
Switch your operator back to their default skin.

Community-reported workaround: This isn’t something Activision has officially confirmed, but a number of players in Reddit and Steam Community threads have specifically traced this error to non-default operator cosmetics — Operator Daniel’s level-10 unlock skin comes up repeatedly in these reports. If you’re using any unlocked skin instead of the base outfit, switching back is worth testing.

Worth flagging: separately, some gaming outlets have documented a similarly-numbered Dev Error 5537 tied instead to crashes when changing an operator’s outfit in the customization menu itself, rather than during regular play. Error numbers get reported inconsistently across sources for Call of Duty titles, so if the skin-swap fix above doesn’t help, it’s possible you’re dealing with a related-but-distinct issue rather than the exact one described here.

Fatal Error

If the game tells you outright that your CPU doesn’t meet requirements, go back to the AVX section above — that’s almost certainly the explanation, per Activision’s own stated CPU requirement.

If it’s not CPU-related, the GPU is the more likely factor, based on community troubleshooting reports:

If your GPU is overclocked, revert to stock settings first.
If it’s already at stock and still crashing, some players have found stability after slightly underclocking the GPU core using MSI Afterburner — small steps of around 50MHz, testing after each change. This is reversible and generally low-risk to your hardware, but it’s a community workaround rather than an official fix, and the amount that helps (if any) will vary depending on your specific card.
Capping your max FPS is a lower-risk alternative worth testing before you touch clock speeds at all.

Error 0xC0000005

Worth knowing upfront: 0xC0000005 is a generic Windows access-violation error code (STATUS_ACCESS_VIOLATION), not something unique to Vanguard — it shows up across many different Windows applications when a program tries to access memory it shouldn’t. That makes it harder to pin down, and there’s no single fix confirmed to resolve it for everyone in Vanguard specifically. Steps some players have reported trying, with mixed results:

Verifying and repairing game files.
A clean GPU driver reinstall.
Reducing the number of friends on your Steam friends list — this is an unconfirmed community theory posted in Steam Community discussions, linking the error to an old bug tied to friends-list size. Neither Activision nor Valve has confirmed this connection, and player reports on whether it helps are inconsistent, so treat it as a low-priority thing to try rather than something to count on.

If you’ve worked through everything above with no luck, this is a reasonable point to reach out to Activision Support directly, since this particular error doesn’t have a documented universal fix.

“Vivacious” Error

This one’s different from the others on this list because it’s described by gaming outlets as a connection-related error rather than a local crash — affected players report the game failing to reach Vanguard’s multiplayer servers, with error messaging referencing a failed download. There’s no confirmed specific cause, but player reports suggest these steps are worth trying:

On PC: restart your router, and double-check your internet connection. Also close any bandwidth-heavy background apps (streaming, large downloads) that might be competing for your connection.
On console: a full power cycle — turn it off, unplug it for about 10 seconds, then plug back in and restart — is the most commonly reported fix.

If your issue is that the game won’t open at all rather than a connection-specific error, a router restart on its own isn’t likely to help — it’s specific to this error, not a general launch fix.

Error 887A0005

Gaming outlets have documented this error as a sudden PC crash with the message that “the application unexpectedly stopped working.” The quick fix most commonly cited is simply exiting and relaunching the game. Beyond that, community troubleshooting threads suggest a few more targeted options, offered here as community-reported workarounds rather than confirmed fixes:

If you’re on an RTX card, try disabling ray tracing.
On non-RTX GPUs hitting this error, some players have reported success underclocking by roughly 150MHz through MSI Afterburner.
Set your refresh rate to Automatic and cap your frame rate to match your monitor’s Hz.

If You’ve Tried Everything and Vanguard Still Won’t Launch

At this point, you’ve covered the checks most likely to help. Here’s what’s left, roughly in order of how drastic each step is:

Do a full reinstall. Uninstall completely, restart your PC, then reinstall through Steam or Battle.net. Back up any save data or config files you care about first.
Run System File Checker. Open Command Prompt as administrator and run sfc /scannow. This is a built-in Windows tool — not specific to Vanguard — that repairs corrupted system files, which can occasionally cause problems that look game-specific but aren’t.
Check whether it’s actually a server issue. Visit Activision’s support page and confirm Vanguard shows as Online across platforms before assuming the problem is local to your PC.
Contact Activision Support directly, especially if you’re dealing with an error like 0xC0000005 that doesn’t have a reliable community fix. Filing a ticket also helps them see how widespread a given issue actually is.

A full Windows reinstall is technically an option if you suspect something deeper is wrong at the OS level, but it’s a significant time investment and should really be your last resort after exhausting everything above — not a first response to a game that won’t launch.

Quick Answers to Common Vanguard Launch Questions

Why is Call of Duty Vanguard not launching on my PC?
Common causes include corrupted game files, an outdated GPU driver, antivirus interference, or a CPU that doesn’t support the AVX instruction set. Activision’s own troubleshooting guide starts with file verification, antivirus exceptions, and disabling known conflicting apps (NZXT CAM, MSI Afterburner, Razer Cortex) — that combination resolves a meaningful share of cases, though some specific errors need more targeted fixes.

Does COD Vanguard require DirectX 12?
Yes — it’s an official requirement confirmed on Activision’s system specs page, and Activision’s troubleshooting guide separately notes that Windows 8 doesn’t support DirectX 12 at all. The -d3d11 launch argument some players use as a workaround isn’t officially supported, since the game isn’t built around DirectX 11.

Can an outdated graphics driver really cause this?
Yes, it’s a commonly reported cause of both launch failures and mid-game instability. If a normal driver update doesn’t help, a full clean reinstall from NVIDIA or AMD is worth trying next — Activision’s own driver update guide covers this too.

Could my antivirus be blocking Vanguard from starting?
It’s possible, and this is one of the few fixes Activision officially recommends: adding Vanguard’s install folder as a targeted antivirus exclusion, rather than disabling protection altogether.

Should I just reinstall the game if nothing else works?
It’s a reasonable step once you’ve exhausted the fixes above, but it shouldn’t be your first move — most launch problems resolve through file verification, driver updates, or permissions and background-app fixes without needing a full reinstall.

Why does Vanguard get stuck on the loading screen?
This is often tied to a corrupted shader cache, a background app conflict, or — on a first launch specifically — leaving the Shader Preloading process before it finishes. Verifying your files and letting shader preloading complete uninterrupted are both worth checking.

Why won’t Vanguard launch specifically through Battle.net?
Start with Scan and Repair via Blizzard’s official repair guide, then clear the Battle.net cache (%ProgramData% → delete the Blizzard Entertainment folder). Also check for a stuck background update, which can silently block the game from opening.

What to Do If None of This Fix It

Not every launch issue has a documented fix, and it’s worth being honest about that rather than pretending otherwise. Errors like 0xC0000005, in particular, don’t have a single confirmed solution even now, years after launch — it’s a generic Windows crash code rather than a Vanguard-specific one, so what works for one player’s setup doesn’t always work for another’s.

If you end up needing to contact Activision Support or ask for help elsewhere, having the following ready will get you a faster, more useful answer than just describing the symptom:

The exact error code or message, if you’re getting one.
Your Windows version (10 or 11, and whether it’s fully updated).
Your GPU model and current driver version.
Whether you’re on Steam or Battle.net.
What you’ve already tried from this guide, so you’re not repeating steps that already didn’t help.

That combination of details is usually what separates a quick fix from weeks of back-and-forth — both with support and in this comment section, if you’d rather crowdsource it. If you’ve found something that worked for your specific setup, especially for one of the trickier error codes above, it’s worth sharing — troubleshooting threads like this one are often how the community-reported fixes above got discovered in the first place.

Visit Our Post Page: Blog Page

Discover more from Izoate

Subscribe to get the latest posts sent to your email.