The driver \Driver\WUDFRd failed to load for the device... error

[frozenreads]

Hi,

Since the 11/18/2012 event viewer (Event ID 219, Task Category 212) has been posting a warning:

The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN (followed by name of USB device)

It only occurs on start up if I have a USB memory device plugged into a USB port. The USB memory device functions perfectly and the error never occurs when I plug in and out a memory device after boot up.

The error only occurs for memory devices like memory sticks, external USB hard drive does not cause this error.

Checking back to around the 11/18/2012 I see nothing that I have changed/installed that might indicate something that has caused this. No other Windows 7 failures or issues.

Booting a second hard drive with windows 7 on the same system (I have this second installation for testing faults etc), the issue does NOT occur.

From checking forums and searching I have found a few others with this issue and a few articles on its cause

WUDFRd failed to load for the device

Event ID 219 is logged after you install Windows 7 or Windows Server 2008 R2

I was just curious as to why it would suddenly start occurring after a particular date when as far as I can tell I have not made any changes to anything around this date.

Also I wondered if there was a fix to stop this, other than removing a memory stick before boot up!

Any thoughts?

 

[idahosurge]

I just started getting this exact same error message logged in Event Viewer when I plug a USB stick into a USB port. It happens with two different sticks from two different manufactures, but it does not happen every time I plug them in. It seems that it may mostly happen the first time I plug a stick in after I have booted up my PC.

Have you been able to find a solution to get these error codes to stop logging?

 

[frozenreads]

Well after much researching I narrowed down the cause of the error message. I noticed that the messages started appearing around the date I very first plugged in a friends Sony Powershot DSC-H9 and installed its device drivers. Indeed when we checked his computer he had the very same message. The error seems to have been caused by the installation of this cameras drivers for some reason. I have found no way of fixing it though, but everything seems to be working so I am guessing its nothing too much to worry about, but its annoying and I would be interested in finding a fix and understanding why this cameras driver causes this. I would be interested if you also have recently just plugged in a Sony!

 

[idahosurge]

The last new USB device that I plugged in and loader drivers for was a Spyder4, that was on 9/29, this did not start until 12/8 so I doubt that the Spyder4 had anything to do with it.

I changed absolutley nothing on the PC just before this started three days ago. It only happens to me for the first USB stick I plug in after the PC boots up. After the first time I can eject the USB and plug in back in, no error code. I can plug in numerous other USB sticks after I plug the first in and no error code. It is only the first USB stick I plug in after the PC boots into Windows 7.

 

[frozenreads]

My issue looks slightly different to yours but perhaps with a similar symptom. This message definitely started occurring after installing this particular cameras device driver. This I confirmed by checking the camera owners event viewer who reports the same message, again starting at around the time this camera was first plugged in. Perhaps this link I found clues us in on what is happening, perhaps certain device drivers cause this to occur. I dont think its anything to really worry about.

WUDFRd failed to load for the device

 

[idahosurge]

I seemed to have fixed it thanks to the link you posted in your last response. WUDFRd is a service and it is called "Windows Driver Foundation - User-mode Driver Framework".
Windows Administration - What Is wudfsvc and wudfsvc.dll

I went into services.msc and looked at Windows Driver Foundation - User-mode Driver Framework, it was set to manual, but under "Status" it was off. I plugged in a USB and the status changed to "Started".

I changed the startup type to "Automatic", shut down the PC, restarted, checked to see that it was still set to automatic and that it was started. Plugged in a USB and no error code, plugged in another USB and no error code. Shut down, started again, checked again and no error code.

If you change Windows Driver Foundation - User-mode Driver Framework to automatic start let me know if it works for you. Also before you change it the service has to be stopped. For some reason you can not stop it after it has started so you need to boot your PC and before you do anything go into services.msc and change it before it has started. Your PC may let you stop it, but mine would not.

 

[frozenreads]

Hey, thanks for the feedback, this fixed it for me too. I am wildly speculating here but I am guessing that upon driver installation the driver software has to switch this off to install, perhaps there is a bug under certain circumstances where it does not get reverted back to Automatic. (checking under test systems this should be set to Automatic by default). Again, thanks for the feedback, between us we fixed it!

 

[mpw101]

This worked for me. I did not have to stop the service. Just went to services, found "Windows Driver Foundation - User-mode Driver Framework", changed it to automatic and the warning disappeared. Thank you.

 

