03-13-2017, 10:09 PM | #1 | |
Junior Member
Join Date: Mar 2017
Posts: 2
|
High CPU since Win 10 Anniversary update
As with some others posting here, I've been experiencing high CPU usage of WUDFHost.exe since updating to Win 10 Anniversary edition.
It only really becomes an issue when I have Remote Desktop Connection Manager maximised on one of my two monitors. When I minimise it, the CPU drops again, so I guess it's struggling to "paint" the RDC window while it's up. Downloaded and ran the Support Tool, please let me know any other details I can provide: Quote:
|
|
03-23-2017, 10:06 PM | #2 |
Junior Member
Join Date: Mar 2017
Posts: 2
|
I, too, am curious as to any news/updates regarding this issue.
|
04-11-2017, 03:21 PM | #3 |
Junior Member
Join Date: Apr 2017
Posts: 1
|
WUDFHost.exe high CPU - one solved at least!
I didn't have this issue until a couple of weeks ago on Windows 10. All of a sudden the WUDFHost ran at 30-50% in Task Manager and pushed the CPU to 100% virtually all the time. This slowed the PC to a point of being nearly useless. It seemed to coincide with a large update to Windows.
If I stopped the WUDFHost in Task Manager the CPU immediately dropped to 70% but it popped back up a moment later. This meant that something was relaunching ever few seconds. I had another PC which was unaffected. I eventually found it. I had been doing some work with Near Field Communications about a year ago and had loaded the driver for an NXP dongle. I hadn't used it for a while. I removed the NXP program and associated entry for the hardware in Drivers. I restarted the PC and had an immediate result with the CPU no longer pushing 100% and the WUDFHost no longer visibly ran. The CPU now hovers around 27%. So a simple deep tidy up and getting rid of the dead wood cured it. I would suspect most others are the result of a similar driver conflict. IOBit Driver Booster had not found it needed updating. I found many useless suggestions on the internet to resolve the problem and a number of them were close to being stupidly dangerous to the health of the PC. |
|
|