How to Remove Old FRC Programs Before Reinstalling New Ones

If you're working with FIRST Robotics Competition (FRC) software, you've likely hit a point where something isn't working right — a broken WPILib installation, an outdated version of the Driver Station, or a corrupted roboRIO imaging tool. The standard fix is a clean reinstall. But doing that correctly means fully removing the old programs first, not just installing over them.

Here's how that process works, what's actually involved, and why it matters.

Why a Clean Removal Matters for FRC Software

FRC development tools aren't like typical consumer apps. They install multiple interdependent components — the WPILib libraries, VS Code extensions, Java or C++ toolchains, NI (National Instruments) Game Tools, the FRC Driver Station, imaging utilities, and more. These components share dependencies, write to specific directories, and register with your operating system.

Installing a new version on top of an old one often causes:

• Version conflicts between library files
• Extension duplication inside VS Code
• Corrupted environment variables pointing to old toolchain paths
• Lingering NI licensing files that confuse the new installation

A clean removal eliminates these conflicts before they start. 🔧

What FRC Software Is Actually Installed on Your Machine

Before you remove anything, it helps to know what you're dealing with. A typical FRC development setup includes:

These come from two separate installation pipelines: WPILib's own installer and NI's package ecosystem. You'll need to address both.

Removing WPILib (VS Code + Libraries + Tools)

WPILib installs everything into a specific folder — typically C:UsersPublicwpilib<year> on Windows. The VS Code instance it installs is separate from any other VS Code you may have on your machine, so removing it won't affect your regular development environment.

Steps to remove WPILib:

1. Open Windows Settings → Apps (or "Add or Remove Programs" on older Windows)
2. Search for WPILib or look for the year-specific entry (e.g., "WPILib 2024")
3. Select it and choose Uninstall
4. After the uninstaller runs, manually navigate to C:UsersPublicwpilib and delete the year-specific folder (e.g., 2023 or 2024) — the uninstaller doesn't always catch everything here
5. Optionally, check your user environment variables for any WPILib-related paths and remove them

On macOS or Linux, WPILib installs to ~/wpilib/<year>/. Deleting that folder and clearing related shell profile entries (.bashrc, .zshrc) handles most of the cleanup.

Removing NI FRC Game Tools (Driver Station, Imaging Tool)

The National Instruments components use their own NI Package Manager, which tracks all NI software on your machine.

Steps to remove FRC Game Tools:

1. Open NI Package Manager (search for it in your Start menu)
2. Navigate to the Installed tab
3. Look for FRC Game Tools and any associated packages (roboRIO Imaging Tool, FRC Driver Station)
4. Select them and choose Remove or Uninstall
5. Let NI Package Manager handle the dependency resolution — it will flag if other NI software depends on shared components

If NI Package Manager itself is corrupted or won't open, you can uninstall it through Add or Remove Programs, which will cascade to remove the NI components it manages.

Cleaning Up Residual Files and Settings

Even after a clean uninstall, some artifacts tend to linger:

• VS Code workspace settings stored in your project folders — these won't cause problems but may reference old paths
• Gradle cache in ~/.gradle/ — sometimes holds old WPILib dependencies
• Deploy artifacts on the roboRIO itself — not a PC issue, but worth noting if code behavior seems inconsistent after reinstall
• Windows Registry entries — rarely a problem, but NI software sometimes leaves orphaned keys

For most users, deleting the WPILib year folder and running the NI Package Manager uninstall is sufficient. A full registry sweep is typically unnecessary unless you're troubleshooting persistent installation failures.

Variables That Affect How This Process Goes for You

The steps above are straightforward in a clean environment. In practice, several factors shape how complicated the removal process gets:

• Number of FRC seasons installed — if you have 2022, 2023, and 2024 WPILib folders, each is independent and can be removed selectively or all at once
• Whether LabVIEW is installed — sharing the NI ecosystem with LabVIEW adds complexity to removing Game Tools
• Windows vs. macOS vs. Linux — the NI tools are Windows-only; macOS/Linux users only need to remove WPILib
• Corrupted vs. functional installation — a broken install sometimes can't self-uninstall cleanly, requiring manual folder deletion
• Team-shared machines — multiple user accounts may have project folders or cached files scattered across different user directories

The right level of cleanup — minimal, standard, or deep — depends on what you're trying to solve and what else lives on that machine. 🛠️