HP Support Forums
Join in the conversation.
05-09-2009 04:55 AM
Hi. Looking at "Services" and "Startup" processes on a tx2500z, what is hpqwmiex? Google results vary from special keyboard functions, to image mgmt, to something to do with hp printers? Thnx.
Solved! Go to Solution.
08-07-2009 11:06 AM
I can confirm CharlesHP's response. I noticed that the QuickPlay/DVD buttons on the QuickLaunch bar of my dv6835ca Pavilion don't work if I disable the hpqwmiex service.
I get a strange notification in my Event Viewer everytime I boot-up (start Windows Event Viewer , then look in Windows Logs | Applications for events with the source name hpqwmiex) that has the description:
The description for Event ID 0 from source hpqwmiex cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
This event started immediately after I updated my HP QuickLaunch Buttons to v. 126.96.36.199 H (SP40139.exe). All the buttons are working on my QuickLaunch bar so I decided to leave things as they are in case a re-install of SP40139.exe just makes matters worse.
Sorry I didn't see this post earlier. I wasted alot of time trying to figure out just what the hqpwmiex service does.
09-27-2009 07:21 PM - edited 09-27-2009 07:29 PM
Many users no doubt will see that event log error ID ('zero') for hpqwmiex, some very likely due to those seeking to and
disabling the Pavilion QuickPlay button (as given that the last time I checked, HP neglects to afford means for users to
disable Quick Launch's 'Quick Play' button).
To disable that annoying button, assumedly where certain software and updates are installed (see below), one can
'simply' untick the msconfig startup box's ticked 'QT Buttons', which (at least on my system) thereafter disables
QP's screen overlay (QP won't appear on the screen) which essentially 'disables' the quasi nuisance of the otherwise
perpetually active QP button (which leaving the QL's volume slidebar and mute buttons still active). Tidy users can then
wipe off 'our' Pavilions w/o starting up an unwanted program.
Users no doubt do that, not only to stop the unintentional start ups, but even more so, to curtail software designed to
ensure screen hogginess. By that I mean, the added Pavilion annoyance of whenever QP started up (until I fixed mine), HP and/or CyberLink's failure to afford "disabling" the QP button-sensor, additionally ensured the apparent lack of a
default (at least my inital QP, QL & QT installs) customary program linkage for minimizing or exiting the program.
Although updates to all the QP utilities (and the program itself) seem to have partially remedied that aspect of the HP
Quick Play, Quick Touch and Quick Touch Buttons annoyances, as thereafter when intend for QP to start up, at least the exit/minimize linkage now briefly appears (until it automatically times out and disappears) no longer leaves this user to the
substancial process of drilling down to even find the exit link.
For what its worth, 'my' system (Vista SP1) currently has the following HP 'Quick/CyberLink' installations:
QuickPlay for Windows v188.8.131.52, v2.04.2823 and v4.5.0.0000, QP's SP35813 v3.2 aka v184.108.40.2069, Quick Launch
Buttons SP38688 v6.4.0 D3 aka 220.127.116.119 and SP43616 v18.104.22.168, QuickTouch's SP40139 v22.214.171.124 H and SP38358 v126.96.36.1999 aka v1.00 D.
06-30-2011 06:36 AM
The thing is that, due to a long-standing bug with hpqwmiex.exe, it's a toss-up between the QuickPlay buttons working and a USB mouse freezing each time you switch user.
It would be so good to have it fixed... but as I say, it's a very long-standing bug (years) so I'm not holding my breath.
07-26-2011 05:25 PM - edited 07-26-2011 05:29 PM
don't stop this service, or some of the buttons will stop working.
That's exactly why someone would want to stop that service, to stop the ridiculously badly made buttons from turning wireless on and off, changing volumes, etc, all without anyone being near the computer.
But thank you, as your response wound up sort of fixing my problem.