How to Fix Assassin’s Creed Shadows Not Launching on PC?
Assassin’s Creed Shadows can fail before the main menu in two different ways: the launcher returns to Play before a game window appears, or the game opens briefly and closes at the Ubisoft logo, black screen, or add-on check.
If the launcher shows Running and then returns to Play, the game usually never reached a real window. A crash after the logo points more toward overlays, damaged files, local settings, drivers, display mode, or save sync.
Match the fix to the last thing you saw before the failure. The table below keeps Steam-only, display-only, and save-risky steps out of the way until they actually fit your screen.
| What you see | Most likely area | Use |
|---|---|---|
| Launcher returns to Play before a game window | Requirements, SSD, Ubisoft Connect, account link, or Steam client state | Methods 1-2 |
| Ubisoft logo, splash screen, or black window appears first | Overlays, mods, damaged files, local settings, driver, or display mode | Methods 3-5 |
| Checking for Memory add-ons or Checking Add-On Content crash | Save or cloud-sync handling | Method 5 |
| AVX2, DX12, GPU, or driver error | Hardware requirement or Windows/GPU launch path | Methods 1 and 5 |
1. Check Requirements and Install Location First
If Shadows returns to Play before a game window appears, this pattern usually points to a requirement or install-location check failing before the game can show a useful error.
This check helps because unsupported hardware, a non-SSD install, or missing DirectX 12 support will stop the game before launcher repairs matter.
- Let Steam, Epic Games Launcher, or Ubisoft Connect finish every pending Shadows update before testing.
Assassin’s Creed Shadows has a stricter PC floor than older Assassin’s Creed games, including an SSD requirement and DirectX 12. - Compare your CPU, GPU, RAM, Windows version, DirectX support, and free storage against the current Ubisoft requirements.
- If you are not sure what Windows sees, press Windows + R, type
dxdiag, and check the DirectX Diagnostic Tool System and Display tabs. - If the launch message says the processor does not support AVX2, the CPU is below the requirement. If AVX was disabled in BIOS or boot settings, re-enable it and test again.
- Make sure Shadows is installed on an SSD, not an older HDD or slow external drive. If Ubisoft Connect shows a disk access or write error while patching, fix that Ubisoft Connect disk error before retesting.
- If you use an Intel Arc GPU, confirm that Resizable BAR is enabled.
If the game misses the SSD rule or the Arc ReBAR requirement, later launcher fixes usually will not change the result.
If the PC is below the requirement, the issue was the hardware or install target. If the PC qualifies and still returns to Play, continue below with Ubisoft Connect.
2. Repair the Ubisoft Connect Link and Launcher Session
Steam and Epic copies still pass through Ubisoft Connect. This works only when the store launcher, Ubisoft Connect, and the linked Ubisoft account all agree on the same purchase.
Stay here for launcher or account-link problems. If you are not seeing sign-in, ownership, sync, offline, or instant return-to-Play behavior, do not spend much time here.
- Close Steam, Epic Games Launcher, and Ubisoft Connect from the Windows system tray.
Ubisoft’s own launcher-account fixes often start by closing both storefront and Ubisoft Connect from the tray so the next launch starts fresh. - Open Ubisoft Connect by itself and finish any update, sign-in, offline, or sync prompt.
- Launch Shadows from the same Steam, Epic, or Ubisoft Connect Library where you own it. Do not start from
ACShadows.exefor this test. - Sign in with the Ubisoft account originally linked to that Steam or Epic purchase.
Steam and Epic purchases can fail before launch if Ubisoft Connect is signed into the wrong linked account.
| If Ubisoft Connect shows this | Do this |
|---|---|
| Offline, sync, or purchase verification issue | Disconnect VPN, proxy, or virtual-network software for one sign-in test. Do not disable the physical internet adapter. |
| Service or server unavailable | Update Ubisoft Connect and check Ubisoft Help > Server Status. If status looks normal but the message remains, use our Ubisoft service unavailable guide. |
| Launcher keeps looping | Close Ubisoft Connect and rename its cache folder in C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\ to cache.old. |
| Game says it cannot find the Ubisoft Launcher | Repair the Ubisoft Connect install first, then use our Ubisoft Launcher not found guide if the message stays. |
| Game is tied to another account | Stop and use Ubisoft Account Management > Linked accounts or Ubisoft Support. Do not unlink casually. |
If Shadows opens after this, the issue was the Ubisoft session or linked account. If the game window appears and then closes, continue below with startup hooks.
3. Remove Overlays, Mods, and Startup Hooks
If the Ubisoft logo, splash screen, or black window appears first, the account check has already passed. The next clean test is one launch without tools that inject into or monitor the game.
This pass isolates programs that attach to Shadows during startup, which matters most after the game window or logo has already appeared. It is not needed when Shadows never opens a window at all.
- Disable the Ubisoft Connect in-game overlay.
Ubisoft still treats its overlay as a meaningful startup variable when a game fails before or during the first launch screen. - Close the Discord, Steam, NVIDIA, AMD, and Xbox Game Bar overlays.
- Exit tools such as MSI Afterburner, RivaTuner, RGB utilities, recorders, hardware monitors, and frame-rate limiters.
Ubisoft’s software-conflict guidance is aimed at tools that inject into or monitor the game before the main window can stabilize. - Remove mods, ReShade, custom DLLs, translation patches, or community launch tweaks for this test.
- For modded installs, move any
DataPC_boot_patch_*.forgefile added or replaced by a mod out of the game folder, then verify files. - If security software quarantined a Shadows or Ubisoft Connect file, restore only the verified file and add the game folder to the product’s allow-list.
If the game opens cleanly, the issue was one of those startup hooks. If it still closes during startup, continue below to repair files and reset local settings.
4. Verify Files and Reset Local Startup Settings
File verification repairs the installed package, but it does not reset every file in your Windows profile. A damaged ACShadows.ini or cache folder can keep reloading the same bad startup state after every launch attempt.
After the account and overlay checks are clear, this gives you two clean resets: repair the installed files, then force Shadows to rebuild its local startup settings. If you are not past the Ubisoft/session checks yet, fix those first.
- Verify the game from the launcher you use: Properties > Installed Files in Steam, Library > Manage > Verify in Epic, or the verify/repair option in Ubisoft Connect.
Verification is the fastest way to catch missing or damaged files before you move into local config resets or a full reinstall. - Exit Shadows and every launcher.
- Open the Assassin’s Creed Shadows folder inside your Windows Documents folder. If OneDrive redirects Documents, use the Documents location shown in File Explorer.
- If
ACShadows.iniorcachedoes not exist, skip the missing item instead of creating empty replacements. - Rename
ACShadows.initoACShadows.ini.oldand renamecachetocache.old.
Ubisoft support replies and repeated user reports both point to the local ini and cache reset when the game reaches startup and then collapses. - Launch Shadows again and let it rebuild default settings.
If the reset works, the issue was damaged files or local startup data. If the symptom is more specific, continue below to the stop-point table.
5. Use the Matching Fix for Specific Errors or Stop Points
When Shadows stops at one named screen or error, the failure usually points to the subsystem named by that screen: save sync, display mode, driver handoff, or Steam client state.
The table helps you apply the matching fix without turning every rare stop point into a full method. Unless one row matches your screen, keep the focus on the earlier sections.
savegames folder before changing cloud-save sync or touching local save data. Do not delete local or cloud saves unless you are intentionally wiping progress. - Install pending Windows updates and restart the PC.
Ubisoft still treats current system updates and graphics drivers as core launch checks before deeper escalation.
| Symptom | What to try |
|---|---|
| Checking for Memory add-ons around 93% or Checking Add-On Content around 99% | Back up C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\savegames, then test once with cloud-save sync off. Do not delete local or cloud saves without a backup. |
| DX12, GPU, missing-GPU, or driver error | Install Windows updates, install the stable GPU driver, set ACShadows.exe to High performance in Windows Graphics settings on hybrid systems, and rerun failed Visual C++, DirectX, or Ubisoft installers from InstallerResources or support. |
| Crash began after a GPU driver update | Test the previous stable driver once, or use the driver’s clean-install/factory-reset option if several updates were stacked. |
| Black screen, flicker, full PC crash, or display-specific crash | Temporarily use 120 Hz, test once with G-SYNC/FreeSync/VRR off, unplug a second monitor if it crashes near Connecting online, and test Disable fullscreen optimizations after a black screen right after the Ubisoft logo. |
| Steam still returns to Play after verification | Run Steam > Settings > Storage > Repair Folder, clear the Steam download cache, opt out of Steam Beta, delete the game’s In-Game Overlay Data, and clear Steam Web Browser Data. |
| Other Steam games also fail to launch | Use our Steam games not launching guide before treating Shadows as a unique game-side failure. |
| Overclock, undervolt, frame-generation, or optimization-profile instability | Return GPU/CPU tuning and game optimization profiles to stock for one launch test, then restore them only after Shadows reaches the menu. |
If one row works, the issue was that specific stop point. If it still fails after the relevant row, continue below with one clean reinstall and support evidence.
6. Reinstall Once, Then Send Ubisoft Useful Evidence
A reinstall belongs at the end because it only helps when the installed package or drive state is still bad after the earlier checks.
Do this after the relevant rows above have failed. Avoid this if one earlier fix already worked; keep that state and skip another large download.
- Uninstall Shadows once and reinstall it fresh on the SSD.
- When practical, keep Steam or Ubisoft Connect on that same SSD for this clean reinstall test.
- Launch once before restoring mods, overlays, custom graphics profiles, or custom launch options.
- If it still fails, press Windows + R, run
dxdiag, and save the report. Then runmsinfo32and save that report too. - Send Ubisoft Support those files with the store where you own the game, GPU driver version, and the exact stop point: Play-button reset, Ubisoft sign-in loop, splash-screen exit, black screen, or add-on/memory check crash.
If a clean reinstall still fails, a support ticket with those reports is more useful than repeating unrelated settings changes.
