Immunization NOT complete - Global (Hosts) 15492 not protected
Hello!
Using SPYBOT for many years ... now with Windows 8.1 and SPYBOT 2.3.
Each week reveals some number of unprotected items.
This weeks result is:
Global (Hosts) (C:|Windows\System32\drivers\etc\hosts.) 15492 not protected.
What is my exposure with these not protected?
Is there a way to have them protected?
Thanks very much!
I get 57, unlike his where he seems not to have immunization at all.
As I said, in the global hosts file I get that 57 are still unprotected.
However between AVG, Malwarebytes and what Firefox has and from what I understand of the FAQ,
I needn't worry, because often Firefox or AVG or Adblock Plus or NoScript will warn me away from a bad site.
Does that sound correct?
For no matter how often I re-immunize, the same results happen.
All it means that Spybot can't write to the hosts file for some reason because its being blocked?
http://i64.tinypic.com/2l5qo2.jpg
I used to be able to get around that, but ever since my heart attack I can't remember what I did before to get full
immunization. I've been a nerd since 1980 [but before that was more interested in motorcycles] still build my own
desktop machines, but it just bugs my ass that I can't remember what I did to solve it on the earlier machines.
As for the home built PVR, I really don't care, all a hacker would find are TV shows and some support files, those of
which are already backed up on removables standing by for a simple restore, if necessary.
Yes, I'm an old fart. :laugh:
i get a no entry path found message when i try to immunize
this has not appeared in the past.can anyone tell me what this is?also,i am new to posting.am i in the right place to post questions?
Immunization of etc\hosts Still A Problem
I saw this thread. and I know that it is old. But I did not see a "fix" in the existing thread. I am running Spybot 2.7 in Windows 7 Professional. Every time I do an Immunize, I get the message that etc\hosts "has nn hosts unprotected". I looked at the
C:\Windows\System32\drivers\etc
file, and a dir/od shows, at the end:
06/29/2016 08:41 AM 452,964 hosts.20190305-142135.backup
06/29/2016 08:41 AM 452,964 hosts.20190305-142532.backup
06/29/2016 08:41 AM 452,964 hosts.20190403-090308.backup
06/29/2016 08:41 AM 452,964 hosts
06/29/2016 08:41 AM 452,964 hosts.20160803-081230.backup
09/18/2016 10:52 AM 452,999 HOSTS1
04/03/2019 09:03 AM <DIR> .
04/03/2019 09:03 AM <DIR> ..
So, Spybot has taken the 06/29/2016 hosts file and copied it into a backup file. But a new hosts file has not been written. I looked at the
Immunization-Browsers.log
file, and I do not see the string "hosts" in that log file. So that log does not have any diagnostic information.
This thread has stated that Spybot probably does not have permissions to replace the etc\hosts file. When I look at the security permissions for that file, I see that SYSTEM, Administrators, and Users have full control. Everything is checked, except "Special Permissions". The "Advanced setting" show that SYSTEM and Administrator have full control, while User has only read and execute.
I know that the Spybot scan runs with admin privileges, as when I click "Scan" in the main Spybot window, I get a security pop-up window from Windows 7 asking my permission to run the scan. But the same thing does not occur when I click "Immunize", so the immunization process is running without elevated privileges. Is there a way for the Immunization process to be run with admin privileges? If not, is there a security risk if I give my User full control (instead of Read & execute)? From my many years in IT system administration, I believe that the lack of permissions is the problem; I doubt that another security program running is denying Spybot's access to the hosts file. And I get no pop-up from any other security product that Spybot's access has been denied. But I may be wrong, as I do not know a lot about the internals of Windows 7.