Overview
There is a specific job this program does better than anything larger: open a disc image, change something inside it, save it, and have the result still boot. Every other tool either refuses to edit an image in place or rebuilds it in a way that quietly destroys the boot sector. This one has done it correctly for two decades, in a program smaller than a photograph.
The premium build here has the license applied, which removes the file size ceiling that makes the trial useless for anything modern, since every operating system image exceeds it. Writing bootable USB sticks, extracting, converting between image formats and mounting to a virtual drive are all available without restriction.
Editing images in place
The interface is a two pane file manager: the image contents above, your local files below. Drag a file in, drag one out, delete, rename, create folders. Save, and the image is written back with its boot information intact. This is the whole reason the program exists, and it works on images far larger than the ones it was originally written for.
Boot information can be extracted from an image, saved separately and applied to another, which is how a custom installation image gets built from parts. The program understands the boot formats used by both the old optical standard and the newer firmware path, so an edited image still starts on modern hardware.
Formats, conversion and mounting
It opens essentially every optical image format that has ever been in common use, including the proprietary ones from the disc burning suites, and converts between them. That conversion capability is often the only reason a decade old image is usable at all today, since the tool that created it is long gone.
A virtual drive component mounts an image as a drive letter so its contents can be used without extracting or burning anything. Several drives can exist at once, and mounting can be made permanent across restarts, which is convenient for software that insists on seeing its disc.
Writing sticks and discs
The USB writing function handles both boot styles and lets the file system be chosen, which matters because firmware requirements differ between machines. A stick written for the newer firmware path with the wrong file system simply will not appear in the boot menu, and this is where most failed installation sticks come from.
Disc burning is still present for the machines that need it, with verification after writing. Images can also be created from a physical disc, which is the correct way to preserve an old installation disc before the media degrades further than it already has.
What you get
- Edit files inside a disc image in place with boot information preserved
- Extract and apply boot information between images
- Support for both legacy optical and modern firmware boot formats
- Opens and converts essentially every common optical image format
- Virtual drive mounting with multiple simultaneous drives
- Bootable USB writing with boot style and file system selection
- Disc burning with post write verification
- Image creation from a physical disc for preservation
- No file size ceiling, so current operating system images work
Inside the archive
- UltraISO Premium installer, offline
- Virtual drive component
- Portable build that runs without installing
- Language files for the interface list shown above
- Notes covering boot style selection for USB writing
System requirements
| Operating system | Windows 7 or newer |
|---|---|
| Processor | Any processor from the last twenty years |
| Memory | 1 GB |
| Graphics | No dedicated graphics required |
| Storage | 50 MB for the program, plus working space for images |
| Media | A USB stick or an optical writer, depending on the task |
Installing it
- Unpack the archive. The portable build needs no installation at all.
- If installing, run setup as administrator so the virtual drive component registers.
- Restart once if the virtual drive does not appear immediately.
- When writing a USB stick, pick the boot style that matches the target machine's firmware.
- Verify a written disc or stick before using it on a machine you cannot easily recover.
Mirrors
| Route | Region | Note | State |
|---|---|---|---|
| Direct, primary | Europe | No wait, resumable | Online |
| Direct, secondary | North America | No wait, resumable | Online |
| Torrent magnet | Global | Tiny file, direct is simpler | Online |
Release history
- Virtual drive component rebuilt for current Windows builds
- Fixed boot information loss when saving very large edited images
- USB writing file system selection made explicit rather than automatic
- Additional legacy image formats readable
- Portable build added
- Modern firmware boot writing support improved
Questions about this release
Will an edited image still boot?
Yes, provided you save in a format that carries boot information. That is the program's defining feature and it works reliably even on large images.
Why does my USB stick not appear in the boot menu?
Almost always the wrong boot style or file system for the target machine's firmware. Write it again with the other combination.
Is there a file size limit?
Not in this build. The trial ceiling is removed, which matters because every current operating system image is larger than it was.
Do I need to install it?
No. The portable build works from a folder, which is handy on a machine where you would rather not install anything.
Comments
Portable version lives on my repair stick alongside everything else.
Pick the right boot style, that was my problem for an hour. The notes explain it.
Comments are read before they appear. If a build stops working, say so here and it gets rebuilt rather than quietly left up.
Swapped one driver file inside an installation image and it still booted. Nothing else does this cleanly.