The driver \Driver\WudfRd failed to load for the device .......


  1. Posts : 152
    Windows 10 Pro x64
       #1

    The driver \Driver\WudfRd failed to load for the device .......


    At Windows 10 startup this Warning appears in my Event Log as Event ID: 219.

    The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{a1c931b2-3b00-11e5-9c14-806e6f6e6963}#0000000008100000.

    I know why this happens. The device in the message is an internal SATA AHCI hard drive. All AHCI drives, even internal ones, are considered removal or hot swapable. It even causes the safely remove icon to appear sort of like it was a USB drive. It happened on Windows 8.x. Don't remember if it happened on Windows 7. I can't make any changes in my BIOS to make it not hot swapable as there is no option for this drive.

    The fix to get rid of the message in W8 was to modify the Service 'Windows Driver Foundation - User-mode Driver Framework' Changing the Startup type from Manual to Automatic fixed the problem. However, on Windows 10 this method does not work.

    I can't disable the Service as it's needed for other devices. Just wondering if anyone found a nice clean way to get rid of the warning message like in W8?
      My Computer


  2. Posts : 2
    Win 10
       #2

    I have the same issue. I have upgraded from Win 7 home, had some issues so I did a clean install of Win 10 home, and I also tried changing the Windows Driver Foundation - User Mode Driver Framework from manual to auto and same as you it did not work. And, Yes, I have downloaded and installed all of the latest driver/firmware from my manufacturer for all my hardware but still have this issue.
      My Computer


  3. Posts : 1
    Windows 10 64 Bit
       #3

    Disabling hard disk hibernation solved the problem for me.

    Just go to Power options -> Advanced Settings -> Hard Disk -> Turn off hard disk after -> Never

    Hope it helps

    Gal
      My Computer


  4. Posts : 2
    Win 10
       #4

    galgu said:
    Disabling hard disk hibernation solved the problem for me.

    Just go to Power options -> Advanced Settings -> Hard Disk -> Turn off hard disk after -> Never

    Hope it helps

    Gal
    Thank you galgu for your response, but I have already done that and still having the issue. After some extensive online scouring, I saw one article that mentioned that Windows 10 will see your internal hard drive as a removable drive as well, and that that is what they believe is the issue, but there is no fix for it....
      My Computer


  5. Posts : 10
    Windows 10 Pro
       #5

    streetwolf said:
    At Windows 10 startup this Warning appears in my Event Log as Event ID: 219.

    The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{a1c931b2-3b00-11e5-9c14-806e6f6e6963}#0000000008100000.
    I recently did a clean install of Windows 10 Pro and noticed this exact same error, it occured 4 times on every boot. The only difference in the 4 Event Errors was after the #sign the numbers were different. I have cleaned/fixed several other Event Errors but this one was hard to fix since there are so many hardware variants with the same ID when you start searching.

    By searching through the registry (in this case it would be for "a1c931b2-3b00-11e5-9c14-806e6f6e6963", I found it was related to may Samsung 840 EVO 1TB hard drive. Since the drive was partitioned into 4 drives I guess is why the 4 errors. Another side effect to this was that these drive letters showed up twice in Windows Explorer, which I also tried to find a solution to with no success. I also have 3 other drives, 2 in raid 0 and 1 cd rom drive.

    I noticed that if I uninstalled the driver for the Samsung SSD and restarted the system the errors were gone but several different ones appeared and also the drives only appeared once in Windows Explorer. Of course after a restart the 219 Event Errors were back and the double drive letters also reappeared. My motherboard has 2 SATA controllers, the Samsung SSD was hooked up to the ASMedia controller and the other 3 drives were on an Intel controller. I updated the ASMedia controller driver to the latest Windows 10 version to no avail. Since the Intel controller has room for 6 drives I figured I would add the other drive to that controllers SATA port. After the next boot all the Event Errors were gone and the drives only showed up once in Windows Explorer.

    I found in other forums people trying to resolve this issue by changing settings in their BIOS to put the hard drive setting to IDE instead of AHCI but I think they ran into other issues. As mentioned above with the Windows Driver Foundation Service this only worked for USB storage devices for me it didn't help in this case but I did use it to remove a similar error in Windows 7 and in Windows 10.

    Some people may not have the option to use a different mother board controller for this fix but hopefully this might help you figure out what the issue might be, whether it is for fixing the 219 Event Error or the double drive letter showing up in Windows Explorer.
      My Computer


  6. Posts : 579
    Windows 10
       #6

    I have a Lenovo Laptop and I have also this error.
    In Device Manager Disabling (not delete) "Lenovo Vhid Device" solves the issue.
      My Computer


  7. Posts : 7,860
    Windows 11 Pro 64 bit
       #7

    I get those warnings too at every boot. It's a common issue and I wouldn't bother about it. Beware of disabling things in Device Manager unless you really know what you are doing.
      My Computers


  8. Posts : 116
    Windows 10
       #8

    In my case the Event ID 219 reads: "The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_SCSI#Disk&Ven_Ricoh&Prod_SD#MMCStorage&Rev_3.00#SD0001#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}."

    This is pretty clearly my SD card which identifies as Ricoh but is a Sandisk card. I suspect there might be something wrong with my USB drivers, or perhaps even the motherboard hardware itself, since running speed tests on cards in this slot has also sometimes shown erratic results, and this was true on Win 7 before I upgraded to Win 10. I've read elsewhere that the "driver \Driver\WudfRd failed to load" message usually occurs for USB devices or possibly power supply issues.

    It was helpful to hear that some have gotten the message even on fresh installs of Win 10, because mine is upgraded and I thought that could be part of my problem. What makes this pointed for me is that I am also getting occasional blue screens and sometimes one program just goes "Poof" and disappears from the screen. That is what is difficult about getting error messages which people advise are safe to ignore. If you are actually having a serious problem, how do you know you can ignore any Event Viewer error?

    I'd be glad to hear a reply if any of this sounds familiar to anyone or you have some inkling about why I could be getting this.
      My Computer


  9. Posts : 579
    Windows 10
       #9

    try to change in Services the "Windows Driver FOundation - User Mode Framework" to "Automatic".
    Sometimes it is turning back to "Manual" , I do not know why.
      My Computer


  10. Posts : 116
    Windows 10
       #10

    Adalwar said:
    try to change in Services the "Windows Driver FOundation - User Mode Framework" to "Automatic".
    Sometimes it is turning back to "Manual" , I do not know why.
    I haven't tried that because the first couple of posts in this thread mentioned this solution and say it does not work in Windows 10 (although it did in 7 and 8.) I have also seen that solution mentioned in some other posts. Are you saying you have reason to believe it WILL work in Win 10?

    Thanks,
    Michael
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:39.
Find Us




Windows 10 Forums