Modifying folders not created in the workspace sometimes causes Error: EPERM: operation not permitted

[Dahesor]

I started a new data pack, and copied some files and folders from another data pack to this new one. However, when I am trying to rename the copied folders, vs code took a minute and said Error: EPERM: operation not permitted.

I disabled all my extensions and it can rename normally again. I then enabled my extensions one by one and test if it can rename, and I learned it is Spyglass causing this problem.

Moving all the contents inside this folder away makes it rename-able again, but if I put them back in then I can no longer rename it.

This never happened on folders that I created in this new data pack.

When I copied the folders from another data pack into this new one, a lot of warning popped out because all the name space paths are incorrect. It might has something to do with this? Or something wrong in the cache?

I also searched on the internet and found the following posts, not sure if they are useful:

https://stackoverflow.com/questions/58707277/vs-code-error-eperm-operation-not-permitted

microsoft/vscode#184145

Thanks

[misode]

Duplicate of #1414

[carloswm85]

Here's a workaround to this problem: https://stackoverflow.com/a/78900972/7389293

---

This seems to be a problem related to running MULTIPLE processes inside VSCode, and with this disallowing the move of folders.

I received this error while running an Angular 17 app and a NodeJS server at the same time, and trying to move one of the project folders:

I solved it in Windows 11 by using File LockSmith.

1. Stop all the visible task and processes you may have running:

   

2. And then execute File Locksmith in the projects root folder (in this case, named _ta-app).

3. Press End Task buttons for all child processes, except for the main VSCode editor one.

   

4. That should enable moving/renaming folders.

   

As you can see, it is working now.