[Bug]: Access denied error when installing, reloading or uninstalling Vibrancy due to .node files being locked as "in use"

[tengri123]

A change was made to VSCode on Windows that causes it to lock all .node files as "in use", meaning that they're unable to be changed in any way while VSCode is running, which presents an issue to Vibrancy as it works as an extension in VSCode.

Need to investigate how to either:

• Unlock the file using handle.exe or other methods
• Update the file while VSCode is restarting
• Find other way to inject those files without VSCode locking them.

Current workaround: remove %APPDATA%\..\Local\Programs\Microsoft VS Code\resources\app\out\vscode-vibrancy-runtime-v6 manually using Explorer while VSCode is not running.

Edited by @illixion to add more info

[tengri123]

had to delete it's folder to fix it

[Jnorm911]

Same issue here, where is the local folder in Windows?

:edit: C:\Users\yourUserName\.vscode\extensions

[illixion]

Updated the issue with info on what the root cause of the problem is and a workaround. I don't have a lot of time to look into this as I don't use VSCode on Windows, so if anyone wants to take a look into it, I'd appreciate the help.

[illixion]

Added a workaround that should prevent this error from occurring on Windows. Any help with fixing this would still be appreciated as this issue prevents .node files from being updated, though they don't change often so this isn't high priority.