Forum Discussion
Teams causing windows to not shutdown properly, takes a long time or hangs at shutdown
When disabling the "HP Audio Analytics Service" the problem is solved. I will contact HP about this issue.
- GotEtlJan 12, 2024Copper Contributor
Bob van der Woude - Hello, did you get a reply from HP regarding this? Thanks very much.
- Bob van der WoudeJan 15, 2024Copper Contributor
sorry i missed your conversation here. no i did not get a answer.
Reading the post of Seen_Hudson that he has an answer from HP. Thanx for the update Seen_Hudson
- GotEtlJan 15, 2024Copper Contributor
Bob van der Woude @Seen_Hudson - I have a HP laptop without the issue but I do notice that that CPU of the process can be "excited" when creating audio events, e.g. changing the volume in the system volume mixer for an application for example.
It seems to be the HPAudioAnalyticClientLib module of the process causing the work and it appears to have a log file which we could tail with the PS command:
get-content C:\users\admin\appdata\roaming\hpqlog\HPAudioAnalyticClientLib.log -wait -tail 1 | ogv
Where "admin" is the logged on user.
That has some info about the audio events and could be insightful for you. Other logs could be under:\windows\system32\config\systemprofile\appdata\roaming\hpqlog\
\users\<user>\appdata\roaming\hpqlog\
But I suspect HPAudioAnalyticClientLib.log contains the info of interest. HTH
- Seen_HudsonJan 12, 2024Copper ContributorGotEtl, I raised a call with HP and provided all the logs to escalate. Apparently, level 2&3 teams have been looking into the issue and have identified it to being a HP Hotkey driver problem? To resolve, a new driver is set to be distributed in February. I'm currently seeing if we can download prior to the release date.
- jackdeadJan 29, 2024Copper ContributorDid you get any update on this from HP? We are also heavily affected by this problem and I wonder if HP has confirmed a release date with you. Best regards
- Seen_HudsonDec 15, 2023Copper Contributor
Bob van der WoudeOur companies HP devices look to be having the same issue and started around mid November. Did HP provide a fix or are they still investigating? As you said, disabling this service works but is only a workaround as reading various threads, suggest any driver updates could re-enable this service.