F5F Stay Refreshed Software Operating Systems Problem with loading USB storage devices

Problem with loading USB storage devices

Problem with loading USB storage devices

Pages (2): 1 2 Next
A
Asaseufy
Member
179
09-17-2021, 07:06 PM
#1
In recent days, I've experienced issues with USB sticks not being mounted. This problem appears to affect all USB storage solutions and USB ports. The USB ports themselves remain functional, and devices like keyboards, mice, YubiKey, game controllers work without issue. My system runs Linux, and on that platform, USB ports operate normally, mounting and reading devices correctly. This behavior is consistent across other Windows 11 systems I've tested, and it's also visible in the UEFI. Windows 11 is fully updated, and I have the latest chipset drivers. Downloading the newest drivers from Gigabyte didn't resolve the issue. The UEFI has been flashed to FG, and I suspect an FH might be present now. When the USB device is uninstalled and the USB Host Controller removed, rebooting restores the problem. What could be causing this?
A
Asaseufy
09-17-2021, 07:06 PM #1

In recent days, I've experienced issues with USB sticks not being mounted. This problem appears to affect all USB storage solutions and USB ports. The USB ports themselves remain functional, and devices like keyboards, mice, YubiKey, game controllers work without issue. My system runs Linux, and on that platform, USB ports operate normally, mounting and reading devices correctly. This behavior is consistent across other Windows 11 systems I've tested, and it's also visible in the UEFI. Windows 11 is fully updated, and I have the latest chipset drivers. Downloading the newest drivers from Gigabyte didn't resolve the issue. The UEFI has been flashed to FG, and I suspect an FH might be present now. When the USB device is uninstalled and the USB Host Controller removed, rebooting restores the problem. What could be causing this?

M
mymonitorisoff
Junior Member
16
09-18-2021, 10:52 PM
#2
Maybe you've tried mounting from Linux and ended up facing the exact issue
M
mymonitorisoff
09-18-2021, 10:52 PM #2

Maybe you've tried mounting from Linux and ended up facing the exact issue

D
Darek06
Junior Member
16
09-19-2021, 12:02 AM
#3
The USB sticks are formatted with FAT or exFAT and work well across both Windows 11 and Ubuntu Linux environments. This suggests you're modifying the USB controller's behavior during a Linux session so that Windows doesn't detect mass storage devices, while other devices remain recognized.
D
Darek06
09-19-2021, 12:02 AM #3

The USB sticks are formatted with FAT or exFAT and work well across both Windows 11 and Ubuntu Linux environments. This suggests you're modifying the USB controller's behavior during a Linux session so that Windows doesn't detect mass storage devices, while other devices remain recognized.

C
COLIN20052012
Posting Freak
857
09-19-2021, 03:06 PM
#4
Yes.
C
COLIN20052012
09-19-2021, 03:06 PM #4

Yes.

Y
yuyi11
Junior Member
8
09-19-2021, 04:26 PM
#5
Can you please elaborate?
Y
yuyi11
09-19-2021, 04:26 PM #5

Can you please elaborate?

S
sacapatates
Posting Freak
843
09-19-2021, 05:19 PM
#6
I reviewed the response you provided with bold, but you didn't see it. What would you like me to explain?
S
sacapatates
09-19-2021, 05:19 PM #6

I reviewed the response you provided with bold, but you didn't see it. What would you like me to explain?

K
Klyner
Member
184
09-19-2021, 11:46 PM
#7
It's clear that my Windows 11 setup has an issue that others don't, which is why I'm raising this concern. It seems the challenge comes from running a Linux environment on the same hardware. I'm not sure why this happens or how to resolve it.
K
Klyner
09-19-2021, 11:46 PM #7

It's clear that my Windows 11 setup has an issue that others don't, which is why I'm raising this concern. It seems the challenge comes from running a Linux environment on the same hardware. I'm not sure why this happens or how to resolve it.

C
csige791
Posting Freak
818
09-20-2021, 01:33 AM
#8
The issue stays the same, even though I'm fixating on it. I'll note that I've executed the system file checker without any modifications. The following action is to reinstall Windows.
C
csige791
09-20-2021, 01:33 AM #8

The issue stays the same, even though I'm fixating on it. I'll note that I've executed the system file checker without any modifications. The following action is to reinstall Windows.

I
iKegreenS_
Posting Freak
878
09-20-2021, 03:37 AM
#9
Check Reliability History/Monitor for any error codes, alerts, or relevant events around the time of the mount failures. Also examine Event Viewer.
Maybe there are faulty or damaged files.
In Windows, execute "dism" and "sfc /scannow".
FYI:
https://www.windowscentral.com/how-use-d...s-10-image
https://www.lifewire.com/how-to-use-sfc-...es-2626161
I
iKegreenS_
09-20-2021, 03:37 AM #9

Check Reliability History/Monitor for any error codes, alerts, or relevant events around the time of the mount failures. Also examine Event Viewer.
Maybe there are faulty or damaged files.
In Windows, execute "dism" and "sfc /scannow".
FYI:
https://www.windowscentral.com/how-use-d...s-10-image
https://www.lifewire.com/how-to-use-sfc-...es-2626161

T
Tico_32
Senior Member
680
09-20-2021, 06:06 AM
#10
Outputs from sfc and dism don't show any significant activity during removal or insertion of the drive. The event viewer also fails to capture any errors or warnings when using a custom view. I'll note that in the Device Manager, under Properties > Events, it displays a null driver. Information shows the driver name as null and the class Guid as {000000000-0000-0000-0000-000000000000}. The date is recorded accordingly. When checking hidden devices in the Device Manager, a large list of unknown devices appears. I'm unsure why so many are present, but they all display yellow bang marks and have null drivers, consistent with the previous findings. There might be around 20 of them, and removing them restores normal behavior.
T
Tico_32
09-20-2021, 06:06 AM #10

Outputs from sfc and dism don't show any significant activity during removal or insertion of the drive. The event viewer also fails to capture any errors or warnings when using a custom view. I'll note that in the Device Manager, under Properties > Events, it displays a null driver. Information shows the driver name as null and the class Guid as {000000000-0000-0000-0000-000000000000}. The date is recorded accordingly. When checking hidden devices in the Device Manager, a large list of unknown devices appears. I'm unsure why so many are present, but they all display yellow bang marks and have null drivers, consistent with the previous findings. There might be around 20 of them, and removing them restores normal behavior.

Pages (2): 1 2 Next