Hosts File update glitch?

I just recently began seeing error messages in the place of a blocked ad, as depicted here in Yahoo mail ...

post-8751-0-10031200-1393623034_thumb.jpg

Quickly traced it to my Hosts File with a list of entries carrying 0.0.0.0 instead of 127.0.0.1.

All I can think of the reason for this is maybe a recent update to the Hosts file, as I simply can't think of anything else which would change the "127.0.0.1" to "0.0.0.0".

I do know that I had no 0.0.0.0 entries the last time I edited that file.

Used "Hostman's "Edit\Replace IP" menu to bulk change the long list of 0.0.0.0 entries to 127.0.0.1 ...

post-8751-0-97834400-1393623477_thumb.jpg

... and the blocked address error no longer shows.

This is all for info really in case anyone else running a Hosts file suddenly starts seeing blocked ADdress errors.

ADdress ... get it? :)

MVPS.org HOSTS file switched to using 0.0.0.0, something which Hazelnut pointed out to me when I started a topic about it. You'll just have to use your HOSTS manager software to switch them after each and every MVPS.org HOSTS File update.

Edit:

Actually I didn't start a topic about it, I posted it in the HOSTS file update topic here.

Thanks for that big man, I sadly missed that one.

My bad, but maybe some others missed it.

Important Note: The HOSTS file contains a change in the prefix in the HOSTS entries to "0.0.0.0" instead of the usual "127.0.0.1".

This was done to resolve a slowdown issue with the new Win8.1/IE11 and the HOSTS file.

that was straight off the winhelp2002.mvps.org site.

i guess if you use IE, leave them as 0.0.0.0 else find/replace to 127.0.0.1

HostsXpert has a one button fix under Editing, click Swap Localhost (twice)