guide · static export
Productivity

Run a Portable Toolkit From a USB Stick

Diagnostics, an archiver and a browser on one stick, working on any Windows machine without installing anything. The trick is relative paths and local settings.

by@guidox updated:10/31/26 time:30 min level:Beginner tested on:Windows 11 24H2 works on:Windows 10, Windows 11 tools:USB stick, Portable tools
TL;DR

Use **exFAT** for large files, keep every tool in its own folder, redirect **APPDATA and LOCALAPPDATA** in a launcher script and always call tools through **%~dp0** so a different drive letter changes nothing.

Before you start

Requirements

  • A USB stick of 32 GB or more
  • Portable builds of your tools
  • Twenty minutes
Step by step

Instructions

01

Format the stick for the job

exFAT handles files over 4 GB and works on every Windows version; NTFS adds permissions and is slower to mount on some machines. A stick that must also work on a Mac or a TV is exFAT by default.

Format-Volume -DriveLetter E -FileSystem exFAT -NewFileSystemLabel Toolkit
02

Lay out one folder per tool

A flat pile of executables becomes unusable after ten tools. One folder each, with its config next to it, means a tool can be removed by deleting one directory.

E:\ools\zip\nE:\ools\WiNFO\nE:\ools\irefoxPortable
03

Find out where each tool writes its settings

Portable builds differ: some keep an ini next to the executable, some honour a flag, and some write to the user profile regardless. Start each tool, change one setting and look for the file.

⚠ warningA tool that silently writes to APPDATA leaves data on the host machine. That is exactly what a rescue stick is supposed to avoid.
04

Redirect the profile folders in a launcher

A small batch file can point APPDATA and LOCALAPPDATA at folders on the stick for the duration of the tool. The host profile is untouched and the settings travel with you.

set APPDATA=%~dp0profile\oaming
set LOCALAPPDATA=%~dp0profile\ocal
start "" Tools\irefoxPortable\irefoxPortable.exe
tip%~dp0 expands to the folder of the batch file with a trailing backslash, which is why it survives a drive letter change.
05

Test it on a machine that is not yours

Plug the stick into a second PC and launch everything once. Missing runtimes, a blocked executable and a path that only works on your drive all show up in the first minute there.

06

Keep a copy and a checksum

A stick in a bag gets lost. Keep a zipped copy on a drive at home, and note the tool versions so you can tell whether the stick is stale when a diagnosis fails.

Troubleshooting

Common issues

The tool saves settings on the host anyway

It ignores the redirected variables. Look for its own config option or use a build that keeps an ini next to the exe.

A tool will not start from the stick

Blocked by policy, or missing a runtime. Test the same exe from a local folder to separate the two.

Everything is slow

A USB 2.0 stick on a 3.0 port, or small random reads. Diagnostics tools are fine; a browser profile is not.

Windows warns about the drive

The stick was pulled without ejecting. Run a repair once, and eject properly from then on.

FAQ

Frequently asked

Is a portable browser safe on a foreign PC?

It runs with that user's rights. For anything sensitive, boot your own system instead.

How big should the stick be?

32 GB is plenty for tools. Add a rescue image and 64 GB is the practical size.

How to undo this

Nothing is installed, so there is nothing to uninstall. Delete the folder on the stick or format it, and remove the profile directory the launcher created if you want a clean start.

Changelog · 1 entry
  1. 2026-10-31
    First version
Interactive version: checklist, feedback, related guides →

Free · no account needed · tracks your progress