Shutdown/Reboot error

[Zardoc]

Hi,

Here is a message that I’m often getting on my machine. I’m not sure what it implies but the service control manager error happens at every shutdown of the computer.

The other error, I can’t find the source.

Attachments:

[Cato]

Hello Zardoc,

We failed to reproduce the issue so far. What Windows and NoMachine versions are you using?

[Zardoc]

Hi 6.0.8.0

Windows 10 16299.334.

I suspect that the wait to kill command might react faster than software has time to shut down.
[HKEY_CURRENT_USER\Control Panel\Desktop]
“AutoEndTasks”=”1”
Default 0
“HungAppTimeout”=”5000”
Default 5000
“MenuShowDelay”=”0”
Default 400
“LowLevelHooksTimeout”=”5000”
Default 5000

[HKEY_USERS\S-1-5-19\Control Panel\Desktop]
“AutoEndTasks”=”1”
Default 0
“HungAppTimeout”=”2000”
Default 5000
“MenuShowDelay”=”0”
Default 400

[HKEY_USERS\S-1-5-20\Control Panel\Desktop]
“AutoEndTasks”=”1”
Default 0
“HungAppTimeout”=”2000”
Default 5000
“MenuShowDelay”=”0”
Default 400
“WaitToKillAppTimeout”=”5000”
Default 20000

[lis]

Did you install NoMachine before a Windows update took place?
Did you reinstall NoMachine after the Windows Update?

EDIT:
If you have not tried reinstalling nomachine, do it first.

Please make backups of your NoMachine configurations.

For example my Audio didnt work after the Windows aniversary Update. The last major Win 10 Update killed my Touchpad settings dialog.

Technical stuff:
UUIDS may have changed so the msvcrt service manager is not able to find all relations to NoMachine anymore.
Paths of dlls/drivers whatever may have changed and there are leftovers.
Try to run this from an elevated console (to check the windows folder for proper file layout, and if errors found download official files from ms):

1. DISM.exe /Online /Cleanup-image /Restorehealth
2. sfc /scannow

If there where errors found reinstall NoMachine and reboot.

Greetings, Louis

• This reply was modified 6 years, 7 months ago by Britgirl.
• This reply was modified 6 years, 7 months ago by Britgirl.
• This reply was modified 6 years, 7 months ago by lis. Reason: clarification

[Cato]

Hello Zardoc,

We failed to reproduce the issue with NoMachine Device Service shutdown timeout. However, the shutdown times of service are on average longer than 5 seconds. We will try to make them shorter in future. You can increase WaitToKillAppTimeout value and check if this helps.

To investigate further the problem with nxnode’s exception, we need to check the logs. Please, follow the instructions from:

https://www.nomachine.com/DT07M00098#3

and send logs to forum[at]nomachine[dot]com.

[Author]

Posts