

The fact that this issue was raised 9 months ago and nothing was done to help prevent your users from this experience is a not a good look. This root cause / issue might not be your fault technically, but it doesn’t mean your company should not act on it. Telling your users to ask the manufacturer for a refund is not. Perhaps blacklisting drives with known issues is an option, or publishing a compatibility list of some kind…anything that would have given me a notion this thread existed before I attempted to flash these keys would be acceptable. There is definitely an issue with Etcher X SanDisk. I was able to use Rufus to successfully format / flash a new key I picked up. While the issue may be with SanDisk, it is still really inconvenient and frustrating to wind up destroying drives. I experienced the exact same issue, and just lost two Sandisk USB flash drives. There should be a large clear warning on your software and your website should warning people using SanDisk drives NOT to use your software, as it is clearly capably of easily incorrectly triggering the failsafe locking feature built into this particular hardware…… Your defense is that you did not kill them, your push was gentle and only moved them a couple of inches.

You give them a tiny push, gentle, but enough to move them a couple of inches, enough to push them off the ledge, which leads to their death, caused by the long fall to the ground. Say there is someone sitting on the ledge of the roof a high rise building, and you are walking along, near them, and behind them.

So your claim that it was not your software that causes the drive to brick itself is nothing but a lame word -play ie - a lie - that I could perhaps best illustrate with a physical analogy. Looking on the SanDisk website, it seems this write protection mechanism is something that is built into the firmware of these drives to protect data when the drive’s firmware controller thinks it has detected data corruption. Well, I’ve tried everything in the post, and the comments below, and these two drives are still bricked ie write protected.Īs to your assertion that your software does nothing that could possibly do this is obviously simply not true.
