Event Viewer Error 219

Since 12/8/12 Event Viewer has been posting a warning:

Event ID 219, Task Category 212

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 after I turn on the PC and the PC has completely booted into Windows 7 I then plug a USB stick into a USB port. It will do this on different ports. Even though an error has been logged the USB stick works fine.

After event viewer logs the first error code I can plug a different USB stick in and Event Viewer does not log any additional error codes after I plug more USB sticks in.

I can eject the original USB stick that caused the error code and plug it in again after the error code was logged the first time and event viewer will not log another code.

Any thing a google search produces does not relate to what I am seeing expect another thread on this site. I thought that I would post this in a different forum on this site to see if I can get some responses. The other poster did not get any other than one I made.

Does anyone have any ideas how I can get EV to stop logging this error message for the first USB stick I plug in everyday?

idahosurge said:

Since 12/8/12 Event Viewer has been posting a warning:

Event ID 219, Task Category 212

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 after I turn on the PC and the PC has completely booted into Windows 7 I then plug a USB stick into a USB port. It will do this on different ports. Even though an error has been logged the USB stick works fine.

After event viewer logs the first error code I can plug a different USB stick in and Event Viewer does not log any additional error codes after I plug more USB sticks in.

I can eject the original USB stick that caused the error code and plug it in again after the error code was logged the first time and event viewer will not log another code.

Any thing a google search produces does not relate to what I am seeing expect another thread on this site. I thought that I would post this in a different forum on this site to see if I can get some responses. The other poster did not get any other than one I made.

Does anyone have any ideas how I can get EV to stop logging this error message for the first USB stick I plug in everyday?

Have you checked for updated drivers?

The PC is two years old and this just started three days ago, nothing on the PC was changed before this started. If it is the drivers then why did it just start now after two years.

idahosurge said:

The PC is two years old and this just started three days ago, nothing on the PC was changed before this started. If it is the drivers then why did it just start now after two years.

I suggested a driver update based on the error message you posted; "The driver \Driver\WUDFRd failed to load for the device...". In reference to "Why did it just start" I wouldn't know.

HTH

Problem solved.

WUDFRd is a service and it is called "Windows Driver Foundation - User-mode Driver Framework".

I went into services.msc and looked at Windows Driver Foundation - User-mode Driver Framework, startup type was set to "Manual".

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.

I have three PC's with Win7 and I looked at another one this morning. It had just started throwing this error code on Monday, the service on this PC was also set to manual, changed it to automatic and no more error code. I looked at my third PC this evening and the service was set to automatic.

I have no idea why, but somehow on two out of three Win7 PC's this service got changed from automatic to manual last Friday. I used one on Saturday and that is when the error code started on that one. I used the second one starting on Monday and that is when the error code started on that one.