Hi guys. There was a thread about 2 weeks ago about the problem with se.dll and the About:blank trojan. In the thread, everyone refers to "Lou's" solution, so I did. Here is what he said- <<<The "se.dll" problem is embbeded deeper in the startup of Windows. The culprit is a 'window hook' called "won.---" located in the Windows/ directory. Use Dr. Watson to verify this. This hook intercepts all window activity and periodically recreates the temp/se.dll pest that's been bothering everone in the internet these days, if it is missing or has been deliberately corrupted, which in turn creates the random message generator located in the /system directory and loaded as a Browser Helper Object. This nasty hook also modifies the Registry with the home page and BHO overwrites. I received this pest ungloriously while I was surging a 'porn site' and didn't have my security level set appropriately...>>> When I ran Dr. Watson, it seems the "hook" is a file named mozvtr.dat- It isn't the "won." Lou speaks of. I have no idea what to do now, since it specifically states the hook should be "won." If someone could explain what to do and how to get rid of this ridiculous thing, I would be GREATLY appriciated.

That's pretty much complicated.. Just backup and format your computer :P

I am trying not to do that...I have 4 weeks left until school ends and I have a lot of stuff on my computer...plus it isn't that big of an inconvinence. I know there are a lot of people with se.dll and can get rid of it somewhere...

try this http://www.wilderssecurity.com/showthread.php?p=382326#post382326

It was 'won.---' on my machine, but I have since then found that it randomly names itself at the moment it attaches itself to a machine. You have to boot do DOS, remove the offending 'hook' found by DRWatson and Reboot by simply 'Del'eleting, or 'Era'sing it. Use 'HijackThis' to remove any reference to SE.dll or the BHO from the registry.

The problem is a hidden dll in the windows directory. You need a program called Registrar Lite to find it. Once its removed, the se.dll will no longer be created and the problem is solved. I have used this procedure many times on customers machines, it works well. Go to this page and use the methods they describe. http://www.securiteam.com/securityreviews/5RP0L0UD5U.html Good luck