FortiClient (Windows) reports off-fabric status when policy does not include on-fabric detection rules.

FortiClient gets stuck as registered to EMS but in an unreachable state.

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

No FortiClient IPsec VPN information in Security Fabric logical topology.

Bitlocker Zero Trust tagging rule does not match on endpoint with USB drive attached.

FortiClient must properly handle trying to register to FortiClient Cloud with invitation code with errors.

FortiClient (Windows) shows incorrect connection details.

FortiClient (Windows) fails to register to EMS if registration key contains special character.

EMS shows incorrect user information in endpoint summary when Google/LinkedIn option is selected in FortiClient (Windows) About page.

ISDB_map and ISDB_app signatures should be visible on About page.

@ displays in GUI as %40.

FortiClient can open attached file before receiving Sandbox result for the attachment.

Machines cannot connect to FortiSandbox Cloud with port 514 open.

Antivirus AMSI feature crashes Visual Studio project.

Blocked exploit attempts shows as 0 when antiexploit events have been triggered.

Protected files may already have been encrypted and failed to be restored when FortiClient detects and suspends the suspicious process.

Antiransomware fails to work after timeout.

Antiransomware has popup and logging issues.

Realtime protection on Citrix VDA server blocks remote sessions.

fmon.exe locks with writers some files stored in excluded folders.

FortiClient (Windows) fails to establish SAML VPN connection if FortiOS SSL setting Require Client Certificate is enabled.

SAML login does not work for IPv6.

SSL VPN TLS 1.3 does not work.

With per-app VPN split tunnel, websites with HTTP defined in <fqdn> do not work properly.

FortiClient registers all interfaces' IP addresses to the DNS server when IPsec VPN tunnel is up.

FortiClient (Windows) cannot connect to VPN when push tokens are enabled and certificate is untrusted.

FortiClient (Windows) cannot connect to IPsec VPN if password is saved and certificate required.

FortiClient (Windows) does not automatically restore DNS settings after closing VPN tunnel.

Restarting Windows does not remove SSL VPN tunnel established by VPN before logon.

Application-based split tunnel does not send traffic outside tunnel.

When system level proxy is enabled and certificate is in local machine, SSL VPN fails to work and gets stuck during connection.

IPsec VPN IKEv2 and always-up do not work reliably.

Vulnerability scan cannot patch Firefox: Error connecting to patch website. Please try again later.

Vulnerability patch status does not change from scheduled to failed if FortiClient cannot autopatch it.

Vulnerability scan reports excluded applications.

Feature list for log settings are inconsistent between EMS and FortiClient (Windows).

FortiClient fails to upload large diagnostic tool result file to EMS.

Antiransomware event that FortiClient (Windows) sends to FortiAnalyzer has only vague Found suspicious process message.

FortiClient clients do not generate endpoint control log for FortiAnalyzer.

FortiClient (Windows) does not send diagnostic result to EMS.