Bdtyktl

OK, this is actually my own answer to an unwritten question on this title problem chasen today ...

Why there is WUDFHost.exe constantly on some 12-20% CPU?

According to several posts on the net "The WUDFHost.exe process is part of Windows Driver Foundation of Microsoft", and an essential one, if found on %WinDir%System32 folder. It is pointed to be taking care of "User-mode Drivers".

After checking the drivers on this about half-year old laptop, first 3 most critical ones manually and also updating them, I didn't still note any change on the CPU list. Then I went on checking others automatically this time with the Free Driver Booster 3, and it found some 12 more drivers outdated. So, now I let twice some 3-4 "easy" ones get updated automatically by DB3 and there between checked the actual CPU list, but still no change. But, after an automatic DB3 update of the last "critical/difficult" 5 m/b drivers the WUDFHost.exe was on 0% CPU, great! Note also, that all of the updated 15 drivers were just 3-12 months old.

Edit 18.08.2016 10:30 (GMT+3):

Sorry, to inform, but this cure was a short joy, after Windows 10 was Upgraded from 1511 to 1607 the problem did return, i.e. back to 15-17% CPU, and now the DB3 did recognise only up-to-date drivers ... See below my comments on this.

Edit 18.08.2016 12:30 (GMT+3):

OK, the new troublemaker identified -> Lenovo Quick Optimizer, see below my comment on it, and now this case hopefully finally cleared.

Analyzing the ETL with WPA shows, that the driver iMDriver.dll causes the WUDFHost.exe cpu usage

^{(Click images to enlarge)}

Maybe this file is also part of the Lenovo Quick Optimizer. This process also causes a lot of CPU usage:

The driver and the program do IO calls via Windows Usermode Driver framework (WUDF) and this is the usage you see.

Another program that can cause this issue is the DisplayLink Driver, which is installed when you use (most) Docking Stations, in my case one from Toshiba.

However, they are aware of the problem and are actually improving the driver in every update.

Support Thread: http://www.displaylink.org/forum/showthread.php?t=64887

Driver Update: http://www.displaylink.com/downloads

This indicates that a driver of some kind is repeatedly creating a task and hogging the CPU. I've had the problem for a few weeks with the CPU running at 100% with most taken up by WUDFHost.exe

No doubt it occurred after the last major Windows update. Some kind of conflict.

In my case I eventually tracked it down to a driver I had for NFC from NXP semiconductors. I had left this on after doing some development work about a year ago and it seemed innocent enough. I removed the NXP stuff and the drivers then rebooted. Instant solution as the CPU dropped immediately.

It just shows you need to keep things tidy and not go off into flights of fancy in finding a solution. Most 'advice' that I found on the internet relating to this issue were a complete waste of time and many were plain dangerous.