I have the same event logged on a hyper-v guest running Windows Server
2016 and FortiClient 5.4.2. I tried to repair FortiClient installation,
but that didn't help. Does anyone have some input?
You are leaving our website
You are leaving our site and we cannot be held responsible for the content of external websites