Overview
A portable operating system on a drive you carry solves problems that nothing else solves cleanly. A technician who needs their own tools on someone else's hardware. A person who works on several machines and wants one environment. A recovery drive that is a full system rather than a stripped rescue shell. This program creates exactly that: a real installation on external media, with your programs, your settings and your files, that boots on essentially any machine.
The archive contains all editions, professional, enterprise and technician, with licensing already handled. That matters because the features split across tiers here, and the ones people actually need, cloning a running system and creating a portable install from an existing installation rather than only from an image, sit in the upper tiers.
Creating a portable system
The source can be an installation image, an installation disc, or an existing system on the machine. From an image it is a normal installation redirected to the external drive. From an existing system it clones what you already have, including your programs and settings, which is how a working environment becomes portable without rebuilding it from scratch.
Two deployment modes exist. Legacy mode installs the files directly onto the drive, which is the compatible option. Portable mode configures the installation to handle changing hardware between boots, generalising the driver state so the same drive works on a laptop and then on a desktop with completely different components. The second mode is what makes the result genuinely portable rather than tied to one machine.
Media, hardware and speed
The single most important decision is the drive. A cheap USB stick will technically work and the result will be so slow it is unusable, because random write performance on flash sticks is dreadful. A solid state drive in a USB enclosure, on a port with real throughput, produces something that feels like a normal machine. This is not a preference, it is the difference between a working tool and a wasted afternoon.
Both firmware boot paths are supported, and the drive can be prepared to boot on either, which is necessary if it will be used on machines of different ages. Encryption of the portable system is supported for the obvious reason that a drive containing a full working environment is exactly the sort of thing that gets left in a hotel.
Other functions in the same tool
Installation media creation writes a bootable installer to a stick from an image, with the option to keep the rest of the drive usable as ordinary storage rather than dedicating the whole thing. Multiple images can be placed on one stick with a boot menu, which is how one drive covers several operating system versions.
System cloning copies an installed system from an internal disk to another disk, including to a smaller one where the used space permits, with the boot configuration rebuilt so the target actually starts. That function overlaps with dedicated imaging tools but is convenient to have in the same place, particularly when the goal is moving an installation to a new machine.
What you get
- Install a full working Windows onto external media from an image, a disc or an existing system
- Portable mode that generalises drivers so the drive boots across different hardware
- Clone a running installation with programs and settings intact
- Support for both firmware boot paths on the same drive
- Encryption of the portable installation
- Bootable installation media creation with the rest of the drive left usable
- Multiple images on one stick with a boot menu
- System cloning to another internal disk including to a smaller target
- All editions included with the tier restricted features available
Inside the archive
- WinToUSB installer covering all editions
- Portable build that runs without installing
- Language files for the interface list shown above
- Notes on media selection and boot path preparation
System requirements
| Operating system | Windows 8.1 or newer to run the tool itself |
|---|---|
| Processor | Any processor from the last fifteen years |
| Memory | 2 GB |
| Graphics | No dedicated graphics required |
| Storage | 100 MB for the tool |
| Media | A solid state drive in an enclosure strongly recommended over a flash stick |
Installing it
- Unpack the archive. The portable build runs without installing if you prefer.
- Run the tool as administrator, since it writes boot configuration.
- Choose a target drive. Use a solid state drive in an enclosure, not a cheap flash stick.
- Select portable mode if the drive will be used on more than one machine.
- Test the finished drive on a second machine before relying on it anywhere.
Mirrors
| Route | Region | Note | State |
|---|---|---|---|
| Direct, primary | Europe | No wait, resumable | Online |
| Direct, secondary | Asia Pacific | No wait, resumable | Online |
| Torrent magnet | Global | Small file, direct is simpler | Online |
Release history
- Portable mode driver generalisation improved for recent chipsets
- Fixed boot configuration failing on drives above a certain size
- Multiple image boot menu handling reworked
- Cloning to smaller targets made more reliable
- Encryption option added to portable installations
- Installation media creation now leaves the remainder of the drive usable
Questions about this release
Can I use a normal USB stick?
You can and you will regret it. Random write performance on flash sticks makes the result unusably slow. A solid state drive in an enclosure is the only sensible choice.
Will the drive boot on any machine?
In portable mode, on most. Driver generalisation handles the common cases, and preparing for both firmware boot paths covers machines of different ages.
Does cloning my system bring my programs?
Yes, that is the point of cloning rather than installing from an image. The environment comes across as it is.
Is the portable system licensed?
This tool handles the creation of the drive. The licensing state of the system you clone or install is whatever it already was.
Comments
Cloned my working install to an external and it came up on a completely different laptop. Portable mode does what it claims.
Three images on one stick with a menu. One drive instead of three.
Comments are read before they appear. If a build stops working, say so here and it gets rebuilt rather than quietly left up.
My whole toolset on a drive in my pocket, boots on customer machines. Solid state enclosure, not a stick, exactly as the notes say.