Hi DaftCashew,
Good day! This is Jhakesong and I will be happy to assist you with this.
I am sorry to hear about the inconvenience. Does this happen regardless where USB port the device is plugged in? There could be an issue with the USB root hub drivers. I suggest resetting them and see if it makes a difference.
- Press Windows key + X
- Open Device Manager
- From Device Manager, Expand Universal Serial Bus Controllers
- For every instance of USB root hub, right click and uninstall.
- Reboot your computer every uninstallation and proceed to the next ones, once you have uninstalled all the root hubs check device manager again to make sure they were reinstalled back by Windows properly.
- See if the issue still persists.
Let me know how it goes. Have a great day!
Thank you for your reply! I tried your steps and uninstalled the only instance of USB root hub that I found in my device manager (which was 3.0). Apparently my computer is new enough that there aren't any 2.0 or lower ports in the system, or at the very least every last port is controlled by the same root hub even if a couple of them are 2.0 ports.
Good news: I haven't been able to reproduce the HDD eject issue since the system rebooted! So I think the problem is fixed (for now). Thanks for the help!
Bad news: You failed to warn me that after uninstalling the USB root hub, all my input devices stopped working! I tried all of the ports, both front and back, but none of them would accept my mouse or keyboard anymore after clicking uninstall... so there was no way for me to click "restart" on the dialog box that popped up after the uninstall began! Thankfully while frantically plugging and unplugging USB cables from the back of my PC, I noticed that I still got a device removal sound from Windows when disconnecting my LG monitor with built-in USB hub... this made me realize that Windows still recognized that hub somehow, even though it wasn't recognizing any of my other USB devices. So by plugging my mouse into the monitor's hub, I was finally able to restore input control and safely restart the machine. Everything worked fine again upon rebooting, but damn if I wasn't panicking for a few minutes there! If I had known that might happen ahead of time, I would have been a lot more careful... so maybe add that warning into your steps next time ;)