HP USB flash drive write protected after Windows crash.


  1. Posts : 171
    Windows 10
       #1

    HP USB flash drive write protected after Windows crash.


    I got a NEW HP x796w 64 gig USB 3.2 flash drive and was benchmarking it with ATTO when Windows 10 on my desktop decided to have a bit of a lie down and bluescreen. (I'd already tested it on my laptop's USB 3.0 and was testing to see if it would be faster on my desktop's USB 3.2.)

    When it rebooted the HP drive came up as being write protected.

    This is a NEW drive so it is NOT worn out. Just took it out of the package an hour ago.

    I have already tried Diskpart (from an elevated command prompt) the clean command fails, AOMEI, and Partition Wizard.

    Absolutely nothing has been written to it other than ATTO's testing file.

    Is there any 3rd party software that I can point at this flash drive and tell it "No, you are NOT 'write protected'!"?

    I do have Ubuntu installed in WSL2 so if there's a Linux tool that can fix it, I'll give it a try.
      My Computer


  2. Posts : 112
    Windows 10
       #2

    I once had 3 recently purchased USB3 drives (all same model) in a row doing the same while I was testing them. I believe this behaviour is programmed in the drive's firmware or "circuits", but Idk what concretely triggers it, and if it's the same in all models, if it's an irreversible physical damage that's detected on the fly everytime the drive's used, or more like a flag that could theoretically be flashed back through a port etc. Who would bother making the software for it in the latter case? I know this is not a solution, but I wouldn't lose more time with it. I returned the 3 drives and not much afterwards I bought others same model higher capacity, that worked as expected. I guess the initial 3 were just defective from the same batch, and if I had managed to repair them I would have had to constantly fight their tendency to become unwritable.
      My Computer


  3. Posts : 2,554
    Windows 10 Pro 64bit
       #3

    If it’s newly purchased & the clean cmd failed I’d return it as faulty. Any third party software would report that it is write protected but feel free to try.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:44.
Find Us




Windows 10 Forums