EBUSY: resource busy or locked

Unity Engine
1

Hi there,
I have just downloaded 2019.3.5f1 and I wanted to add Entities package to a new project. This is what I have got as an error message in Console:

Cannot perform upm operation: EBUSY: resource busy or locked, open ‘-----\Library\PackageCache.tmp6760amsihKOTPeMr\copy\Unity.Entities\ConverterVersionAttribute.cs’ [NotFound]
UnityEditor.EditorApplication:Internal_CallUpdateFunctions()
Error adding package: com.unity.entities@0.6.0-preview.24.
UnityEditor.EditorApplication:Internal_CallUpdateFunctions()

Let me know how to fix it.

4 Likes
2

Hello,

Sorry to see that you are having this issue. Could you please include the editor logs. It could be some kind of permission issue on the folder. Maybe a super eager antivirus removing the files?

If you try in other Unity versions do you have this problem?

Cheers,

Supi

1 Like
3

I had the same issue recently. Simply go to the folder location specified, open the folder properties window and make sure to have Read Only unchecked so that Unity could have read/write access to that directory. Hope this helps!

17 Likes
4

Mine was due to having VS Code open for editing my scripts. Once I closed that, it solved my issue.

265 Likes
5

Same issue, happens a LOT. And theres usually no way to move forward, you can try removing your library folder etc reimporting everything. Been seeing this for ages now! Unity need to actually solve these type of issues asap, essentially they brick the whole damn package manager, and in extension the whole engine.

5 Likes
6

Me too.

Thanks

10 Likes
7

i got this in console
Error adding package: com.unity.ml-agents@1.0.5.
UnityEditor.EditorApplication:Internal_CallUpdateFunctions()

1 Like
8

Thanks, mate.

3 Likes
9

this is the one. i love you

3 Likes
10

Problem solved! Thanks!

2 Likes
11

It fixes it, thanks

5 Likes
12

thank you

1 Like
13

solved it. thanks

2 Likes
14

Closing VSCode fixed this for me, too…and that disturbs me. Why is VSCode locking files that I’m not even opening?

3 Likes
15

It seems to try to be smart behind the scenes to facilitate code completion, “go to definition,” and other features. It probably has to open a lot of files to maintain that sort of context.

1 Like
16

Gracias my brother!!

17

Worked for me too.

18

Had the same issue.But once i close vscode and tried again,it worked

1 Like
19

Another one solved thanks to closing VSCode

1 Like
20

Oh man! You saved my night! hahahaha
Closing VsCode solved the problem… f***
xD