issues with fortiauthenticator agent for windows

[TiborH]

Hi all,

We are slowly moving to password-less based login for our users. We have already piloted YubiKeys as our primary method of authentication. As a failsafe we are now testing also FortiAuthenticatior agent for windows since we already have it on-premises. The login with PIN and Token works fine without any issues. What is happening is, that from time to time (once, twice, multiple times per day, or maybe not even happening) login screen starts behaving erratically not displaying login screen at all. In the event logs I can see, that it was caused by crashed LoginUI.exe and Fac_AgentCredentialProvider.dll and ucrtbase.dll.

Here is the log:

Faulting application name: FAC_Agent.Service.ServiceHost.exe, version: 6.0.0.0, time stamp: 0x66dba094
Faulting module name: ntdll.dll, version: 10.0.19041.5007, time stamp: 0x688f8c4b
Exception code: 0xc0000374
Fault offset: 0x00000000000ff3c9
Faulting process ID: 0x14d4
Faulting application start time: 0x01db40bfcd70a7ca
Faulting application path: C:\Program Files\Fortinet\FortiAuthenticator Agent\FAC_Agent.Service.ServiceHost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 134e501b-3500-4108-81de-fbf0720eeeeb
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: LogonUI.exe, version: 10.0.19041.1, time stamp: 0xc08a5452
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc00000fd
Fault offset: 0x000000000000be4d
Faulting process ID: 0x1b04
Faulting application start time: 0x01db40cbef608e6e
Faulting application path: C:\WINDOWS\system32\LogonUI.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 0b43b5f6-e483-4e2c-a945-04160a8578ae
Faulting package full name:
Faulting package-relative application ID:

Has anyone else encountered this issue? And if so, how did you manage to solve it?

Thank you very much for your answers and help.

Kind regards

[AEK]

Hi Tibor

Please provide Windows version (client), FAC version and FAC agent version.

[sjoshi]

Hi,

Can you confirm if FCT v7.0.13 is install on that PC.

Further share the snapshot of the reg from the PC facing the issue.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Fortinet\FAC_Agent_v1.0

[TiborH]

Hi,

Thanks for the replies:

@AEK We are running FAC 6.6.2, FAC Agent 6.0 on Windows 10 22H2 latest version

@sjoshi FCT stands for what? Here is the registry screen shot:

[AEK · Accepted solution]

Hi Tibor

As agent 6.0 is new and not patched yet, I'd recommend to try agent 5.3.

Hope it helps.

[TiborH]

Thanks, i will test

[sjoshi]

Hi TiborH,

FCT means forticlient. If forticlient v7.0.13 is install on the same PC. And is this reg snapshot taken during the issue time when the FAC agent login was not appearing?

[TiborH]

The solution was to downgrade to 5.3 version. Works without issues.

Thank you all

[sjoshi]

glad your issue has been resolved