Starting n8n fails with EBUSY error

I am afraid I don’t know what else might be locking these files :frowning:

Perhaps a particularly aggressive malware scanner or another 3rd party application? No matter what I tried I couldn’t reproduce this on my Windows machine.

If you can’t narrow this down further perhaps you might want to try running n8n using docker rather than npm?