@FLOOD First, thank you for detailed explanation. Second, I cannot now replicate this issue as after clearing cache everything works. Mind you I haven’t found issues with ff.ksk.v2.scr.kaspersky-labs.com after quick googling. There is a lot with ff.ksi.v2.scr.kaspersky-labs.com, but this is different server probably for Kaspersky Internet Security. I guess this issue appears when there are old addresses injected in cache files, but they are not used by new version of Kaspersky product anymore. I think they should provide something like transient period when both function simultaneously. Generally I think KSK is a little too rough around the edges for non IT users. Many people I know, that once used it, doesn’t anymore, because it stopped working for them at some point and they couldn’t figure how to fix it. Which is a shame because it is a nice product.
