C
Carol Haynes
Thanks for your help ...
I have been chatting on Sysinternals Forum about this.
The service name generated is any number of characters long (and as far as i
can tell just capital letters).
I tried RootKit Revealer again and let it scan my registry and my C: drive,
after that I aborted and closed the window.
A randomly named .EXE file was produced in my Local Settings\Temp folder,
and run as a service (I monitored the folder, services and TaskScheduler
while RR was executing).
On exit the file was deleted but not the service name or the service related
registry settings. It can't run 'cos the file doesn't exist.
This is definitely a bug, and (at least to my satisfaction) clearly explains
what has been happening on my system (huge sigh of relief).
Strange thing is that RR doesn't exhibit this behaviour on all systems.
Thanks all for the help sorting this out and giving me a good nights sleep
tonight ;-)
Carol
I have been chatting on Sysinternals Forum about this.
The service name generated is any number of characters long (and as far as i
can tell just capital letters).
I tried RootKit Revealer again and let it scan my registry and my C: drive,
after that I aborted and closed the window.
A randomly named .EXE file was produced in my Local Settings\Temp folder,
and run as a service (I monitored the folder, services and TaskScheduler
while RR was executing).
On exit the file was deleted but not the service name or the service related
registry settings. It can't run 'cos the file doesn't exist.
This is definitely a bug, and (at least to my satisfaction) clearly explains
what has been happening on my system (huge sigh of relief).
Strange thing is that RR doesn't exhibit this behaviour on all systems.
Thanks all for the help sorting this out and giving me a good nights sleep
tonight ;-)
Carol