HP Hotkey UWP Service uses too much CPU

[jimmy12a]

I'm sorry that I overlooked that FChrist. The thread was just a bit longer. Thanks to you for the solution

[DaIceMan]

The solution has been given by the user GParaskov by disabling the Analytics service. However there is also the option to completely uninstall the service so it won't be enabled again by running from an elevated command prompt:

sc delete HPAudioAnalytics

Then reboot.

[patt1988]

I didn't have to disable 'HP Analytics service' and 'HP App Helper HSA Service', disabling 'HP Audio Analytics Service' was enough to resolve my issue.  Hopefully HP will release and actual fix for this.

[Iacopo]

I applied this on my Probook 445 G7 and it fixed the cpu usage but now I can't use the F8 key to mute the microphone

[samsare]

Same issue with my EliteBook x360 830 G8.

[DaIceMan]

@Iacopo Just disable the Hp Audio Analytics Service - don't disable any other related service else audio hotkeys will not work.

[subjecttochange]

Another positive side-effect I've noticed from disabling the HP Hotkey UWP service is that the laptop has stopped mysteriously rebooting when idle and unattended.

[Ma0815]

I have no solution, but I can reproduce the issue on my system (Elitebook 850 G6) by shutting down MS Teams (Classic / New Version). Jabra is also installed. After starting Windows, the service is quite unremarkable. Closing Teams and its going mad.

[digsmann]

@dalceman, Thank your most valuable trick but for other folks, I am adding simple methods with collections from this post.

1. End task with Process name: "HP Hotkey UWP Service"
Service under the process "HP Audio Analytics Service" from Task Manager
2. Go to services and Disable HP Audio Analytics Service
3. Run command as administrator and type sc delete HPAudioAnalytics and Enter
4. Go back to services and check this HP Audio Analytics Service should be gone by doing a refresh
5. Restart computer.

[dlw-EB860G10]

Just purchased 860 G10, and same issue, but without doing anything, the Hotkey UWP Service went down from about 30% to around 3-5% CPU after 8-10 minutes, with about 5 of those minutes having high or full speed fan. That is still way too much CPU usage in my estimation for a polling service. I will bookmark this in case it gets ugly again.