EBUSY: resource busy or locked

that was exactly my problem, thanks!

 

Dang, bro, this did the trick for me! You are a lightsaber! I mean lifesaver

 

Deve-se fechar o VS Code, o recurso está em uso, o compilador o mantém, ao fechar você consegue o acesso, quando um recurso é baixado, precisa compilar para ler e se tornar funcional.
Embora seja um problema chato, não tem muito o que fazer a não ser fechá-lo .

 

This is happening in version 2020.3.29f as well.

 

I have visual studio closed, windows real-time protection turned off. Yet resource is still locked.

This issue will also occur after a fresh boot, and launching straight into Unity.

Incredibly frustrating, really.

Only workaround to get Unity to launch is to remove 'com.unity.visualstudio' from both Packages > manifest.json and packages-lock.json, but this is not a solution as attempting to reinstall the visual studio package will also throw the same error:



Info:
Platform - Windows 10 Pro, 10.0.19044 Build 19044
Unity Hub - v3.0.1
Unity Editor - 2021.2.13f1

 

close your VS code

 

Thanks, It worked. What a silly issue!

 

that solved my problem thanks!

 

I run into this every few months and throw everything at the wall until something sticks. Currently stuck on this again



I have tried all of the following multiple times:

- Delete Packages\packages-lock.json , Temp, and Library recursively
- I already have the git file monitor turned off

- No code editors are open
- Process explorer shows no handles on anything in the folder for the game
- disabled windows defender active protection
- rebooted many times and immediately retried opening the project without opening any other programs


Edit: Fixed it! I started closing processes one by one until I found the issue. I believe the issue was the indexing service of "search everything" by voidtools (great tool btw, gets around the poorly implemented start menu search on Windows).

 

oh god thanks, was driving me crazy

 

I have this exact same issue on 4 different machines but only on Unity 2021 versions. The worst is i always get it to run after thousands of reboots or marking the ProjectCache folder to not be read-only. But I never seem to find the reason for why it did work this time. I also checked the folders via the process explorer and there is only Unity processes acessing the files. Any UnityEngine dev here who knows what the issue is ?

 

Wauuuuuu worked like a charmmm

 

Thanks mate!

 

git monitoring mentioned previous in thread lead me to close Fork app before updating VS (*NOT* VS Code) package
no more EBUSY: resource busy or locked on 2021 LTS but still getting in on 2019 where it's not possible to update it past 2.0.9 (current being 2.0.15)

 

btw I tried to look for the locked resource when the error happened but it looked like the whole temp directory was gone already at the time the error dialog was displayed
(also maybe worth mentioning - my unity UPM/npm caches are not at default location but changed via UPM_ env variables)

 

Thank you, it's work for me

 

FWIW spamming UPM's 'Update to 2.0.xx' button whenever possible eventually worked ¯\(o_o)/¯

 

Perpect!!!!! thanks

 

Revisited this recently on my Windows machine and unsurprisingly I am still encountering the issue.

Whatever the problem is, it's on Unity's end. They aren't interested in solving it, and I'm not incentivised to find a solution. Whatever 'bcl.exe', 'vswhere.exe', 'COMIntegration.exe' is, it's not an issue on OSX.

I'm tired of finding a solution, and have been using Unity with no issues on OSX for the past 3 months. So if you're fortunate enough to own both platforms, just work on your mac.

 

bruh same, thanks!

 

To confirm, closing onedrive fixed the issue for me, presumably because unity and onedrive had access to the same project folder.

 

Thank you so much dude. I was looking solution for this.

 

Works for me! Thanks!

 

Thank you!

 

I had this issue when my VisualStudio Professional trial version was outdated.
After uninstalling VisualStudio 22(which was outdated) via VisualStudio Installer, the error was resolved

 

I just found a possible solve for this issue:
Disable Microsoft Defender Real-time protection! Or even better: If you keep your projects in a single folder, e.g.: "Unity projects/", then exclude it from real-time protection.

 

Thanks very much Sir. It solved the issue.

 

What was the process called? I cant seem to figure out which one it is. and yeah Search Everything is amazing except for now

 

Getting same issue. I don't use VS Code. I've tried unchecking "read only" from my folders - but windows 10 keeps reverting it back to read only. I've tried everything I can find to get windows to stop doing that, no success. Any ideas? Thanks

 

This is what is was for me, but I had to turn off all the options in windows security "virus and threat protection," including cloud-delivered protection

 

Thanks

 

Closing VSCode worked for me, too. Thank you!

 

Thank you so much.><