Search Issue Tracker

Fixed in 2018.2.X

Fixed in 2018.1.X



Found in



Issue ID




Unity crashes on PackageManager::PackageAssets::RegisterPackages after opening a project stored in cloud storage



Steps to reproduce:
1. Download and install Microsoft OneDrive
2. Create a new Unity project in OneDrive directory
3. Close Unity
4. Wait for the project to be uploaded to OneDrive
5. Open Unity
6. Open created project

Reproduced in: 2017.3.0p1, 2017.3.0f1, 2017.2.1p1, 2017.2.0p4
Didn’t reproduce in: 2018.1.0b1, 2017.3.0b11, 2017.2.0p3, 2017.1.3f1, 2017.1.0a1
Regression introduced in: 2017.3.0f1, 2017.2.0p4

Note: Does not crash on 2018.1.0b1, Unity Package Manager Error "Failed to resolve packages" appears instead (Case 981057)

Comments (9)

  1. rdhiraj802026

    Apr 28, 2021 05:46

    Check my comment for solution(not sure it works for everyone).

    PS: Not to spam.. Reposting here so it might help someone :)

  2. awais503

    Jul 19, 2018 15:54

    Exit Unity. Delete Packages folder in your project. Reopen your project. Problem Solved.

  3. papix2008

    May 09, 2018 01:46

    me too,but it's ok when i open the project with unity2017 last month.

  4. gerryhd

    Apr 27, 2018 00:01

    This error is still present in 2017.3.1f1 on Windows 10

  5. davidcox70

    Apr 22, 2018 14:09

    Same here. Unity 2017.3.1f1. Windows 10.

    I had been using a One Drive folder as the project folder without issues for some weeks. Then after a re-install of 2017.3.1f1, I found that Unity almost always crashes on startup unless I (1) kill OneDrive and (2) delete the UnityPackageManager folder from the project folder. Then it will always start successfully. I can restart OneDrive immediately after Unity launches and have no problems while working.


  6. xruizify

    Mar 29, 2018 16:43

    My Unity version was also crashing with the Package Manager while "resolving packages". Running Unity as administrator fixed all my problems!!!

  7. willkillyaquick

    Feb 06, 2018 16:22

    Moving files locally fixes the issue for now. However, this is not ideal as I work on this project from multiple PCs (Not at the same time of course)

  8. Pixel_br

    Jan 30, 2018 11:29

    Looking in to the OBEREON sugestion above, I stumbed in to this...

    I have two computers, one at work and other at home.
    But the usernames are different, hence, they are not the same in the csproj files.

    And the project opens here at my work computer, since the path matches with the csproj file. Need to test in my house later today.

  9. Obereon

    Jan 22, 2018 16:38

    I was able to correct the issue by removing drive references from the csproj files - change c:/x/ to x/
    The root cause appeared to be the inability to find the necessary assets and packages due to the change in drive letter and the use of absolute paths.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.