How to completely remove node.js from Windows

Asked 20/12, 2013 at 20:12 Answered 3/8, 2022 at 22:55

Solved node.js windows npm windows-7-x64

480

I uninstalled my previous version of node.js (0.8.11) and downloaded the latest, 0.10.24 from the node.js website and installed it. However, after running node --version, it still indicates that I'm running v0.8.11. Obviously, some stuff was left behind during the uninstall process, and it's causing me to have all sorts of errors when trying to add modules through npm. I've seen solutions to this for OSX and Linux, but couldn't find anything for Windows. I'm running Windows 7 64-bit.

Furthest answered 20/12, 2013 at 20:12 Comment(2)

This sounds bad, but did you restart afterwards? – Manifestation 20/12, 2013 at 20:19

Find the uninstaller (e.g. WIN-key, Uninstall NodeJS). Worked for me. – Divisionism 9/11, 2020 at 15:9

1164

How to remove Node.js from Windows:

Take a deep breath.
Run npm cache clean --force
Uninstall from Programs & Features with the uninstaller.
Reboot (or you probably can get away with killing all node-related processes from Task Manager).
Look for these folders and remove them (and their contents) if any still exist. Depending on the version you installed, UAC settings, and CPU architecture, these may or may not exist:

C:\Program Files (x86)\Nodejs
C:\Program Files\Nodejs
C:\Users\{User}\AppData\Roaming\npm (or %appdata%\npm)
C:\Users\{User}\AppData\Roaming\npm-cache (or %appdata%\npm-cache)
C:\Users\{User}\.npmrc (and possibly check for that without the . prefix too)
C:\Users\{User}\AppData\Local\Temp\npm-*

Check your %PATH% environment variable to ensure no references to Nodejs or npm exist.
If it's still not uninstalled, type where node at the command prompt and you'll see where it resides -- delete that (and probably the parent directory) too.
Reboot, for good measure.

Manifestation answered 20/12, 2013 at 20:25 Comment(30)

Went through this, and found C:\Users\{User}\AppData\Roaming\npm still existed. Deleted it, and made sure nothing referencing nodejs/npm existed in my PATH variable. Reinstalled, but it's still saying 0.8.11. – Furthest 20/12, 2013 at 20:37

what happens if you echo PATH in your command prompt? what's that output? (redact as necessary) – Manifestation 20/12, 2013 at 20:50

Well this is odd. I walked through your instructions again and can't find a trace of Node anywhere, but when I bring up a command prompt, I can still launch Node (0.8.11). So there's another installation somewhere, but I don't see anything out of the ordinary in %PATH% – Furthest 20/12, 2013 at 21:0

