Upgrading to Windows 11 24H2 causes remote desktop connections to Windows 7 machines not to show graphics correctly.

Alessandro Cipriano 205 Reputation points
2024-10-03T09:25:51.5866667+00:00

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.

RemoteDesktopProblemAfter24H2

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

24 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Hughs 5 Reputation points
    2024-12-11T04:23:24.25+00:00

    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

    Was this answer helpful?

    1 person found this answer helpful.
  2. Marc Picart 15 Reputation points
    2024-12-17T19:00:44.97+00:00

    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 (en-US It depends on the Windows language)

    C:\Windows\System32\en-US\mstscax.dll.mui (en-US It depends on the Windows language)

    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

    Was this answer helpful?

    1 person found this answer helpful.
  3. Dominic_Knight 0 Reputation points
    2024-12-24T12:31:02.5133333+00:00

    I have got same problems , but i did a fresh install of 24h2 and it worked but that isn’t a answer to a fix, but i have got 1 pc out of 15 that updated and worked fine , not sure why

    Was this answer helpful?

    0 comments
  4. Dominic_Knight 0 Reputation points
    2024-12-24T13:16:38.33+00:00

    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

    Was this answer helpful?

  5. sullivanjc 25 Reputation points
    2024-12-27T20:27:32.8433333+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. If this does work for others, maybe this will help futher determine what the actual issue is. My hypothesis at this point is it's something with data compression and that it only comes into play when color depth exceeds 8 bits per pixel or 1 byte.

    Was this answer helpful?

    2 people found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.