Wtf is this
Started by Sida, Feb 04 2009 03:46 AM
3 replies to this topic
#1
Posted 04 February 2009 - 03:46 AM
#2
Posted 04 February 2009 - 06:28 AM
It's either a rogue process (which I doubt cause there is literally shit all about it on the web); or it's a Windows application. Many Windows application - especially those which do not create any windows - create "invisible" windows for the purpose of dispatching events. Since these "windows" are never visible, they are often created with systematically generated names (like app.bl87yEIQuTvEqlk4yz4YZQ.6).
The end task box uses the window title as the name of the application, and if application get stuck (maybe waiting on I/O or something), things like what you saw happen
The end task box uses the window title as the name of the application, and if application get stuck (maybe waiting on I/O or something), things like what you saw happen
#3
Posted 04 February 2009 - 06:28 AM
QUOTE (ChrisTW @ Feb 4 2009, 02:28 PM) <{POST_SNAPBACK}>
It's either a rogue process (which I doubt cause there is literally shit all about it on the web); or it's a Windows application. Many Windows application - especially those which do not create any windows - create "invisible" windows for the purpose of dispatching events. Since these "windows" are never visible, they are often created with systematically generated names (like app.bl87yEIQuTvEqlk4yz4YZQ.6).
The end task box uses the window title as the name of the application, and if application get stuck (maybe waiting on I/O or something), things like what you saw happen
The end task box uses the window title as the name of the application, and if application get stuck (maybe waiting on I/O or something), things like what you saw happen
I just read that same website which you copied and pasted that from.
http://www.broadband...orum/r21232715-
#4
Posted 04 February 2009 - 06:33 AM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users


