Share via

[SOLVED] USB device problem. (Code 38)

Anonymous
2019-04-21T10:04:48+00:00

Hello.

I have problem attaching USB devices.

When I attach USB flash drive or USB HDD or CD card I receive this error:

Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38) <br><br> <br><br>The driver could not be loaded because a previous version of the driver is still in memory.

The interesting thing is that I have attached 2 USB devices that work: USB wireless dongle for mouse and external hard drive.

I tried uninstalling USB controller and then restart the laptop. The problem is still present.

I tried installing USB Fix from Microsoft. It couldn't solve the problem.

I think that the problem appears after the last Win Update.

OS: Windows 10 Pro, x64, v1809

HP ProBook 6560b

EDIT:  THE SOLUTION.

Finally I found a solution!

I used a program called USB Oblivion.

You can download it from here.

This utility designed to erase all traces of connected USB devices - flash-drives, disks and CD-ROMs from computer registry of Windows XP, Windows 2003, Windows Vista, Windows 7, Windows 8, Windows 10 (32/64-bit versions). The utility has a test mode of<br> operation, i.e. without actually removing data from the registry, and, just in case, creates a .reg-file to undo any changes. There is also a fully automatic mode.
Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Anonymous
    2019-04-24T16:18:35+00:00

    Finally I found a solution!

    I used a program called USB Oblivion.

    You can download it from here.

    This utility designed to erase all traces of connected USB devices - flash-drives, disks and CD-ROMs from computer registry of Windows XP, Windows 2003, Windows Vista, Windows 7, Windows 8, Windows 10 (32/64-bit versions). The utility has a test mode of<br> operation, i.e. without actually removing data from the registry, and, just in case, creates a .reg-file to undo any changes. There is also a fully automatic mode.

    I would like to thank everyone who has written this thread for their responsiveness and willingness to help.

    20+ people found this answer helpful.
    0 comments

26 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-04-21T10:29:19+00:00

    I have rebooted the laptop 100 times after I noticed the problem.

    Also I removed the Fast Startup function but with no success.

    7 people found this answer helpful.
    0 comments
  2. Anonymous
    2019-04-21T10:19:19+00:00
    Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38) <br><br> <br><br>The driver could not be loaded because a previous version of the driver is still in memory.

    Rebooting the machine should fix the problem.

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2019-04-24T07:45:53+00:00

    Hi,

    I've read through both of your Q threads concerning and thought that I might chime in here, for what it may be worth.

    I encountered this very same issue (or at least similar) a few years ago on one of my devices. This is what resolved it for me:

    If memory serves me correctly I performed this with the problem USB peripherals (there were two) disconnected from the device (again, if memory serves me correctly, this was key). In Device Manager, expand the USB controllers then select the View tab>Show hidden devices then scroll back down to the USB controllers (expanded). Then uninstall any and all entries shown with an exclamation mark (usually yellow) and choose the uninstall/remove driver file option as well (a restart may be required individually with each one if more than one removal is needed to be performed). After the last one restart once again then let the system stabilize (you can watch the Task Manager for this) and then plug-in the peripheral(s) (one at a time if more than one is involved) and Windows should reinstall the device on it's own in most cases (if the device is not recognized by Windows disconnect the device and install the most recent driver from your OEM or the device manufactures website as applicable).

    For my situation the download and install of a driver was not needed (the peripherals involved had worked fine previously) and the issue has not reoccurred since.

    That being said, during my research I did come across an odd-ball occurrence of the Device Manager code 38 instance that did not apply to my situation but non-the-less could be worth mentioning (linking to) here (with the solution involved):

    https://community.spiceworks.com/topic/487249-code-38-problem-with-device-driver-on-windows-2008-r2

    Again, for what it may be worth.

    Hope this can help and good luck going forward.

    -Richard

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2019-04-21T11:56:41+00:00

    Hi,

    Can you check the following registry key?:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4D36E967-E325-11CE-BFC1-08002BE10318}

    At that registry key, in the right window, is there a "Name" UpperFilters and/or LowerFilters?

    If so, what is "Data" for those Names?

    1 person found this answer helpful.
    0 comments