Cannot update Spybot Hosts file

gnetblast

New member
I have undated 1.4 and I am using Window XP
I tried to add new hosts this morning. It looked like spybot was actice adding new sites but when Spybot finished I got this error message:
"Cannot create file
"c:\Windows\system32\drivers\hosts"
Access Denied!"

This has never happen before. I am MacAfee AV only with Zone Alarm fire wall No proxy.

Does anyone at Spybot have a suggestion for me to fix this bug.

PS:
HOSTs is located at "c:\Windows\system32\drivers\hosts" I donnot know why Winsdow will not update and I get the same error message when I tried Spybot remove hosts. Thanks Spybot but I could not find answer in my searching data base here.
 
Hosts in wrong place?

My Hosts are all grouped in
"C:\Windows\system32\drivers\etc\hosts(55kb)" there is a bunch of them but 'HOSTS' is one of them lots of backup with names like:
"hosts_20050619-110039 backup" 1kb
Sorry for misinformation on file name where Hosts located

Now what do I do about correcting?
 
You can lock the hosts file with Zone Alarm.

I found a bug with the latest release of ZA Free v 6.5.700.000 locking the hosts file even though it it is unselected. I think locking the hosts file is a new feature of ZA. It can be accessed by opening ZoneAlarm > Firewall > Advanced.
from: http://forum.zonelabs.org/zonelabs/board/message?board.id=security&message.id=15537

There's a post about a bug with Zone Alarm locking the hosts file here:
http://forums.spybot.info/showthread.php?p=29004
this one,in particular:
http://forums.spybot.info/showpost.php?p=28933&postcount=7
And here:
http://forum.zonelabs.org/zonelabs/board/message?board.id=security&message.id=15537
 
Last edited:
I forgot :blush:

Spybot does create backups of the hosts file,named as yours are.
"hosts_20050619-110039 backup"

Your hosts file would be named just hosts,with no extension.
 
Last edited:
Zone Alarm is free version not advanced

Thanks I checked and my ZA does not have hosts checker
but it does have 127.0.0.1 loopback adapter in internet zone as trusted

The file name that Spybot is trying to create to place new HOSTS is not where that file is on my computer
it should be drivers\etc\hosts I think????????? rather than
drivers\hosts
The spybots hosts file is there where windows put it with not extension like you said Zenobia, Thanks for your info.
 
Yes,I'm sorry,I missed seeing that,in your post.

it should be drivers\etc\hosts I think????????? rather than
drivers\hosts

Yes,that's correct.I will see if anyone else has any ideas.

edit:Hi,md.Did not see you there.Was going to ask what you thought,you must be psychic.Thank you. :)
 
Last edited:
Further explanation:

For people who have downloaded and installed either of the following:
  • ZoneAlarm 6.5.700.000
  • ZoneAlarm 6.5.714.000
It appears that even if you go into ZoneAlarm Control Center > Firewall (left pane) > Main (tab in the right pane) > Advanced (button at the bottom) > and find "Lock hosts file" uncheck it appears that you must take action to unlock the HOSTS file.

Action required:
  • Check "Lock hosts file".
  • Click OK.
  • Click Advanced (button at the bottom).
  • Uncheck "Lock hosts file".
  • Click OK.
  • Back out of ZoneAlarm Control Center.
In other words; in the aforementioned versions of ZoneAlarm the HOSTS file seems to be locked in spite of the fact "Lock hosts file" is uncheck. You must cycle "Lock hosts file" on and then off to actually unlock the HOSTS file.
 
It looks like ZA locking hosts at startup

md usa spybot fan
Thanks but this is a temporary fix I hope Registry Fix is coming from ZA update or one of you who know their way around windows XP registry
I may fix a tweak for this in goggle maybe. Thank you all at least I can move on to MVP HOSTS file later on when this little bug with ZA is fixed.
 
gnetblast said:
md usa spybot fan
Thanks but this is a temporary fix I hope Registry Fix is coming from ZA update or one of you who know their way around windows XP registry
I may fix a tweak for this in goggle maybe. Thank you all at least I can move on to MVP HOSTS file later on when this little bug with ZA is fixed.
Is far as I can determine a "... Registry Fix ..." or other external circumvention would not fix that problem. I believe that ZoneAlarm actually opens the HOSTS file as if it was going to update it so that no other programs can access it. If that is in fact the cast the only thing that will fix the problem is for ZoneAlarm to fix their program.

The only way that will happen is if everyone experiencing the problem repetitively posts in the Zone Labs User Forum until the problem is fixed. Please consider posting in the following forum:
 
Good news,

The problem has been solved in the new ZA free version 6.5.731.000

The red hot topic helped in their forums.....:bigthumb:

enoskype
 
re:ZoneAlarm Release 6.5.731.000.

Unfortunately as of this time ZoneAlarm's release history page still lists 6.5.722.000 as the latest release:
The latest ZoneAlarm release is 6.5.722.000
So the download of 6.5.731.000 is not available there.

It appears that the 6.5.731.000 release is only available from what is listed as the FREE ZoneAlarm version here:
 
Back
Top