Minecraft Bedrock Crashes on Loading Screen PC: 2026 Fixes

If Minecraft Bedrock crashes on loading screen PC setups, this step-by-step fix stops the red splash freeze and gets you back into your worlds fast.

You launch Minecraft Bedrock Edition on Windows, the red Mojang Studios logo appears, and then the window locks up or vanishes back to the desktop. No error dialog appears. No crash log generates in %localappdata%. Even with Java Edition running cleanly on the same machine, Bedrock on Windows 11 frequently drops out without leaving an error code.

That complete lack of diagnostic output leads many players to assume world corruption and immediately reinstall, risking local saves. In reality, Bedrock usually halts during UWP asset unpacking, the Xbox identity handshake, or display swapchain setup.

Work through this ordered sequence before touching your installation. It isolates the stall point and restores startup without endangering your saved worlds or your catalog of Minecraft Minecoins purchases.

Why Bedrock Dies on the Red Splash Screen

The red screen is not just a static branding splash. Underneath, the Universal Windows Platform (UWP) runtime sets up an app sandbox, checks store licenses, unpacks core assets, and initializes Xbox Gaming Services.

[Launch Executable] 
       │
       ▼
[DirectX / GPU Swapchain Init] ──(Crash if hooks/drivers fail)──► Desktop
       │
       ▼
[UWP Identity & Package Check] ──(Freeze on 0x80073CFB / Store cache)──► Red Screen Hang
       │
       ▼
[Gaming Services Authentication] ──(Fail on build <19.87.13001.0)──► Silent Termination
       │
       ▼
[Marketplace & Menu Display]

DirectX hook injection from background utilities represents one major failure point. When an external overlay attempts to bind to Bedrock before the engine establishes its main swapchain, the display pipeline faults. Memory allocation limits introduce a similar failure mode: if the operating system cannot allocate at least 2GB of free RAM during asset extraction, initialization enters an infinite wait.

Package validation errors also drop the client. Microsoft Store error 0x80073CFB indicates an identity mismatch between the Windows Store cache and the Xbox application. The launcher registers ownership, but the local package manager fails to validate the app manifest. Windows then shuts down the client to prevent an untrusted execution state.

Quick Triage: Workarounds That Take Under Sixty Seconds

Before running OS-level repair scripts, test these rapid bypasses. Over half of all red-screen freezes stem from two minor conflicts: a stalled Runtime Broker child thread or third-party injection hooks.

Terminating stuck background processes breaks the infinite wait state without endangering local player data.

To run the Runtime Broker bypass, open Minecraft Bedrock. Once the red Mojang logo locks up, press Ctrl + Shift + Esc to access Task Manager. Click the arrow beside the Minecraft entry to reveal its child processes. Right-click Runtime Broker and click End Task. The client should bypass the hang and display the main menu.

Next, audit active background software. Discord's in-game overlay frequently collides with UWP swapchain creation. Open Discord, click the gear icon, navigate to Game Overlay, and switch it off. Finally, scan Task Manager's Details tab for lingering instances of MinecraftLauncher.exe or background Java runtimes from earlier sessions; close them to release locked file handles.

The Ordered Troubleshooting Sequence

If the quick bypasses do not restore startup, follow this diagnostic chain from least invasive app checks up to system package repairs.

[Step 1: End Stuck Tasks] 
       │
       ▼
[Step 2: Windows App Repair] ──(Settings > Apps > Advanced Options)
       │
       ▼
[Step 3: Gaming Services Repair] ──(Target Build 19.87.13001.0+)
       │
       ▼
[Step 4: Flush Cache & AppData] ──(wsreset.exe & LocalAppData purge)
       │
       ▼
[Step 5: System File Checker] ──(SFC /scannow & DISM)
       │
       ▼
[Step 6: PowerShell AppX Restore] ──(Re-register broken UWP manifests)

Step 1: Terminate Lingering Launcher Threads

Stale handles can prevent the UWP container from acquiring launch locks. Open Task Manager, select the Details tab, and manually terminate Minecraft.Windows.exe, MinecraftLauncher.exe, and GameServicesLauncher.exe. If a task refuses to close, an underlying Windows service still holds its process lock.

Step 2: Use Windows App Repair

Avoid using the Reset button immediately. Windows separates non-destructive verification from data resets.

1. Press Windows Key + I to open Settings.
2. Navigate to Apps > Installed Apps (or Apps & features on Windows 10).
3. Locate Minecraft (or Minecraft for Windows).
4. Click the three dots menu and select Advanced options.
5. Scroll to the Reset header and click Repair.

