Windows is terrible at handling drives with unreadable sectors in file system meta data as it will try reading this sector Ad infinitum, where Linux does not. And Windows will try reading all drives and, if it's a recognizable file system, interpret the file system.
Here I capture what Windows does as soon as it discovers a drive (clearer video here):
![enter image description here](https://cdn.statically.io/img/i.sstatic.net/w9U1K.gif)
If at any point it runs into a read error it will just keep trying. If this happens during boot the system will appear to be hanging. If you attach the drive while Windows is already running it may hang Explorer or even lock up the system. You may be able to prevent the latter by disabling auto-mount:
Type mountvol /n
into an elevated command prompt and press Enter
. You can then try imaging the drive, for example using DMDE free demo will do).
![imaging a hard drive using DMDE](https://cdn.statically.io/img/i.sstatic.net/lnKvL.png)
Easiest way is to using Linux. Since the file system is corrupt, and assuming you want attempt to recover the data from the drive, you can clone/image the drive in Linux. Tools that can help you accomplish this are for example ddrescue or the demo of DMDE (use Native Linux version). I tend to prefer cloning to an image file (imaging).
Once you have the image file you can use file recovery software and try recover files from the corrupt file system.
Note about failing SSD's: It is my experience what once a SSD starts failing, it tends to happen rapidly so fiddle with it as little as possible. Make all disk access count. You best first set up everything for the recovery attempt:
- a system you can boot
- a drive you can copy to
- familiarize yourself with the software you'll use to clone/image the patient
I am all for DIY, but if the drive contains important data, take it to a data recovery specialist (see https://superuser.com/a/1758901/705502).