KB5050577 does not fix it for sessions to Windows Server 2008 R2 Terminal Server.
Upgrading to Windows 11 24H2 causes remote desktop connections to Windows 7 machines not to show graphics correctly.
After having upgraded Windows 11 to 24H2, the remote desktop connections to machines that use Windows 7 or Windows Server 2008R2 do not show graphic content correctly.
Returning to the previous Windows 11 version (23H2) has resolved the problem.
No problems with remote desktop connections to other machines with more recent operating systems. Unfortunately, the above-mentioned Windows 7 machine is "special", as it is used to control some very old industrial system control and it is not upgradable.
Remote Desktop
-
marc tofsted • 10 Reputation points
2024-10-07T12:42:43.9766667+00:00 This same issue just popped up for me. I just "upgraded" to Win11 24H2 and my remote connection to my OLD development machine is now showing corrupt graphics or blank boxes.
Hitting the Experience settings on the remote session helped.
I set that to "LAN" and checked all the option boxes.I tried both the Bitmap Caching options and neither setting fixed the graphics display.
Microsoft, if you're listening, HELP!
UPDATE:: See below comment from
Michal Kumela Oct 21, 2024, 2:57 AMTry to download Remote Desktop App from Microsoft Store.
This App connect seems a little slower than the Windows 11 RDC, but it fixed the graphics corruption problem for my situation!
-
Antoine-9167 • 30 Reputation points
2024-10-07T14:49:33.8566667+00:00 I have the same problem, on a windows server 2008, the display of certain applications like oracle sql develloper is unreadable.
-
Antoine-9167 • 30 Reputation points
2024-10-07T14:49:56.44+00:00 I have the same problem, on a windows server 2008, the display of certain applications like oracle sql develloper is unreadable.
-
Ryan Jackson • 0 Reputation points
2024-10-10T10:06:24.7233333+00:00 We have noticed this issue as-well, not attempted to Rollback yet
-
Leonardo Zarate • 5 Reputation points
2024-10-18T14:20:18.5766667+00:00 Hi, I have the same problem! someone could downgrade windows 11 update or fix this issue?
-
Leonardo Zarate • 5 Reputation points
2024-10-18T14:43:38.59+00:00 me too, do you solve it?
-
Alessandro Cipriano • 205 Reputation points
2024-10-18T15:04:16.5766667+00:00 I "rolled back" to the previous Windows 11 version, which temporarily resolved the problem. However, in this way, I blocked many other good improvement present in the 24H2.
-
Michal Kumela • 45 Reputation points
2024-10-21T07:39:25.7633333+00:00 I have the same problem when connected to Windows Server 2008. Please help!!!
-
Michal Kumela • 45 Reputation points
2024-10-21T08:53:42.8833333+00:00 Try to download Remote Desktop App from Microsoft Store - it is still working fine.
-
Poyo Poyo • 0 Reputation points
2024-10-22T01:06:30.53+00:00 I also encountered this issue and was confused for a long time, until I finally discovered it was a problem with the new version of the mstsc client in Windows 11 24H2.
-
Mikael Andersen • 0 Reputation points
2024-10-31T09:08:03.83+00:00 Any word from Microsoft on this issue? This causes massive issues for me, who RDPs into older systems, but where I am forced to update.
-
Alessandro Cipriano • 205 Reputation points
2024-10-31T12:48:09.5266667+00:00 Unfortunately, the only solution now is to return to the previous version (23H2). You should do that quickly, or it will become unavailable after a while.
-
DiegoCarmona-4368 • 10 Reputation points
2024-10-31T21:06:47.19+00:00 We are also affected by this. We've reached out to Microsoft but it doesn't seem they're aware of the issue.
-
Guilherme Rodrigues Da Costa • 0 Reputation points
2024-11-11T20:06:41.1366667+00:00 Algum conseguiu ajustar ?
-
Horse Merry • 0 Reputation points
2024-11-17T08:07:44.03+00:00 I also encountered a similar problem! When is Microsoft going to solve it? It is impossible to work fully with a remote desktop!!!!
-
Jason Beaumont • 0 Reputation points
2024-11-19T00:13:53.0733333+00:00 November Cumulative update hasn't fixed this issue
-
HenriquedaCunhaTeixeira-8514 • 0 Reputation points
2024-11-21T12:13:17.61+00:00 The same happened to me, but when accessing applications that needs Java. Windows Explorer and Browsers runs fine.
-
Alexander Galkin • 1 Reputation point
2024-11-25T09:23:47.6233333+00:00 I took old RDP 7.1 client files and that's ok !
-
Алексей Степин • 0 Reputation points
2024-11-25T16:44:59.15+00:00 Аналогичная проблема. Очень жду скорейшего решения!
-
Frederic DM • 0 Reputation points
2024-12-06T20:31:18.2833333+00:00 Same problem here. Thunderbird menus on the remote computer are unusable.
I have recovered mstsc.exe and mstscax.dll from Windows.old ; and both .mui files from subdirectory en-US.
When launched from that location, it fixes the problem, but creates another.
The top menu bar is absent, so that you cannot disconnect from the remote session or reduce it in a window.
Frédéric, from Belgium
-
Stéphane Girard • 0 Reputation points
2024-12-10T12:53:34.4233333+00:00 Same problem with windows 11 24h2 and a 2008 server with excel 2002. All the buttons are hidden and appear when I move the mouse over them.
-
Manie Van Der Raad • 0 Reputation points
2024-12-10T13:00:08.2966667+00:00 Not a very helpful answer?
-
Don • 0 Reputation points
2024-12-14T00:16:48.16+00:00 Same problem with Remote Desktop accessing an older Windows 7 machine after updating to 24H2. At first I thought it was a video card issue, until I noticed that another laptop just updated to 24H2 also had the problem. I will not update my remaining laptop for the time being!
-
Michael Glocker • 0 Reputation points
2024-12-17T10:05:35.44+00:00 Same problem with our Win11 24h2 update: A lot of artefacts in RDP-windows. Moving mouse creates stripes. It's more than annoying...
-
Tim Jones • 0 Reputation points
2024-12-17T14:41:28.34+00:00 I've been looking for the 7.1 download but I haven't been able to find it anywhere.
-
Marc Picart • 15 Reputation points
2024-12-17T18:59:25.7+00:00 Hi Frederic,
To fix the menu bar problem
I copied the following files from the 23H2 version, from the Windows.old folder:
C:\Windows\System32\mstsc.exe
C:\Windows\System32\mstscax.dll
C:\Windows\System32\en-US\mstsc.exe.mui
C:\Windows\System32\en-US\mstscax.dll.mui
C:\Windows\SystemResources\mstsc.exe.mun
C:\Windows\SystemResources\mstscax.dll.mun
It worked fine
-
Frederic DM • 0 Reputation points
2024-12-17T19:07:31.83+00:00 Hello @marc picart, I already tried that (except that I have put a target location outside c:\windows) and the behaviour is a bit different. The remote desktop comes immediately a full-screen, and the top menu bar is absent.
Hence you cannot put the remote desktop in a window, neither close it in order to disconnect.
I cannot test anymore as I have reverted to 23H2 within the 10-days timeframe.
-
Takorn • 0 Reputation points
2024-12-17T23:56:48.1466667+00:00 resolved https://www.facebook.com/share/v/1Jux5xWdSk/
translate THAI to ENG -
sullivanjc • 25 Reputation points
2024-12-24T00:17:51.9+00:00 Is anyone experiencing this issue with Windows 2008R2 or Windows 7 running RDP 8 on their machines (which was an update, not what was released with the OS)? I'm wondering if that changes anything in regards to this issue as I don't think Microsoft will view it as a problem. The OSes of the servers being connected to are past end of of life and running versions of RDP that were not installed to currently supported versions of their PC and server products.
-
Dominic_Knight • 0 Reputation points
2024-12-24T13:22:24.7633333+00:00 I cleared out the group policy history cache and know it works
-
sullivanjc • 25 Reputation points
2024-12-27T20:01:58.4166667+00:00 I believe I found a workaround, albeit a low quality one. I found this while tinkering with mRemoteNG and was able to do this with the Windows Remote Desktop Client with an .rdp file. When I set the color depth to 256 colors, I did not get the bars across my screen running sqldeveloper. I viewed table contents and ran a sql script without issue. It is an ugly screen, but it is legible. The Windows 11 RDP client does not offer 256 colors as an option but you can save a .rdp file and edit the file in notepad to set it there. The value you want to change is session bits per pixel (session bpp). It normally looks like "session bpp:i:32". It could be 15 or 16 depending on color depth picked when you saved the .rdp intially. Change it to the following: "session bpp:i:8", save the file, and then launch your remote desktop session using that .rdp file.
-
James White • 15 Reputation points
2025-01-02T23:30:32.7933333+00:00 It is more complicated when you are using an RDM manager program that uses mstsc API.
This has been broken for some months now. I have to access older servers
it impacts hosts running
windows 2008 x86,
windows 2008 r2 X64
from any Windows 11 machine since the second or third windows insider release preview of 24H2
While RDM supports using older versions of the RDP Api supposedly from RDP6.1 to RDP 10.11 it makes no difference so far
FreeRDP API has problems with cutting and pasting the clipboard which is essential
time for a fix please Bill
-
matt Jensen • 0 Reputation points
2025-01-14T15:32:57.0133333+00:00 I work for a medical Facility and The EHR we use connects via Remote desktop connection the program is centered around Windows Server 2008, When I did the update Windows 11, version 24H2 on 1-13-2025 I had logged into my EHR and it is comparable to the picture above, I went into the Microsoft Store and downloaded remote desktop connection and it fixed the graphical issues but now i cant access my printer. The printer is not wired it connects via Wifi. Does anybody know If i can uninstall the most recent update or how to get my printer to pick up through MICROSOFT REMOTE DESKTOP.
-
sullivanjc • 25 Reputation points
2025-01-14T19:18:47.74+00:00 You can try my suggestion from Dec. 27th to get the standard PC remote desktop application working at 256 colors. The graphics are legible then but the color depth kind of sucks. That would then presumably allow you to use your printer with Remote Desktop. If you updated on the 13th, you might be able to go into the update history on Windows Update and roll the update back. If it's been more than 10 days, though, you won't have that option.
-
Keyser Söze • 5 Reputation points
2025-01-22T09:32:59.4133333+00:00 Hello, has anyone solved this problem properly? When I run the files from version 23h2, everything looks fine, but the top toolbar does not show. Do you have any solution? I am solving the problem on remote computers, so I cannot completely replace mstsc.exe in the system32 directory.. Thanks
-
Dmitry Merkotan • 20 Reputation points
2025-01-22T09:50:28.9733333+00:00 Sort this thread by newest and see my solution just under yours (from Comraddm). You don't need to touch you system mstsc, just copy that archive to any place and make a shortcut to desktop.
-
Thomas-3831 • 5 Reputation points
2025-01-22T09:57:30.4166667+00:00 We also have this problem and urgently need a solution.
It is unacceptable that we have to replace the mstsc files with every Windows update.
Unfortunately, many functions are not possible with the new MS Remote Desktop. -
Comraddm • 115 Reputation points
2025-01-22T10:09:37.9833333+00:00 You don't need to touch your system mstsc, sort this thread by newest and see my solution below.
-
Frederic DM • 0 Reputation points
2025-01-22T10:15:49.9966667+00:00 I do not agree. I did that and explained it in a previous post. The remote desktop comes in a full screen window without a toolbar, and you cannot set the remote session in a window, or minimise it, or disconnect it.
The only way to return to your local computer is to logoff from the remote computer.
I was still in the timeframe to uninstall 24H2 and reverted to 23H2.
(I had other problems with 24H2 related to networking, IPv6, DNS and DHCP.)
-
Comraddm • 115 Reputation points
2025-01-22T10:35:07.8066667+00:00 Frederic DM, no, I insist it really works fine!
Checked on several PCs.
Are you sure you did exactly what suggested?
The situation without toolbar appears if resource files *.mun are absent.
Can you show all files and dirs of your dir with mstsc.exe?
To do that run cmd, then cd to your dir and there type command tree /f.
You should get this:
-
Thomas-3831 • 5 Reputation points
2025-01-22T10:58:21+00:00 Unfortunately, it doesn't work for us with the GPO either.
-
Frederic DM • 0 Reputation points
2025-01-22T10:58:55.0866667+00:00 Sorry, I cannot do that. I have reverted to 23H2.
Anyway, what a mess in order to sort out what is needed and what is crap.
Not counting zillions occurrences in WinSXS
Thanks for your advice, I will keep a copy of those .mun files in a safe place, for the time MS will push forcefully 24H2 sooner or later.
C:\WINDOWS\System32\mstsc.exe
C:\WINDOWS\System32\mstscax.dll
C:\WINDOWS\System32\en-GB\mstsc.exe.mui
C:\WINDOWS\System32\en-GB\mstscax.dll.mui
C:\WINDOWS\System32\en-US\mstsc.exe.mui
C:\WINDOWS\System32\en-US\mstscax.dll.mui
C:\WINDOWS\System32\fr-FR\mstsc.exe.mui
C:\WINDOWS\System32\fr-FR\mstscax.dll.mui
C:\WINDOWS\System32\wbem\mstsc.mof
C:\WINDOWS\System32\wbem\mstscax.mof
C:\WINDOWS\System32\wbem\en-GB\mstsc.mfl
C:\WINDOWS\System32\wbem\en-GB\mstscax.mfl
C:\WINDOWS\System32\wbem\en-US\mstsc.mfl
C:\WINDOWS\System32\wbem\en-US\mstscax.mfl
C:\WINDOWS\System32\wbem\fr-FR\mstsc.mfl
C:\WINDOWS\System32\wbem\fr-FR\mstscax.mfl
C:\WINDOWS\SystemResources\mstsc.exe.mun
C:\WINDOWS\SystemResources\mstscax.dll.mun
C:\WINDOWS\SysWOW64\mstsc.exe
C:\WINDOWS\SysWOW64\mstscax.dll
C:\WINDOWS\SysWOW64\wbem\mstsc.mof
C:\WINDOWS\SysWOW64\wbem\mstscax.mof
C:\WINDOWS\SysWOW64\wbem\en-GB\mstscax.mfl
C:\WINDOWS\SysWOW64\wbem\en-US\mstscax.mfl
C:\WINDOWS\SysWOW64\wbem\fr-FR\mstscax.mfl
C:\WINDOWS\WinSxS\amd64_microsoft-windows-t..cesclient.resources_31bf3856ad3... ... ...
-
Comraddm • 115 Reputation points
2025-01-22T11:32:48.7466667+00:00 -
Thomas-3831 • 5 Reputation points
2025-01-22T12:08:03.21+00:00 Can anyone tell me how to install FreeRDP on Windows?
-
Anwar Mangla • 15 Reputation points
2025-02-03T18:51:43.3866667+00:00 This method of copying mstsc files from old built to a different location and starting older version of mstsc works if you are using remote desktop but if you have a remote app, it does not follow even if you point that remote app file to older mstsc version.
-
DiegoCarmona-4368 • 10 Reputation points
2025-02-07T18:49:15.75+00:00 We have tested this week's Insider Preview build
And we can confirm that the issue has been fixed in this build.
-
Comraddm • 115 Reputation points
2025-02-07T19:10:45.5566667+00:00 Thank you, DiegoCarmona-4368.
Will be waiting for the official stable release.
-
Dave Johnston • 10 Reputation points
2025-02-08T20:04:45.0733333+00:00 Agree, that release does the job, great!
-
Paul Vancluysen • 15 Reputation points
2025-02-16T14:48:31.8966667+00:00 Hi everyone,
I did upgrade recently (14/2/2025) to Windows 11 version 24H2. Also, it causes problems with remote desktop connections to XP virtual machine, graphics are not shown correctly.
Does anyone knows if Microsoft self will solve this issue in future upgrades? It seems to me an unacceptable behavior as so many windows users all have this same problem.
Thanks in advance to Microsoft for professional help!
-
Paul Vancluysen • 15 Reputation points
2025-02-17T13:16:03.1166667+00:00 My last update was at 11/02/2025.
2025-02 Cumulatieve update voor op Windows 11 Version 23H2 for x64 gebaseerde systemen (KB5051989).
There are still problems in my XP virtual machine via remote desktop connection. Missing some icon graphics in XP system environment and also in some XP programs. Graphic curves are not displayed solid, missing data points and also icons are not complete displayed in the programs. Accessing the icon buttons they become visible and complete, but it doesn't become stable at all.
I stay waiting for upgrade that solves it all.
I still use some older XP programs for my company and I cannot replace them by more recent versions, because they don't exist. So, I really need a good working stable XP environment like it was before the Windows 11 24H2 upgrade.
-
Morena Abritta • 5 Reputation points
2025-02-18T18:52:54.4533333+00:00 Same, installed KB5051987 but the issue is still there. It is unacceptable for such a problem to be going on for months.
-
Toni Zapata Yerga • 10 Reputation points
2025-02-20T08:00:53.41+00:00 I have had this issue for two months and Microsoft still hasn't fixed it. I am an IT administrator and I have several affected servers, Windows 2008 and even some Windows 2003. I know they should be updated but they do their job perfectly. I have some users with the 24H2 version but more and more are coming. At the moment we have solved it using the old mstsc.exe. But that can stop working at any time. I hope Microsoft takes this seriously. Otherwise, between Windows 10 end of support and 24H2, companies are going to have to spend a fortune on renewals.
-
Dave Johnston • 10 Reputation points
2025-02-20T08:08:04+00:00 Sorts graphics but can't use as there is no printer and local drive ability.
Sign in to comment
24 answers
Sort by: Most helpful
-
Rob • 0 Reputation points
2025-02-26T01:39:23.1+00:00 -
Dave Johnston • 10 Reputation points
2025-02-26T03:36:22.5433333+00:00 That's odd, did for me, graphics fine after it installed
-
Rob • 0 Reputation points
2025-02-27T01:01:33.4633333+00:00 I might have a slightly different issue. The desktop looks fine in standard Windows apps. Then as soon as even a small java window is opened, the whole desktop goes glitchy. It is not limited to one software vendor, each app using a different java vm version, and it is occurring across multiple RDP servers and clients. The issue started recently with newer Windows clients. Microsoft Remote Desktop on Mac works perfectly.
I have worked around it somewhat, by removing the 16-bit color depth limit via mmc Remote Desktop Services Manager snap-in. Rendering is improved, but performance suffers.
Any tips on getting the Microsoft Store Remote Desktop client working with Windows 2008 R2 SP1? The error is "remote PC might not accept blank passwords", but I am entering the correct password.
-
Clay • 0 Reputation points
2025-02-27T13:42:30.88+00:00 Same here - KB5050577 did not fix the graphics issue with Windows Server 2008 R2 Terminal Server
Sign in to comment -
-
Alan Besnardeau • 0 Reputation points
2025-02-27T13:47:54.3933333+00:00 Microsoft published this article for the latest update KB5052093, a fix with RDP display has been made.
I haven't had time to test this update, I'm posting it here for those who can test and give us feedback please
-
Comraddm • 115 Reputation points
2025-02-27T15:13:39.9+00:00 Hello, Alan Besnardeau.
I can confirm that KB5052093 really helped me with RDP session to Windows Server 2008 R2.
For the clean experiment I did it in Virtual machine Win 11 24H2 without updates.
I downloaded this update from Microsoft catalog:
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5052093
During installation all other Win updates up to February also were installed automatically.
Beta pre-updates switch was turned off.
Next for a check I uninstalled KB5052093 and restarted.
And RDP problems returned again.
So that update really works!
Sign in to comment -
-
Paul Vancluysen • 15 Reputation points
2025-02-27T13:57:13.9333333+00:00 Today my problem with RDP seems to be solved. From one day to the other, whithout any windows update or without any other system settings, the problem has disappeared.
As an inforamtion, the problem was: I did upgrade recently (14/2/2025) to Windows 11 version 24H2 and It caused problems with remote desktop connections to an XP virtual machine, the graphics were not shown correctly.
I don't know how it could happen that all is solved now, Hopefully it stays stable.
-
Lucas José Grande • 0 Reputation points
2025-03-04T17:08:42.3733333+00:00 Para arrumar a desconexão do MSTSC.exe e não ter que utilizar o Desktop Remote app da Microsoft Store. O problema está no acesso UDP, então, nada melhor do que desativar ele no terminal.
@echo off
:: Força a execução como administrador
NET SESSION >nul 2>&1
IF %ERRORLEVEL% NEQ 0 (
echo Solicitando permissões de administrador... powershell -Command "Start-Process '%~0' -Verb RunAs" exit
)
:: Cria a chave de registro
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /t REG_DWORD /d 1 /f
if %ERRORLEVEL% EQU 0 (
echo Chave fClientDisableUDP criada com sucesso!
) else (
echo Falha ao criar a chave. Verifique as permissões ou o caminho do registro.
)
pause