Windows will check package hashes against store signatures. Once a checkmark appears beside the button, relaunch Bedrock. If you later choose to use Reset, back up your world saves first, as this operation clears app settings and local data.

Step 3: Run the Gaming Services Repair Tool

Outdated Gaming Services versions cause launch failures across Windows 10 and 11. Mojang documented that older builds break update pipelines and prevent proper license authorization. Your installation must run build 19.87.13001.0 or higher.

1. Launch the Xbox App on PC.
2. Click your profile icon at the top left and select Support.
3. Open the Gaming Services Repair Tool.
4. Click Start Troubleshooting.

The tool scans version dependencies, corrects registry keys, and updates Gaming Services to restore authentication between the client and Microsoft servers.

Step 4: Clear Store Cache and Package AppData

Corrupt manifest caches trigger Store error 0x80073CFB, halting Bedrock on launch. You must clear both the executable cache and the local session cache.

Press Windows Key + R, type wsreset.exe, and press Enter. A black Command Prompt window opens. Leave it alone. It automatically exits after 10 to 30 seconds and opens the Microsoft Store, confirming that the Store cache reset successfully.

Next, remove stale identity session data. Press Windows Key + R, enter the path below, and hit Enter:

%localappdata%\Packages

Locate the folders starting with Microsoft.XboxApp and Microsoft.WindowsStore. Open each, enter the LocalCache and TempState subdirectories, and delete the files inside. Do not modify any world folders.

Step 5: Repair Underlying Windows Dependencies

Bedrock depends heavily on shared operating system libraries and the UWP app container. Corrupted system files block the client from starting.

Open an elevated Command Prompt by searching cmd, right-clicking the icon, and selecting Run as administrator. Execute:

DISM /Online /Cleanup-Image /RestoreHealth

Once DISM finishes validating the component store against Windows Update servers, run the System File Checker:

sfc /scannow

Let the verification reach 100%. If SFC detects and repairs corrupt system DLLs, restart Windows immediately. This restores system components that Java bypasses but Bedrock requires.

Step 6: Re-register UWP Packages via PowerShell

If the package manifest registration broke in your user profile, re-bind it through PowerShell. Right-click Start and choose Terminal (Admin) or Windows PowerShell (Admin).

Run this script to re-register core Store and Gaming manifests:

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

Press Enter. Blue processing notifications will appear. Disregard warnings regarding active files in use. When the prompt returns, close PowerShell and open Bedrock.

Graphics Drivers, Overlays, and Display Conflicts

Bedrock relies on DirectX to draw its interface. If the graphics driver cannot negotiate a presentation target, the client crashes on startup.

Legacy forum threads frequently suggest setting Windows 7 or Windows 8 compatibility modes on the game executable. That fix applied strictly to legacy Win32 launcher wrappers. Native UWP packages installed via the Microsoft Store do not use compatibility toggles; forcing wrappers via custom shortcuts causes initialization exceptions.

If you use a custom desktop shortcut, turn off fullscreen optimizations in the launcher properties instead. More importantly, keep your display drivers updated. Graphics drivers with corrupt shader cache files often crash when Bedrock builds its initial render targets. Run a clean driver installation to re-establish clean API hooks.

Applying modern display settings and allocating enough memory avoids the legacy compatibility traps that break UWP apps.

Check your available physical RAM before launching. If background processes, browsers with heavy tabs, or virtual machines reduce free memory below 2GB, Bedrock will freeze while loading textures. Close unneeded apps before launching the client.

Antivirus Suites and Network Gateways Blocking Authentication

While the red screen is up, Bedrock opens an encrypted socket to Mojang's authentication servers. If local security tools block that traffic, the game stalls instead of dropping to an offline state.

Several third-party antivirus suites interfere with Minecraft's initial network requests:

• AVG and Avast: Block background UWP network sockets.
• BitDefender: Quarantines dynamic binary updates in the background.
• ByteFence: Flags app manifest verifications.
• McAfee and Norton: Deep packet inspections sever the Xbox identity handshake.

If you run these utilities, whitelist both the WindowsApps directory and the Minecraft installation path, or temporarily suspend live shields to confirm whether they cause the startup hang.

VPN services create identical problems. Free VPNs route connections through shared data center subnets that Microsoft and Mojang authentication endpoints frequently rate-limit. When the client fails to verify profile tokens through a blocked address, it locks on the splash screen indefinitely. Disconnect from proxy tools and VPNs before starting the client.

