Windows 10: Moving my m.2 sad to a USB 3.0 external enclosure to boot

Long story short. I have an older pc that had a m.2 to sata connector. I accidentally broke the adapter and have moved the m.2 ssd to a m.2 USB 3.0 external enclosure to try and boot from that and am not having success. Is this possible? If so how? Don't want to lose my data and don't have access to another pc right now

:)

 

Can't access drives in external USB 3 enclosures

Find someone who has a computer with Windows 10 to test the device. We cannot contribute anything other then keep repeating the same troubleshooting steps over and over.

 

Can't access drives in external USB 3 enclosures


Ever since I switched over to my new Windows 10 PC, I haven't been able to access my external USB 3.0 enclosures. They are all 4-disk enclosures by IcyDock (Black Vortex). On my old Windows 7 PC, all I had to do was turn it on and all 4 drives were detected via USB 3. Now on the new PC none of the drives are detected. I checked their site and they don't list any drivers so I don't think that's the problem. Any idea what I can do? I also have a couple older e-SATA external 4-disc enclosures and those are detected fine through my e-SATA card. So it's an issue with the USB 3.0 enclosures. Also, I have a Mediasonic brand 4-disc USB 2.0 enclosure and that works fine - all drives are detected. So it's just the USB 3.0 enclosures by IcyDock that aren't being recognized.

 

Can't access drives in external USB 3 enclosures

Try another USB 3 device (go to Staples and buy a $9 flash drive). If it does not work, then the drivers for the USB3 port might have to be updated. These might come from the manufacturer of the port, or from the chipset manufacturer (NEC/Renesas, Intel, VIA, etc).

If the flash drive works in USB3 mode, the chances are that the SATA-to-USB bridge controller inside the drive enclosure is incompatible with Windows 10's power management. It is likely that you would run into the same issues with Windows 8.

This would not be a driver issue, but a firmware issue. The microcode in the interface chip of the controller needs reprogramming, and unless the manufacturer of the enclosure recognizes this and seeks to update it from the chip manufacturer (Jmicron, Sunplus, Prolific, Marvell, etc. etc), you're not going to get them to work.