01-08-2013, 02:18 PM
WWAHost.exe runs as an executable in Windows 8 necessary for certain Windows Apps (i.e. Xbox Music).
When I was monitoring a certain process with procmon (Sysinternals) I noticed a really huge stream of messages with a reference to qmhook64.dll (I attached a logfile for you to see a tiny selection, the format is native to procmon). The messages were submitted by wwahost.exe, a process unknown to me, but a quick search on the Internet showed it was a harmless process (http://www.groovypost.com/tips/wwahost- ... g-or-virus). The fact that a QM process was linked to all this, disturbed me a bit. So, I stopped QM to see what would happen: the messages stopped!
I was running QM version 2.3.3.7, the latest official release.
I uninstalled this version and installed the beta QM version 2.3.4.3 and guess what, no more messages. I left the beta on my system (still using the low level hook). I have absolutely no idea why the beta stopped the messages (more Windows 8 compliant?), but perhaps this observation is useful for someone.
Kind Regards.
When I was monitoring a certain process with procmon (Sysinternals) I noticed a really huge stream of messages with a reference to qmhook64.dll (I attached a logfile for you to see a tiny selection, the format is native to procmon). The messages were submitted by wwahost.exe, a process unknown to me, but a quick search on the Internet showed it was a harmless process (http://www.groovypost.com/tips/wwahost- ... g-or-virus). The fact that a QM process was linked to all this, disturbed me a bit. So, I stopped QM to see what would happen: the messages stopped!
I was running QM version 2.3.3.7, the latest official release.
I uninstalled this version and installed the beta QM version 2.3.4.3 and guess what, no more messages. I left the beta on my system (still using the low level hook). I have absolutely no idea why the beta stopped the messages (more Windows 8 compliant?), but perhaps this observation is useful for someone.
Kind Regards.