With network paths clear, your saved skins, server access, and Minecraft Minecoins balances will sync properly at the menu.

Platform Discrepancies: Windows PC vs Console Recovery

Many troubleshooting guides suggest holding L1 + R1 + L2 + R2 + OPTIONS + Touch Pad on a controller while the game starts.

That controller chord was added specifically to PlayStation Bedrock in version 1.16.1.03 to clear console cache storage. It does not work on PC. Connecting a console controller to Windows and pressing that combination does nothing. Windows manages app cache through its own package manager rather than console firmware hooks.

Recovery mechanics are strictly platform-dependent; console button combinations do not apply to Windows PC architecture.

Skip console-specific button shortcuts on desktop setups and use the Windows Store maintenance tools instead.

Backing Up Worlds Before a Clean Reinstall

If every fix fails and the game continues crashing to desktop, clean reinstalling is the final option. Do not look for your data in .minecraft.

That directory belongs strictly to Java Edition. Bedrock Edition writes worlds, resource packs, and player settings to a separate local app package directory. Uninstalling Bedrock or resetting it via Windows Settings without copying this path can delete your worlds permanently.

To back up Bedrock worlds manually:

1. Press Windows Key + R to open Run.
2. Paste this path and click OK: %localappdata%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang
3. Locate the minecraftWorlds folder.
4. Copy minecraftWorlds and paste it to an external drive or your desktop.

%localappdata%\Packages\
 └── Microsoft.MinecraftUWP_8wekyb3d8bbwe\
      └── LocalState\
           └── games\
                └── com.mojang\
                     ├── minecraftWorlds/  ◄── COPY THIS FOLDER
                     └── resource_packs/

With your worlds copied, uninstall Minecraft for Windows via Settings. Reinstall the game from the Microsoft Store or Xbox App onto your primary drive, run it once to recreate the folder structure, and move your saved worlds back.

Log into your Microsoft account, confirm that purchased items and Minecraft Minecoins show up in your profile, and paste your saved world folders into the newly generated directory.

Frequently Asked Questions

Why does Minecraft Bedrock freeze on the red Mojang loading screen on PC?

It typically happens when asset unpacking stalls due to low available memory (under 2GB) or when local authentication handshakes fail. Background software like the Discord overlay or third-party antivirus suites can also interrupt the initialization sequence.

How do I fix Minecraft Bedrock crashing straight to the desktop on launch?

Run the Gaming Services Repair Tool in the Xbox PC app to ensure your background services are on build 19.87.13001.0 or newer. You can also open Windows Settings, locate Minecraft under Installed Apps, and click Repair to restore damaged app binaries without touching your data.

Will resetting the Minecraft app delete my saved worlds on PC?

Using the Repair option never affects your files, but using Reset can wipe local game settings and cached assets. Always back up your minecraftWorlds folder located in %localappdata%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe before running a Reset or reinstalling.

What is the Gaming Services Repair Tool and how does it help?

It is a built-in diagnostic utility inside the Xbox app on Windows that detects damaged or outdated gaming frameworks. Running it brings dependencies up to build 19.87.13001.0+, which resolves package registration mismatches and update crashes.

Can Discord or antivirus software cause Minecraft Bedrock to freeze on startup?

Yes, Discord's in-game overlay injects a hook directly into the game's DirectX pipeline, which often breaks Bedrock's startup window. Antivirus suites such as AVG, BitDefender, ByteFence, McAfee, and Norton are also known to block Bedrock's network authentication threads.

How do I clear the Windows Store cache if Minecraft will not update or open?

Press Windows Key + R, type wsreset.exe, and press Enter. A blank Command Prompt window will appear, flush the temporary Store cache, and close automatically within a few seconds to fix package error 0x80073CFB.

Defeating the Red Screen Crash Loop

Silent Bedrock crashes stem from specific failure points in the UWP pipeline. Immediately reinstalling rarely resolves the issue if the root cause is a locked Runtime Broker process, a dated Gaming Services build, or an aggressive antivirus hook.

Kill the Runtime Broker child process in Task Manager and turn off active overlays. If the red screen remains, update Gaming Services to build 19.87.13001.0 or newer via the Xbox repair tool, execute wsreset.exe, and run an SFC scan to fix corrupted Windows DLLs. If a full reinstall becomes necessary, copy your minecraftWorlds folder first so your local maps remain protected.