Unity Hub - Crash Adding Existing Project from Disk

Unity Engine
, , ,
1

I can no longer add an existing project from disk.

When I click on ‘Add’ → ‘Existing Project from Disk’, the application crashes and closes.

I tried a workaround by adding the project using the command line (Unity -projectPath "PathToProject"), but it didn’t work.

Is there another workaround I can try?

2

did you have used some sort of external drive or usb or something like that? is really strange and an app should not crash if it doesn’t find a location.

it also could be that the app it is trying to access a protected folder and some antivirus/firewall is deniying and closing the app. these apps sometimes have “remember option” so if you ever said yes to not allow the app to access a folder then maybe is why no notifications pops up

3

Could you post the Hub log file?

I would try reinstalling the Hub if Antivirus or permissions can’t be the issue. You may also want to delete any of the Hub’s cache data under AppData before reinstalling.

4

Here are the logs.

I’ll proceed with deleting and reinstalling everything now.

logs.zip (1.2 MB)

No luck. Deleting and reinstalling did not solve the problem.

5

Using a different user account on my machine, I was able to open projects. I’m not sure if it’s related, but I was also having issues with my main user account when trying to create ‘Linux Builds’ because of the space in my username ‘Cezar Wagenheimer’.

6

Any update on what the solution to the issue was?

7

@AppleseedSmoothie
Could you please file a bug report and our support team will be able to help you. If there’s a bug, we’ll get a fix out ASAP.

8

In my case, the crash was caused by the IBM Aspera plugin used for uploading Nintendo Switch builds. Somehow, it interfered with Unity when opening projects. I uninstalled it, which fixed the problem. I later reinstalled it, and the issue never came back.

9

Thanks uninstalling Aspera fixed it for me!

10

I had the same problem and just fixed it by changing some of the windows dll the hub was using.

In summary, some of the windows dll that were used in the hub need to be updated to include fixes microsoft have made.

Looking at the crash report in C:\Users\<User>\AppData\Roaming\UnityHub\Crashpad\reports using WinDbg I saw the error came form MSVCP140.dll and related to mutexes.

Using this info I found someone giving an explanation for another app (this one in particular on github) gave me enough of a hint.

I basically copied the libraries from VisualStudio (C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64) to UnityHub (C:\Program Files\Unity Hub\resources\app.asar.unpacked\node_modules\@edt\proxy-helper\build\Release\win-x64\)

In particular I’ve copied:

"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\msvcp140_atomic_wait.dll"
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\msvcp140_codecvt_ids.dll"
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\vcruntime140.dll"
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\vcruntime140_1.dll"
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\msvcp140.dll"
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\msvcp140_1.dll"
"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\msvcp140_2.dll"

But I’m not sure which ones are actually necessary or not.

11

Hi @betBayo

I’ve passed on the info to the relavent team. We’ll get that package fixed for 3.16 or 3.17.

Thanks for the detailed report!

12

@betBayo Could we have a copy of the crash report if you still have it on hand

13

I had the same problem as well, and @betBayo solution resolved the crashing.
PRE-FIX LOGS + CRASH REPORT:
logs.zip (109.8 KB)
Crashpad.zip (280.3 KB)

POST-FIX LOGS:
logs.zip (34.7 KB)

14

Hey folks,

The team of the package is asking if you could run a windows update. You should receive a newer system version of the VC++ runtime library, which the @etd/proxy-helper package should be able to run against.

We’re looking into a more permanent solution for 3.17.

Thanks!

15

Hi, I ran Windows Update and also installed the latest Microsoft Visual C++ 2015–2022 (x64 & x86), then restarted and the same issue still occurs. I’ve even tried using older Unity Hub versions to see if that did anything, cleared the hub cache, but was still getting the same problem.

16

Hi @AfonsoStuff

Thank you for the update! I’m working with the team responsible to get a fix out ASAP. I can’t provide a ETA yet, but hopefully in the next week or two.

For now, could you follow the fix above: Unity Hub - Crash Adding Existing Project from Disk - #10 by betBayo

17

Awesome! Just tried it and replacing only msvcp140.dll and vcruntime140.dll fixed it for me!

18

This just worked for me as well, thanks everyone!

19

Just had the same issue and managed to resolve it by following @betBayo 's instructions. Does anyone know what’s actually causing this, and whether it affects all Unity Hub installs or just some users?

20

just as a reference,
vs2026 broke 3ds max also (caused crashing),
this was the related issue in VCRedist:
https://developercommunity.visualstudio.com/t/Calling-omp_set_dynamic-before-pragma-o/10973188?%2F10347194=