My WD passport external hard disk is of 2 TB.
I can see the HDD shown as some local disk(not with the HDD given name) but it cannot be accessed. And windows explorer stops responding if i try to access it.
So let me summarise the points i have on my problem:
after connecting it to the device, it continuously blinks and i can hear sound that it is running inside. But in file manager, it just shows the disk name (like Local Disk H) not my harddisk name.
And I cannot access it rom my computer/windows explorer(or whatever it is called)
when it is connected to the device, disk management keeps on loading and does not show the results.
If I open device manager, I can see my HDD there.
Thing I tried or noticed:
It is not device usb port problem(i have tried on more than one device).
2.I have tried updating the driver from device manager.
I also went to the properties of the HDD(which shows as local diskH and not with its actual name) but there is no error message.
I tried to use a data recovery software but it is also stuck at “refreshing disk information” page and keeps loading while the HDD is connected.
If anyone has any idea on what is going on or how to fix it please let me know.
Anything would be highly appreciated.
Two persons (I included) have been having the same problems since some few days ago, I created this topic:
We are waiting for a solution or information about the possible reasons for the problem, or if exists a bug in the windows driver or similar, because I have been checking the disk in Linux and appears the information about it and partitions, without any freezzing the system, but I can’t mount the partition, I think for the encryption.
I reviewed the post and performed all possible steps (for example, the part of Disk Management is not possible for the freezing state when the disk is connected), and I obtained the same behaviour and result.
I tested another time in Linux, and in Linux the system didn’t freezed, the disk appears in the available disks, but is not possible mount the partition for the disk encryption (I hope/think), and this behaviour say me is a possible bug with the driver or similar, but we need information form WD.