Start Building

Problem Summary

On Unity 2026.5, some projects crash or hang as soon as you open Window → Package Manager. You may see the editor disappear without an error dialog, or a generic crash report mentioning package manager, network, or domain reload.

This usually means Unity is hitting a corrupt cache, a broken package, or version compatibility problems while loading the Package Manager UI. The steps below walk you through fixing the underlying causes instead of just retrying and hoping it works.

Step 1 – Confirm It Is a Package Manager Crash (Not Something Else)

Before changing anything in your project, confirm the pattern:

  1. Open the project normally.
  2. Work in the Scene or Game view for a minute.
  3. Open Window → Package Manager.

If the editor only crashes when opening Package Manager (and not during normal editing), you are likely dealing with:

  • Corrupted cache folders.
  • A broken or missing package.
  • A registry or network configuration problem the Package Manager does not handle gracefully.

If the editor crashes at random moments, treat that as a separate general stability issue and check logs for GPU drivers, memory, or script issues.

Step 2 – Clear Unity Package Manager Cache and Temp Folders

Unity caches package metadata and downloads locally. If that cache is corrupted, the editor can crash when trying to read it.

  1. Close all Unity editor instances.
  2. Locate the Unity cache folders for your OS (paths may differ; use the 2026.5 docs for exact locations):
    • On Windows: look for AppData\Local\Unity\cache and AppData\Local\Unity\cache\packages.
  3. Delete or rename the package cache folders:
    • Example: rename packages to packages_backup so you can restore if needed.
  4. Reopen your project in Unity 2026.5.
  5. Try opening Package Manager again.

If the crash disappears, the cause was likely corrupted cached metadata. Unity will rebuild the cache from scratch, which may take slightly longer the first time.

Step 3 – Check Packages/manifest.json for Broken or Incompatible Packages

Unity reads your project’s Packages/manifest.json when it loads the Package Manager. Invalid or incompatible entries can cause hard crashes, especially if they reference custom registries or missing files.

  1. With Unity closed, open your project folder.
  2. Open Packages/manifest.json in a text editor.
  3. Look for suspicious entries:
    • Packages with "file:" or "git:" URLs that no longer exist.
    • Custom scoped registries pointing to servers that are offline.
    • Experimental or preview packages tied to older Unity versions.
  4. Temporarily comment out or remove recently added or obviously broken entries.
  5. Save the file and reopen Unity.
  6. Try Window → Package Manager again.

If the editor no longer crashes, re-add packages one by one to find the culprit. Keep a note of the exact package name and version that causes the crash so you can avoid it or look for a newer build.

Step 4 – Disable Custom Registries Temporarily

If your project uses scoped registries (for example, a self-hosted npm feed or a partner’s registry), a misconfigured or unreachable registry can crash the Package Manager.

  1. Open Packages/manifest.json.
  2. Find the scopedRegistries section.
  3. Comment out or temporarily remove all custom registries, leaving only the default Unity registry.
  4. Save the file.
  5. Reopen Unity and open Package Manager.

If Package Manager now opens safely:

  • The issue is likely a network, certificate, or compatibility problem with that registry.
  • Fix the registry configuration or talk to the provider before turning it back on.

Step 5 – Try a Fresh Empty Project in Unity 2026.5

To confirm this is project-specific and not a general 2026.5 editor bug on your machine:

  1. Launch the Unity Hub.
  2. Create a new empty 3D or 2D project using Unity 2026.5.
  3. Once it opens, go to Window → Package Manager.

Outcomes:

  • If the empty project works fine:
    • The crash is project-specific.
    • Focus on your Packages folder and manifests as described above.
  • If the empty project also crashes:
    • You may have a broken Unity 2026.5 installation or a deeper system issue.
    • Reinstall the editor version from Hub and verify GPU drivers and OS updates.

Step 6 – Reinstall or Add a Clean Unity 2026.5 Editor Instance

Sometimes the installed editor binaries or local modules are themselves corrupted.

  1. In Unity Hub, install another 2026.5 editor instance or reinstall the existing one.
  2. Ensure the installation includes:
    • The platforms you actually target (Desktop, Android, iOS, etc.).
    • The latest modules recommended for Package Manager.
  3. Open your project using the fresh editor install.
  4. Try opening Package Manager again.

If this fixes the crash globally, keep this editor as your primary 2026.5 install and remove any older broken copies.

Step 7 – Verify Network and Proxy Settings

Package Manager talks to Unity’s services and any custom registries. Aggressive firewalls, proxies, or VPNs can cause timeouts or crashes in certain versions.

  1. Temporarily disable VPNs, strict proxies, or filtering tools.
  2. Ensure your firewall allows Unity editor and Hub network access.
  3. Restart the editor and open Package Manager.

If it now works, add exceptions for Unity’s executables and services or configure your proxy to allow the relevant endpoints.

Prevention Tips

To reduce the chance of this happening again:

  • Avoid keeping stale or unused packages in manifest.json.
  • Regularly commit and back up your Packages folder and manifest so you can roll back a bad change.
  • Test new or preview packages in a separate branch or test project before using them in production.
  • Keep Unity 2026.5 updated to the latest patch release, where many Package Manager crashes are usually fixed over time.

Related Fixes and Next Steps

If you are still running into issues after these steps, see these related help articles:

  • Unity Package Manager Hangs/Stuck Loading – How to Fix (Network and cache issues).
  • Unity Build Fails with Scripting Backend Error – Complete Solution.
  • Unity 2026 Editor Slow or Laggy – Performance Fix.

Bookmark this page for future troubleshooting and share it with your team so everyone has the same checklist the next time Package Manager misbehaves.