Running NoMachine at the next startup

[x8009]

Hi,

There is a bug when closing the tray icon.  It asks if I would like it to run on the next startup choosing YES, as soon after it closes it, it restarts the NoMachine program on the same Windows session without restarting the Windows.  Am I not understanding the question it asks or it’s a bug because the next startup means when I restart Windows, not after closing the program tray icon, right?

When I tell it ‘No’ it doesn’t restart the program on the same Windows session. It closes it and all services running.

Now it would be great if it just closes the program and restarts the services automatically like standard software.  and when I open, it would restart the service automatically, instead me manually start it after selecting ‘No’ on the answer selection

Attachments:

1. 

   3232323.jpg
   

[Britgirl]

Hi, the correct behaviour is:

Click Yes if you want to close the NoMachine app, and upon the next Windows session, everything will be started up again.

Click No if you want to close the NX services and at next reboot, you prefer to restart NoMachine manually.

So you have understood correctly it would seem 🙂 However, selecting either requires Administrator rights and the system will ask you to enter your Windows account credentials. Do you not see the box asking you to enter admin credentials?

Please tell us the Windows version you are using. This will be useful to be able to investigate whether services are being restarted within the same session rather than at start-up.

[x8009]

Hi,

It does ask me for administrative credentials.

I am using Windows 10 x64 1903 175 build.

 

[Mth]

Hello.

next startup choosing YES, as soon after it closes it, it restarts the NoMachine program on the same Windows session without restarting the Windows.

This is indeed not the expected behavior. Could you provide more information?

Please tell us if it is a fresh installation or an update from an older version?
Is anything in the system logs concerning nxservice system service?

We will probably need to see the logs to know why is it happening. Please collect
logs from server (whole log directory) and client –monitor. This would be points 2.3 and 1.4 from article.
I don’t know if it can be reproduced, but just in case, please try doing everything from point 1.4
(steps 1-5)

Article on how to collect logs:

https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)

After gathering logs, please send them to forum[at]nomachine[dot]com using the title of that forum’s
thread as the mail’s subject.

/Mth

[Author]

Posts