Site icon WebFactory Ltd

How to Remove Old FRC Programs Before Installing the Latest Version

Ethan Martinez

Before a robotics team installs the newest FRC software, it is wise to remove older tools, outdated libraries, and duplicate components that may interfere with the season’s official release. FRC programming environments change from year to year, and leaving old versions installed can lead to confusing build errors, mismatched roboRIO images, incorrect Driver Station behavior, or vendor library conflicts.

TLDR: A team should back up code, uninstall old FRC software through the operating system, remove leftover folders only after verifying they are no longer needed, and then restart the computer before installing the latest tools. The most important items to check are WPILib, NI FRC Game Tools, Driver Station, roboRIO Imaging Tool, old VS Code extensions, and outdated vendor libraries. Careful cleanup helps prevent version conflicts and saves troubleshooting time during build season.

Why Old FRC Software Should Be Removed

FRC software is not always designed to coexist perfectly across multiple seasons. While some tools install side by side, others replace shared components or depend on specific yearly updates. A computer that has been used for several seasons may contain multiple versions of WPILib, old vendor tools, outdated National Instruments components, previous roboRIO images, and older Driver Station software.

When these older tools remain in place, a team may encounter errors that appear unrelated at first. Code may build successfully on one laptop but fail on another. The Driver Station may not communicate properly with the robot. A project may use an old vendor dependency without the programmer realizing it. These problems can consume valuable meeting time, especially when deadlines are close.

Removing old programs before installing the latest FRC release creates a cleaner environment. It also makes it easier for mentors and students to confirm that every programming laptop matches the current season’s requirements.

Step 1: Back Up Important Robot Code

Before anything is uninstalled, the team should protect existing work. Old projects may contain useful drivetrain code, autonomous routines, controller mappings, constants, and documentation. Even when a team plans to start fresh, previous code can serve as a reference.

A proper backup should include:

The best backup method is a version control system such as Git, stored in a remote repository. If the team does not use Git, the files should be copied to a shared drive, external USB drive, or cloud storage location. The backup should be tested by opening at least one copied project and confirming that the files are present.

Step 2: Identify Installed FRC Programs

The next step is to identify which FRC related programs are installed. On Windows, most items can be found under Settings > Apps > Installed Apps or Control Panel > Programs and Features. The exact list varies depending on the team’s programming language and tools, but common items include:

Not every item must always be removed. However, when preparing for a new season, many teams prefer a clean install of the official current tools. The team should compare installed versions with the current season’s official documentation before deciding what to keep.

Step 3: Uninstall Old WPILib Versions

WPILib is central to most Java and C++ FRC projects. It includes the libraries, templates, Gradle tools, command line utilities, documentation, simulation support, and a bundled version of Visual Studio Code. Because WPILib is updated annually, old versions can cause confusion if a student opens the wrong VS Code shortcut or uses an outdated project template.

To remove old WPILib versions, the team should use the normal uninstall process first. On Windows, the uninstaller may appear in the installed apps list, or the team may find it inside the WPILib installation directory. After uninstalling, a restart is recommended.

In many cases, WPILib folders remain after uninstalling. These folders may be located in places such as:

These leftover folders should not be deleted blindly. The team should check whether they contain project files, downloaded dependencies, or useful reference material. Once the team confirms that the folders are only old installed tools, they can be removed.

Step 4: Remove Old NI FRC Game Tools

The NI FRC Game Tools package includes important components such as the Driver Station and roboRIO Imaging Tool. Because these tools must match the current season’s control system requirements, old installations should usually be removed before installing the latest version.

Using Windows uninstall tools, the team should search for National Instruments or FRC related entries. There may be several NI components installed, including runtime engines and shared services. If the computer is used only for FRC, removing older FRC Game Tools is generally appropriate. If the computer is also used for other engineering software, a mentor or system administrator should review the list before removing shared NI components.

After uninstalling, the computer should be restarted. This helps clear background services and ensures the new installation can register drivers, utilities, and system components correctly.

Step 5: Clean Up Visual Studio Code and Extensions

Many FRC teams use the WPILib version of Visual Studio Code rather than a separate standard installation. This bundled editor helps ensure the correct extensions and tools are available. However, students may also install regular VS Code, old WPILib extensions, or unrelated extensions that affect behavior.

