How to Fix Zenless Zone Zero “Unity Error” On PC

The “ZenlessZoneZero – Unity 2019.4.40f1_0d9cc85b4” message on PC is usually the title of a Unity crash window that appears when Zenless Zone Zero fails very early during startup. In simple terms, the game begins launching, but Unity crashes before the game can fully open because something interrupts engine initialization, such as the graphics renderer, GPU driver communication, launcher access, game files, overlays, or required runtime components.

This crash can appear immediately at launch, right after pressing Play in the launcher, or during the first loading screen. In some cases, the game closes silently. In others, Windows shows a Unity crash popup with the engine version in the title instead of a more specific in-game message.

This issue is most commonly linked to temporary launcher or Windows glitches, permission problems, graphics API conflicts, corrupted or unstable GPU drivers, damaged game files, overlay or monitoring software conflicts, or missing/corrupted runtime components such as Microsoft Visual C++ Redistributables.

If the game crashes immediately after clicking Play, start with the launcher, permissions, overlays, and graphics-related fixes first. If it crashes during the first loading screen, game file corruption, drivers, or runtime components become more likely.

1. Restart Your PC

Restarting your PC helps because launcher services, overlays, cached processes, or partially closed background tasks can remain active even after you exit the game. If one of those processes is stuck, it can interfere with the next launch and cause Unity to fail during initialization.

A full restart clears temporary memory, refreshes Windows services, and gives the game a clean startup environment.

1. Save any open work and close all running applications.
2. If HoYoPlay, Epic Games Launcher, or Zenless Zone Zero is visibly stuck, press Ctrl + Shift + Esc to open Task Manager and end those processes first.
3. Restart your PC normally from the Start menu.
4. After Windows loads again, open the launcher and test the game.

2. Run the Launcher and Game as Administrator

Running the launcher or game as Administrator can help when Windows is blocking access to installation folders, cached files, anti-tamper components, or runtime dependencies needed during startup. This is especially worth trying if the game crashes immediately after you press Play, or if the launcher opens the game and it closes right away.

Because some startup problems are tied to the launcher and others are tied to the game executable, test both instead of only one.

1. Close Zenless Zone Zero and its launcher completely.
2. Right-click the launcher you use to start the game, such as HoYoPlay or Epic Games Launcher, then click Run as administrator.
3. Try launching the game.
4. If the crash still happens, open the folder where Zenless Zone Zero is installed.
5. Right-click the game’s .exe file and click Run as administrator.
6. If either method works, you can make it permanent through Properties > Compatibility > Run this program as an administrator.

3. Try Launching the Game with a Different Graphics API

This Unity crash can sometimes happen when the game starts with a graphics API that does not behave well with your current driver or hardware setup. In such cases, forcing a different DirectX mode can help the engine initialize properly.

For some systems, DirectX 12 causes instability during launch. On others, DirectX 11 is the less stable option. Testing both can help because the issue is often tied to how the current GPU driver handles the game’s renderer during startup.

1. Close the game and its launcher completely.
2. Right-click the Zenless Zone Zero .exe file and click Copy as path.
3. Right-click inside the same folder and select New > Shortcut.
4. Paste the copied path, add a space, and then test a launch argument such as -force-d3d11 or -force-d3d12.
5. Name the shortcut and click Finish.
6. Launch the game using that shortcut and test it.

Note: Start with -force-d3d11 if the crash began after a GPU driver update or if DirectX 12 seems unstable on your system. If that does not help, test -force-d3d12 instead. However, some launcher-managed games may ignore manual launch flags, so if there is no change at all, do not assume this step proved anything. It may simply mean the launcher did not pass the argument to the game.

4. Clean Reinstall Your Graphics Driver

A damaged or unstable graphics driver installation can cause Unity-based games to crash during startup. This usually happens after a driver update, a failed installation, or a conflict left behind from older driver files.

Using a proper cleanup method removes old driver remnants more thoroughly than a normal uninstall. After that, installing a stable driver again can restore proper communication between the game, DirectX, and the graphics card.

• AMD users: Use AMD Cleanup Utility or DDU to remove the current AMD graphics driver completely.
• NVIDIA users: Use DDU or choose a clean installation when reinstalling the NVIDIA driver.
• Restart your PC after the cleanup finishes.
• Install a stable graphics driver version manually instead of relying on a possibly broken in-place upgrade.
• If the crash began right after a new driver version, consider testing an older stable driver instead of the newest one.
• Restart your PC again after installation.
• Launch the game and test whether the Unity crash is resolved.

Note: Some users report better results with specific driver versions, but that varies by GPU model, Windows build, and system configuration. Treat those reports as examples, not guaranteed best versions for every PC.

5. Fully Reinstall the Launcher and Game

If the problem still continues after trying all of the fixes above, the next safest step is a full reinstall of both the launcher and the game, especially if the crash began after a failed update, an interrupted install, or a sudden system shutdown.

This helps rule out a broken launcher component, damaged cached data, or a corrupted game installation that an ordinary repair scan may have missed.