HP Hotkey UWP Service uses too much CPU

[TimButterworth]

Well, that's kind of you to offer but the point I'm making is that we shouldn't have to do anything because HP should already have fixed it by now.

[MonJayy]

---

@JimSchuuz wrote:

---

net stop "HP Audio Analytics Service" && taskkill /f /im:hpaudioanalyticsservice.exe" && SC CONFIG "HP Audio Analytics Service" start=Disabled

---

This command didn't work for me.
net stop didn't work, it says the service doesn't respond
taskkill didnt work because the Process couldn't be found.
what was enough and worked for me is finding the PID of the Service and using that with the taskkill.

My PID was 26736, it can be found in task manager -> services

The SC Config Command references the wrong name and seems to have a syntax error?

The finished command is:

taskkill /f /im 26736 && SC CONFIG "HPAudioAnalytics" start= disabled

You just need to replace the PID with the one you found.

[JimSchuuz]

@MonJayy I had a typo in the command, thanks for bringing it to my attention.  I fixed it in my original post and again down below.  It would be better to use the image name (IM) instead of the process ID (PID) because there is always a chance that the executable is running more than once in memory ie. from an orphaned call, and using the IM switch instead of PID will terminate all instances of it.  Not to mention, it's quicker than trying to locate the PID of the service first, and although many people may be familiar with looking in Task Manager, the PID is not displayed by default and could be tricky for some users to enable.  But, yes, that's another method that's valid also.

For everyone else, here is the breakdown of the commands:

net stop HPAudioAnalytics

This attempts to stop the problem service cleanly.  There is a strong chance that this does not work or it times out, so we add the second command to stop the service forcefully:

taskkill /f /im HPAudioAnalytics.exe

"taskkill" terminates a program running in memory. The /f switch tells it to forcefully close, and the /im switch gives the name of the service, aka the "image" name.  After this is terminated, we need to prevent it from starting on the next reboot:

SC CONFIG "HP Audio Analytics Service" start=Disabled

The command "SC CONFIG" modifies service parameters.  This is followed by the name of the service we're modifying.  To use the Display name of the service, you should use quotes. To use the Service name of the service (I know, this sounds redundant) you don't need quotes but it cannot have any spaces in it (it won't have them; if there are spaces, it's the Display name, and needs to be in quotes).  The switch START= tells Windows to modify the startup type for the service.  In our case, we want it disabled.

net stop "HP Audio Analytics Service" && taskkill /f /im HPAudioAnalytics && SC CONFIG "HP Audio Analytics Service" start=Disabled

The commands above can be run individually, or all at once.  But to run them all at once, you need to separate each command using a space preceding and following 2 ampersands - " && ".  This is just part of the old command interpreter that allows running multiple commands as one.

Hope this helps everyone.

[glenh2]

I have windows 11 installed.  I tried the recommended patch and it did no work.  Instead I disabled Hotkey (see link below) as I don't use any of its features.  Per below link I also tried running malware scan, but no malware was detected. 

https://www.thewindowsclub.com/hp-hotkey-uwp-service-high-memory-and-cpu-usage 

[JimSchuuz]

@Glenh2 - I understand that you went to the page at the link you posted.  Unfortunately, that article was written without any actual knowledge of the problem, and generally just offers some very generic steps.

The problem that's reported by Task Manager as being the "HP Hotkey UWP Service" is really the "HPAudioAnalytics" service.  Going into SERVICES.MSC, locating that service, stopping it and then disabling it should fix your problem.  Disabling the HPHotkeyUWPService will not.

[MichalM79]

So three month and nothing has happened in HP ? To me it seems someone else is using power of our laptops. It sure uses the machine more, so there is bigger probability notebook dies soon. And that is fine for the corporation. Nope- no more HP in the house.

Btw. is this official HP support forum? No official answer?? Just other users telling us to disable the process? If I disable it, most of the keys work- the ones I don't need and don't use. Only ones that don't work and those that I only use are the dimming of screen. So not really solution.

HP can you do something about it? 

[JimSchuuz]

@MichalM79 If you disable the correct service, it won't affect any hotkeys.  That's because it isn't Hotkeys service, it's the AudioAnalytics service.  The confusion is because it's reported as the Hotkeys service by Task Manager.

From what I heard on the grapevine, a fixed version is set to be released sometime in February.  After that happens, it will be up to you to update your own systems.

Nobody is "using power of" your laptops - it's a process that gets hung and doesn't terminate when it is supposed to, just like the thousands and thousands of other processes that have had similar problems since the beginning of Windows multitasking.

[Slava5]

Try this. Solved: HP Hotkey Support warning - Page 5 - HP Support Community - 8907036

Post from Dan-Wabwile.    ‎01-04-2024 03:09 AM 

[SirSunFox]

Disabling Jabra Direct software solved the issue. I enable every once in a while, for firmware update checks, but leave it off by default. No more HP hotkey CPU issue.

[JimSchuuz]

@SirSunFox  That's great that this worked for you. However, the problem is occurring on many computers that do not have any Jabra software installed.  Therefore, the workaround that disables the correct "HPAudioAnalytics" service is the solution for those machines.  Likewise, if you would rather not continuously disable and reenable your Jabra Direct software, you can also disable the correct HP service and fix the problem as well.

The problem is not with Jabra software, the problem is with the audio analytics service.  Yes, it conflicts with Jabra sometimes, but it also conflicts with plenty of other software processes while it's doing a test for interactivity, and disabling the correct service should be the workaround for most people. If someone has Jabra installed and they don't ever use it, the software should be uninstalled, but the problem with the "Hotkey UWP Service" is resolved by disabling the HPAudioAnalytics service.