A portable toolkit lives on the USB stick but executes inside the running copy of Windows on the machine you're servicing. Nothing is installed — you plug the drive into a Windows 10/11 machine, launch the toolkit from the USB root, approve the UAC admin prompt, and work. Because the operating system is up, the toolkit sees everything a live system exposes: event logs, running processes, startup items, Windows Update state, network configuration, user profiles, installed software.
Use a portable toolkit when the machine still boots and the complaint is anything short of "it won't start": slowness, malware suspicion, crashes and freezes, network problems, deleted files, failing-drive triage, or a pre-repair health audit. This is the majority of bench and house-call work — most broken PCs still boot.
A bootable toolkit doesn't need the installed Windows at all. The machine boots from the USB into a self-contained environment — almost always WinPE (Windows Preinstallation Environment), a minimal Windows that runs from the stick with repair tools preloaded. From there you can rebuild bootloaders with bootrec and bcdboot, partition with diskpart, repair file systems with chkdsk, run SFC/DISM against the offline installation, unlock BitLocker with manage-bde, and image a failing drive before touching anything.
Use a bootable toolkit when Windows won't start: blue-screen stop codes like INACCESSIBLE_BOOT_DEVICE or 0xc000000e, boot loops, BitLocker recovery loops, corrupted system files that block login, or any time you want to image a drive without the installed OS writing to it. Classic suites like Hiren's BootCD PE, MediCat, and Sergei Strelec's WinPE are bootable-only tools in this category — see the full toolkit comparison.
| Portable (runs inside Windows) | Bootable (boots the machine) | |
|---|---|---|
| Requires | Windows still boots; admin rights (UAC) | Working firmware & USB boot; Windows can be dead |
| Environment | The machine's own live Windows | Self-contained WinPE from the stick |
| Sees | Live state: event logs, processes, updates, network | Offline state: disks, partitions, boot config, files |
| Typical jobs | Diagnostics, malware sweep, file recovery, tune-up | Boot repair, offline SFC/DISM, imaging, BitLocker unlock |
| Limits | Useless if the OS won't start | Blind to live-system behavior (running processes, live logs) |
GRAM (Guardian Repair & Analysis Module) is a portable toolkit: copy it to a USB drive, plug it into the Windows 10/11 machine being serviced, double-click Start GRAM, and approve the admin prompt — the dashboard opens in the browser with system diagnostics, security sweep, network diagnostics, file recovery, and drive imaging ready, plus a built-in AI repair agent that reads the live machine's diagnostics and walks the fix. The program runtime is bundled on the USB, so nothing is installed on the customer's machine. GRAM does not boot the machine itself — for a PC that won't reach the desktop, use Windows Recovery (on the PC itself; see the boot error index) or a bootable WinPE suite to get it starting, then run GRAM to root-cause the failure and finish the job on the live system.
When Windows won't start: stop codes at boot, boot loops, BitLocker recovery prompts, corrupted system files that block login, or a drive you want to image before the installed OS can write to it. If the machine reaches the desktop, a portable toolkit is usually faster because it can read the live system. See the boot error index for the won't-boot cases.
They're close relatives. WinRE is the recovery environment installed on the machine's own disk (reached by forcing three failed boots); WinPE is the same kind of minimal Windows but running from external media like a USB stick. WinPE works even when the on-disk recovery partition is damaged or missing — which is exactly when you need it most.
Yes, by combining tools. A Ventoy multiboot stick still works as normal USB storage, so a common bench setup is one drive carrying bootable ISOs (MediCat, Sergei Strelec's WinPE, Hiren's PE) for machines that won't start, with the GRAM folder copied onto the same drive for portable, inside-Windows work on machines that do. GRAM itself is portable-only — it doesn't boot the machine.
No. A portable toolkit runs from the USB drive and doesn't install software — GRAM, for example, is extracted to the USB root and launched from there, needing only an admin (UAC) approval to run diagnostics and repairs. When the stick is ejected, the toolkit goes with it.