none
Event ID 219 "The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\

    Question

  • Ultrabook Samsung NP530U3C with Windows 8.1 Pro x64 with latest updates.
    Microsoft .NET Framework v4.5. Microsoft Visual C++ 2005,2008, 2010, 2012, 2013 Redistributable
    I have  1TB Seagate Backup Plus Portable Drive ( Model: SRD0SP0 )connected to my Samsung NP530U3C ultrabook via USB3.
    The disc is divided into 3 partitions D:\, E:\, F:\
    I get notifications in EventViewer constantly at every system startup
    Event ID 219 "The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{3835fa96-4796-11e3-8329-c485082a7bdb}#0000003204300000" ( FriendlyName E: \ )
    Event ID 219 "The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{3835fa96-4796-11e3-8329-c485082a7bdb}#000000D558A00000" ( FriendlyName F: \ )
    Event ID 219 "The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{3835fa96-4796-11e3-8329-c485082a7bdb}#0000000000100000 " ( FriendlyName D: \ )
    All partitions are functioning normally,seems, despite the warnings about driver failed to load. What does it mean?

    Windows does not find driver update - "Windows has determined the driver software for your device is up to date."
    Neither driver updates nor new FW on the manufacturer's website also.


    • Edited by smarty8 Monday, May 11, 2015 4:28 PM
    Monday, May 11, 2015 4:27 PM

Answers

All replies

  • go to run and type services.msc
    Change the 'Windows Driver Foundation - User-Mode Driver Framework' from 'Manual' to 'Automatic'

    I assume this device is attached during Windows upgrade or Windows update

    Tuesday, May 12, 2015 1:59 AM
  • Hi,

    Event ID 219: A Plug and Play device driver on your system is failing to load due to a device driver or device malfunction. This event happens randomly at times due to latency issues associated at system boot up.

    Refer to the link below for its solution:

    http://social.technet.microsoft.com/wiki/contents/articles/3164.event-id-219-windows-kernel-pnp.aspx


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, May 12, 2015 8:27 AM
    Moderator
  • wudfsvc is set to "Automatic ( Trigger start )" course. 

    This disk is connected permanently, but errors occur at at every system startup.


    • Edited by smarty8 Tuesday, May 12, 2015 8:57 AM
    Tuesday, May 12, 2015 8:42 AM
  • Event ID 219: Windows Kernel PNP....
    User Action
    "Check with your device manufacturer to determine if there is an updated device driver available and if Windows 7 or Windows Server 2008 is supported."

    I've already written - "Neither driver updates nor new FW on the manufacturer's website."

    Tuesday, May 12, 2015 8:54 AM
  • Hi,

    How about your problem now? According to the error message, it is indeed hardware driver problem.

    To fix this problem, you can try to run Hardware troubleshooter for test:

    Access to the link below for more details:

    http://windows.microsoft.com/en-US/windows7/What-to-do-when-a-device-isnt-installed-properly


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, May 27, 2015 2:46 AM
    Moderator
  • I'm upgraded to Windows 10 2015.07.29.  The above warnings are also present 
    in the Event Viewer. I drew attention to the fact that even if I order to wudfsvc be run as Atomatic, it runs as Automatic (Ttriggerl Start).
    I did sc qtriggerinfo wudfsvc to learn 
    which event is the trigger to start wudfsvc. 
    That' s output.... 
    C:\WINDOWS\system32>sc qtriggerinfo wudfsvc
    [SC] QueryServiceConfig2 SUCCESS

    SERVICE_NAME: wudfsvc

            START SERVICE
              CUSTOM SYSTEM STATE CHANGE EVENT   : 2d7a2816-0c5e-45fc-9ce7-570e5ecde9c9
                DATA                       : 75 08 bc a3 38 03 82 07
    I tried to find the GUID 2d7a2816-0c5e-45fc-9ce7-570e5ecde9c9 in the registry, but that GUID
    is not in the registry.
    How can I find out which event with GUUD 2d7a2816-0c5e-45fc-9ce7-570e5ecde9c9 
    wudfsvc waiting for  start?
    Perhaps it is the absence of the GUID is reason for delay wudfsvc start? 

    There are many triggers in Task Scheduler. But how do I know which one has the GUID 2d7a2816-0c5e-45fc-9ce7-570e5ecde9c9 (if these are  the very triggers )





    • Edited by smarty8 Tuesday, August 4, 2015 1:16 PM
    Tuesday, August 4, 2015 12:09 PM