Since going to W10, RDP to the machine looks like crap.

Forums › Microsoft Windows › Since going to W10, RDP to the machine looks like crap.

richms

28070 posts

Uber Geek

Trusted

Lifetime subscriber

#189156 18-Dec-2015 17:57

I'm getting blocking over things when I scroll them, areas that should be solid colours have rectangles of slightly different colours on them and other things.

Its like its compressing it with h264 or something (badly) before pushing it across the lan.

Can this be disabled so that I can go back to it looking nice like 7 did? I RDP into my machine to photoshop etc since adobe make it a pain to log out and in on other PCs, and this leaves me wondering if my photo is crap or its RDP.

Richard rich.ms

Regs

4064 posts

Uber Geek

Trusted

Snowflake

#1455430 22-Dec-2015 16:14

Sounds like you've just set the "experience" down to optimise for a slow connection. Something available on any version of RDP client on any version of Windows. hit the "show options", the "experience" tab, set to "detect automatically" or "LAN (10Mbps or higher)". Also check the "colors" dropdown on the "display" tab.

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

Poll

343 posts

Ultimate Geek

#1455436 22-Dec-2015 16:19

I've had this happen at home as well, I didn't change any settings and no one else has access to change them. It's noticeably blockier than before and the screen redraw lag is measurably worse at the same time.
That's going from 10 to 10, admittedly at 2560x1440 but still it was fine before upgrade when going from 7 to 8.1.

MadEngineer

4245 posts

Uber Geek

Trusted

#1455442 22-Dec-2015 16:25

Try changing the settings to use a lower screen resolution. Also flush the rdp cache

You're not on Atlantis anymore, Duncan Idaho.

richms

28070 posts

Uber Geek

Trusted

Lifetime subscriber

#1455468 22-Dec-2015 17:02

Im not seeing any latency, but compare the backgrounds of my gmail between the 10 and a 7 machine to see how bad 10 is.

Lower screen resolution isnt an option, since 1080p is as low as I am prepared to go, and matches my good monitor as well.

10 here http://i.cubeupload.com/5JuAcr.png

7 here http://i.cubeupload.com/78oIIs.png

Will look into clearing the cache shortly, but I would have thought that anything in the cache that was rubbish looking would have expired by now? I have never connected to this machine over anything but gigabit lan so no reason for it to be compressing something down to prime tv quality levels for RDP anyway.

I think its doing something totally different compression wise, because video is completely different in RDP to 10 compared to 7.

edit: geekzone damnwell recompresses the png's into horrid jpegs so they look as bad as each other. Standby, will find somewhere else to put the pictures that will leave them alone.

Richard rich.ms

MadEngineer

4245 posts

Uber Geek

Trusted

#1455496 22-Dec-2015 17:40

you want to fix the problem, but you're not interested in trying something to see if it fixes the issue? Righto ...

i have other things to suggest, but start as above.

You're not on Atlantis anymore, Duncan Idaho.

raytaylor

4009 posts

Uber Geek

Trusted

#1457585 26-Dec-2015 23:33

Your PNGs look the same to me
I can see some background shading behind the subject line that looks like someone has scribbled a slightly lighter shade of grey but its in both pictures. That is normally a result of 16 bit colors instead of 24/32bit

Oh on the server machine, what is the maximum allowable image quality. I know on terminal server we could set a maximum level for bandwidth reasons - on many installations where staff are working remotely I would set a hard limit to 16bit instead of 24bit to speed up their session response times. I wonder if your desktop version of 10 has a similar setting somewhere?

Ray Taylor

There is no place like localhost

Spreadsheet for Comparing Electricity Plans Here

richms

28070 posts

Uber Geek

Trusted

Lifetime subscriber

#1457590 26-Dec-2015 23:49

The light horizontal lines dissapear in places on the connection to 10, on 7 they are fine.

its set to 32 bit. This isnt a server I am remoting into, its one of my gaming PC's that is much faster to do video in premiere than my old machine on the nice monitor. Problem is that its pointless being on the nice monitor if its being compressed to hell so it looks like a bad jpeg for everything.

Richard rich.ms

GoodSync

GoodSync. Easily back up and sync your files with GoodSync. Simple and secure file backup and synchronisation software will ensure that your files are never lost (affiliate link).

CYaBro

4568 posts

Uber Geek

ID Verified

Trusted

#1457636 27-Dec-2015 07:49

I'm also disappointed with rdp to a win10 enterprise vm.
Images are often blocky and videos and sound lag or don't work at all.
This is all on a local lan running gigabit.
Never had the issues when connecting to the old win8 vm.
Seems strange that this happens yet work mate can teamviewer to his home PC, and play videos etc without a problem, over the Internet!

