Xshell CPU will reach one hundred percent [5]

Hello, my computer is win10 1709 version, before using the xshell update win10 everything is normal, after the update win10, using Xshell1335 version at the same time open multiple sessions will become very slow, and the CPU will reach one hundred percent, is this a BUG Or is my system problem?How can I solve it?

Program Ver. : Xshell 5

I have the same issue

There seems to be some issues with Windows 10 Red stone 3. This problem is not unique to Xshell, but we are continuing to investigate.

For now, try using Xshell's single process mode by going to Tools -> Options -> Advanced tab -> 'Use single-process mode for better performance.'

Technical Support

Like us on Facebook
Follow us on Twitter
Visit our blog Blog

Thanks for your reply, Xshell works fine by using Xshell's single process mode, and I hope Xshell will get better and better

Hello.
I experience similar troubles. After upgrading to Windows 10 Fall Creators Update (version 1709), Xshell 5 started to consume more CPU resources and in some situations become unresponsive.
First I noticed that navigation in Midnight Commander using arrow keys become really slow, like a turn-based strategy (due to high CPU usage).
Then I noticed high CPU usage when the program starts (up to 20 sec, program window is not responding at this time) and when creating a new tab (up to 20 sec, program window is not responding at this time). The XshellCore.exe process consumpt up to 25% of the CPU time on each of above operations.
I have 4 cores.
I upgraded Xshell to version 6 Beta (Build 0065) - same problems.
When I turn on the "Use single-process mode..." option Xshell starts in up to 30 sec, XshellCore.exe consumpt up to 25%, but new tabs are created quickly. Midnight Commander navigation also very slow or even more slowly.

I just wanted to add that I too am having the problem with Xshell after the creator's (1709) update for Windows 10.

I did set it to use a single processor for now and that helps once the application is open, however opening the application is still taking an excruciatingly long time.

I will leave it open on my desktop to minimize the time but when I am in the field, I cannot always do that so I look forward to a resolution!