After update to Windows 10 CU (1703) "No available session on server"

[TeutonJon78]

I recently updated all my computers I support to the Windows 10 CU.

After performing the install, I’m no longer able to use NoMachine on several of them reliably. I can still connect to the computer reliability, but it will often show “No available session on the server”. The server itself sometimes doesn’t start automatically either. It does work sometimes, after restarting the server.

Anyone else seen this problem?

All affected computers are W10 Home with intel GPU. All are running NoMachine 5.2.11.

[brotech]

Hello TeutonJon78.
We are trying to reproduce problem which you described. In the meanwhile could you enable logs in server and node configurations file, then restart Windows, and after a while compress var/log directory and send to us ?

The guide how to collect logs on windows is available here:
https://www.nomachine.com/DT07M00098

Please send them to forum[at]nomachine[dot]com with
“After update to Windows 10 CU (1703) “No available session on server” as a title of the mail.

Thank You

[cloudland]

I saw something similar on 15 machines I updated with CU and NoMachine 5.2.11 quit working except on one that was Win 10 Home–all the rest were Win 10 Pro and quit working NoMachine.  I believe is has to do with the LAS service.  All were running Panda AV free before and after CU update. I believe NoMachine needs to update the App for CU.

[TeutonJon78]

Logs just sent.

[eleshar]

Experiencing the same issue reported by TeutonJon78 after upgrading to Windows 10 Creators Update. Additionally the tray icon is missing although it is enabled in the settings to display. I’ve attempted reinstalling but no luck yet.

[thomasflad]

Same problem here

[Britgirl]

Hi everyone, just to let you know we are working on a fix. It’ll be released as soon as possible.

[TeutonJon78]

I just downloaded and tested 5.2.21 and it worked correctly on both computers that were having issues. Thanks for the quick fix.

[cloudland]

I installed 5.2.2.1 on 20 machines with the Creators Update and it fixed them all–thanks.

[Author]

Posts