Fix 0x80070426 Xbox App Launch Errors on Windows: Step-by-Step Guide

If the Xbox app on your PC crashes at launch and returns error code 0x80070426, the cause is almost always the same: Windows isn’t providing the background services the app depends on. The app itself — installation package, UI and local files — is usually present, but the platform services that handle store licensing, sign‑in, background installs and gaming integration are either stopped, set to Disabled, or otherwise misregistered. This feature guide explains why 0x80070426 appears, how to triage it quickly, and a safe escalation path from one‑click fixes to an in‑place Windows repair. It also highlights risks, edge cases, and the logging you should gather before escalating to support.

Background​

The modern Xbox experience on Windows is not a single monolithic executable — it’s a layered pipeline built on Microsoft Store components and several platform services. That pipe includes:

• Microsoft Store (licensing, update metadata and installs)
• Gaming Services (Xbox platform integration, install pipeline)
• Xbox Live Auth Manager (sign‑in and token handling)
• Xbox Live Networking Service (network features for Xbox Live)
• Microsoft Store Install Service and other Windows servicing services (installation engine, AppX/MSIX deployment)

If any of these layers fails to start or is disabled at the service level, the Xbox app often aborts with error codes such as 0x80070426 or other Store/AppX install and sign‑in errors. The error therefore signals a platform failure, not necessarily a broken “Xbox.exe” binary. Community and support runbooks report the same dependency pattern repeatedly, and the best repairs target the platform services first.

---

What 0x80070426 actually means (in plain language)​

• At runtime the Xbox app asks Windows for licensing, account tokens, and access to the AppX install broker. If a required Windows service is set to Disabled or fails to start, the app’s requests time out or return an error.
• Common symptoms: instant crash at launch, “Sign in required” loops, or immediate error dialog with 0x80070426. Often the Microsoft Store will also show odd behavior — stuck downloads, “Working…” messages, or inability to install updates.

Because the code is a symptom rather than a single definitive root cause, the troubleshooting approach should be systematic: start with non‑destructive fixes, confirm service state, then escalate to package re‑registration and system servicing repairs if needed.

Quick triage: five things to try first (under 10 minutes)​

Try these in order. They’re low‑risk, fast, and resolve the majority of Store/Xbox launch errors.

• Restart the PC (full reboot, not Sleep). This clears transient service states.
• Repair the Xbox app (Settings → Apps → Installed apps → Xbox → Advanced options → Repair). If that fails, use Reset. Repair preserves app data; Reset will clear local cache and sign‑in state.
• Ensure date, time and time zone are correct: Settings → Time & language → Date & time → enable Set time automatically and Set time zone automatically, then click Sync now. Authentication tokens can fail if the clock is out of sync.
• Run wsreset.exe to clear the Microsoft Store cache: press Windows+R, type wsreset.exe, Enter. Wait for the Store to reopen and test.
• Sign out of the Microsoft Store, reboot, sign back in with your Microsoft account. Token refreshes solve many license checks.

If one of these steps fixes the problem, stop — you’ve saved time and avoided heavier repairs. If the Xbox app still fails immediately with 0x80070426, move to the service checks below.

---

Step 1 — Repair or Reset the Xbox app (GUI method)​

Why: The app’s registered state or local cache can become inconsistent. Repair will attempt to fix core files without deleting local data; Reset clears app data and forces a fresh registration for the user.
How to:

• Press Windows + I → Apps → Installed apps.
• Search for Xbox → click the three dots → Advanced options.
• Click Repair, test. If it still fails, click Reset.
• Restart and test again.

Notes and caveats:

• Repair is minimal risk; Reset may require you to sign in again and will clear local app caches. Always try Repair first.

---

Step 2 — Quick Microsoft Store checks (one‑minute fixes)​

The Xbox app relies on the Store for licensing and installs. If the Store is broken, Xbox frequently fails.

• Run wsreset.exe to clear Store cache.
• Open Microsoft Store and try installing a small app or updating an existing app. If Store updates/install fail, that confirms the platform layer is affected.
• If downloads are stuck, run the built‑in Windows Store Apps troubleshooter (Settings → System → Troubleshoot → Other troubleshooters → Windows Store Apps) — it can auto‑fix common account and cache problems.

If the Store works and Xbox still fails, the issue is more likely to be a service or package registration problem.

---

Step 3 — Verify critical Windows services (most common cause)​

This is the step where you often find the problem: a required service is set to Disabled or refuses to start.
Important services to check:

• Microsoft Store Install Service (InstallService)
• Windows Update (wuauserv)
• Background Intelligent Transfer Service (BITS) (bits)
• Gaming Services (various Gaming Services entries)
• Xbox Live Auth Manager (XblAuthManager)
• Xbox Live Networking Service (XblNetApiSvc)
• AppX Deployment Service (AppXSvc) and Client License Service (ClipSVC) in some cases

