Search Issue Tracker
Fixed
Fixed in 3.6.1
Votes
1
Found in [Package]
3.6.0
Issue ID
HUBX-987
Regression
Yes
LicenseClient launch error code 5 in the Unity Hub (ACCESS_DENIED)
Reproduction steps:
1. Open the Unity Hub
Expected results: The Unity Hub opens successfully
Actual results: The Unity Hub fails to open
Reproducible with: 3.6.0
Reproducible on: Windows 10, Windows 11
Note: Not reproduced by the CQA
Workaround:
Launch Unity Editor directly by double-clicking on the executable. A window will pop up with options to Create an empty project to Open an existing project.
Alternatively, you can create a new project by using the command in Terminall/CMD
`<path_to_editor_executable> -createProject <path_of_new_project>`
or open an existing project with
`<path_to_editor_executable> -projectPath <path_ofexistiong_project>`
More information about Unity Editor command line arguments can be found here: [https://docs.unity3d.com/Manual/EditorCommandLineArguments.html]
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 3.6.1):
Fixed in 3.6.1