Forum / General Discussions / Screen tearing and slow screen updates with Win10 to Win11 connection
- This topic has 5 replies, 2 voices, and was last updated 1 week, 4 days ago by
Britgirl.
-
AuthorPosts
-
May 31, 2026 at 15:18 #56096
lukyduckParticipantI have a connection problem between 2 Windows machines. In the past, this exact connection has worked fine and I have spent hours doing remote designs using Fusion360, as well as using other applications. Suddenly, the connection is very poor. I have updated NoMachine, so I am running the same version on both ends.
My Network – Local, I have a Windows 10 PRO Desktop and a Linux Ubuntu laptop. At the remote end, I have a Windows 11 desktop PC and a Linux desktop PC. Both Windows PCs are running the latest NoMachine version 9.6.3
When I connect to the remote Win11 PC from my local Win10 PC, the video is poor, screen tearing, very slow updates, and I can not even perform basic functions using my mouse. It is unusable
BUT – If I connect to a Linux PC (Ubuntu) at the remote location (same network as the Win11 PC), and THEN connect to the Win11 box through the remote Linux box, the connection is much better. So, it seems that I have this issue only when connecting to the remote Win11 PC directly from the local Win10 PC.
Any suggestions on where to look would be much appreciated. I can provide more details if that would help.
June 3, 2026 at 16:48 #56116
BritgirlKeymasterHow about if you connect from the Linux PC to the Windows 11 PC? Do you get the same issues? This would help us to understand if the issue is on the Win11 side or on the client side.
If it’s happening only when connecting from Win10, please try disabling HW decoding. You can do that within the session. Open the menu (Ctrl-Alt-0), go into Display > Change settings > Modify (Advanced settings) and tick the box Disable client side hardware decoding. Does that help?
If nothing changes, we need to logs from both sides. For client-side logs, simply open the menu again > Connection > Take logs. For the server side system you are connecting to, go to Settings > Server > Security > Take logs. Submit everything here or send to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
June 4, 2026 at 17:36 #56125
lukyduckParticipantThanks for your reply. I just connected from the LINUX PC to the WIN11 PC and it appears that connection is fine. These are on the same LAN (one wired and one wireless).
I will try the WIN10 to WIN11 connection again when I go back to the WIN10 location this weekend. I will try disabling hardware decoding and will try to gather logs from the two computers. I may try using a LINUX laptop to connect to the WIN11 PC, through the WIN10 PC. I would expect to have similar issues.
What really seems strange is that this exact connection used to work well. I spent many hours sitting at the WIN10 PC while connected to the WIN11 PC (up to about 2 months ago+/-). I do not know enough about NoMachine to have made any settings changes (knowingly). I always suspect Windows upgrades for causing strange problems.
June 7, 2026 at 01:31 #56132
lukyduckParticipantDisabling Client Side HW Decoding seems to have fixed the connection problem. This is just a quick look, and I will need to spend more time to verify this, but it looks good. Thanks very much for your help. Now, I want to understand this, and why it was not a problem in the past.
Tom
June 7, 2026 at 22:59 #56135
lukyduckParticipantI know that my replies are being delayed due to “moderation” cause I am a newbie here. I just want to thank BRITGIRL for the quick and accurate solution to my connection problem. I never would have gotten to the point of trying that setting without the help.
Despite this little hiccup, I highly recommend NoMachine for Remote Desktops. I use it to connect to several computers at 2 different locations. 99% of the time it is solid and reliable.
June 9, 2026 at 15:12 #56151
BritgirlKeymasterHi, so it’s a drivers-related problem. It could have been caused by a drivers update since the last time you used NoMachine maybe? Maybe there is a more recent update that you can try?
Please tell us:
- graphics card model
- version of the drivers
- a screenshot (or a video) showing the screen tearing (you’ll have to re-enable HW decoding again)
- client side logs taken while reproducing the issue (during the session > Ctrl-Alt-O > Connection > Take the Logs)
You can attach them here or send directly to forum[at]nomachine[dot]com.
-
AuthorPosts
You must be logged in to reply to this topic. Please login here.
