How to Uninstall Python, Node and Java on Windows

Development tools are unusual among Windows programs in that they deliberately leave things behind, and that is the right default: your installed packages and configuration are your work, not the vendor's files. It only becomes a problem when you are uninstalling precisely because something is broken, and the reinstall cheerfully picks up all the same broken state you were trying to escape.

This guide covers the ordinary uninstall and then the leftovers, per tool.

The uninstall itself

Python

Python is the one most likely to leave a machine in a genuinely confusing state, because it is so easy to end up with three versions installed from three different sources without ever having decided to.

1. Uninstall every Python entry in Installed apps, oldest first. Also remove Python Launcher, which is a separate entry and is what actually resolves the py command.
2. Check for a Microsoft Store version. Typing python on a machine without Python opens the Store, and some people install it from there. It appears in Installed apps as *Python 3.x* published by the Python Software Foundation.
3. Delete the leftover folders: %LOCALAPPDATA%\Programs\Python, %APPDATA%\Python and %LOCALAPPDATA%\pip\Cache.
4. Clean PATH. Remove entries pointing at Python directories that no longer exist; see the PATH section below.
5. Remove the Store aliases. Settings → Apps → Advanced app settings → App execution aliases, and turn off the python.exe and python3.exe entries. Left on, they intercept the command and reopen the Store, which looks exactly like a broken install.

Node.js and npm

Node's uninstaller takes the runtime and leaves behind every globally installed package plus the entire npm cache, which on a working development machine is usually the largest leftover of the lot.

1. Uninstall Node.js from Installed apps.
2. Delete `%APPDATA%\npm` — globally installed packages and their shims.
3. Delete `%APPDATA%\npm-cache` or %LOCALAPPDATA%\npm-cache depending on version. This is frequently several gigabytes.
4. Delete `C:\Program Files\nodejs` if it survived the uninstall.
5. Remove `%USERPROFILE%\.npmrc` if you want a genuinely clean slate — note that it may hold registry credentials you need.
6. Clean PATH of any nodejs or npm entries.

If you juggle Node versions, consider not installing Node directly at all. A version manager such as nvm-windows keeps each version in its own folder and switches the PATH for you, which removes this entire category of problem.

Java

Java machines accumulate versions the way drawers accumulate cables. Check Installed apps for every entry beginning *Java*, *Java SE*, *JDK*, *OpenJDK*, *Temurin*, *Zulu* or *Corretto*: different vendors, all providing the same thing, and very often all present at once without anyone remembering installing them.

1. Uninstall each Java entry. Oracle also publishes a Java Uninstall Tool that removes older versions its installer left behind.
2. Delete leftover folders under C:\Program Files\Java and C:\Program Files (x86)\Java.
3. Remove the Maven repository at %USERPROFILE%\.m2 if you no longer need the cached dependencies. It is commonly a gigabyte or two.
4. Remove the Gradle cache at %USERPROFILE%\.gradle, which is often larger still.
5. Clear `JAVA_HOME` and remove Java entries from PATH. A JAVA_HOME pointing at a deleted folder breaks build tools with a message that does not obviously say so.

Eclipse

Eclipse usually has no uninstaller at all, because it ships as a folder you extract and run. Getting rid of it means deleting that folder, plus three things it quietly created elsewhere that nothing will clean up for you.

• The installation folder, wherever you extracted it. If you used the Eclipse Installer, look in %USERPROFILE%\eclipse.
• Your workspace, by default %USERPROFILE%\eclipse-workspace. This contains your projects — check before deleting.
• `%USERPROFILE%\.p2`, the plugin bundle pool, which the Eclipse Installer shares between installations and can be large.
• `%USERPROFILE%\.eclipse`, holding settings and licence acceptance state.

Cleaning up PATH

This is the step that actually matters, and the one everybody skips. A PATH entry pointing at a folder that no longer exists is harmless in itself. Two live entries for different versions of the same tool is not: the wrong version runs, and nothing you do to the one you can see makes the slightest difference. If a tool keeps reporting a version you thought you removed, this is why.

If the reason for all this is disk space rather than a broken install, it is worth running through the guide on deleting temporary files and Windows.old as well — between the two you will usually find considerably more than you expected. If C: is still short afterwards, extending the partition is the next step. To check what is actually installed and running, the terminal guide covers the where and Get-Command lookups used above.