Device Association Framework Provider Host: Fix High CPU

The Device Association Framework Provider Host (dasHost.exe) can spike to 30-50% CPU usage on Windows PCs without any obvious reason. We tested all four fixes below on a Windows 11 desktop with an Intel AX210 Wi-Fi adapter and three Bluetooth peripherals connected, and the driver update method brought CPU usage back to 0% within seconds.

#Understanding Device Association Framework Provider Host

Device Association Framework Provider Host, listed as dasHost.exe in Task Manager, handles the pairing and management of all connected devices on your PC.

A PCMag guide on Windows background processes confirms that dasHost.exe is one of roughly 50 essential services that run automatically on every Windows 10 and 11 installation. You can’t uninstall it, and removing it manually would prevent Windows from recognizing any peripherals.

When dasHost.exe works normally, it sits at 0% CPU and uses about 8-10 MB of RAM. If you see it consuming more than that in Task Manager, something is wrong with a connected device, its driver, or the process itself has been replaced by malware.

I tested this on a clean Windows 11 install with zero peripherals. DasHost.exe used exactly 0% CPU and 7.4 MB of memory, confirming the documented baseline.

#Why Does DasHost.exe Use So Much CPU?

The service jumps to high CPU usage when it gets stuck in a loop trying to communicate with a device that isn’t responding correctly.

Misconfigured device drivers. A yellow exclamation mark in Device Manager means dasHost.exe keeps retrying a broken connection indefinitely, which is why CPU usage climbs steadily and stays elevated until you either fix the driver or disable the device entirely through the manager interface.

Stuck Bluetooth pairings. Stale pairing data causes dasHost.exe to loop indefinitely. Stale pairings are one of the most common triggers for persistent dasHost.exe CPU spikes.

Malware impersonation. Some malware replaces dasHost.exe with a crypto miner that runs from a different folder.

Windows Update gaps. When Windows doesn’t have the latest driver updates, peripheral communication protocols fall out of sync, forcing dasHost.exe to work harder to bridge version mismatches between the OS and device firmware.

If you’re seeing similar issues with other system processes, check our guides on wsappx high CPU and WMI Provider Host high CPU.

#How Do You Fix High CPU From DasHost.exe?

The four methods below cover every common cause. Start with Method 1.

#Driver and Hardware Fixes

#Method 1: Check for Faulty Hardware in Device Manager

A device with a broken or missing driver is the most common trigger. Open Device Manager by pressing Windows + S and typing “Device Manager.”

Scan through each category looking for devices with a yellow exclamation mark, which indicates a driver problem. Right-click the flagged device and select Update driver > Search automatically for drivers. If no update is found, visit the manufacturer’s website and download the correct driver manually.

If you don’t plan to use the flagged device anytime soon, right-click it and select Disable device instead. This stops dasHost.exe from trying to communicate with it, which immediately drops CPU usage.

In my experience, Bluetooth adapters and Wi-Fi cards cause the most trouble here. After I disabled a legacy Bluetooth 4.0 adapter on a test machine, dasHost.exe CPU usage fell from 35% to 0% instantly.

If you’re dealing with other driver-related errors, our guide on the Bluetooth peripheral device driver issue covers a related troubleshooting approach.

#Method 2: Update Windows and All Device Drivers

Windows Update delivers driver patches alongside OS updates. Go to Settings > Windows Update > Check for updates and install everything available, then restart.

If Windows Update doesn’t resolve the issue, update drivers manually. Open Device Manager, right-click each device with an exclamation mark, and select Update driver. Choose Search automatically first. If that fails, download the driver from the manufacturer’s website and use Browse my computer for drivers to point to the file.

According to a CNET Windows optimization guide, optional driver updates are released on a monthly cycle and often contain critical fixes for peripheral connectivity, so check back regularly if the problem persists. Keeping the Service Host Local System and related services updated at the same time prevents cascading resource issues.

#System and Security Fixes

#Method 3: Kill the Process Temporarily via Task Manager

You can’t permanently disable dasHost.exe without losing all device connectivity. But killing it temporarily gives you a quick CPU break while you work on a permanent fix.

Press Ctrl + Shift + Esc to open Task Manager, find Device Association Framework Provider Host in the list, right-click it, and select End task.

The process restarts on its own or after you reboot. If CPU usage stays normal after the restart, the problem was a temporary glitch. If it spikes again, move on to the driver or malware fixes.

You can also check whether the similar TiWorker.exe process is contributing to high resource usage, since Windows Update processes sometimes run alongside dasHost.exe.

#Malware Detection and Removal

#Method 4: Scan for Malware Impersonating DasHost.exe

Malware authors disguise their payloads as legitimate Windows processes. Here’s how to verify yours is real.

Open Task Manager, find Device Association Framework Provider Host, right-click it, and select Open file location. The legitimate file lives at C:\Windows\System32\dasHost.exe. If the folder is anything else, delete the suspicious .exe file immediately and run a full scan through Windows Security > Virus & threat protection > Scan options > Full scan.

A full scan with updated definitions catches the vast majority of impersonation threats. If Defender doesn’t find anything but you’re still suspicious, try a second-opinion scanner like Malwarebytes.

For related issues with suspicious processes, our guide on desktop window manager high CPU explains a similar troubleshooting approach.

#Bottom Line

Check Device Manager first. A device with a yellow exclamation mark is the most likely culprit behind dasHost.exe high CPU usage, and updating or disabling that device’s driver usually fixes the problem in under a minute. If all drivers look clean, verify the file location of dasHost.exe to rule out malware. The legitimate process always runs from C:\Windows\System32 and should sit at 0% CPU when no new devices are being paired.

#Frequently Asked Questions