so wat do u think about spybot? mao ni ako gigamit karon
so wat do u think about spybot? mao ni ako gigamit karon
spybot is also a good tool for removing viruses,
gamita lang nang duha bro,
unaha lang ang combofix kay dali raman na cya mahuman, observe dayon sa imong system after nimo padaganan...
pasundi dayon sa spybot kay medyo dugay manang spybot gud...
im using spybot and symantec av. payts na tingali ni silang duha. dli ba muhinay if dugangan pa ug combofix?
Bro ang combofix on demand rana sya meaning run only once you open the application, and after cleaning it will close, unlike anang mga spybot, symantic, etc. memory resident na sila, they are waiting or it will detect if naa spyware or virus mo sulod coming from the internet or any devices nga imong gi plug like USB, HD, CD's, etc.
Bro but to much antivirus or antispyware softwares mag kamang dyud pc nimo, but it depends on your pc specs, pero much better if gamay ra dyud nag dagan for memory resident programs and other process.
Hello there,
Recently found the msln.exe in my system32 directory and got to wondering what was it for. This page shows up high in the google rankings when searching for msln.exe and got me headed in the right direction, so thought I'd share back what I figured out about this.
The authentic msln.exe is a part of Symantec's antivirus product, in my case Symantec Endpoint Protection 11 mr4. Viewing properties of msln.exe, on the version tab it shows Symantec info and opening the file in notepad shows references to verisign (for code signing purposes). This convinced me the file was authentic.
The reference in the registry, bootexecute key, says that on reboot, in that brief period between showing the big XP logo and actually cranking up the graphical interface for Windows, run this program. (Chkdsk is typically started in the same fashion.) Symantec uses the msln.exe to delete infected/bad files before they are loaded into system memory of Windows proper and become protected by being in use.
The error you're getting is because msln.exe is being called by the autochk line specified in the bootexecute key, but (for whatever reason) there is no corresponding msln.exe file in your system32 directory.
Similar Threads |
|