W10 Pro not seeing secondary HDD/SSDs

[sswilson]

So.... I tried to clone a non booting drive and now windows won't recognize either the old or the new drive in Disk Management on boot yet they'll both show up in bios, and acronis. To make matters worse.... I can plug the bloody things into the USB and they'll work (including correct drive ident to allow onedrive to recognize the correct path) as well as showing up in Disk Management.

There's gotta be something simple I'm missing here, but I'm scratching my head and haven't found anything yet....

Any ideas?

[zoob]

Sounds like a disk signature collision. Did you check Disk manager (start -> run -> diskmgmt.msc)?

[sswilson]

Disk manager doesn't see the drives at all unless they're plugged in through the USB and then they work normally. Secondary drive is "D", Boot is "C" and I've ensured that neither of the recovery/system partitions are showing Drive letters.

Only thing I haven't tried yet is to copy the files off of the drive and then attempt to completely remove all partitions in order to see if it then shows up. The first drive has been re-imaged for my dell 2-in-1 and appears to be working fine, while the second one is currently working as required via USB.

This all would have been much simpler if the 320GB WD Black wasn't a thick 2.5 which wouldn't fit into my 2-in-1.... :)

[zoob]

Woops, sorry I misread your post. Do you see any strange messages in event viewer -> system related to the disk subsystem?
Maybe you can also run it through something like Partedmagic and see if some kind of weird metadata is corrupt.

[WolfBane]

Originally Posted by sswilson

Disk manager doesn't see the drives at all unless they're plugged in through the USB and then they work normally. Secondary drive is "D", Boot is "C" and I've ensured that neither of the recovery/system partitions are showing Drive letters.

Only thing I haven't tried yet is to copy the files off of the drive and then attempt to completely remove all partitions in order to see if it then shows up. The first drive has been re-imaged for my dell 2-in-1 and appears to be working fine, while the second one is currently working as required via USB.

This all would have been much simpler if the 320GB WD Black wasn't a thick 2.5 which wouldn't fit into my 2-in-1.... :)

i as well had this problem running win 10 pro , i had to compleatly format all6 drives and do a fresh reinmstall then it found all drives and gave them drive letters accoudinly ! and let me tell ya steve what a PIA it was lol

[sswilson]

Originally Posted by WolfBane

i as well had this problem running win 10 pro , i had to compleatly format all6 drives and do a fresh reinmstall then it found all drives and gave them drive letters accoudinly ! and let me tell ya steve what a PIA it was lol

Heh.... that's what I'm doing right now. Considering the keys are tied to hardware/MSA and it takes less than an hour to install it's hardly worth spending a day or more trying to track something like this down.

edit: And yeah.... no problems picking up and using that drive after a fresh install......

[MARSTG]

Having the same issue here : drive is seen in BIOS, seen in HD Tune and tests fine, but is not seen in Disk Management. I heard that one possible solution is to format the drive with a Windows setup disk.

[sswilson]

Originally Posted by MARSTG

Having the same issue here : drive is seen in BIOS, seen in HD Tune and tests fine, but is not seen in Disk Management. I heard that one possible solution is to format the drive with a Windows setup disk.

Hrmmmmmmmm.....

Maybe this is a recent development and that's why I couldn't find anything useful online.

[Lysrin]

Is this happening post Win10 Creator update? Just wondering if I should prepare myself for update sadness...

[sswilson]

Originally Posted by Lysrin

Is this happening post Win10 Creator update? Just wondering if I should prepare myself for update sadness...

In my case, the cloning I did was on a PC that hadn't been upgraded yet, and it does appear to have been something relating to the cloning process.

As far as the update goes.... it went relatively cleanly as an update on one PC using the update assistance, and super slick on two as a fresh install, but seems to be hung on my main PC that got it as part of the normal windows update system. :(

edit: And a forced restart on that PC brought me back to 1607.... dunno if it tried to install and then rejected it because of the hardware it saw.......