- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Forticlient Prevents Sleep in Windows 10
My laptop will not sleep or hibernate with the "FortiClient Service Scheduler" windows service running. More specifically, the laptop starts to sleep and the screen goes dark, but the hardware never powers down. During normal operation on my Thinkpad, the power LEDs go from solid on (indicating the laptop is powered on) to a heartbeat or slow blink indicating sleep mode. It is this last step, the slow blink, that never happens with the FortiClient service enabled.
With the FortiClient Service Scheduler running, the power LED stays solid indicating the laptop (hardware) hasn't gone to sleep completely. Furthermore, it is not possible to wake the computer up from this state without powering the system down fully and subsequently rebooting. This sometimes results in a loss of work.
My current workaround is to start the FortiClient Service Scheduler only when I need to VPN into our data center and disable it otherwise. Note that once I've enabled the service, even if I don't log into the tunnel and whether or not I stop/disable the service, the aforementioned problem/behavior occurs.
Can someone tell me how to fix this?
I'm using FortiClient version 5.4.1.0840.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It appears this is not a new issue:
https://forum.fortinet.com/tm.aspx?m=58126
https://forum.fortinet.com/tm.aspx?m=142777
We're losing lots of productivity time to restarts. If anyone has solved this particular problem, please post your solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've had a similar problem. In my case the real problem was that system was generating a memory dump for seeeeeveral minutes with the screen in black so it was frozen apparently but it was generating the memory dump.
After analyzing the memorydump in c:\windows\system\ the root problem was related with WAN Miniports (xxxx) and indirectly with FA_Scheduler which seems to be the root cause of the problem.
In my case I disabled all WAN Miniports (XXXX) and restarted Windows... After the restart new WAN Miniports (XXXX) were reinstalled and sleep & hibernate worked again.
