Superfish removal help

[Peace-]

I recently helped my mom pick out a new computer for her work from newegg (ended up getting a lower end lenovo as for what she was looking to do with it wasn't that stress inducing computer wise) and it came today, while I was doing the normal basic new computer things for her (PC decrapifier, ninite, exc.) the antivirus on the initial scan picked up super fish so I looked into it further and and by using malwarebytes and hitman I was able to get rid of almost all of it but there is still one instance of it in system32/config/software.log.1 and I do not know how to get rid of it, I didnt find anything about it online and I tried the lenovo superfish removal tool and it does not pick it up.

Any advice on this would be helpful, thanks.

 

[Saga Lout]

I'm fairly certain that as long as there is also a file named software.log, it would be quite safe to delete the file software.log.1. That said, hang on for some other opinions on this. My suggestion is based on tye fact that it's only a log - a plain text report on an event - and if you can delete it, no harm would be done.

If you tried to delete software.log you would see the message that it's in use elsewhere so give it a shot. If it lets you delete it, end of problem and if it doesn't it wlil not have done anything at all.

 

[Peace-]

I'm fairly certain that as long as there is also a file named software.log, it would be quite safe to delete the file software.log.1. That said, hang on for some other opinions on this. My suggestion is based on tye fact that it's only a log - a plain text report on an event - and if you can delete it, no harm would be done.

If you tried to delete software.log you would see the message that it's in use elsewhere so give it a shot. If it lets you delete it, end of problem and if it doesn't it wlil not have done anything at all.

When I checked the files that were there there was no software.log and in attempt to see if it would let me delete it, it gave me an error that the file was in use and that I cant complete the action because the file is open in the system. its kind of similar when avast picks it upwhere it gives you the option to try to fix it/move it to their chest/delete it goes through the 1st 2 unsuccessfully and attempts to delete it but the action gets postponed.

Thank you for the reply

 

[Saga Lout]

It could be worth a shot at removing it as the system Administrator in Safe Mode. Which version of Windows are you running?

My thinking is may only be in use in your account so if you log in as Administrator,, it may not be running when you try to delete it. It's a risky strategy though, so I suggest you rename it first to software.log.old then run the System File Checker to see if it creates a new file named software.log. If it does, you could then delete the log.old version.

Another possibility in Safe Mode as Admin would be to edit that file if you're allowed to, and simply remove the offending line.

Personally, I would let it. It is only a plain text log and can't run anything from there. Avast is obliged to flag it up but I think you're stuck with it.