Iv came from virgin media security but everytime I try to download f secure internet security 2013 it says internet explorer cannot display webpage
Is that from following this link?
Before trying to download again, I would make sure that you have completely removed the previous AntiVirus;
Have you followed the instructions to install F-Secure in this video? Heather does a good job here.
(But, as stated above, ignore the advice that says to allow the F-Secure Safe package to uninstall the previous Virgin Media Security/previous AV-use a specific uninstaller).
Have you tried a different browser?
Report back if you still have problems.
Please note that actively running malware often try to defend themselves against removel. If your computer is already infected, trying to visit any info-security themed websites may not be successful, because the virus had modified the IP-to-DNS table either in the Windows hosts file or in the process memory to block the web browser connection.
In such cases a standalone disinfection utility should be transferred to the victims computer via an USB stick or something like that. After the computer is cleaned, the regular Antivirus for Windows suite can be downloaded and installed.
Best Regards: Tamas Feher, Hungary.
As I mentioned in a post above, try connecting to the F-Secure site with an alternative browser (such as Firefox or Chrome) to see if the problem persists.
If it does, an issue with your Internet Service Provider, network setup or even as etomcat suggests, malware is more likely to be the cause rather than Internet Explorer itself.
1. Try an alternative browser first.
2. Download, install and run the free Malwarebytes and run a scan for malware; http://www.malwarebytes.org/products/malwarebytes_free/
You can run Malwarebytes on infected systems; https://helpdesk.malwarebytes.org/entries/20872371-Use-Chameleon-to-run-Malwarebytes-Anti-Malware-on-infected-systems
3. Remove remnants of previous Antivirus and then try installing F-Secure.
The reason for my original question was that the issue could simply be an incorrect URL, or perhaps the page was temporarily unavailable. Hopefully we will hear back from Chris with some more information.