To stay updated on your favorite discussions, please create an account or log in. Then, click the Bookmark icon to subscribe and receive notifications.

Virus definitions not updating after upgrading from CSPr11 to CSP 11.5

hyvokar W/ Alumni Posts: 165 Junior Protector



Yesterday I upgraded my test environment from Client Security Premium 11 to 11.5. It all went smoothly, and I pushed the the updates also to production environment. After a while I noticed that not a single 11.5 client had it's virus definitions updated. I immediatly pulled the update out from production, but unfortunately, it had already installed on several computers.


The update process goes smoothly as always, and f-secure status window shows green "your computer is protected". After a while it turns to red. Manually cheking the updates says "update check was succesfull". "your product is already up to date".


If I go to settings -> other settings -> automatic updates, it says that virus definitions have never been updated. Also the policy manager says that virus definition are out dated ; 2008-03-24_01. The old (version 11) clients have their virus definitions updated as they should.


I already opened a support ticket, but hoping to get a faster reply from here.


  • Ben
    Ben W/ Alumni Posts: 664 Cybercrime Crusader

    Hello Hyvokar,


    Thank you for sharing the solution, and the follow up on your issue.


    It is indeed good to note that Policy Manager 11.10 (or PM 10.30 for Linux) is mandatory to manage Client Security in version 11.50 as well as for our Server solutions versions10.50.


    This information can be found in the documentation for each product.


  • Martin
    Martin W/ Alumni Posts: 6 Security Scout

    I'm running fspm 11.10.49586 but still have a few percent of users running into the problem when upgrading from fsav9/10 to fscs pr 11.5. It happens on all client OS. I've filed a report and am waiting for reply.



  • Vad
    Vad W/ Alumni Posts: 1,069 Cybercrime Crusader

    Hello Martin,


    Probably you have the same issue as discussed in this thread:

    It's still under investigation. Reinstallation of the product is the only workaround for now.


    Best regards,


This discussion has been closed.