[capricorn8]

I have the same problem, and would like to remove it to avoid repetitive entries in Event Viewer.

Also for me the method described in this thread works.
However, it works just one time. The next time I boot the service startup type gets reset to "Manual" again.

Anybody have an idea how I could find out how this happens, or what I can do to prevent this?

Thanks

 

[mpw101]

Sorry, I don't know why it only worked one time for you. Mine is still set to automatic after all this time. Never got any more warnings.

 

[frozenreads]

Hi, I am afraid I dont have an answer, I have noticed that certain devices seem to randomly revert the setting back to manual again. My GPS unit ALWAYS changes it, my camera and certain USB sticks will sometimes change it back to manual. I really have no solution other than keep chaning it back to automatic. I notice that on Windows 8, the default setting for the service is Automatic - Delayed Start, I have not tested it, but it might be worth trying this setting to see if it helps. It's a very odd thing, and probably just a strange Windows 7 quirk.

 

[paul1149]

Thanks, Idaho. Worked great.

 

[NoN]

After having installed a Camera or installed an internal Usb Card Reader I found when i looked at my C:\Windows\System32\drivers\UMDF\(language-Language)


That there's some .mui files dedicated for the those drivers.

If you're looking now at the folder \UMDF\, you'll see is missing the .dll to match those .mui files. (Capture1.png)

I had for exemple for my internal USB Card Reader, to copy/paste the "WUDFUsbccidDriver.dll" in order it loads the driver when i do plug a SD Card. (Capture2.png)

After that it had recognized the SD Card in device manager as a generic USB device (Capture3.png).

My Card Reader use also Realtek Card Reader drivers, but i can still let the Microsoft generic Usb driver on place as the drivers versions are both similar for the card reader i do use with similar performances.

Now for the "WpdFs.dll" i do not have the "WpdFs.mui" associated to it, but in Services it is started but set to manual on mine, with time to time some errors in the Events Viewer.

I do suspect missing the WpdFs.mui for your language version being cause of some errors & also the WUDFRd . But when the service "Windows Driver Foundation - User-mode Driver Framework" is started, everythings work fine.

Hope this help!

 

[newpgm]

I would like to thank you, this thread has now helped me on more than one occasion. Installed an SSD recently & forgot to make Windows Driver Foundation automatic.

Log showing msgs:
The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC&PROD_FLASH_HS-CF&REV_4.49#000022272228&0#.
&
The UMDF reflector was unable to complete startup because the WUDFPf service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again.

Above suggestion appears to have once again fixed the problem.

Seven Forums is the most helpful forum I have come across for Windows 7 related issues.
Thanks again to all who contribute.

 

[2harts4ever]

The driver \Driver\WUDFRd failed to load

Just for the record, the fix about changing the setting in Services from Manual to Automatic worked for me too.

Thanks and regards,

2harts4ever

 

[cooltooler]

Event id 219

Ok...this fixed it for me, too. Win 8.1 Pro/64bit on Surface Pro after reset.

the driver \Driver\WUDFRd failed to load

 

[Dragonchaser]

I would like to thank you, this thread has now helped me on more than one occasion. Installed an SSD recently & forgot to make Windows Driver Foundation automatic.

In my case it was also an SSD (Adata brand). I would like to add one thing: please make sure your SSD has the latest firmware. This can avoid a lot of problems.

Seven Forums is the most helpful forum I have come across for Windows 7 related issues. Thanks again to all who contribute.

Very well spoken, newpgm! I couldn't agree with you more! Thanks to everyone who contributes!

 

[Dragonchaser]

Update: it wasn't my SSD causing problems in my case, it was an external hard disk enclosure (basically a box in which you can put any hard disk):
Conceptronic Grab'n'Go CHD3SU - Storage enclosure - 3.5" - SATA-300 - USB 2.0
(link to their website: here)

The problem is I had set the Windows Driver Foundation - User-mode Driver Framework service to Automatic and everything worked fine, however, that external hard drive somehow set it back to Manual.

For now I have disconnected that external hard drive and everything seems to be fine.

 

[tiger168]

It's amazing this thread continue to help people, LIKE ME!!

First of all, THANKS!!!

Secondly, I can't believe Microsoft still has not resolve this issue in their own updates. UNBELIEVABLE!!!!

 

[olelundan]

Thanks Idahosurge, it solved my WUDFRd prob as well!