Old FRC software can feel like a box of tangled robot wires. One cable says “2023.” Another says “beta tool.” A third one may be hiding under a pile of driver station logs. The good news is simple. You can clean it up. You can reinstall fresh tools. And you do not need to be a wizard with a soldering iron.
TLDR: Back up your robot code first. Then uninstall old FRC tools, remove leftover folders, and restart the computer. After that, install the newest WPILib and NI FRC Game Tools from official sources. Open a test project to make sure everything works before competition day.
Why a Clean Reinstallation Helps
FRC software changes every season. That is part of the fun. It is also part of the chaos.
One year you have one version of WPILib. The next year you have a new one. Your team may also install vendor tools from REV, CTRE, PathPlanner, AdvantageScope, and more. Over time, the laptop becomes a little robot museum.
A clean reinstall helps when:
- The robot code will not build.
- VS Code acts strange.
- The Driver Station will not open correctly.
- Old libraries are causing errors.
- New students are using an old team laptop.
- You want a fresh start before build season.
Think of it like wiping grease off a gearbox. The parts may still work. But fresh and clean is better.
Before You Delete Anything
Stop. Take a breath. Do not start smashing the delete key like it is the last match of finals.
First, back up the important stuff. This is the most important step. Old programs can be reinstalled. Lost robot code can cause sadness, panic, and a mentor making “the face.”
Back up these items:
- Robot code projects, usually in your Documents folder, Desktop, or a team folder.
- Command examples and test projects your team still uses.
- Vendor dependency files, if they are stored inside projects.
- PathPlanner paths, if your team uses them.
- Driver Station logs, if you want old match data.
- Custom dashboards, layouts, scripts, or notes.
- Team documentation, such as wiring notes and setup checklists.
Copy these files to a safe place. Use a USB drive. Use cloud storage. Use a team Git repository. Use all three if you want to feel powerful.
Rule of thumb: If you are not sure what a folder is, do not delete it yet. Ask a programming lead or mentor.
Know What You Are Removing
FRC software is not just one thing. It is a small herd of helpful tools. Some are needed every season. Some are old. Some are optional.
Common FRC programs include:
- WPILib, which includes the FRC tools, libraries, and often a bundled VS Code.
- NI FRC Game Tools, which includes the FRC Driver Station and roboRIO Imaging Tool.
- FRC Driver Station, used to control and monitor the robot.
- roboRIO Imaging Tool, used to image the roboRIO.
- Vendor tools, such as REV Hardware Client or CTRE Phoenix tools.
- Extra utilities, like AdvantageScope, PathPlanner, or custom team tools.
You may not need to remove every single tool. But if the computer is messy, old, or broken, a full clean reinstall is often easier than chasing ghosts.
Step 1: Close Everything
Close VS Code. Close Driver Station. Close browsers. Close vendor tools. Close anything that might be using FRC files.
If the robot is connected to the laptop, disconnect it. You are cleaning the laptop, not trying to surprise the robot.
Also make sure you have administrator access. Many FRC tools need admin permission to install or uninstall. If you are on a school laptop, you may need help from IT.
Step 2: Uninstall Old Programs
On Windows, open Settings. Then go to Apps. Search for old FRC tools.
Look for items like:
- WPILib from old years.
- NI FRC Game Tools from old seasons.
- Old versions of REV tools.
- Old versions of CTRE tools.
- Old extra FRC utilities your team no longer uses.
Click each old item. Choose Uninstall. Follow the prompts. If Windows asks for permission, say yes if you trust the program and know it is the correct item.
Some uninstallers may take a while. That is normal. Do not panic if the progress bar moves slower than a robot with one dead battery.
If a program asks you to restart, you can usually wait until you have removed the rest. But if something fails, restart and try again.
Step 3: Remove Old WPILib Folders
WPILib often lives in a public folder. On many Windows machines, you may find it here:
C:\Users\Public\wpilib
Inside that folder, you may see folders named by year. For example, you might see 2022, 2023, 2024, or 2025.
If you are doing a clean reinstall, remove the old year folders that you no longer need. Be careful. Do not delete active robot code if your team stored it there. Most teams should keep robot projects somewhere else, but every team is different.
You may also remove old desktop shortcuts. These can point to old tools and confuse new students.
That is how a student opens the 2023 version during a 2025 meeting and says, “Why is Java angry?” Nobody wants that.
Step 4: Clean Up Optional Leftovers
Some files stay behind after uninstalling. This is normal. Uninstallers are not perfect. They are more like polite raccoons. They clean most things, but leave a snack wrapper.
You can check these places:
- C:\Users\Public\wpilib
- Documents, for old example projects.
- Downloads, for old installers.
- Desktop, for old shortcuts.
- AppData, only if you know what you are doing.
Be careful with AppData. It contains settings for many programs. Deleting random things there can cause strange problems. If you are not sure, leave it alone.
You may also clear old Gradle caches, but this is optional. Gradle is the build system used by FRC projects. It can store lots of files. If builds are acting weird, clearing caches may help. But it can also make the next build take longer because files must download again.
A safer choice is this: remove only the old FRC folders you understand. Then restart.
Step 5: Restart the Computer
Yes, really. Restart it.
A restart clears stuck processes. It finishes uninstall steps. It gives Windows a chance to stop holding onto old files like a dragon guarding treasure.
After the restart, check that old shortcuts are gone. Check that old tools do not appear in the Start menu. If something is still there, uninstall it again or remove the leftover shortcut.
Step 6: Download Fresh FRC Software
Now it is time for the fun part. Fresh tools. Fresh start. Fresh hope.
Always download FRC software from official sources. Use the official WPILib documentation for the current season. Use the official NI FRC Game Tools download page for the current season. Use official vendor sites for REV, CTRE, and other hardware tools.
Do not use random downloads from old team chats unless you know exactly what they are. An installer named final final real this one works.exe is not a great plan.
You will usually need:
- Current WPILib installer.
- Current NI FRC Game Tools.
- Vendor tools for your motor controllers and sensors.
- Vendor libraries for robot projects.
If your team codes in Java or C++, WPILib will guide you through the setup. It often includes the tools needed for FRC development, including a configured VS Code environment.
Step 7: Install WPILib
Run the WPILib installer for the correct season. Choose the options your team needs. Most teams should install the standard tools.
If the installer asks where to install, use the default location unless your team has a reason to change it. Defaults are boring. Boring is good during setup.
Let the installer finish. Do not close it early. Do not start five other installers at the same time. Your laptop is not a robot pit crew.
When WPILib is installed, open the new FRC VS Code shortcut. Make sure it opens. Check the WPILib menu or command palette. You should see FRC commands, such as creating a new project or building robot code.
Step 8: Install NI FRC Game Tools
Next, install the current NI FRC Game Tools. This package includes the Driver Station. It also includes tools used to work with the roboRIO.
Follow the installer prompts. Use the current season version. When it finishes, restart if asked.
After installing, open the FRC Driver Station. It should launch without errors. You do not need to connect to the robot yet. Just make sure the program opens.
Step 9: Install Vendor Tools
Now install tools for your hardware. This may include REV or CTRE software. It may also include tools for cameras, logs, path planning, or dashboards.
Only install what your team uses. More tools are not always better. Too many tools can make the laptop messy again.
After vendor tools are installed, update your robot project vendor dependencies if needed. In WPILib VS Code, teams often use the vendor dependency manager. This keeps libraries matched to the season.
If your project uses old vendor libraries, it may not build. That does not mean the laptop is cursed. It may just mean the project needs updates.
Step 10: Test With a Simple Project
Do not wait until competition morning to test the install. That is how gray hairs are born.
Create a simple new robot project. Build it. If it builds, that is a great sign.
Then open your team’s real robot project. Build that too. If it fails, read the error. Many errors are simple. They may point to old vendor dependencies, old code, or a missing library.
Test these items:
- Can VS Code open?
- Can you create a new WPILib project?
- Can you build a project?
- Can Driver Station open?
- Can vendor tools open?
- Can your real robot code build?
If all of those work, celebrate. Maybe not with confetti near the robot. But you may do a small victory dance.
Common Problems and Easy Fixes
Problem: VS Code opens, but WPILib commands are missing.
Fix: You may be opening the wrong VS Code shortcut. Use the FRC version installed with WPILib, or check that the WPILib extension is installed.
Problem: The robot project will not build.
Fix: Check the season version. Check vendor dependencies. Old projects may need to be imported or updated.
Problem: Driver Station does not launch.
Fix: Reinstall NI FRC Game Tools. Restart. Make sure Windows permissions did not block the install.
Problem: A vendor tool cannot find hardware.
Fix: Check USB cables, robot power, firmware, and drivers. Also make sure you installed the current version.
Keep It Clean Next Season
Once the laptop is clean, keep it that way. Make a team setup checklist. Write down the software versions. Save official installer links in team documentation. Keep robot code in Git. Teach new students where projects belong.
At the end of each season, archive the old code. Label it clearly. For example, use a folder name like 2025 Robot Code Archive. Clear names beat mystery folders every time.
A clean FRC laptop is a happy FRC laptop. It builds faster. It confuses students less. It helps mentors sleep. Most important, it lets your team focus on the robot instead of fighting old software goblins.
So back up your code. Remove the old tools. Install the fresh ones. Test early. Then go build something awesome.