FS Protection PC Release 214

Fengping
Fengping Posts: 66 Former F-Secure Employee
in Home Security Beta Programs

New Features:

Common:

  • Improved product event history.

Removed features:

Common:

  • Internet Explorer 10 is no longer supported.

Fixed issues:

Common:

  • Flyers do not work after upgrade in win10 (PBL-3386)
  • Installation fails with some languages (SAFE_BUG-02289, PBL-3372)
  • About dialog content formatting (SAFE-BUG-02285, PBL-3353)
  • Upgrade event does not have link (PBL-3365)
  • Windows 10 toasts show "F-Secure OneClient" instead of "fs protection" (PBL-3389)
  • Event history details as not aligned properly (PBL-3398)
  • Upgrade event parameters are in wrong order (SAFE_BUG-02321, PBL-3406)

Antivirus:

  • Unicode bidirectional characters problem in targets list of scan report (SAFE_BUG-02326, PBL-3395)
  • Inappropriate and misleading messages when security features turned off (PBL-3342)

Browsing Protection:

  • Browsing protection breaks google adwords (PBL-3367)

  • Time limits: remaining time limits doubles after extension (PBL-3361)

  • Three rating icons in Bing search results (PBL-3378, SAFE_BUG-02294)

Ukkoyeoldfartmaaretp
3Like Awesome

Comments

  • Simon
    Simon Posts: 2,665 Superuser

    Cool, thanks.

     

    I had a pop-up the other day, asking me to agree to the terms and conditions again.  Is this normal?

    Like Awesome
  • Fengping
    Fengping Posts: 66 Former F-Secure Employee

    Yes. EU law requires that if we updated the user license agreement.

    Like Awesome
  • Ukko
    Ukko Posts: 3,556 Superuser

    Hello,

     

    Thanks for release!

    Just as my own feedback: system (Windows 10) with 'invisible' toasts with TP213 -> start be with visible toasts with TP214.

     

    Thanks!

    Like Awesome
  • yeoldfart
    yeoldfart Posts: 556 Superuser
    not a glitch, congrats
    Fengping
    1Like Awesome
  • Lord_Ami
    Lord_Ami Posts: 70 Active Engager

    Both this and 213 upgrades went fine.

     

    However, I dislike the change that DeepGuard detections can not be allowed in Event history.

    DeepGuard detections do not show up in Event history.

    Ukko
    1Like Awesome
  • Ukko
    Ukko Posts: 3,556 Superuser
    @Lord_Ami wrote:

    Both this and 213 upgrades went fine.

     

    However, I dislike the change that DeepGuard detections can not be allowed in Event history.

    DeepGuard detections do not show up in Event history.

    Hello,

     

    I do suspect (or expect) that redesign still is not completed. Otherwise - I do able to think about some more potential 'strange' changes (inabilities with current design).

     

    Thanks!

    Like Awesome
  • Fengping
    Fengping Posts: 66 Former F-Secure Employee

    Yes, we did some changes on event history and currently we are working on bug fixing on that area.

    Like Awesome
This discussion has been closed.

Categories