Jump to content

Recommended Posts

Dude, that's the official BF download.....I'd turn AVAST off, download the patch, install it, repeat this for any further patches, then Turn AVAST on and tell it not to look in the directory where CM:SF is installed, ever. 

This just my personal opinion, but I'm about to do exactly this with both Webroot and MSE to allow me to reinstall CM:FI, which MSE had kindly deleted for me.

Edited by Sgt.Squarehead
Link to post
Share on other sites

A false positive. I'm not sure what it may be in the patches that would trigger an 'adware' issue with Avast.

As 'Sgt. Squarehead' mentions, disable Avast temporarily while downloading and installing the patch. When you re-enable Avast, whitelist the game directory and possibly the patch directory (so it doesn't get quarantined in the future). Avast is usually good about false positives, but I have seen A LOT of the Battlefront patches and installers get tagged as being infected with Adware or something to that effect (and they're not, especially the downloads from the official Battlefront servers).

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...