I have a fairly recent rig, Win 10, 12GB RAM, NvIdia 1060GTX, etc. But, to keep the expense of this build down, I had to opt for a very small SSD drive…250GB, on which Windows sits.
No problem, I thought…my son got a 4TB Seagate External for his Xbox1 to replace the 1TB Seagate drive, which I absconded with.
I was having issues with it originally, and we deduced a bad cable, which we swapped with the other one on the Xbox. When plugged in, Windows would chime with that “Hey, I understand you just plugged something into me” via USB, but it wasn’t recognizing the drive. All my USB connected devices (my phone, vaping charger, etc) all worked fine in any of the four open USB ports.
So it worked fine for awhile, I was able to now download most of my Steam games onto it so I could play them and not crowd my C drive as it is so small.
Fast forward to today…unbeknowst to me, my ex-wife decided to bring her fax machine over here to send a fax to a new employer, needing to use my landline. Whatever.
But when I got home from work, I was seeing several disc connection errors, so I decided to reboot. The PC would freeze on the Intel screen (1st one)…until I figured out that it seemed the PC was trying to boot from the D (external) drive. My son told me his mom knocked the drive off the top of the PC tower by accident, and now I am back to Windows recognizing a USB device being plugged in via the chime, but not recognizing the drive itself.
We have not tried to plug it back into the Xbox to see if it works there, that’s the next step. But the thing is displaying the very same symptoms it displayed before I swapped the cable, which has never failed on the new HDD on the Xbox.
Any ideas?