The DLL extension is used to store common application logic accessed by other common applications.
High disk and CPU usage by Windows host process rundll32 can occur due to scheduled tasks or if the computer has malware issues.
This article explores a few troubleshooting steps to help you resolve the Windows host process rundll32 high disk / CPU usage problem in Windows 10.
How do I fix the Windows host process rundll32 high CPU usage problem?
1. Disabled items from the Task Scheduler
- Press the Windows key, type administrative tools, and open it.
- In the File Explorer window, scroll down and launch Task Scheduler.
- In Task Scheduler, expand the Task Scheduler Library and navigate to the following location:
Task Scheduler LibraryMicrosoftWindowsCustomer Experience Improvement
- On the right pan, right-click on Consolidator.
- Select Properties.
- Open the Triggers tab.
- Select the OneTime trigger and click on Edit.
- In the Edit Trigger window, uncheck the Enabled box under Advanced Settings.
- Click OK to save the changes.
- Now go back to the Item list, right-click on the following items one by one, and select Disable.
Note: After you’ve performed these steps, don’t forget to restart your computer.
After the restart, check if the high CPU and disk usage issue is resolved.
If not, make sure to reverse the changes made in the earlier steps to enable Consolidator from the properties and item list.
2. Disable Telemetry services
- Press the Windows key + R to open the Run dialogue box.
- Type services.msc and click OK.
- In the Services window, search for Connected User Experience service.
- Righ-click on the service and select Properties.
- Click the Stop button to stop the service.
- Set the Startup Type to Disabled.
- Click Apply and OK to save the changes.
Close the Services window and restart your computer. Open the Task Manager to check if the high disk and CPU usage issue is resolved.
Microsoft’s User Experience service is also known to cause high disk and CPU usage problem. Disabling the service seem to have resolved the problem for some users.