[SOLVED] Code 19 in device-manager for WPD-filesystem-volume driver

Hedini

Contributor
Joined
May 8, 2018
Posts
38
Hello,

seems like I am fighting with my system again after it has been stable for nearly three years (thanks to your support in this forum here :-) ).

It all started with some really random BSOD which may be related to a faulty NVidia Geforce driver (installation)... I don't know, it was always a different error message, rarely connected to a driver at all and if, then it was some Microsoft driver like acpi.sys and it drove me nearly insane as even shutting down the PC spawned new BSOD after booting it and suddenly the crashes vanished for a complete week only to reappear without warning.
Booting to a Linux-system via the UBCD boot CD always worked, running MemTest86+ for 9+ hours did not show any errors at all.
SFC.exe and DISM.exe always told be that there was not a single error, SFCFix.exe also didn't tell me anything new.

But that's only the introduction to my problem I have right now, as the system seems to be stable... at least for now.

I noticed in the device-manager that a bunch of yellow signs in front of the "WPD-filesystem-volume driver" popped up. I think they are connected to my USB-card reader and I'd like to fix this problem. :-)


The error message is: "This hardware device cannot be started, as its configuration information (in the registry) are incomplete or damaged. (Code 19)"... translated from German.


In its event log are often those messages: "The device "SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_General&Prod_USB_Flash_Disk&Rev_1.00#1310020000000011&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}" does need further installation."
followed by "The process for adding the service WUDFWpdFs for device instance-ID SWD\WPDBUSENUM\_??_USBSTOR#DISK&VEN_GENERAL&PROD_USB_FLASH_DISK&REV_1.00#1310020000000011&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} has been closed with status: 0."

What I tried so far:
- Running sfc.exe (no success in solving it)
- Running Dism.exe (nope)
- Deinstalling the WPD-thingy and searching for new hardware (nope)
- Deinstalling the USB-hostcontrollers and searching for new hardware (nope)
- Reassigning a driver letter for the card reader (nope)
- Deinstalling iTunes (nope)
- Manually deinstalling gearsapiwdm.sys (leftover by iTunes as it has been added in several upperfilters - nope)
- Checking Windows Update for any updates / new drivers (nope)
- Running the Windows hardware troubleshooter via command line (it showed me the errors, but could not fix them, so... nope)

My USB card reader has no drivers of its own on the manufacturers homepage and that problem just popped up yesterday after a bunch of BSOD, so I have to stick to the standard Microsoft drivers for this device. It worked for about three months without any problem, so I think it should be something fixable... but I am running out of ideas.

Kind regards,
Chris
 
The USB card reader is attached to a PCIe USB 3.0 card which uses a standard Via Labs 805/806 chip as the ASMedia-Chip from my Asrock 970 Extreme4 does not work under Windows 10.

Nevertheless I got the driver, updated the firmware for the PCIe card, installed the driver (VL800 v4.70c) and rebooted the system. The problem persists.
 
Nope, but I found a news blog dealing with MTP-driver errors in Windows when I searched for the class ID {eec5ad98-8080-425f-922a-dabf3de3f69a} of the items in the device-manager which were marked there with that yellow triangle. The guy wrote that it could be connected to a faulty "UpperFilters"-entry and indeed - there was a value named "WpdUpFltr" for its UpperFilters-entry.

I backed up the branch HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{eec5ad98-8080-425f-922a-dabf3de3f69a} with regedit.exe and removed the UpperFilters-entry as in his screenshot this one was also not present.

I rebooted and after that the errors disappeared and I got my drive letters under the node "portable devices" in the device-manager again instead. Yay! :-)

What I don't know is if the change has any other implications, but for me the result looks good.
Case closed... for now. :-)

P.S.: The USB card reader was working all the time, that's something I did not mention before... it was just this error-sign in the device-manager that was bugging me. I could connect USB-devices to the USB 2.0 and 3.0 ports and even SD-cards without any problems.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top