1. #1

    Antivirus False Positive?

    I've started pre-loading the beta and my antivirus has reported the following:

    HTML Code:
    Feature:Antivirus
    
    The file o:\trials rising - closed beta\uplay_download\5233\support\software\extra\firewall.exe is infected with Gen:Variant.Ursu.282276 and was moved to quarantine. It is recommended that you run a System Scan to make sure your system is clean.
     4 people found this helpful
    Share this post

  2. #2

    trials antivirus alert

    I get the same on bitdefender 2018...

    Feature:
    Antivirus

    The file c:\program files (x86)\ubisoft\ubisoft game launcher\games\trials rising - closed beta\uplay_download\5233\support\software\extra\fi rewall.exe is infected with Gen:Variant.Ursu.282276 and was moved to quarantine. It is recommended that you run a System Scan to make sure your system is clean.
     2 people found this helpful
    Share this post

  3. #3
    Exact same issue as SonicFRAG: Bitdefender Internet Security 2018 is triggered by the same file (trials rising - closed beta\uplay_download\5233\support\software\extra\fi rewall.exe) on my Windows 10 machine during pre-loading.
    Share this post

  4. #4
    Ubi-Redbeard's Avatar Ubisoft Support Staff
    Join Date
    Mar 2017
    Posts
    7,279
    Hey folks,

    Are you still experiencing this issue?

    If you are, please try temporarily disabling your anti virus.
    Share this post

  5. #5
    VassyP's Avatar Junior Member
    Join Date
    Mar 2014
    Posts
    17
    Same here. This game is not even in tehnical alpha. No 1080p resolution, graphical settings not getting saved, i have an extreme bloom effect (the game is unplayble), if i chose custom graphic settings i cant even adjust the settings by myself, even if i selected custom. Rlly, you are not able to make basic functions to work, and you call it a beta. lul
    Share this post

  6. #6
    UbiGabrinth's Avatar Ubisoft Support Staff
    Join Date
    Mar 2017
    Posts
    6,366
    We are aware of those issues, and we have released a post with known workarounds.
    Share this post