Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1f1
Issue ID
921947
Regression
No
Unity Launcher hangs when Windows user has no access to "C:\Users\<name>\AppData\Roaming\Unity\Packages" folder
Reproduction steps:
1. Navigate to "<Drive Letter>:\Users\<Name>\AppData\Roaming\Unity\"
2. Right click on "Packages" folder and open properties
3. Open "Security" tab
4. Click "edit"
5. Select your Windows user account in "Group or user names" list
6. Put the checkbox in the row "Full control" and column "Deny" in the "Permissions for <...>" list
7. Click "Apply"
Expected: Unity launches
Actual: Unity home screen opens, but is blank -OR- "Copying file failed" error window appears
Also, if the error window appears, clicking on any available button will throw the same error just about another file (see the attached Editor.log file). After all error windows are closed, it proceeds to the blank Unity home screen.
Reproduced on: 5.5.4f1, 5.6.1f1, 2017.1.0f3, 2017.2.0b2
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
Add comment