The "Preparing Game Data" freeze is almost always a software communication breakdown rather than a hardware issue. In 90% of cases, or disabling OneDrive file locking will resolve the issue immediately.
Cut and paste this folder onto your Desktop (this serves as a backup for your replays).
Troubleshooting StarCraft 2 "Preparing Game Data" Issues . This problem usually stems from a language localization mismatch between your Battle.net desktop client and the internal game engine settings, which forces the system to repeatedly stream uninstalled asset packs. What Causes the "Preparing Game Data" Loop? starcraft 2 preparing game data
Look at your Windows taskbar tray and click the (the blue or white cloud).
In the folder that opens, locate the and Battle.net folders. Right-click these folders and select Delete . The "Preparing Game Data" freeze is almost always
What are you using (Windows 10, Windows 11, or macOS)? Are you using a third-party antivirus program?
Ensure your system meets the recommended specs for modern SC2 play, as insufficient RAM can bottleneck data preparation: 4 GB Recommended (8 GB preferred for modern systems). Troubleshooting StarCraft 2 "Preparing Game Data" Issues
The progress bar had been stuck at 64% for three hours. Outside, the neon signs of the Seoul district hummed in the rain, but inside the darkened apartment, the only sound was the frantic whirring of a cooling fan struggling against a decade-old processor.
What is being prepared? Not just maps or assets. The game is aligning three asymmetrical nightmares: the swarm’s digestive creep, the Protoss’s psionic matrix, the Terran’s mechanical grind. It is verifying build orders not yet chosen, computing the exact second a reaper will peek over a cliff, pre-calculating the supply block that will inevitably hit at 36/36.
Right-click the and select Properties . Navigate to the Compatibility tab.
Ji-Hoon had finally found the old drive in a box of mothballed tech. But the modern Battle.net launcher didn’t recognize the architecture. It hung there, spinning, trying to bridge the gap between 2010’s code and 2026’s hardware. 65%.