USB Image Tool 1.76

Version 1.76 fixes an issue with the log output window and adds the possibility to copy the log messages directly to clipboard.

Download USB Image Tool

View FAQ


14 Responses to “USB Image Tool 1.76”

  1. Andrew Says:

    Does starting a device backup image write 0s to empty space? And if not, could you make that a feature? I don’t like running e.g. “ciper /w:F” to clear out the empty space, when it can be done from your program. Send an email back with your reply.

  2. Alex Says:

    Initializing with 0 can be activated for the remaining space during restore (when the restored image is smaller than the device).
    The backup image from a device will contain also sectors, that might not be covered by a partition.

  3. Mattias Soderberg Says:

    Will test your program and see if works

  4. Andrey Says:

    Please tell me – is it Possible to change the Serial of a USB device using your program, provided that the Usb device of the same type and differ only in the serial number?

  5. Alex Says:

    @Andrey: No, this is not possible with USB Image Tool.

  6. abel Says:

    Thanks for the tool, It’s very useful. I do have some question though. I need to write image skip 512 byte at the beginning of sd card, so than my arm board can get up. but there is no way to do that form you software. linux command dd has para “skip seek and count” to write image, that’s very useful, could you make that a feature?

  7. Alex Says:

    @abel: I will put it on the todo for next version.

  8. Martin Gerhold Says:

    Just downloaded after reading about the tool on AskWoody: it seems to not see my Win10 1803 install stick (8GB FAT32, named ESD-USB), although W10 explorer can see it. Explorer hardware properties show it as a Sandisk Cruzer Edge USB device. Any ideas? Has Windows medai creation tool done something odd?

  9. Alex Says:

    @Martin: Please check

    If that is not working, please check the forum in how to activate debug output.

  10. fainder Says:

    Please make it possible to split the file img into the parts so that it can be sent to the cloud

  11. Mark Says:

    I have a 64 GB USB 2.0 Stick for the installation of Win 10 64Bit. I need an iso file of this to burn a win 10 install DVD because my pc doesn’t support to boot from usb stick. When i make a backup of the stick the iso file has a size of 60GB a DVD has only 4,3GB and the files have 4,03GB. Is there a possibility to resize the iso file i can burn a DVD?

  12. Alex Says:

    @Mark: Please see FAQ

  13. Shane Says:

    Hello. Thank you for making this program. It’s very cool.
    First off, I have a problem when trying to make an image using Device Mode (which I need because the image needs to be bootable). For the specific drive I’m using, there are less than 6GB used on a drive with about 32GB of space total. When I try to create the image though, it takes much longer than I would expect, and the image file ends up eating up all the available space on my system drive (file ballooned up to over 158GB). Any idea why this would happen and how I can address the issue? To be clear, the process never finishes. It errors out because of the lack of free space on my system drive.
    Also, when I read the FAQ it sounds as though images created using Device Mode will have file sizes of the entire drive from which they were created including free space. In the example I gave above, does that mean that even though I’ve got about 6GB of data, because the drive is 32GB total, it will create an image file around 32GB?

  14. Alex Says:

    @Shane: Even in device mode, the file (raw image) should not exceed 32 GB. Can you tell me the name of the device (SD card or flash drive), which you are using? Can you provide a screenshot of the first page with device info and a log of the device search? Right now USB can only work with sector sizes of 512 byte, but there might be devices out there, that have 2048 bytes. Maybe this can be the issue for that behaviour.

Leave a Reply