B
Bigjon
Anybody know why *linktest.exe* keeps appearing in the running process list
(xp pro), even after I turn it off and delete it?
(xp pro), even after I turn it off and delete it?
D
Duane Arnoldreating
Sounds to me that you have some kind of malware situation happening and you
need to find out what's creating the file. You can use something like
Process Explorer (free use Google) to look inside for a possible clue as to
its origins. You can also use AD-Aware or Spybot both are free as well and
try to remove it off of the machine, if you don't know about the two
applications.
Duane
B
Bigjon
Duane Arnoldreating declared:
Ok, I used all the above, adaware found a few bits and pieces but nothing
significant (a few cookies and alexia). Spybot and pest patrol the same. A
registry serach returns no hits, nor does a file searcg apart from the .EXE
file thats created on boot.
The Process explorer found some reg keys but nothing else, no dlls etc. I
deleted the process and tree.
Each time I boot, it starts up again. I kill it, and delete the file from
C/WINDOWS.
when I reboot all runs ok except the screen goes blank for a second as the
desktop initialises. Then the process and the file _linktest.exe_ are back.
The file has no properties sheet.
I guess it MUST be malware or a virus, but I cannot find anything on Avast,
Trend micro housecall, AVG 7 pro, or stinger.
Has anybody any ideas as to what is creating it, or how to find what
creates it and remove it?
Sounds to me that you have some kind of malware situation happening and you
need to find out what's creating the file. You can use something like
Process Explorer (free use Google) to look inside for a possible clue as to
its origins. You can also use AD-Aware or Spybot both are free as well and
try to remove it off of the machine, if you don't know about the two
applications.
Duane
Ok, I used all the above, adaware found a few bits and pieces but nothing
significant (a few cookies and alexia). Spybot and pest patrol the same. A
registry serach returns no hits, nor does a file searcg apart from the .EXE
file thats created on boot.
The Process explorer found some reg keys but nothing else, no dlls etc. I
deleted the process and tree.
Each time I boot, it starts up again. I kill it, and delete the file from
C/WINDOWS.
when I reboot all runs ok except the screen goes blank for a second as the
desktop initialises. Then the process and the file _linktest.exe_ are back.
The file has no properties sheet.
I guess it MUST be malware or a virus, but I cannot find anything on Avast,
Trend micro housecall, AVG 7 pro, or stinger.
Has anybody any ideas as to what is creating it, or how to find what
creates it and remove it?
G
Geese_Hunter
Get Hijack this from majorgeeks.com it is in the spyware tools section &
then post the results on spywareinfo.com/forums/ If you delete the
items yourself you could do harm to your pc, so be careful.
Run it when just after you boot up but, don't have other programs
running, like your browser, email etc.. just leave your normal startup
items running
T
Tormod Kvalheim
Duane Arnoldreating said:Sounds to me that you have some kind of malware situation happening and you
need to find out what's creating the file. You can use something like
Process Explorer (free use Google) to look inside for a possible clue as to
its origins. You can also use AD-Aware or Spybot both are free as well and
try to remove it off of the machine, if you don't know about the two
applications.
Duane
www.sysinternals.com
Tormod
B
Bigjon
Geese_Hunter declared:
hmmm...
I turned off and deleted the registry entries to _roing.ocx_ and
_roing.cab_ also entries for a browser toolbar
(http://www.findthis.websiteyouneed.com) that was already supposedly
removed.
The problem has gone, but whatever it was, it was a real PITA to track down
and kill..
Thanks to all, some useful tools there,
especially _listdlls.exe_ from www.sysinternals.com.
hmmm...
I turned off and deleted the registry entries to _roing.ocx_ and
_roing.cab_ also entries for a browser toolbar
(http://www.findthis.websiteyouneed.com) that was already supposedly
removed.
The problem has gone, but whatever it was, it was a real PITA to track down
and kill..
Thanks to all, some useful tools there,
especially _listdlls.exe_ from www.sysinternals.com.