
If you're using NVM for Windows and see the following error: nvm enabled activation...
If you're using NVM for Windows and see the following error:
nvm enabled activation error:
NVM_SYMLINK is set to a physical file/directory at C:\Program Files\nodejs
Please remove the location and try again,
or select a different location for NVM_SYMLINK.
You're not alone. This is a common issue when switching from a traditional Node.js installation to NVM.
This guide explains the root cause and provides a guaranteed step-by-step fix.
When Node.js is installed using the official Windows installer, it creates this directory:
C:\Program Files\nodejs
However, NVM for Windows uses this same path as a symbolic link (NVM_SYMLINK) to dynamically switch between Node versions.
If a physical directory already exists there, NVM cannot override it — and activation fails.
Before making changes:
This prevents file locking issues.
cmdAdministrator privileges are required because we are modifying Program Files.
Windows may block deletion due to TrustedInstaller permissions.
Run:
takeown /f "C:\Program Files\nodejs" /r /d y
Then grant full permissions:
icacls "C:\Program Files\nodejs" /grant %username%:F /t
taskkill /f /im node.exe
taskkill /f /im npm.exe
This ensures no processes are locking files.
rmdir /s /q "C:\Program Files\nodejs"
Command flags explained:
/s → Deletes all subdirectories and files/q → Suppresses confirmation promptsOpen PowerShell as Administrator and run:
Remove-Item "C:\Program Files\nodejs" -Recurse -Force
If the directory still refuses to delete:
rmdir /s /q "C:\Program Files\nodejs"
This resolves most background file lock issues.
Once the directory is removed:
nvm on
Then install and activate a Node version:
nvm install 18
nvm use 18
node -v
You should now see the installed Node version.
If you're switching from a direct Node installation to NVM:
C:\Program Files\nodejs is deletedThis prevents activation conflicts entirely.
This error occurs because NVM relies on symbolic linking, and Windows does not allow it to overwrite an existing physical directory.
Following the above steps will completely resolve the NVM_SYMLINK activation error in most Windows environments.
gemmaI ported the whole Gemma-4 family — E2B, E4B, 12B, 31B, and the 26B-A4B MoE — to run on...
communityHey DEV, I'm Tobore. Let's actually connect. I've been on here for a while now, mostly writing and...
ai(yep, kinda clickbait, just for the funsies 😊) At the beginning of the year, I relaunched my...
aiMy laptop was sitting idle with the fan at full tilt. Nothing was running that I knew of. The culprit...
githubactionsI Built a Thing! TL;DR — Google Gemini-based Pull Request reviews and Issue Triaging for...
aiI've been hearing the word "harness" thrown around a lot lately. I assumed it just meant "the IDE" or...
Workflows from the Neura Market marketplace related to this DeepSeek resource