Assassin's Creed Origins not starting? Fix splash-then-close on PC with NVIDIA AA off, dedicated GPU, Ubisoft Connect cache clear, and official VC++ — for a legitimate copy you own.
Hello awesome people! 👋 Yosh here. If Assassin's Creed Origins shows the splash screen and then closes — never reaching the menu — this guide walks you through fixes that work on the official Steam, Epic, and Ubisoft releases. Even Nando approves. 😼
How to Fix Assassin's Creed Origins Not Starting After Launch 😺
Origins boots CPU, GPU, and Ubisoft Connect at the same time. When any link breaks — outdated driver, missing Visual C++ runtime, corrupted Connect cache, wrong GPU on a laptop — the process dies right after the logo. No error popup, just back to desktop.
Why the splash screen closes
- Global GPU overrides — forced anti-aliasing in NVIDIA/AMD panel crashes some Ubisoft titles
- Ubisoft Connect cache corruption — launcher hooks fail silently
- Integrated graphics selected — laptop tries Intel instead of dedicated GPU
- Missing runtimes — VC++ or DirectX not installed after a Windows update
Fix 1: NVIDIA — disable forced anti-aliasing
Right-click desktop → NVIDIA Control Panel → Manage 3D settings. Set Anti-aliasing to Off (or Application-controlled). Click Apply, close the panel, launch Origins from Ubisoft Connect/Steam. Many NVIDIA users report this alone fixes the splash-then-close loop. Easy and fast! ✨
Fix 2: AMD — global graphics settings
Right-click desktop → AMD Radeon Software → Gaming → Global Graphics. Set anti-aliasing to Use application settings and Texture filtering to Standard. Apply, relaunch the game. 😺
Fix 3: Force dedicated GPU (laptops)
Settings → System → Display → Graphics → Browse → add ACOrigins.exe → Options → High performance. On NVIDIA laptops, also set Control Panel → Manage 3D settings → Program Settings → ACOrigins.exe → High-performance NVIDIA processor.
Fix 4: Ubisoft Connect & runtimes
- Update Ubisoft Connect — latest client from ubisoftconnect.com
- Clear Connect cache — close Connect, delete
Program Files (x86)/Ubisoft/Ubisoft Game Launcher/cache, relaunch - Install VC++ 2015–2022 — x64 and x86 from Microsoft; reboot
- Update GPU drivers — official NVIDIA/AMD installers only
- Verify game files — Steam → Properties → Installed Files → Verify (or Epic/Ubisoft repair)
Fix 5: Compatibility & overlays
Right-click ACOrigins.exe → Properties → Compatibility → enable Disable fullscreen optimizations. Disable Discord, GeForce, and Xbox Game Bar overlays one at a time and test. Windowed launch on first boot is normal — the game still counts as working.
Fix 6: If the game reaches menu but stutters
Lower resolution and disable extra background apps. Check specs with our system requirements tools guide. Origins is demanding — 8 GB RAM minimum, dedicated GPU strongly recommended.
FAQ
Steam vs Ubisoft store version?
Steam still opens Ubisoft Connect. Both need a valid license and an updated Connect client.
Will reinstalling help?
Yes if files are corrupted — verify first; full redownload is last resort.
Similar crash on other games?
Try our God of War won't start fix or general PC game error guide.
Run as administrator?
Test once to rule out permissions; don't leave permanent unless required.
Does Origins need Ubisoft Connect forever?
Yes for online features and ownership checks on most storefronts — keep Connect updated even if you launch from Steam.
Order of operations that saves time
- NVIDIA/AMD AA / filtering overrides off
- Force high-performance GPU on laptops
- Update Connect + clear cache
- VC++ x86+x64 + GPU driver
- Verify files last — large downloads only when earlier steps fail
Related: missing DLL guide · Vulkan DLL fix
What “splash then close” usually means on Origins
When Origins paints the Ubisoft splash and exits before the main menu, the engine typically failed during GPU setup, overlay injection, or Connect handshake — not during “story loading.” That is why verifying game files first often wastes hours: the files are fine; the startup stack is not.
- GPU profile overrides (forced AA, anisotropic, FXAA) break the splash path on many NVIDIA setups
- Wrong GPU on laptops (Intel/AMD iGPU selected) fails the DX11/DX12 device create step
- Stale Ubisoft Connect cache can leave a half-signed session that closes the child process
- Missing VC++ runtimes show as silent exits more often than clean DLL popups on this title
Treat the splash as a diagnostic signal: you are one layer away from the menu, so small environment changes beat full reinstalls.
Laptop checklist (G-Sync / Optimus / AMD switchable)
- Plug in power — many laptops drop to iGPU on battery
- Windows Graphics settings → add
ACOrigins.exe→ High performance - NVIDIA Control Panel → Program Settings → add Origins → Anti-aliasing Mode = Application-controlled / Off
- Close overlay stacks you do not need for the first successful launch (extra FPS overlays on top of Connect)
- Launch once from Ubisoft Connect directly, then retry Steam if that is your storefront
If the laptop has an external monitor only on the iGPU, move the window or use the built-in panel for the first boot after a driver change.
What not to do
- Do not download “Origins crack fixes,” DLL packs, or “offline bypass” tools — they are malware magnets and violate store ToS
- Do not delete your entire Ubisoft folder without backing up saves
- Do not force exotic compatibility modes (Windows 8 / reduced color) unless Microsoft or Ubisoft document it for your build
- Do not stack five overlays hoping one “unlocks” the menu
After it finally opens: stabilize the next 10 launches
Once you reach the menu, lock the winning config:
- Keep GPU driver on a known-good Game Ready / Adrenalin build for a week before chasing new betas
- Leave AA Application-controlled unless you have a measured reason to override
- Let Connect finish its background update before traveling offline
- If you dual-boot or move the install drive letter, re-verify once — path changes confuse Connect more than Steam
Still stuck after the ordered checklist? Note the exact splash duration (instant close vs 3–5 seconds) and whether Task Manager shows ACOrigins.exe briefly — that detail tells you GPU-init vs Connect-auth when you ask for help on Contact.
Steam overlay, Connect, and antivirus false positives
Origins launches a second process tree through Ubisoft Connect. Security software sometimes quarantines a helper DLL right after splash, which looks identical to a GPU crash. If the ordered GPU/Connect fixes fail:
- Add temporary exclusions for the Origins install folder and Ubisoft Connect folder — then retest once
- Disable Steam overlay for Origins as a quick A/B test
- Confirm Connect is not stuck on “Installing prerequisites” in the background
Remove exclusions that you do not need after a successful week of launches. The goal is diagnosis, not a permanent hole in your AV.
Keep notes: storefront (Steam/Epic/Ubisoft), GPU brand, laptop vs desktop, and whether the splash lasts under one second. That package is enough for a useful Contact message if you still need a second pair of eyes.
Multi-store installs and leftover helpers
If you once installed Origins on Ubisoft, then again on Steam, leftover helpers can fight over the working directory. Uninstall unused storefront copies cleanly from Windows Apps & features, keep the storefront you actually own, and only then clear Connect cache.
Reboot after uninstalls so file locks release. Then run the ordered checklist from the top — GPU overrides first, Connect second, redistributables third. That sequence still wins more often than a blind reinstall.
When the game finally stays open, create a Windows restore point or note your driver version. Origins is old enough that a future “clean driver” experiment can reintroduce the splash-close loop; knowing the last good build saves a weekend.
More PC and game tips: PressCatToStart – from Yosh 😼
.jpg)
