The device driver cannot be loaded (code 38).

Upgrade from 6.4.2 fails.

Clicking Unlock Settings does not enable Clear Logs button in settings page.

Google social network login does not work properly.

Wrong password dialog is missing when connecting via SSL VPN.

FortiClient (Windows) saves encrypted password incorrectly when user uses Spanish characters and FortiClient (Windows) is configured to save username and password.

User cannot launch FortiClient (Windows) from SSL VPN web portal.

For SSL VPN dual stack, GUI only shows IPv4 address.

FortiClient reports corporate EMS as unreachable when SSL VPN is connected.

Disable context menu in antivirus (AV) scan dialog when FortiClient is connected to EMS.

GUI does not refresh after disabling Hide User Information in EMS profile.

SSL VPN password is blank with FortiToken.

Entire console should not launch during ZTNA TCP forward proxy authentication.

FortiClient (Windows) should remove browser-based ZTNA settings.

FortiClient (Windows) reaches Unable to retrieve EMS Details state after user cancels connection key popup.

FortiClient does not calculate Active Directory group-based policy rule for tags.

After FortiClient (Windows) migrates to new EMS successfully, it does not remove original EMS from EMS list.

Switching AD users does not modify user details in EMS Endpoints table.

FortiGate waits about one minute to get ZTNA EMS tag update.

CLI parameter to register FortiClient to EMS with Telemetry key.

Migrating FortiClient to different server fails when connection key is enabled.

FortiClient does not register to EMS after silent installation.

When connected to a full VPN to FortiGate, FortiClient sends virtual IP and MAC addresses to EMS.

EMS does not apply the tag for file type even though file exists on endpoint.

FortiClient stays in registration progress to FortiClient Cloud and never returns connection result.

Zero Trust tag rule does not work properly for AD-joined devices when endpoints connect to EMS via SSL VPN.

FortiClient uses FortiSASE SIA egress IP address as the public IP address.

FortiClient registry is missing key encryption when EMS-pushed rules enable encryption.

FortiClient (Windows) does not detect AV is not up-to-date tagging rule result properly.

Antiransomware fails to detect some popular ransomware samples.

realtime_scan log disappears after ten seconds.

Ransomware protection rollback for Magniber.

Exceptions do not work for AntiExploit.

FortiClient (Windows) flags bin_x64\FctRtMonitor.exe as Win32/AI.Pallas.Suspicious.

FortiClient (Windows) sends browser cache files to FortiSandbox and user cannot exclude them while browsing pages with FortiClient (Windows) installed.

FortiClient quick scan cannot detect the av_custom_malware.exe file.

Compatibility with USB key.

User cannot look up file hash in antiransomware events.

FortiClient cannot quarantine file with Ukrainian characters.

FortiClient (Windows) blocks Veeam backups.

FortiClient does not respect exclusions if it detects malicious file as riskware.

Certificate-only SSL VPN tunnel displays Empty username is not allowed error.

IPsec/SSL VPN per-app VPN split tunnel does not work properly.

SAML authentication on SSL VPN with realms does not work.

FortiClient does not use fallback server IP address when Show VPN before Logon option is set.

User can update SSL VPN user password without entering the same password to confirm the new password.

IPsec VPN fails to autoconnect with Failed to launch IPsec service error.

SSL VPN with SAML (Azure AD) and two gateways does not work.

Per-user autoconnect starts to autoconnect before Windows logon.

Per-user autoconnect does not get established, and per-machine autoconnect still remains connected after Windows logon.

SAML connection stays in connecting state and never returns with error when FortiGate gateway is inaccessible.

MTU issues when DTLS is enabled and client network tunnels IPv4 over IPv6.

VPN disclaimer message present in EMS profile is not present on endpoints and endpoints show no disclaimer.

FortiSASE SIA VPN failed to reestablish after FortiSASE SIA-related components were upgraded.

After powering on/rebooting Windows, FortiClient (Windows) cannot establish SSL VPN tunnel for approx two minutes due to host check failure.

Per-application split tunnel does not work for FortiSASE SIA SSL VPN. FortiClient cannot exempt the Trusted FQDNs effectively from FortiSASE SIA VPN.

VPN client takes 20 seconds to disconnect.

FortiClient appears disconnected when trying to connect to SSL VPN.

FortiClient must dynamically update Windows hostnames in DNS AD-integrated database.

SSL VPN negate split tunnel IPv6 address does not work on FortiClient (Windows).

Negate split tunnel IPv4 address does not work for dual stack mode using IPv6 access.

FortiSASE SIA trusted traffic feature (split tunnel) requires restarting FortiClient (Windows) SSL VPN connection to take effect.

Without EAP enabled, certificate-based IKEv2 does not work.

FortiClient is stuck at 98% connecting to SSL VPN tunnel when integrated with SAML (Azure AD) authentication.

SSL VPN SAML login displays Empty username is not allowed. error.

SSL VPN redundant_sort_method does not work with realms.

When per-machine autoconnect before OS start is enabled, FortiClient (Windows) keeps trying to connect after failing to connect to VPN.

For per-machine autoconnect, certificate dropdown lists certificates in current user store before Windows logon.

IPsec VPN sends unexpected xAuth authentication attempt.

Web Filter conflicts with third-party VPN client.

FortiProxy fails to start.

Web Filter blocks some WebEx communication due to unrated IP address.

Web Filter affects Manufacturing Execution System software.

Web rating overrides behavior between FortiClient Web Filter and FortiGate Web Filter differs.