USBIT v1.82: Error with failure on initialization of Verify pass

[Geoff]

UPDATED - Please see Additional Information at the bottom of this post.

Consistent error, regardless of two different brands and sizes of flash drives used (128 MB FAT32, 4 GB NTFS).

OS: Windows 10 Pro 64-bit, 21H1, OS build 19043.1586. All current MS updates. Only Antivirus is Win10-native A/V.
Windows File Explorer NOT open on the flash drive.

Backup (only) of both drives to uncompressed and compressed images complete successfully.

If set to backup AND verify, the process fails at the beginning of the Verify pass with the pop-up error message:

"Could not seek the USB device (Code: 6)! The handle is invalid."

Even with a failed verify, the image would seem to be OK (haven't tried to restore, though).

The debug logs for successful backup and failed backup & verify are identical (I copied to text files and performed a file compare at the command prompt). No entries appear to be made in the debug log after the device rescan, therefore no differences between the two debug logs.

Debug log from failed backup & verify:

FD01: \\?\usbstor#disk&ven_chipsbnk&prod_flash_disk&rev_2.00#7&c9700fa&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
FD02: Chipsbnk Flash Disk USB Device
FD04: Device ID is USBSTOR\DISK&VEN_CHIPSBNK&PROD_FLASH_DISK&REV_2.00\7&C9700FA&0
FD05: Media Type is 11
FD06: Location Port_#0003.Hub_#0004
FD07: Hardware ID USB\VID_0204&PID_6025&REV_0100
FD08: Device Number is 1
FD09: FOUND!

FD01: \\?\ide#disktoshiba_mk5065gsx_______________________gj002c__#4&24833bee&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
FD02: TOSHIBA MK5065GSX
FD04: Device ID is IDE\DISKTOSHIBA_MK5065GSX_______________________GJ002C__\4&24833BEE&0&0.0.0
FD05: Media Type is 12
FD06: Location PCI bus 0, device 31, function 2
FD07: Hardware ID PCI\VEN_8086&DEV_3B29&SUBSYS_1439103C&REV_05
FD08: Device Number is 0


FV01: \\?\storage#volume#{9c43e216-ddf6-11df-ac60-806e6f6e6963}#0000000000100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0

FV01: \\?\storage#volume#{9c43e216-ddf6-11df-ac60-806e6f6e6963}#000000000c800000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0

FV01: \\?\storage#volume#_??_usbstor#disk&ven_chipsbnk&prod_flash_disk&rev_2.00#7&c9700fa&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 1
FV03: Volume match PCI bus 0, device 31, function 2
FV04: Partition number is 1
FV05: Volume name is \\?\Volume{51c230de-a073-11ec-b11c-a8019d88a037}\ (IFL_3_50)
FV06: Volume path is G:\
FV07: MATCHED!

FV01: \\?\storage#volume#{9c43e216-ddf6-11df-ac60-806e6f6e6963}#000000746a400000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0

FV01: \\?\storage#volume#{9c43e216-ddf6-11df-ac60-806e6f6e6963}#0000007029900000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0

FV01: \\?\ide#cdromhp_dvd_rw_ad-7701h______________________2.86____#4&24833bee&0&0.1.0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0

======================================================================================================================

EDIT: Additional information

I just formatted (full, not quick) the 4 GB NTFS flash drive and copied files to it.
After transferring the files and deleting them on the flash drive, I quick formatted it.

I then performed a Restore AND Verify of the previous compressed (.imz) 4 GB NTFS image and it verified without any errors. Also, as you would predict, the restored image booted and worked as expected.

So, the Verify error and failure would seem to be limited to the BACKUP process!

I hope that all the above is helpful.

[Alex]

Thanks for reporting in detail. I was able to re-create the issue. Will try to find & fix it.

[Alex]

Fixed with version 1.83. Thanks for reporting.

[Geoff]

Thanks, Alex, for your rapid reply and fix!

When creating uncompressed images, backup + verify works perfectly.

Unfortunately, the fix exposed another issue hiding behind the original one. When running backup + verify to create compressed images (both .imz and .img.gz formats), as soon as the verify pass initializes, the app crashes (UI disappears). I have collected in a zip archive data and files from the Windows Event List that I would be happy to provide to you, but I haven't found a way to upload anything to the forum.

Please let me know if there is a way for me to provide what I have for your review. Feel free to use the email address that I provided as part of my forum registration.

Regards,
Geoff

[Alex]

Hi Geoff,

Thanks for reporting. Seems the combination zip + verfify indeed is broken. Happens with by tests as well . Will fix it this weekend.

[Alex]

Version 1.84 fixes the crash on verify init. Something seemed to be wrong with the release linked zlib library, that I did'nt notice during my tests.

However, I still need to put a little more work on this, as a security issue was found in zlib versions prior to 1.2.12. I'm currently trying to integragte this version (still using 1.2.11 with 1,83), but this release of zlib seems a little bit buggy from the contributor side. The VC projects don't work for x86 target anymore and the masm projects are missing. Additionally, some strange warnings when compiling zlib make me unsure of a fast integration of this version in USB Image Tool.

[Geoff]

Hi Alex,

Es tut mir leid! I seem to have inadvertently opened "a can of worms" for you.
I assume that this is a part-time, off-hours activity for you and I don't wish to upend your weekend, so I promise to be patient! Hopefully you will achieve success.

Thanks and regards,
Geoff

[Alex]

New version 1.85 adresses the latest security issue in zlib and updates to zlib 1.2.12. It took some steps to get zlib workung with Visual Studio, but the comments/PR on zlib github page did help.

Thanks for the patience!

[Geoff]

Alex,

Just checked the download page today and was very happy to see version 1.85. Danke schön!

Please take time to enjoy the summer.

Regards,
Geoff