The new version of usb Image Tool fixes two small bugs and adds a logging option. Also new is the option to fill up the remaining space of an USB device after restore with zeroes to overwrite the old GPT backup partition table at the end of the device.
Bonjour,
Thank you for this great program!
Just a question: do you plan to translate it to other languages than English?
Best regards.
@Argolance: I did some tests with other languages. It might be possible in the future.
Thanks
Hello, thanks for this useful tool !
Is there a way to avoid creating a 30Gb image file when creating an image of a 32Gb USB key which contains only 10Gb of data ?
I saw no option related to ‘bootable’ keys. My USB being bootable, will the image contain boot info and therefore, if I create another USB key from that image, will it be bootable as well ?
Thanks,
Laurent
@Laurent: Please try compressed images. More info is in the FAQ. Please see forum and correspondig page for that. Device mode will contain the boot sector.
Nice tool so far. But i wonder is it open source? Is the source code available somewhere?
@Peter: It’s freeware, but not open source. Please see license.txt.
Thank you for a useful tool.
An option to set the maximum amount to read when creating the image would be useful.
For example: I have a bootable 64GB usb stick, where the ext4 partition ends at 8GB. I would like to read the sectors from 0 to 8GB into the image file, then stop.
Thanks!
Download failed far any version – files are damaged.
Nice tool, would like to encrypt the image file with a password. Any chance to get this feature in the future?
@Thorwine: This won’t be implemented in near future. Please see FAQ for reasons.
Hi,
nice tool! I tried the Win GUI Version – works well. Use die command line version -> Code 32: no access! Any idea what went wrong?
I’m using Win7 64 bit
@Martin: Maybe you switched the directory to the USB device and are locking it this way?
Hey Alex,
nice tool. would like to make a exampe line for cmd using ?
thanks an best wishes from munich
Michl
Its rely a nice good work thank you for that and may god bless you and your family members.
Hi,
I found a bug: the program doesn’t check the physical parameters (
size) of target USB flash. It only asks Windows “what is the size of LOGICAL xxx USB drive”.
I’ve got USB flash of 16Gb and restored 2Gb image onto this flash by your USB Image Tool. Windows shows thet the flash drive has 2Gb logical drive and 14Gb unallocated space, but your program doesn’t see these unallocated 14Gb and can restore only 2Gb size image and smoller on this 16Gb flash
@Vladislav: In device mode, the physical size is checked. Even if you restored a smaller image to a physically larger device, you can still see its physical (real) size in the Device section. This is also used for size checks in device mode.
I have version 1.59
Wondering if the program can make the USB bootable, or perhaps not?
@Scott: Make it bootable – no. It just keeps bootable devices bootable on copying.
This software is DON …. Hats off.
Is there an android version of your tool?
@imagic: No, no Android.
I have 3 questions at this moment:
1. Can I open the image file with a compression manager or file explorer? Which one (or just none)?
I’d like to check and modify the content on the image file without need to restore it to a physical device.
2. Do you intend to add ISO files support (that can be opened with a compression manager or an image burner softwares)? I think it’s better to handle instead of .IMG files.
3. Does the software encrypt the image files in any ways? Because I can’t seem to open it anywhere else, so I’m asking myself why.
In other words, the app is great. Thanks for developing it. =)
@Alex, sorry, I didn’t notice there were FAQ and Forums sections. Some of my questions are already answered there.
But you may feel free to reply the other comment in case you want to make it clear here. =)
Hello, I can not take the image of the USB flash drive usb 3.0 uefi, 53% gives an error could not read from the USB device (code: 2)!
Oleg, what could be the problem? how to view the logs?
For example, in the log “E 18:56:02 JetFlash Transcend 8GB USB Device (00002168): Backup failed! Could not read from the USB device (code: 2)! Can not find the file.”
can I find out which file I’m talking about? see the implementation process.
@igor: Can not find te file is an error message, Windows returns during the reading process of the device. Maybe the device is re-detected for some reason and this interupts the reading process. You could see this in the protocol. If it happens at the same percentage every time, maybe there is a read error at this part of the device.
I’ve been using this program for ages now. There are others out there, but this is just quick, simple and amazing.
I have no requests or moans. This is just a note to say thanks for the great work.
Sean 🙂