Overview
This tool does something the standard installer refuses to: it puts a complete, bootable, persistent Windows onto an external drive. Not a recovery environment and not a live session that forgets everything, but a real installation that keeps settings, installed software and files across reboots, and runs on whatever machine it is plugged into.
The uses are practical. A technician carries a known good working environment to a client site. A locked down office machine gets a personal system without touching its internal disk. An external drive holds a test installation for software that should not go near a production system. A failing machine keeps working from an external drive while a replacement is arranged. In each case the internal disk is untouched.
Sources can be an installation image, a physical disc, an existing installation on the machine, or a captured system image, and the destination can be a USB stick, an external solid state drive or a hard disk. The tool handles the partitioning, the boot configuration for both firmware types and the driver injection needed to make the installation portable across different hardware. It also builds ordinary installation media and can clone a running system onto another disk.
What it does well
Persistent portable Windows
A real installation on an external drive that keeps files, settings and software across reboots and across machines.
Multiple sources
Install from a disc image, a physical disc, the currently running system or a captured system image.
Firmware handling
Boot configuration written for both modern and legacy firmware so the drive starts on almost any machine.
Driver portability
Injects the drivers needed for the installation to boot on hardware it was not created on.
Installation media and cloning
Build ordinary setup media, and clone a running system onto another disk from the same tool.
Changes in this build
- Faster deployment onto external solid state drives through better block copy scheduling.
- Support added for the current release branches as a source image.
- Driver injection improved for recent storage and network controllers.
- Cloning gained a resize option so a system moves onto a smaller target.
- Fixed a boot configuration failure on drives with an unusual existing partition layout.
What is in the package
- WinToUSB installer, 32 and 64-bit
- Deployment and cloning modules
- Installation media builder
- Driver injection components
- Multilingual interface files, 14 languages
System requirements
| Processor | Any x86 or x64 processor |
| Memory | 2 GB minimum |
| Graphics | Not applicable |
| Storage | 100 MB for the tool, 32 GB or larger target drive |
| Display | 1024 x 768 minimum |
| System | Windows 7 through Windows 11, administrator rights required |
Installation
- Extract the archive and run the installer with administrator rights.
- Apply the included configuration step before first launch.
- Connect the target drive and back up anything on it, deployment erases it.
- Pick the source image and the target drive, checking the drive letter twice.
- Let the deployment finish completely, then boot the drive on a test machine.
Before you start
Use a solid state external drive if you can, a portable install on a USB stick is painfully slow.
Some machines need the boot order changed or fast startup disabled before they will boot external media.
Deployment erases the target drive entirely, confirm the destination before starting.
Questions about this title
Is this a live system or a real install?
A real installation. Files, settings and installed software persist across reboots.
Will it boot on different machines?
Usually, driver injection handles the hardware differences, though very unusual hardware can still refuse.
Can it clone my current system?
Yes, the running installation can be used as the source and deployed to another disk.
Which drive type should I use?
An external solid state drive. A standard USB stick works but performance is poor.
About this listing
This entry was checked on a clean install of Windows 7 / 8 / 10 / 11 before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.