Verification fails using USB3 port

[TheMariday]

rpi-imager still seems to be failing to verify contents of SD cards connected via a USB3 port / port on the front of PC's and wanted to raise a ticket explicitly for this so it's more easily findable.

This links recent comments and fixes on #426, #626, #41 and possibly #244

This also seems to be affecting Balena: https://github.com/balena-io/etcher/issues/3399 however mine doesn't seem to be being triggered by Windows Defender as I've got no recent actions in windowsdefender://History

USB2.0 still works fine.

Flash OS: Windows 10 Imager version: 1.7.5 image: Bullseye 64 lite SD: 8gb Sandisk

Hope this helps and I'll link any more tickets I can find, I imagine that this is going to cause more issues as more devices and laptops move over to USB3.0

[tdewey-rpi]

I've been using a USB-3 card reader on a laptop, along with a PCI-E card reader built in to my laptop, and both have written and verified across all available ports without issue. FWIW, the laptop is a Dell XPS 15.

As this is also affecting Belena, and I'm unable to reproduce it, I'm minded to suggest this is not in fact an issue with rpi-imager, but is an issue with the hardware it's running on. I'll hold this open until November 15th to allow other users to chime in - but right now I can't see what we can reasonably do to address this.

[ig-sinicyn]

Hi! Same issue here. Rpi Imager v1.8.1, Windows 11 (RU locale).

I've checked with three SD cards, three card readers and two PCs - it stable fails when USB3 port is being used.

Other tools such as Rufus and sd imager works without any issue. I've also checked the cards with RMPrep's quick scan check to be sure they are ok.

UPD: it seems the behavior depends on sd card speed: image write fails with low speed (C10 class) cards but passes always with U3 or better cards.

[tdewey-rpi]

Thanks for the report, @ig-sinicyn.

Your point on card speed is particularly interesting - I've been testing with an [A1, U1, C10] card, and see no sign of failure. Unfortunately, as this is a rare occurence and happening in other projects too, I'm inclined to suggest this is not an issue with Raspberry Pi Imager, but instead is possibly a multi-factor problem exposed with individual user's PC and sdcard combinations - both of which are beyond our ability to try and address without being able to reproduce the failure.

In my previous comment, I suggested to close this issue on November 15th. Unfortunately we haven't made any traction in terms of finding a reproducible case, and as such I'm closing this as Won't Address on the basis that I can't see how we can meaningfully make progress on it.

[ghiathkamel]

i have same issue i tried two laptops, many RPI OS