F5F Stay Refreshed Software Operating Systems Problem with new USB devices not working

Problem with new USB devices not working

Problem with new USB devices not working

Pages (2): 1 2 Next
J
JulianKillerYT
Junior Member
33
06-05-2016, 07:27 PM
#1
Hello. I'm experiencing an unusual issue where unplugging and plugging a USB device back in causes the computer to lose recognition of it, requiring a reboot to temporarily resolve the problem. Despite running "DISM /Online /Cleanup-Image /RestoreHealth," the issue persists. The operating system in use is: Microsoft Windows 10 IoT Enterprise LTSC (x64) Build 19044.5965 (21H2). If you need further assistance, I'm happy to help. Thank you.
J
JulianKillerYT
06-05-2016, 07:27 PM #1

Hello. I'm experiencing an unusual issue where unplugging and plugging a USB device back in causes the computer to lose recognition of it, requiring a reboot to temporarily resolve the problem. Despite running "DISM /Online /Cleanup-Image /RestoreHealth," the issue persists. The operating system in use is: Microsoft Windows 10 IoT Enterprise LTSC (x64) Build 19044.5965 (21H2). If you need further assistance, I'm happy to help. Thank you.

C
Chester007
Senior Member
528
06-05-2016, 08:00 PM
#2
If you're on the Enterprise version of Win10, reach out to your system administrator or the company's IT team regarding this problem. Alternatively, contact the IoT device builder—they are responsible for installing the software and must offer support. Home users don't have any legal way to use the Enterprise edition.
C
Chester007
06-05-2016, 08:00 PM #2

If you're on the Enterprise version of Win10, reach out to your system administrator or the company's IT team regarding this problem. Alternatively, contact the IoT device builder—they are responsible for installing the software and must offer support. Home users don't have any legal way to use the Enterprise edition.

R
Replicatings
Member
124
06-07-2016, 07:21 AM
#3
That seems to be a company policy. Most organizations restrict USB drive usage on that version of Windows. The IoT versions typically lack many drivers, which can lead to similar problems indirectly.
R
Replicatings
06-07-2016, 07:21 AM #3

That seems to be a company policy. Most organizations restrict USB drive usage on that version of Windows. The IoT versions typically lack many drivers, which can lead to similar problems indirectly.

G
Gingershire
Junior Member
40
06-07-2016, 10:51 AM
#4
But here's the thing. If I put a new USB device in, it will identify it, and I can see the partitions just fine, but as soon as I take the USB out (even when ejecting), and put the USB back in, it will not be identified. No sound. Nothing. This problem goes away after I reboot the computer, and doing this
everytime
I want to plug a new device in, is getting a bit tiresome.
G
Gingershire
06-07-2016, 10:51 AM #4

But here's the thing. If I put a new USB device in, it will identify it, and I can see the partitions just fine, but as soon as I take the USB out (even when ejecting), and put the USB back in, it will not be identified. No sound. Nothing. This problem goes away after I reboot the computer, and doing this
everytime
I want to plug a new device in, is getting a bit tiresome.

U
Ungenuine
Member
214
06-09-2016, 08:58 AM
#5
When you release the device, do you receive a message indicating it's safe to remove?
U
Ungenuine
06-09-2016, 08:58 AM #5

When you release the device, do you receive a message indicating it's safe to remove?

P
Purplz29
Junior Member
42
06-13-2016, 03:36 PM
#6
Yes, I understand. Then inserting the same USB device doesn't work—it fails to recognize it completely, not even a fresh one, until I restart the system.
P
Purplz29
06-13-2016, 03:36 PM #6

Yes, I understand. Then inserting the same USB device doesn't work—it fails to recognize it completely, not even a fresh one, until I restart the system.

J
Jerryx01
Posting Freak
870
06-13-2016, 06:04 PM
#7
Experiment with the device mgr policy configurations to determine their impact.
J
Jerryx01
06-13-2016, 06:04 PM #7

Experiment with the device mgr policy configurations to determine their impact.

