USB SanDisk 3.2Gen1 USB Device (64Gb Flash Drive)
WinX
EaseUS
The drive is visible in Windows Explorer but...
if I click to open it...
the cursor changes to the hourglass icon for about 40 seconds...
then I get this error popup:
| Error | When Error occurs |
|---|---|
| 1. Location is not available 2. D:\ is not accessible. 3. The request could not be performed because of an I/O device error. |
Popop box image |
chdisk /f D:
cannot open volume for direct access
I fear if I unplug it & replug it, the drive will no longer appear in windows explorer. Or that it will make the problem worse. It may also fix it, but I'm not taking that chance till I'm more aware.
Drive is Very Precious
The drive has 63Gb of important backups on it. College, taxes, previous jobs & projects, pictures of friends and family. It's that kind of drive you put everything important on. :) Properties Panel of the Drive
For additional clarification and context.
The flash drive WAS FULLY functional. I was only using EaseUS because I accidently deleted my Dads tax documents, I successfully recovered them, but continued playing around with the recovery tool seeing what else it could recover. And then the EaseUS window wouldn't pop up anymore, it was still visible in the taskbar but clicking the EaseUS taskbar preview did nothing and trying to close the application did nothing. I tried opening the drive from windows explorer to make sure it was okay, and that's when windows explorer froze too. After an hour of trying to close EaseUS in a subtle way, I had to taskkill the EaseUS .exe
Questions
Since the drive was FULLY functional and I HAVEN'T unplugged the drive since the problem started occurring, what steps can I take to acquire more info about drive's status, state, and problem? What may have EaseUS done to the drive to put it in such a vulnerable state? What may have EaseUs done to the drive to cause the drive to produce an error like this upon experiencing critical problems with the EaseUS application? And just generally, how can I get the drive working again :)
Also, I have the windows setting for letting peripheral devices sleep disabled, so that's not a possible cause.