Look in C:\Windows\System32? The exe is simply node.exe (be default it lives in the %programfiles%\nodejs dir, but maybe it's ended up elsewhere? – Manifestation 20/12, 2013 at 21:1

Ohh slight possibility that it's been virtualized into C:\Users\{User}\AppData\Local\VirtualStore ? – Manifestation 20/12, 2013 at 21:7

Ahh, it turns out I had Meteor installed which came packaged with it's own node.exe. Thanks for your help! – Furthest 20/12, 2013 at 21:11

I also had an %AppData%\npm-cache directory which was ~100 MB. – Singlehearted 6/5, 2014 at 20:1

Check if you have the x86 x64 installed, make sure you install-reinstall same as previous – Bossism 24/8, 2015 at 1:10

I had to use git bash: rm -r /c/Users/<me>/AppData/Roaming/npm because of a too long file path – Haphazard 8/2, 2016 at 17:35

I would also suggest to remove the folder `c:\Users\{username}\node_modules` – Lockage 10/5, 2016 at 15:23

Make sure you also remove your %USERPROFILE%\.npmrc file! (usually C:\Users\my_username\.npmrc) If this has the wrong prefix=, literally nothing will work and it will leave you stumped seeing your fresh install just loop infinitely. See https://mcmap.net/q/35729/-npm-hangs-on-any-command. @brandonscript, maybe add this to your answer as it is still a very popular google search result. – Peisch 15/8, 2016 at 12:16

What about C:\Users\{User}\.node-gyp directory? – Wellintentioned 12/12, 2016 at 8:45

That worked for me, but I also had to remove this entry from regedit: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib_V2Providers\{1e2e15d7-3760-470e-8699-b9db5248edd5} As posted here: github.com/nodejs/node/issues/4329 – Glennglenna 4/10, 2017 at 12:59

I was able to uninstall from "Add and Remove Programs" / Node.js program. It went fine. And then reinstalled a lower version as I needed a lower version of nodejs – Sigmund 11/1, 2018 at 19:53

Good idea to check this SO question about deleting large amounts of files. Also check for .jspm installed by node at C:\Users\{User}\AppData\Local. SO: #187237 – Nucleoplasm 19/1, 2018 at 14:50

Lately, if you follow the shortcut left in Program Files you actually get to an nvm folder buried in C:\ProgramData. Not sure if deleting the folders would take these out, but thought it was worth a mention to possibly add to the list. – Godoy 22/11, 2018 at 15:5

If you use chocolatey for package management, you will need to also get rid of C:\choco\lib\nodejs* folders – Castoff 27/2, 2019 at 15:34

I'm not sure if this is the same point as @Wowdude's but I forgot I was using nvm for windows to manage versions, and thought I just had a missing uninstaller. Sent me on a wild goose chase before I noticed. – Purkey 3/8, 2019 at 2:52

Also, if you've installed a process manager such as PM2, you'll have to delete any pm2 related files and folders from all of those same folders, plus clean out the following system environment variables: PM2_HOME, PM2_SERVICE_PM2_DIR, SET_PM2_HOME, SET_PM2_SERVICE_PM2_DIR. – November 9/10, 2019 at 15:19

Very useful answer. Add this locations: C:\Users\{User}\.config C:\Users\{User}\.node_repl_history – Errolerroll 7/2, 2020 at 10:16

Maybe one more place: C:\Users\{User}\.config\configstore\update-notifier-npm.json. In Win 10. – Vein 17/3, 2020 at 13:53

I couldn't remove the installation from "Programs & Features" in control panel due to some bad permissions setup on my machine so ended up uninstalling Node.js v12 from powershell: wmic product where "description='Node.js' " uninstall – Radius 26/6, 2020 at 22:7

Followed exactly the same steps and finally node was uninstalled(I had only one version of node installed). Later installed a newer version of node and added the paths then everything was finally working. Thanks @Manifestation – Console 14/7, 2020 at 13:53

Might be a good idea to just search for 'npm' on the whole hard disk and delete leftover folders just in case. – Flori 11/8, 2020 at 3:51

got "No Instance(s) Available." after running wmic ... suggestion. It looks like the uninstallers don't work, nor npm (which apparently does not exist), so off to manual deletion! I hate node.js with a passion - gobbles up resources – Evaluate 27/10, 2020 at 17:10

You know an answer is good when Microsoft links to it in their documentation... – Sawbuck 19/1, 2021 at 20:38

What about the NodeJS installed by visual studio, that isn't configured to be in your path in the visual studio developer prompt. Should you uninstall it, or use that version instead? It is located in: c:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\NodeJs and in c:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\NodeJs\win-x64 – Marvelous 13/9, 2021 at 20:0

where node helped me. The node was from other program. – Lorenlorena 7/2, 2022 at 8:43

Found another C:\Users\{User}\AppData\Roaming\npm-cache on my system – Sisterly 21/3, 2022 at 11:6

It works for me to uninstall the old version from the system. – Kaleidoscopic 2/6, 2022 at 11:14

Scenario: Removing NodeJS when Windows has no Program Entry for your Node installation

I ran into a problem where my version of NodeJS (0.10.26) could NOT be uninstalled nor removed, because Programs & Features in Windows 7 (aka Add/Remove Programs) had no record of my having installed NodeJS... so there was no option to remove it short of manually deleting registry keys and files.

Command to verify your NodeJS version: node --version

I attempted to install the newest recommended version of NodeJS, but it failed at the end of the installation process and rolled back. Multiple versions of NodeJS also failed, and the installer likewise rolled them back as well. I could not upgrade NodeJS from the command line as I did not have SUDO installed.

SOLUTION: After spending several hours troubleshooting the problem, including upgrading NPM, I decided to reinstall the EXACT version of NodeJS on my system, over the top of the existing installation.

That solution worked, and it reinstalled NodeJS without any errors. Better yet, it also added an official entry in Add/Remove Programs dialogue.

Now that Windows was aware of the forgotten NodeJS installation, I was able to uninstall my existing version of NodeJS completely. I then successfully installed the newest recommended release of NodeJS for the Windows platform (version 4.4.5 as of this writing) without a roll-back initiating.

It took me a while to reach sucess, so I am posting this in case it helps anyone else with a similar issue.

Diablerie answered 2/6, 2016 at 19:41 Comment(5)

In case someone wants to go with this answer, here's all Node versions available for download: nodejs.org/en/download/releases – Vegetative 17/12, 2016 at 2:22

Worked form, I had to update from 0.12.0 -> 0.12.18 and then 0.12.18 -> 6.5 – Mishandle 2/2, 2017 at 0:46

I am having node version 0.12.2 installed with VS 2015/2017 installation. I need to upgrade it to latest version, so I went forward with your solution. After installing that version via installer, I was able to remove Node.js from Control Panel. But when I checked node current version, it is still showing me the same version installed. Any ideas? Thanks. – Antimacassar 16/5, 2017 at 6:45

This solution has worked for me twice, on different machines. Its behavior suggests that the new NodeJS version you installed was not truly removed. You want a fresh command prompt or console window. Make sure that you have closed any command prompts or console windows you were using before uninstalling Node. Open a fresh command prompt and verify the version. Finally, I do not believe that NodeJS writes any Win Registry keys, although you could have a second installation of Node that is still referenced by the Windows Path, such as from an IDE or other developer application. – Diablerie 26/5, 2017 at 20:0

You could also have a memory/file lock. If you haven't resolved your issue yet, simply perform a fresh boot of Windows without launching any unnecessary applications. Then try uninstalling NodeJS again. – Diablerie 26/5, 2017 at 20:6

Whatever Node.js version you have installed, run its installer again. It asks you to remove Node.js like this:

Bomarc answered 22/3, 2019 at 13:6 Comment(4)

I tried this. I had a node 9.x and a node 12.x. both managed by nvm. It uninstalled the 9.x but it left the 12.x orphaned. Rerunning the installer didn't recognize that I had a version of node on machine still. The solution was to run the installer again to reinstall it then uninstall it. There is no more node but "nvm list" still shows those 2 versions. – Merrymerryandrew 7/4, 2020 at 2:43

@Mark Irvin that is because this works for a specific version, and if you used an installer – Berri 28/5, 2020 at 3:53

this is the correct answer – Accelerando 5/1, 2022 at 18:31

not relevant in 2023 – Ballistic 16/1, 2023 at 21:3

I actually had a failure in the Microsoft uninstall. I had installed node-v8.2.1-x64 and needed to run version node-v6.11.1-x64.

The uninstalled was failing with the error:

Windows cannot access the specified device, path, or file

or similar.

I ended up going to the Downloads folder right-clicking the node-v8.2.1-x64 MSI and selecting uninstall.. this worked.

Pierpont answered 1/8, 2017 at 0:31 Comment(1)

Thank you! I no longer had the older version, however fetching the same version of the installer it's complaining about that's missing, and then following the same steps you suggested worked perfectly. – Gentle 10/3, 2021 at 1:8

In my case, the above alone didn't work. I had installed and uninstalled several versions of nodejs to fix this error: npm in windows Error: EISDIR, read at Error (native) that I kept getting on any npm command I tried to run, including getting the npm version with: npm -v.

So the npm directory was deleted in the nodejs folder and the latest npm version was copied over from the npm dist: and then everything started working.

Ictus answered 21/9, 2015 at 21:29 Comment(1)

Wow, quite a chore to remove Node from Windows, isn't it? I don't think this is a common state, but it has obviously happened to a number of us... ;-) I'd expect that installation and removal is more streamlined and successful using Mac OS and Linux, since their underlying architecture is native for npm and node. – Diablerie 28/2, 2017 at 17:20