How to check:

• Press Windows + R → type services.msc → Enter.
• Find each service above, double‑click.
• Ensure Startup type is not Disabled; set to Manual or Automatic as appropriate.
• If the service is Stopped, click Start. If Start is greyed out or returns an error, note the error text.

Command‑line alternative (for quick status checks — run as Administrator):

• sc query wuauserv
• sc query bits
• sc query InstallService
• sc query AppXSvc

If services keep switching back to Disabled, and your PC is a work/school device, group policy or MDM may be forcing the state — contact your administrator. Managed devices frequently revert service settings.
Why this matters: users repeatedly report that setting InstallService, BITS and the Xbox platform services to manual/automatic and starting them resolves 0x80070426 immediately. Community runbooks emphasize this check because it's quick and diagnostic.

---

Step 4 — Reinstall the Xbox app (PowerShell method)​

If services are fine but the app still fails, the app’s package registration may be corrupted. Reinstalling the Xbox package forces Windows to register a fresh copy.
PowerShell (Admin) commands:

• Open Windows Terminal (Admin).
• To find the package:
• Get-AppxPackage [I]gamingapp[/I] | Select Name, PackageFullName
• To remove the Xbox app:
• Get-AppxPackage Microsoft.GamingApp | Remove-AppxPackage
• If multiple package names appear, remove the package that matches Microsoft.GamingApp exactly.
• Restart the PC, then reinstall the Xbox app from the Microsoft Store.

Notes and warnings:

• Use the exact package name to avoid removing unrelated packages. If the Get-AppxPackage command returns no result, confirm the package fullname first. Always reboot after removal before reinstalling.
• If you prefer a non‑PowerShell route, uninstall through Settings → Apps and reinstall from the Store. PowerShell is faster for advanced users.

---

Step 5 — Repair system servicing: DISM and SFC​

Why: When multiple system components and Microsoft apps fail, the Windows component store (WinSxS) or protected system files may be corrupted. DISM and SFC are the standard escalation path.
Recommended sequence (run as Administrator):

• DISM /Online /Cleanup-Image /RestoreHealth — repairs the component store. This may take 10–30+ minutes. If DISM cannot download files, you can supply a Windows ISO as a source.
• sfc /scannow — checks and repairs protected system files using the component store. Run after DISM finishes.
• Reboot and test the Xbox app.

Notes:

• Run DISM first then SFC; the community and Microsoft guidance recommend this order because DISM repairs the store SFC depends on. If SFC reports unrepairable files after DISM, an in‑place upgrade or Reset this PC may be required.

---

Step 6 — Re‑register Store/AppX packages (last resort before in‑place upgrade)​

When GUI Reset/Repair fails, re‑registering AppX manifests with PowerShell forces Windows to rebuild app registrations.
PowerShell (Admin) command options:

