Dead usb ports on front panel

Topic

New Reply

This morning I plugged a USB stick into the front port of my Win 10 HP510 to look at its contents. Worked fine.  “Ejected” it and looked at another USB stick, and nothing. Didn’t even recognize there was anything there. Tried the second port and still nothing.  USB sticks read just fine on another PC.

The rear USB ports are all working just fine.

 

Thoughts?

Reply | Quote

Replies

My first port of call would be to open the case (whilst PC powered off) and check the front USB header is seated properly, as these connector blocks tend to work loose on motherboard pin headers. An anchoring tab on the block connector has been an oversight for years IMO

Windows - commercial by definition and now function...

Reply | Quote

Cable is seated just fine.

I went to the device manager and and all the usb stuff reports working except for the “AMD 3.1 eXtensible Host Controller – 1.10 (Microsoft)” which reports that “Windows has stopped this device because it has reported problems. (Code 43)” but I can’t find anything on what to do about it, what the problem really i, or how to restart it.

Reply | Quote

I’ve had USB drives “go missing” in my Desttop machine (Asus MB).   It was BIOs issue now corrected with updated BIOs flash.   BUT, before the BIOs update a simple total MB power down worked.  It’s very likely unique to my machine, but might be worth a try:

Full shutdown then unplug the machine so there is zero power to the MB.  Wait about 20 seconds to allow full discharge of any capacitors.  Plug the power cord back in and boot.

 

Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.

Reply | Quote

to do an actual complete or full shutdown of the Win10 OS, type shutdown.exe -s in the Run dialog box, instead of using the Shutdown menu option from the Start menu. then after the computer powers off, unplug the power cord from the computer.

Reply | Quote

Powering down and unplugging fixed the issue.  Thank you. Never would have thought of that.

Reply | Quote

I would recommend to bring the motherboard to some of your local IT services (if available). I suugest to let them re-load the firmware.

My experience is, that this method fixed my same issue, there was broken controller on the MB and reloading the firmware fixed my issue.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote