[FONT="]Changing the Windows Driver Foundation - User-mode Driver Framework Service from Manual to Automatic did NOT solve the Warning message problem in Event Viewer after startup for me. [/FONT][FONT="]
My particular problem appears to be caused by the device driver related to a Biometric Fingerprint scanner device that is integrated into the laptops keyboard/palm rest area on the right hand side.
[/FONT][FONT="]The existing device driver detailed information was AuthenTec version 1.6.2.352 (dated 2/27/2013). Although there appears to be a newer (date anyways) device driver version from Lenovo 5.9.9.7282 (dated 2013-04-21), if you look carefully at the driver Readme.txt file you’ll see that the actual version of the WBF device driver is exactly the same version (i.e., 1.6.2.352). I also verified that the Lenovo driver is the same exact version of the driver by installing the software.
[/FONT][FONT="]If you go into the Device Manager, select the driver and select Properties, the General Tab indicates ‘This device is working properly.’ Not sure why Event Viewer displays the warning message.
[/FONT][FONT="]If you don’t use this particular device, you can Disable the device in the BIOS settings. In the BIOS, go to Security: I/O Port Access: Fingerprint Reader and change the setting from Enabled to Disabled. That “fixed” the warning message showing up in the Event Viewer after restarting the system.[/FONT][FONT="]
Just going to have to live with it I guess.[/FONT][FONT="]
[/FONT][FONT="]By the way, I did try uninstalling all of the USB controller devices in the Device Manager and re-installing the devices to make sure that I had a clean USB controller setup to see if that would correct the problem, but unfortunately it did NOT.
[/FONT][FONT="]=======================================================[/FONT][FONT="]
For reference, the exact warning message I was seeing in the Event Viewer was:[/FONT] Warning message:
The driver \Driver\WUDFRd failed to load for the device USB\VID_147E&PID_2016\6&253484d9&0&3.
And the message just before the above Warning message:
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.
[FONT="]
[/FONT]I did notice that both of these messages showed up VERY early in the startup process, (i.e., only 4 seconds after the OS is counting the number of CPUs and two seconds after the wired Ethernet link has been established messages are logged). My guess is that something related to this device is not being done in exactly the correct order to prevent the Warning message from occurring.