T
ThaBear
Member
224
06-14-2016, 02:41 AM
#8
I agree with @Bob.B on this matter.
Nevertheless, my standard procedure is to pause for a while longer and confirm that no applications are still connecting to or attempting to access the drive.
I’m not always confident about Windows’ reliability concerning "Safe to Remove."
I recommend examining Reliability History/Monitor for any error codes, warnings, or informational events recorded when the USB devices are initially used and then stop functioning or fail to be recognized upon subsequent use.
Event Viewer can offer comparable details but demands more time and effort to interpret.
Regarding Group Policy, it may be more complex—review the settings at:
Computer Configuration ---> Administrative Templates ---> System ---> Removable Storage Access.
There are several options and configurations to consider.
T
ThaBear
06-14-2016, 02:41 AM #8

I agree with @Bob.B on this matter.
Nevertheless, my standard procedure is to pause for a while longer and confirm that no applications are still connecting to or attempting to access the drive.
I’m not always confident about Windows’ reliability concerning "Safe to Remove."
I recommend examining Reliability History/Monitor for any error codes, warnings, or informational events recorded when the USB devices are initially used and then stop functioning or fail to be recognized upon subsequent use.
Event Viewer can offer comparable details but demands more time and effort to interpret.
Regarding Group Policy, it may be more complex—review the settings at:
Computer Configuration ---> Administrative Templates ---> System ---> Removable Storage Access.
There are several options and configurations to consider.

S
Silvinha10
Senior Member
694
06-14-2016, 04:32 AM
#9
I will take a look at these. To be truthful, the IoT LTSC support is expected to end around 2032, and I genuinely don’t want Windows 11 with all its unnecessary bloat.
EDIT: It looks like drvinst.exe is damaged.
I also executed sfc /scannow and it reported corrupted files. You can check the complete log there.
Additionally, I didn’t mention that on June 17, 2025, the system crashed with a BSOD related to "DRIVER_POWER_STATE_FAILURE" during a restart. You can find the crash dump here, and the WinDBG output is available there.
S
Silvinha10
06-14-2016, 04:32 AM #9

I will take a look at these. To be truthful, the IoT LTSC support is expected to end around 2032, and I genuinely don’t want Windows 11 with all its unnecessary bloat.
EDIT: It looks like drvinst.exe is damaged.
I also executed sfc /scannow and it reported corrupted files. You can check the complete log there.
Additionally, I didn’t mention that on June 17, 2025, the system crashed with a BSOD related to "DRIVER_POWER_STATE_FAILURE" during a restart. You can find the crash dump here, and the WinDBG output is available there.

L
leonism
Member
171
06-14-2016, 10:22 PM
#10
Please confirm if you reviewed the Security and Maintenance Control Panel as described in the 1/3 screenshot.
I haven’t (fully disclosed) tested Windows Enterprise. But after considering @Aeacus’s comment, it makes sense that issues could arise without proper IT support for Windows Enterprise.
It seems updates from Microsoft, drivers, or applications might be causing conflicts.
The crash dump file was encrypted and readable as plain text.
Noted: "Implicit thread is now ffffb006`7593f040"
*** WARNING: Timestamp for mrcbt.sys cannot be verified***
mrcbt.sys is linked to Macrium Reflect.
Is Macrium Reflect installed? Are you attempting to make images on the USB drives?
L
leonism
06-14-2016, 10:22 PM #10

Please confirm if you reviewed the Security and Maintenance Control Panel as described in the 1/3 screenshot.
I haven’t (fully disclosed) tested Windows Enterprise. But after considering @Aeacus’s comment, it makes sense that issues could arise without proper IT support for Windows Enterprise.
It seems updates from Microsoft, drivers, or applications might be causing conflicts.
The crash dump file was encrypted and readable as plain text.
Noted: "Implicit thread is now ffffb006`7593f040"
*** WARNING: Timestamp for mrcbt.sys cannot be verified***
mrcbt.sys is linked to Macrium Reflect.
Is Macrium Reflect installed? Are you attempting to make images on the USB drives?

Pages (2): 1 2 Next