- This topic has 7 replies, 3 voices, and was last updated 2 weeks, 4 days ago by
.
-
Posts
-
Hi!
After resetting Windows 11 and then reinstalling NoMachine, nxserver no longer starts automatically or manually.
I saved the logs. Can you help me please ?
Thanks a lotCan you send us the logs from the Windows 11 machine? Zip up the entire .nx folder and submit to forum[at]nomachine[dot]com. Include the link to your topic. Thanks!
Hello
please bit more details about “After resetting Windows 11”. What did you exactly? Did you restart?
Additionally:
1. check whether after installing nomachine and restarting, the file C:\Windows\System32\nxlsa.dll is present in system.
2. open power shell as admin and run command
get-childitem “\\.\pipe\”
and provide lines containing nx* pattern. like: nxdevice, nxfsd, nxserver, nxsspi.
3. As administrator in power shell window try the next commands
net stop nxservice
net start nxservice
then check if in C:/ProgramData/NoMachine/var/logs an nxtrace.log appears.
Check windows Event Viewer and in section “Windows Logs” check (Application, System) and provide error/warning events generated by nxservice, nxserver, nxnode if they are present.
Inside Event Viewer check section “Applications and Services Logs > Microsoft > Windows > LSA” if it contains some events,
If yes, send content to us.Remember that some event viewer data might contain sensitive data and so please avoid sharing to public here. You can redact the file by removing sensitive data.
Thanks
Hello Practice,
Please also provide us the Windows build version: open the power shell and run the command
winver
It would be useful for us to have a screenshot of the appearing window (but with your private data censored).Regarding the logs, we notice that you try to install NoMachine on the D:\ disk space, instead of the default C:\Program Files.
Have you tested to install on the default path to compare the result?
And is the D: space a real local disk partition, or some network drive mounted with some service?
This is also something I’ve been thinking about in the meantime !
I indeed reinstalled on disk c: yesterday and it works now. I waited a bit before posting my response.
The disk D: is a partiton of local disk…
I’m surprised because on another PC it works perfectly on disk D:
This may be linked to disk management by the motherboard perhaps….Thank you very much for your support and for taking the time !
You must be logged in to reply to this topic.