Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
2
Found in
Issue ID
1287098
Regression
Yes
Unity fails to open project with error: Failed to resolve packages: An operation that requires exclusive access to the project..
For some users Unity is failing to open and shows the following error:
Failed to resolve packages: An operation that requires exclusive access to the project is already running and must be completed before another can be started.. No packages loaded.
This issue happens only if the resolve package operation takes over 2 minutes to complete. Users will find this failure randomly while opening their projects.
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
- Action can't be undone after changing the base Controller on the Animator Controller
- The Axes Gizmo is wiggling around when moving around the Scene View with enabled Physical Camera and Isometric View
- The script can be dragged and dropped before it is compiled
- Double clicking script field no longer opens it in the external script editor
- [Android] Build fails with built-in PAD custom asset(s) when using sample Addressable
lupin4
Oct 02, 2022 18:10
Not fixed!!!!!!!!!!
lbenard
Apr 21, 2022 08:24
Not fixed, it still occurs in Unity 2020.3.25f1
vasaromb
May 28, 2021 08:51
2021.1.7f1 (64-bit), still occurs
PrabhakaranRajendran
May 17, 2021 04:37
2020.3.4 still the same issue is there
HiziProjects
Apr 14, 2021 12:17
2020.1.10, still occurs
Toylips
Nov 20, 2020 00:31
2019.4.14f1 same
Arthur_Kenichi
Nov 18, 2020 05:11
I had this problem in 2020.1.13f1. My workaround was selecting Continue instead of Retry or Quit, then the project opened with a lot of errors from missing packages, then I opened a scene of the game and right clicked on a random asset in the Project tab/window and then selected Reimport All.
Silverlock
Nov 17, 2020 15:42
I installed Unity 2019.4.14f1 yesterday and this error occurs each time I open Unity. The description says it's fixed in 2019.4. Is that accurate? Is there a patch I need?
AdamBebko
Nov 16, 2020 22:54
I also have this problem in 2020.1.11f1 can't figure out how to resolve it.
TCROC
Nov 16, 2020 05:27
I'm currently on 2019.4.14f1 and this error is still occurring for me