Forum / NoMachine for Linux / Remote disks unavailable after 9.4.14 update
- This topic has 6 replies, 4 voices, and was last updated 20 hours, 5 minutes ago by
jakdud1.
-
AuthorPosts
-
April 23, 2026 at 02:41 #55912
funky99ParticipantHello,
I’m running the NoMachine Enterprise Client on the latest version of Windows 11, connecting to a Mint 21.3 VM running the free version of NoMachine. After upgrading both the client and server to 9.4.14, I can no longer see the remote Linux disks after connecting, and the local Windows disks can take up to a minute to appear after establishing the NoMachine connection.
I uninstalled the enterprise client and reinstalled the 9.3.7 version, and after removing the old connection to my Mint VM and creating a new one, the remote disk functionality worked as expected. I tried updating the client to 9.4.14 again and this worked initially, but after rebooting my Windows machine it stopped working again. Uninstalling and reinstalling the client from scratch and recreating the connection had the same issue.
I’m now back on the 9.3.7 version of the Enterprise Client, connecting to the 9.4.14 version of the server, and all is working properly. It seems something is wrong with the latest Enterprise Client in this scenario.
Thank you for your time!
May 21, 2026 at 18:25 #56028
BritgirlKeymasterHi, could you try the latest 9.5 and tell us if you still encounter the issue?
https://kb.nomachine.com/TR03X11769 – this TR was solved in the latest update.
May 25, 2026 at 08:30 #56048
SoftwareSamuraiParticipantI’m seeing the same problem too.
Client: Win11 25H2 running NoMachine v9.5.7
Server: Ubuntu 24.04 running NoMachine v9.5.7I’ll connect from my Win11 to the Ubuntu PC and everything appears to work just fine.
I go to the control page (Ctrl + Alt + 0) > Devices > Connect a disk > Remote disks “/” > Enter a folder name, check “Private”, click Connect. It just sits there with a little moving spinner next to the disk and never connects.
Oddly, I do see the folder on my Win11 desktop. (It’s empty.)May 30, 2026 at 20:30 #56095
SoftwareSamuraiParticipantFollow up: I just installed v9.6.3 on both machines. I’m still seeing the same results.
June 3, 2026 at 07:43 #56114
jakdud1ParticipantHi,
We’ve tried to reproduce the issue on our machines, but without success. Could you please send us the logs from both the client and server sides of the connection?
You can find detailed instructions on how to gather them here:
https://kb.nomachine.com/DT08U00298.
Please ensure the log level is set to 9 in the UI.Once gathered, please send them to forum[at]nomachine[dot]com, making sure to use the forum topic title as the subject of the email.
Also, did you perform a fresh installation of v9.6.3, or did you update v9.5.7?
Kind regards,
JakubJune 3, 2026 at 20:40 #56118
SoftwareSamuraiParticipantI have sent the logs.
Also, to answer the question in the thread: I did an update on both machines via the Main window > Settings > Updates > Check Now. On my Ubuntu PC, I did a reboot. But on my Win11 PC, did not.
June 10, 2026 at 12:59 #56156
jakdud1ParticipantThank you for the logs. I’ve checked them but I couldn’t find any entries related to this issue. For further investigation, could you please run the following command on Windows machine?
C:\ProgramFiles\NoMachine\bin\nxservice64.exe --status all(Use a different path if NoMachine was installed elsewhere, and nxservice32.exe if this is a 32-bit system.)
Please check the status assigned to nxdisk and let us know the result. If the status is shown as “Mark for deletion” or “Not running”, could you please uninstall the NoMachine appliation and then reinstall it using the latest installer?
We suspect that something may have gone wrong during the update process, causing the nxdisk module to malfunction.
Kind regards,
Jakub -
AuthorPosts
You must be logged in to reply to this topic. Please login here.
