Skip to main content
C
ConLa
New Member
May 4, 2026
Question

FortiClient VPN-only - configuration backup and restore broken

  • May 4, 2026
  • 1 reply
  • 103 views

Hello,

In the current version of FortiClient VPN-only, the backup and restore function is broken.

 

Although you can select a file and enter the password, nothing happens when you click “OK.”
Conversely, when restoring (a backup from before the upgrade), you can select the file, but even then nothing happens (and there's no mention of it in the logs either).

 

Configuration Backup

→ nothing happens when you klick OK (menu is closed but no file created)

 

The version numbers don't quite add up either (to me, it just looks like it was thrown together quickly and hasn't really been quality-checked):

Tray: 

Tray Version Info: 7.4.3.4726

GUI:

GUI Version Info: 7.4.3 hotfix 1.8758

 

1 reply

Toshi_Esumi
SuperUser
Toshi_Esumi
SuperUser
May 4, 2026

What was the previous version when saved the config?
By the way, they re-released 7.4.3.4726 in march, which includes the same fixes the hotfix version has.I recommend you uninstall it again and re-install a new 4726 then try uploading the saved config.

Toshi

    C
    ConLaAuthor
    New Member
    May 5, 2026

    It was a file from versions 7.4.3.8758 HotFix Release and 7.4.3.1790, None of them work.

    But that's not the point; if the version doesn't match, a warning or message—whatever—would appear, but nothing happens at all.
    The same thing happens when saving the config; here, too, nothing happens at all. That's a bug.

    Of course, the new version has already been installed (tested on two devices and a VM, with the same error occurring).

     

    And the problem has been occurring since the “new” version released from March (the digital signing date is Thursday, March 19, 2026, 5:45:26 PM)

     

    The same applies to right-clicking the tray icon; starting with this version, you can no longer select a connection directly from there either, even though that worked without any issues in previous versions. I’m not sure, though, whether this is intentional or a bug.…

     

    P.S.: The screenshots are also from the very latest (March) version.

    C
    ConLaAuthor
    New Member
    May 5, 2026

    So, we've been able to run several tests in the meantime. When updating from an older version (i.e., simply installing “over” it), these errors occur.

    Uninstalling the old version and then installing the latest version works fine (unfortunately, however, all data will be lost if a backup wasn't made in an earlier version).

    Support has now confirmed the bug as well.

    Terms & ConditionsAccessibility statement