Re: Unity Hub 3.6.1 (Windows 10) not opening prior to 2023.1.19f1 version projects

Unity Engine
1

Re: Unity Hub 3.6.1 (Windows 10) not opening prior to 2023.1.19f1 version projects

Hello, I just updated my Unity Hub (Windows 10) to version 3.6.1 and now it no longer opens my projects versioned before 2023.1.19f1.

I have tried:

-Restarting my computer

-Restarting Unity Hub

-Reinstalling Unity Hub

-Opening an earlier version game from an open 2023.1.19f1 version game (this crashed and corrupted the open game)

-Opening the Scene asset from an earlier version game, directly in Windows Explorer (did not work)

Any assistance would be greatly appreciated. Thanks in advance.

(PS - This is my first time posting in the forum so please excuse if I’m not posting in the right place or manner.)

2

What does “not open” mean? Nothing happens? Error message?

Check the editor.log for errors. Feel free to post them here.

3

Thank you, @CodeSmile , for responding.

Hub attempts to open the project, and the spinning loading wheel icon appears next to the project name. However, after 10+ minutes, the project has not opened and the spinning loading wheel icon disappears. The project remains in the Hub project list with an updated “Modified” time stamp – according to how long ago I tried to open it.

I’ve inspected the Hub logs, and slimmed down the below excerpt to what seems relevant, though with my present understanding am unable to identify what the problem is:

{“timestamp”:“2023-11-11T23:56:02.503Z”,“level”:“info”,“moduleName”:“LocalProjectService”,“message”:“[ ‘openProject projectPath: D:\\UnityGamesSept2023\\TEMPLATE - Pickup Game - D Drive, current editor:’, undefined ]”}

{“timestamp”:“2023-11-11T23:56:02.533Z”,“level”:“info”,“moduleName”:“LaunchProcess”,“message”:“[ 'Spawning editor instance with command: ', ‘D:\\UnityGamesSept2023\\UnityVersionInstalls\\2019.4.7f1\\Editor\\Unity.exe’, ', and arguments: ', [ ‘-projectpath’, ‘D:\\UnityGamesSept2023\\TEMPLATE - Pickup Game - D Drive’, ‘-useHub’, ‘-hubIPC’, ‘-cloudEnvironment’, ‘production’, ‘-licensingIpc’, ‘LicenseClient-Debbie’, ‘-hubSessionId’, ‘bd247da3-2471-4f2e-8ebf-bc603ec5afe0’, ‘-accessToken’, ‘_8_K8M-dhO2TXSkEQDjPQmEwRJN6-7SMREvJYqJzWmA002f’ ] ]”}

{“timestamp”:“2023-11-11T23:56:12.543Z”,“level”:“info”,“moduleName”:“LaunchProcess”,“message”:“[ ‘child process exited with code 0’ ]”}

4

I meant the editor.log not the hub log. If the editor fails to load any errors will be in the editor.log. :wink:

But seeing that you have both projects and editor installs on D: it could be a permission issue. It may depend on how you created that drive and folder (via the installer or manually, on this or a previous system, as the logged in user or as admin, etc etc). The executables and the project may likely require a different set of permissions too.

Also make sure you add the root folder to Windows Defender‘s exclusion list, and if you run any 3rd party so-called ‚security‘ software uninstall that (or at least disable) as they cause more trouble and harm than what their supposed purpose and that they take money for it would indicate.

5

same issue.

Licence file is removed. Workspaces are removed/installed. Got a new licence file.
Editor.log shows:
Current license is invalid and cannot be activated. You must delete the license file and then activate a new license on current machine.
Exiting without the bug reporter. Application will terminate with return code 0

So, repeated again and again with no results.

Suspect something wrong in “Unity_lic.ulf” file:

Also, OS (Windows 11 Pro) is switched to English locales everywhere.

Could you please share any suggestions?

UPD:
Have produced unlogic step - switched project version from 2021.3.4f1 to 2021.3.23f1.
The issue is passed and all projects are works successfully.

Looks like a licence bug between some Editor versions and Hub 3.6.1.

6

This bug is happening with me too :slight_smile:

7

Thank you @CodeSmile and @VladimirNull for the feedback.

I have been searching through my hub and editor logs, and it seems I have a license issue as well, which from researching, seems to be affecting other users too.

(It doesn’t seem to be related to the drive, nor the security settings, as no settings have changed in these arenas, and it was working before. In addition, the logs flag license issues.)

At this time, I will continue to dev in the version that is working, and monitor/troubleshoot the issue.

Again, thank you for all the feedback and assistance. I have learned a lot through the process. Take care.