How to completely remove node.js from Windows

I also ran into this issue on Windows 10.

Solution

I uninstalled NVM for Windows 1.1.7. During the uninstallation, it said it would uninstall all versions of Node.js and npm. Both are now gone :-)

Loosing answered 3/8, 2022 at 22:55 Comment(0)

I came here because the Remove button was not available from Add/Remove programs. It was saying "Node.js cannot be removed".

This worked:

Got the .msi of my installed Node version. Ran it to repair the installation just in case.
Opened the Administrator command prompt and ran msiexec /uninstall <node.msi>.

Fluffy answered 20/4, 2020 at 19:46 Comment(0)

I had the same problem with yesterday and my solution is to

Uninstall from the control panel, not from your cli
Download and install the latest or desired version of node from its website.

If by mistake you tried uninstalling through cli (it will not remove completely most often), then you do not get the uninstall option in the control panel. In this case, install the same version of node and then follow step 1.

Hope it helps someone.

Pincushion answered 12/7, 2018 at 7:38 Comment(0)

-1

The best thing to do is to remove Node.js from the control panel. Once deleted download the desired version of Node.js and install it and it works.

Unrelenting answered 5/10, 2018 at 10:45 Comment(1)

as mentioned in the question, older nodejs uninstalled by the user and installed latest, and then he faced an issue, that is the reason he posted this question, you might not have faced the same issue, so this is not an answer to the question. – Abigailabigale 5/10, 2018 at 11:22

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

How to remove Node.js from Windows:

Solution

Recommended topics

Hot tags