Opinions are my own and not the views of my employer.

networkn

Networkn
32257 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#1457686 27-Dec-2015 11:23

I can add to that, I have noticed it as well.

CYaBro

4568 posts

Uber Geek

ID Verified

Trusted

#1457688 27-Dec-2015 11:40

I forgot to also mention that every morning when I first try to connect to the Win10 VM, via RDP, I have to try three times 99% of the time.
The first time I just get a black screen so have to disconnect. If I try to connect again too soon I get a grey screen with a message that the Remote Desktop service is busy and can't connect.
I have to wait a few minutes then try again. This 2nd time it connects and I can see my desktop but nothing responds so I have to disconnect again and try for a 3rd time and then everything works as normal.
It then works fine for the whole day, and even if I get disconnected when I leave my machine to go to sleep, I can reconnect the 1st time.
The issue with having to connect 3 times only happens in the morning.
This never happened with the Win8 VM and I have a Server 2012R VM running on the same tin and that works fine every time.

Opinions are my own and not the views of my employer.

Aaroona

3192 posts

Uber Geek

#1457821 27-Dec-2015 17:36

CYaBro: I forgot to also mention that every morning when I first try to connect to the Win10 VM, via RDP, I have to try three times 99% of the time.
The first time I just get a black screen so have to disconnect. If I try to connect again too soon I get a grey screen with a message that the Remote Desktop service is busy and can't connect.
I have to wait a few minutes then try again. This 2nd time it connects and I can see my desktop but nothing responds so I have to disconnect again and try for a 3rd time and then everything works as normal.
It then works fine for the whole day, and even if I get disconnected when I leave my machine to go to sleep, I can reconnect the 1st time.
The issue with having to connect 3 times only happens in the morning.
This never happened with the Win8 VM and I have a Server 2012R VM running on the same tin and that works fine every time.

Dear God this drives me insane.
I've had this issue ever since installing Win10. Connect, black screen, connect, maybe RD Services are busy, connect again and I *may* get a live shot of my desktop, but still frozen. Connect again and all good.

What I do now is just connect the first time, leave it on the black screen for about 1-2 mins and it comes up and works... but somethings also excruciatingly slow.

RDP is a bag of crap now, IMO. Haven't been able to find a fix.

networkn

Networkn
32257 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#1457831 27-Dec-2015 18:15

Aaroona:
CYaBro: I forgot to also mention that every morning when I first try to connect to the Win10 VM, via RDP, I have to try three times 99% of the time.
The first time I just get a black screen so have to disconnect. If I try to connect again too soon I get a grey screen with a message that the Remote Desktop service is busy and can't connect.
I have to wait a few minutes then try again. This 2nd time it connects and I can see my desktop but nothing responds so I have to disconnect again and try for a 3rd time and then everything works as normal.
It then works fine for the whole day, and even if I get disconnected when I leave my machine to go to sleep, I can reconnect the 1st time.
The issue with having to connect 3 times only happens in the morning.
This never happened with the Win8 VM and I have a Server 2012R VM running on the same tin and that works fine every time.

Dear God this drives me insane.
I've had this issue ever since installing Win10. Connect, black screen, connect, maybe RD Services are busy, connect again and I *may* get a live shot of my desktop, but still frozen. Connect again and all good.

What I do now is just connect the first time, leave it on the black screen for about 1-2 mins and it comes up and works... but somethings also excruciatingly slow.

RDP is a bag of crap now, IMO. Haven't been able to find a fix.

Sadly so many things that have worked PERFECTLY since Windows XP are broken in Windows 10. Something is really broken at Redmond in my opinion. W8 really sucked UI wise, but was relatively stable.

The UI is better (Relatively) in W10, but stability is Ratsh!t. (I have not seen a BSOD on one of my machines since XP SP2 and now I can pretty much guarantee I'll see at least 1 a fortnight.

3 of my 4 machines are now rolled back, I have 1 which isn't that stable but since MS sees fit to ram W10 down everyones throat, we need it to support those customers who have been upgraded with or without their knowledge.

richms

28070 posts

Uber Geek

Trusted

Lifetime subscriber

#1458309 29-Dec-2015 01:52

I'm now also getting about a 20-30 second lag on the audio from the remote session. Will reboot it tomorrow and see if that changes anything

Richard rich.ms

roobarb

652 posts

Ultimate Geek

Trusted

#1458340 29-Dec-2015 07:12

Now you know why MS recommend PowerShell for remote admin.