Try to download Remote Desktop App from Microsoft Store
Use it instead of classic RDC App. For me worked!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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 AM
Try 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!
I have the same problem, on a windows server 2008, the display of certain applications like oracle sql develloper is unreadable.
I have the same problem, on a windows server 2008, the display of certain applications like oracle sql develloper is unreadable.
We have noticed this issue as-well, not attempted to Rollback yet
Hi, I have the same problem! someone could downgrade windows 11 update or fix this issue?
me too, do you solve it?
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.
I have the same problem when connected to Windows Server 2008. Please help!!!
Try to download Remote Desktop App from Microsoft Store - it is still working fine.
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.
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.
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.
We are also affected by this. We've reached out to Microsoft but it doesn't seem they're aware of the issue.
Algum conseguiu ajustar ?
I also encountered a similar problem! When is Microsoft going to solve it? It is impossible to work fully with a remote desktop!!!!
November Cumulative update hasn't fixed this issue
The same happened to me, but when accessing applications that needs Java. Windows Explorer and Browsers runs fine.
I took old RDP 7.1 client files and that's ok !
Аналогичная проблема. Очень жду скорейшего решения!
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
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.
Not a very helpful answer?
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!
Same problem with our Win11 24h2 update: A lot of artefacts in RDP-windows. Moving mouse creates stripes. It's more than annoying...
I've been looking for the 7.1 download but I haven't been able to find it anywhere.
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
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.
resolved https://www.facebook.com/share/v/1Jux5xWdSk/
translate THAI to ENG
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.
I cleared out the group policy history cache and know it works
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.
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
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.
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.
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.
You don't need to touch your system mstsc, sort this thread by newest and see my solution below.
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.)
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:
Unfortunately, it doesn't work for us with the GPO either.
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... ... ...
Can anyone tell me how to install FreeRDP on Windows?
Try to download Remote Desktop App from Microsoft Store
Use it instead of classic RDC App. For me worked!
The RDP app from Microsoft Store is a limited edition compared to the standard one: it does not create the tunnels for the ports (for example: serial ports), so the resolution is not good enough for me.
The RDP app from the store worked for me. Same problem but connecting using a secure remote access solution. It'll do the job for now until Microsoft patch this.
Remote desktop app worked for me after 24H2 upgrade. The issue is limited to only one server 2008 and is fine for maintenance
that fixed it! thanks!
Hi
I have just found something which i just tryed , and that was to delete and rebuild the group policy's and it's working,
This is what i did below:
To delete the local Group Policy cache on a Windows computer, you can:
Open My Computer or Computer
In the address bar, paste %windir%\system32\GroupPolicy
Right-click and delete the Machine and User folders
Restart the computer to reapply the group policies
You can also delete the contents of the local Group Policy cache by following these steps:
Locate the hidden folder C:\ProgramData\Microsoft\Group Policy\History
Delete the contents of the History folder, but do not delete the folder itself
Run GPUpdate /force from the command prompt to rebuild the cache
Restart the system
A corrupt or de-synchronized local Group Policy cache can cause problems, such as Group Policy settings not updating.
Group Policy is automatically refreshed when a user logs on to a domain member computer, when the computer is restarted, and periodically. The default periodic refresh interval is every 90 minutes, with a randomized offset of up to 30 minutes
Worked for me to, in my case connecting to XP (yes, I know, but using it with developement tools not available for later versions).
I found article
and there is helpful two comments
Like suggest Richard (FreeRDP)- but below app is from MS
I tested app with icon with red circle and signs >< inside - and artefact (on APP via RDP) does not occur.
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"
(on Client PC)
Before You will change this files i sugest create copy of theme.
I coped from C:\windows.old this files (but when You usage Windows in another language this en-US directory be diferent - corectly to OS language) and
I cope files on Windows Recovery Mode (press and hold shift when You click reboot OS; on Recovery mode -> Trabelshoot -> Advanced options -> Command Prompt) - becouse when OS normaly works, this files is lock.
Useful comands on cmd
-to change partition:
C:
-after chenges partition to C: - changes folders
cd c:\Windows\System32\
-to list files on directory or check file size
dir mstsc.exe
-delete files
del C:\Windows\System32\mstsc.exe
-copy files between folders (first is source directory second is destination directory)
copy C:\Windows.old\System32\mstsc.exe C:\Windows\System32\mstsc.exe
Unfortunately, our internal policy prohibits the substitution of any system files, the virus will block these operations.
Unfortunately, our security system prohibits the modification of system files, even if I merely copy them from the old version.
Try copy this files (from 2) ) to new folder (keeping language directory) in User profile and run RDP from this folder (i think i try that and that's works - but RDP have graphic artefacts, without advanced options)
Same issue,and how long will it take Microsoft to fix it?
düzeldi. teşekkür ederim.
Hi everyone!
Here's a required structure:
Just copy those dirs and files from old build of Windows 11 23H2 to some place and then make a shortcut for this mstsc.exe file to your desktop and use it for rdp connections instead of a new one from 24H2.
If you have another locale than en-US, e.g. uk-UA, copy it with corresponding files too.
Also you can try to download my version, it includes en-US, ru-RU and uk-UA locales (5.4MB):
https://mega.nz/file/gMIh2bLI#vyX1PUuGeuj5NI__VX9KgUSAUY5U2tlt1cU5xqR4MJE
This wasn't working for me before but it is now. However, when I had added the SystemResources folder and files previously, I had already tried without it and I had continued to have the issue where menu options were missing. Another thing is when I went into the 24H2 client previously, I could swear it had the same blue title bar with the cutoff corners that dropped down on prior clients (including the 23H2 one):
Now when I go into the 24H2 client, the drop down bar is black and rectangular:
I tried multiple things since this time and last time (such as installing the Remote Desktop app from the store as well as some third party apps all of which were since uninstalled) and there's also been an update or two since then. Is there anyone who tried this previously who is still having the issue and can tell me if I was imagining things about that title bar being the same old blue in 24H2 previously? Anyway, this does work for me now and is a considerably better workaround than what I suggested if one still has access to the old 23H2 files.
Before 24H2 title bar was blue, but after updating to 24H2 it became ugly rectangular black or white.
This works if I run the mstsc.exe directly and then connect, but if I try to launch it specifying an .rdp (remote app) connection file it defaults to the the version in c:\windows\system32. I've tried from the command line, and through a shortcut. Any ideas? Thank you.
I was not able to assign to open rdp files with the old version of mstsc. But there is another way. Make a shortcut to the old mstsc on your desktop and just drag and drop the rdp file onto it to open.
I was not able to assign to open rdp files with the old version of mstsc.
But there is another way.
Just make a shortcut to the old mstsc on your desktop and just drag and drop the rdp file onto it to open.
Hello, Colin H.
You can try to make a shortcut of the old mstsc on you desktop and then drug and drop your rdp file onto it to run with it.
Hi @Comraddm,
Thanks for the suggestion, unfortunately that didn't work either, whatever I do, the Remote App is launched with mstsc.exe and when I check the location of the executable through Task Manager it shows C:\windows\system32\mstsc.exe and not the path of the older version.
Thanks again.
Colin.
Hello, Colin H.
Download my archive from mega.nz, unzip it to your desktop, go to unzipped folder to subfolder system32 and make a shortcut from mstsc.exe in that folder to your desktop.
Then just drug and drop your rdp file onto this shortcut.
It should work!
Hi Comraddm,
I tried that, but what happens is that a process is launched which is the old version of mstsc.exe, but then this seems to launch a new process which is new version in c:\windows\system32.
I grabbed a screenshot of this happening in Process Explorer.
I don't understand why a new process is spawned upon launch of the RDP file.
Many thanks again for your help.
It looks like mstsc in Windows 11 24H2 no longer understands bitmap updates that contain multiple rectangles. It seems to draw the first rectangle (maybe) and ignore the rest. It's not clear whether this change is intentional.
FreeRDP updated their code to deal with this by restricting all bitmap updates to a single rectangle.
I succeed : take file mstsc.exe and mstscax.dll from a computer with 23H2 (windows\system32. Replace theese 2 files on your installation with 24H2.
I copied the following files from the 23H2 version, from the Windows.old folder:
C:\Windows\System32\mstsc.exe
C:\Windows\System32\mstscax.dll
These two files alone are not enough to make everything look good, the other 4 support files are missing, which I show below:
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
Of course I made a backup of the originals from 24H2 in case Microsoft takes notice and solves the problem
To copy these files I did it from the recovery environment using the command line
I hope it is useful to you
I get this same problem on our customers Windows 11 too.
I copy all the mstsc*.* (version 10.0.22621) from my notebook which doesn't update to 24H2 yet.
Copy those files to customers c:\windows\mstsc (10.0.22621). And make a shortcut for them to use temporarily until Microsoft release a fix
This thread is about RDP issues with windows 7 and server 2008 r2
Your issues is the difference between the Modern App "Remote desktop" and the windows application MSTSC.exe "Remote Desktop Connections"
Go to Settings App, Remote Desktop where you can set the default app/application for rdp files.