USB Image Tool 1.80

New version 1.80 adds support for high-res DPI settings. This requires .NET version 4.7 to be installed (instead of prior necessary 4.0 as minimum requirement). The blurry look should be gone now when using DPI zoom settings. I also fixed an issue, where the 2nd volume description was not displayed correctly.

Tags:

20 Responses to “USB Image Tool 1.80”

  1. Malte Says:

    Hi Alex, thanks for providing USB Image Tool! I noticed a small typo in the logs. It probably should be ‘received’ instead of ‘recieved’.

  2. Alex Says:

    @Malte: Thanks for reporting. I will fix it with the next release (maybe an 1.8.0.1 small fix).

  3. Feurich Says:

    Guten Tag Herr Beug, ich nehme an sie sprechen Deutsch.
    Ihr USB Image Tool hat funktioniert und eine .img Image Datei erzeugt, diese ließ sich jedoch nicht mit Rechter Maustaste – Bereitstellen – zu einem Laufwerk mounten. Sie ließ sich mit Rufus auf einen anderen , gleich großen Stick, entpacken. Erwarte keinen Support, nur zur Info. Gruß Feurich

  4. Feurich Says:

    Hello, this is a website with international visitors. So i will repeat it in English. I created a .img file successfully from a USB drive. It is re – writable to another USB Stick by using the Rufus programm. The .img file cannot be used with the Provide command on contect menu in Windows 10 to mount a .img file as a drive. I do not expect any support , only for your information.

  5. Alex Says:

    @Feurich: Thanks for your feedback. Windows can only mount ISO files of CD/DVD drives directly. To mount images of USB drives or hard disks, you need a tool like OSFMount (please check FAQ).

  6. Allex99 Says:

    Allex99:
    April 29th, 2020 at 18:00
    Hi Alex, thanks for sharing the USB Image Tool!
    This tool does not recognize the GoodRam (Wilk)32GB flash drive.

  7. Alex Says:

    @Allex99: Please check the “non-removable drives” option. If it still not working, please provide the “Copy to clipboard” log of the debug output tab.

  8. Cyanlabs Says:

    Hi Alex, Can USB Image Tool Helper be used in another application with all licenses kept intact etc?

  9. Alex Says:

    @cyanlabs: Please see license.txt. Depends on the project. If it’s non-commercial and not just copying the functionality, I usually give permission. Please contact me by mail for details (mail adress is available in the txt files or the applications info tab).

  10. Gabriel Says:

    Hi Alex,

    I found your program very useful to backup my pendrives! But, although I can perfectly backup (in device mode) any pendrive, I cannot restore them: I get “Restore failed! Could not update disk properties (Code: 6)! Controlador no válido.” as soon as I confirm I want to write the USB.
    I tried two different 16GB pendrives (different brand and model) and I got the same. I am working under Windows 10, with version 1.80 of USB Image Tool.
    What info could I supply to you for help?

    Thank you very much in advance!
    Gabriel

  11. Alex Says:

    @Gabriel: Could you please provide the log and debug output and additional details on USB hardware and image (size of the device, size of image, current format of flash drive).

  12. evandro Says:

    Good afternoon Alex, I always use the USB tool, I bought a CF card reader model sandisk extreme USB Cfast 2, does not recognize the partition. the match appears in explore.

  13. Alex Says:

    @evandro: Please activate the HDD option. If it’s still not working, please post log output.

  14. evandro Says:

    I 15:48:44 (00000000): Device change notification recieved!
    I 15:48:44 (00000000): Device change notification recieved!
    I 15:48:45 (00000000): Device change notification recieved!
    I 15:48:45 (00000000): Device change notification recieved!
    I 15:48:45 (00000000): Device change notification recieved!

    where I activate the HDD, follow the log above

  15. Alex Says:

    @evandro: Please check, if you have activated the “non-removables devices” option on the options tab. Then activate the Debug output on the debug tab and post the debug log.

  16. evandro Says:

    FD01: \\?\scsi#disk&ven_st500lm0&prod_34-2gh17a#4&1774b54b&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
    FD02: ST500LM034-2GH17A
    FD04: Device ID is SCSI\DISK&VEN_ST500LM0&PROD_34-2GH17A\4&1774B54B&0&000000
    FD05: Media Type is 12
    FD06: Location Barramento PCI 0, dispositivo 23, função 0
    FD07: Hardware ID PCI\VEN_8086&DEV_282A&SUBSYS_08171028&REV_21
    FD08: Device Number is 0

    FD01: \\?\scsi#disk&ven_sandisk&prod_cfast_sddr-299#000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
    FD02: SanDisk CFast SDDR-299 SCSI Disk Device
    FD04: Device ID is SCSI\DISK&VEN_SANDISK&PROD_CFAST_SDDR-299\000000
    FD05: Media Type is 12
    FD06: Location Port_#0015.Hub_#0001
    FD07: Hardware ID USB\VID_0781&PID_C7CF&REV_0101
    FD08: Device Number is 1
    FD09: FOUND!

    FV01: \\?\storage#volume#{85695229-bc12-11e9-80b6-806e6f6e6963}#0000007432100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
    FV02: Device number is 0

    FV01: \\?\storage#volume#{85695229-bc12-11e9-80b6-806e6f6e6963}#0000000032900000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
    FV02: Device number is 0

    FV01: \\?\storage#volume#{85695229-bc12-11e9-80b6-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
    FV02: Device number is 0

    FV01: \\?\storage#volume#{d2a2da45-a87c-11ea-80eb-24ee9a3b3b9c}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
    FV02: Device number is 1
    FV03: Volume match Port_#0015.Hub_#0001
    FV04: Partition number is 1
    FV05: Volume name is \\?\Volume{cd876fa3-0000-0000-0000-100000000000}\ (Volume)
    FV06: Volume path is E:\
    FV07: MATCHED!

    FV01: \\?\storage#volume#{d2a2da45-a87c-11ea-80eb-24ee9a3b3b9c}#00000004e2100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
    FV02: Device number is 1
    FV03: Volume match Port_#0015.Hub_#0001
    FV04: Partition number is 2
    FV05: Volume name is \\?\Volume{cd876fa3-0000-0000-0000-10e204000000}\ (Application)
    FV06: Volume path is F:\
    FV07: MATCHED!

    FV01: \\?\storage#volume#{d2a2da45-a87c-11ea-80eb-24ee9a3b3b9c}#000000076df00000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
    FV02: Device number is 1
    FV03: Volume match Port_#0015.Hub_#0001
    FV04: Partition number is 3
    FV05: Volume name is \\?\Volume{cd876fa3-0000-0000-0000-f06d07000000}\ (System Reserved)
    FV06: Volume path is G:\
    FV07: MATCHED!

    Alex worked! you are the best !

  17. Carlos S. Says:

    Very good application, I really like it. Perfect for backing up the Raspberry’s micoSD. Thank you very much.

  18. Sven Says:

    Hi Alex,

    the USB-Image Tool version 1.80 doesn’t recognize my usb-device (ASMT 2135), but up to the version 1.70 this device is recognized. The “non-removable drives”-option is checked.

    The debug log shows:

    FD01: \\?\usbstor#disk&ven_asmt&prod_2135&rev_0#wd-wmc3f0fa5ss7&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
    FD02: ASMT 2135 USB Device
    FD04: Device ID is USBSTOR\DISK&VEN_ASMT&PROD_2135&REV_0\WD-WMC3F0FA5SS7&0
    FD05: Media Type is 12
    FD06: Location Port_#0003.Hub_#0001
    FD07: Hardware ID USB_AMD\VID_174C&PID_55AA&REV_0100
    FD08: Device Number is 0

    Thank you in advance!

  19. Alex Says:

    @Sven: Reason seems to be USB_AMD\VID_174C&PID_55AA&REV_0100. The Hardware ID us checked for being like USB\ or tagged as Removable, so the device is excluded like internal drives. I guess I need to modify the check a little bit. Do you have a PC with AMD CPU/Chipset?

  20. Sven Says:

    That’s right. I have a PC with an AMD Ryzen 7 1800X. The mainboard is a Gigabyte GA-AB350-Gaming3 (Chipset: AMD B350).

Leave a Reply