The team should check whether old shortcuts point to outdated WPILib folders. If there are multiple FRC VS Code icons, they should be labeled or removed so students do not accidentally launch the wrong one. Inside VS Code, the extensions panel should be checked for old WPILib extensions, Java extensions, C++ tools, or Gradle plugins that are no longer needed.

If the team decides to remove VS Code settings, it should proceed carefully. User settings may include helpful editor preferences, keybindings, and custom snippets. A safer approach is to remove only old FRC specific extensions and shortcuts unless a full cleanup is required.

Step 6: Review Vendor Libraries and Hardware Tools

Modern FRC robots often use motor controllers, sensors, pneumatic modules, power distribution devices, and other hardware that requires vendor libraries. Common vendors provide software tools, firmware clients, and JSON dependencies that integrate with WPILib projects.

Old vendor libraries can create subtle problems. For example, a project may compile against an outdated library but fail to work with updated hardware firmware. In other cases, a new WPILib project may accidentally import dependencies from a previous season.

The team should review:

Vendor tools should be updated according to official vendor instructions. The team should also update project dependency files using the current season’s recommended URLs or install methods.

Step 7: Remove Old Robot Images and Deployment Artifacts

Programmers sometimes overlook old roboRIO images, Gradle caches, and deployment artifacts. While these files may not always cause problems, they can make troubleshooting harder. A team may think it is deploying current code while old build outputs or cached dependencies are still being referenced.

Common cleanup targets include:

Deleting a project’s build folder is usually safe because it can be regenerated. However, deleting global caches may force tools to download dependencies again, so the computer should have internet access afterward.

Step 8: Restart Before Installing the Latest Version

Once old software has been removed, the computer should be restarted before installing the latest FRC tools. This step may seem simple, but it prevents many installation issues. A restart clears locked files, stops old services, refreshes system paths, and allows driver changes to complete.

After restarting, the team should install the newest official FRC software in the recommended order. Typically, this means installing the current WPILib release and the latest NI FRC Game Tools, followed by vendor utilities and libraries. The team should use official sources and verify that the downloaded files match the current season.

Step 9: Verify the New Installation

After installation, the team should confirm that everything works before connecting to the competition robot. A clean verification process can prevent field side surprises.

The team should check the following:

If a build fails, the team should read the error carefully before reinstalling everything. Many errors come from a project still referencing old dependencies. Updating the project’s Gradle files, vendordeps, or source imports may solve the issue.

Best Practices for Team Computers

A team with multiple programming laptops should standardize setup. Each laptop should use the same current tool versions, vendor libraries, and project settings. A shared checklist can help students configure machines consistently.

Good practices include:

Teams should avoid making major software changes immediately before a competition unless necessary. If updates are required, at least one mentor or experienced student should supervise the process and confirm that the robot still builds and deploys correctly.

Common Mistakes to Avoid

One common mistake is deleting folders before backing up projects. Another is leaving old shortcuts on the desktop, which may cause students to open outdated tools. Teams also sometimes update WPILib but forget to update vendor libraries, leading to build errors or runtime issues.

It is also risky to assume that one successful laptop means every laptop is ready. Differences in Java versions, cached dependencies, installed extensions, and system paths can cause inconsistent behavior. A written setup process reduces this risk.

FAQ

Should all old FRC software always be removed?
Not always, but removing old season tools is usually the cleanest approach. If a computer is used for multiple engineering programs, shared components should be reviewed before removal.
Will uninstalling WPILib delete robot projects?
Usually, uninstalling WPILib does not delete projects stored in separate folders. However, the team should always back up code before uninstalling anything.
Can old vendor libraries break a new robot project?
Yes. Outdated vendor dependencies can cause compile errors, missing classes, firmware mismatches, or unexpected robot behavior.
Is it safe to delete a project’s build folder?
In most cases, yes. Build folders are generated automatically and can be recreated when the project is built again.
Why is restarting the computer important?
A restart clears old services, releases locked files, and refreshes system settings. It helps the latest FRC installers run more reliably.
How can a team confirm the latest tools are installed correctly?
The team should open the current WPILib VS Code, build a new example project, launch the Driver Station, check the roboRIO Imaging Tool, and test vendor libraries.
Should software be updated during competition week?
Only when necessary. Updates close to an event should be tested carefully on the robot to avoid unexpected problems.
Exit mobile version