• Broad re‑register (affects all users — powerful):
• Get-AppxPackage -AllUsers | ForEach-Object { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" }
• Targeted re‑register for the Store:
• Get-AppxPackage -AllUsers Microsoft.WindowsStore | ForEach-Object { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" }

Cautions:

• These commands can generate red error messages during execution for in‑use packages — that’s normal. They are powerful and can alter state across profiles; create a restore point or image before running them. Use -AllUsers only when you understand the scope.

---

Step 7 — In‑place upgrade (repair install)​

If DISM/SFC and re‑registration don’t fix the problem, an in‑place upgrade reinstalls Windows system files while keeping apps and data. This often repairs broken servicing components that other tools can’t.
How:

• Run Windows setup for your version and choose Keep personal files and apps (Windows 10: Media Creation Tool; Windows 11: Installation Assistant or ISO). Follow the prompts and allow the repair to complete.
• Make a full backup first and ensure you have device drivers/keys you might need.

Why it works: an in‑place upgrade rewrites the system files and component store, restoring the servicing stack used by the Store and AppX infra. It’s slower but often the most reliable fix when lower‑level tools fail.

---

Advanced diagnostics: logs and what to collect before contacting support​

If you need to escalate to Microsoft/Xbox support, gather this evidence — it saves time and avoids back‑and‑forth:

• Exact error code text and screenshot/video of the failure.
• Windows build (Settings → System → About).
• Output of DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow logs.
• PowerShell removal/re‑register errors and console output (copy/paste).
• Event Viewer logs around the launch time — check Application and System channels for AppX, StoreBroker, ClipSVC, and Gaming Services errors.
• If services won’t start, note the service error numbers or Event Viewer entries showing why they failed.
• If your device is managed, note any MDM/Group Policy that could affect Store or AppX behavior (e.g., policies that disable the Store).

Provide these items to support — they let engineers correlate local failures with known backend or package issues.

---

Common edge cases and gotchas​

• Enterprise or school devices: service settings may be forced by policy. If services revert to Disabled, consult your IT admin — local fixes may be repeatedly undone.
• Third‑party security tools and “debloat” scripts: these can remove or block Store components. Avoid third‑party “Store fixers” and be cautious with debloat scripts; they can remove core AppX infrastructure that’s hard to restore without an in‑place repair.
• WebView2/AAD broker issues: sign‑in failures sometimes result from broken WebView/AAD broker flows; reinstalling WebView2 or re‑registering broker packages can help in those cases.
• Partial installs or stub packages: in rare cases the Store may be publishing a stub package that doesn’t include the full client — this is a store publishing problem rather than a local bug. If many users report the same behavior, check service status and community updates before deep local troubleshooting.

---

Safety checklist — what to back up and precautions​

• Create a System Restore point or full disk image before running destructive package operations (Remove-AppxPackage, Add-AppxPackage -AllUsers).
• Back up any local app saves or profiles (some launchers keep data in %localappdata% or %appdata%).
• Avoid permanently disabling security protections as a troubleshooting fix. Temporary diagnostics are okay, but never leave the system less protected.

---

A practical, ordered checklist you can copy/paste​

• Reboot the PC (full restart).
• Repair Xbox app: Settings → Apps → Installed apps → Xbox → Advanced options → Repair. If fails, Reset.
• Check date/time and sync now.
• Run wsreset.exe (Win+R → wsreset.exe).
• Open Microsoft Store and try installing/updating a small app.
• Press Win+R → services.msc. Verify Startup type and Start status for: InstallService, wuauserv, bits, Gaming Services, XblAuthManager, XblNetApiSvc. Start any stopped services and set Startup type to Manual/Automatic (not Disabled).
• If services won’t start, run Admin CMD checks:
• sc query wuauserv
• sc query bits
• sc query InstallService
• net start wuauserv (if needed).
• If still failing, run DISM then SFC (Admin):
• DISM /Online /Cleanup-Image /RestoreHealth
• sfc /scannow and reboot.
• If problem persists, re‑register packages (Admin PowerShell — create a restore point first):
• Get-AppxPackage -AllUsers | ForEach-Object { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" }
• As last local step, uninstall Xbox with PowerShell and reinstall from the Store:
• Get-AppxPackage Microsoft.GamingApp | Remove-AppxPackage → reboot → reinstall.
• If still failing, escalate to an in‑place upgrade/repair install. Back up first.

---

Critical analysis — strengths, limitations and risk profile of this troubleshooting flow​

Strengths

• The flow moves from safe, non‑destructive fixes (restart, wsreset, Repair) to deeper repairs (DISM/SFC, re‑register) so most users stop when the problem is fixed. This minimizes risk to user data.
• It addresses both symptoms (store cache, sign‑in tokens) and root causes (disabled services, corrupted component store), which is necessary because 0x80070426 is a symptom, not a single root cause.

Limitations and unverifiable claims

• There’s no single Microsoft public post that declares “0x80070426 always equals X” — the code represents a class of platform failures. Any single fix cannot be guaranteed for all environments. Treat reported community workarounds (VPN, pause/resume of downloads) as diagnostic, not definitive fixes. Flag these as anecdotal.

Risks

• PowerShell re‑registration and -AllUsers operations are powerful and can change system state across profiles; if they fail partway they can leave the system in an inconsistent state. Always create a restore point or full image beforehand.
• Running DISM requires internet access or a local source; if blocked by firewall/enterprise policy, DISM may fail to fetch replacement files and need an ISO source.

---

When to contact Microsoft/Xbox support​

Contact support if:

• The Xbox app consistently fails on a clean account or a newly created local admin account after following the steps above.
• Services revert to Disabled and you’re not on a managed device.
• You’ve collected logs (DISM/SFC outputs, PowerShell errors, Event Viewer entries) and the issue persists after an in‑place repair.

When you contact support, provide:

• Exact error message and code.
• Windows build and update history.
• The steps taken and their outputs (logs). This speeds escalation and can shorten time to a fix.

---

Conclusion
Error 0x80070426 is frustrating because it looks like an app failure but is almost always a platform or service problem. A measured, layered approach — quick repairs (Repair/Reset, wsreset), targeted service checks, PowerShell package maintenance, and finally system servicing repairs (DISM/SFC or an in‑place upgrade) — resolves the problem for most users while protecting data. If you’re on a managed device, coordinate with IT; if you reach support, bring logs and a clear checklist of the steps you’ve tried. Follow the ordered checklist in this article and you’ll either restore Xbox functionality or gather the necessary evidence for a rapid escalation.

---

Source: Appuals Fix: Xbox App Error 0x80070426 on Windows