RDP Issue Post Windows 11 24H2 Upgrade

RDP Issue KB ID 0001901

Problem: RDP Issue

Post updating Windows 11 to version 24H2, remote desktop connections to older systems i.e. running Windows 7 or Windows Server 2008 R2, encounter issues with displaying graphical content properly.

Reverting to the earlier version of Windows 11 RDP (23H2) does resolve the issue.

Connections to devices with newer operating systems remain unaffected.

Solution: RDP Issue

Note: You can simply use the RDP client from the MS Store and this should eliminate the problem,

The solution involves copying files form an older (23H2 or older) version of Windows, but first locate all the following files and RENAME them with a .OLD extension, to do this you will need to boot into safe mode, or from the recovery environment. Press and hold the Shift key while clicking Restart from the Start menu, Power menu, or the sign-in screen. Then the computer will reboot and enter the Recovery Mode.)

  • C:\Windows\System32\mstsc.exe
  • C:\Windows\System32\mstscax.dll
  • C:\Windows\System32\en-US\mstsc.exe.mui (en-US your locale may be different if you not using English US)
  • C:\Windows\System32\en-US\mstscax.dll.mui (en-US your locale may be different if you not using Engish US))
  • C:\Windows\SystemResources\mstsc.exe.mun
  • C:\Windows\SystemResources\mstscax.dll.mum

Copy those files back from a known working older system.

Related Articles, References, Credits, or External Links

NA

Network Connection Failiure

Network Connection Failiure KB ID 0001894

Problem

Logon failure the user has not been granted the requested logon type at this computer.

{Location} is not accessible. You might not have permission to use this network resource.
Contact the administrator of this server to find out if you have access permissions

Solution : Network Connection Failiure

If you’re seeing the error “The user has not been granted the requested logon type at this computer” while trying to connect to a network share on a Windows  machine, it usually means that the user account you’re using doesn’t have the correct permissions to access that computer remotely. But don’t worry I’ll guide you through a simple troubleshooting process to fix it.

Here’s what you can do:

Step 1: Network Connection Failure Log in as Administrator

You’ll need to be on the computer you’re trying to connect to. Make sure you’re logged in with an account that has administrator privileges.

Step 2: Open Local Security Policy

  1. Press Windows + R to open the Run dialog.
  2. Type secpol.msc and hit Enter. This opens the Local Security Policy window.

Step 3: Navigate to User Rights Assignment

  1. In the left-hand pane, expand Local Policies, then click on User Rights Assignment.
  2. In the right-hand pane, scroll down to find “Deny access to this computer from the network”.
    • Why? If the user you’re trying to connect with is listed here, they won’t be able to connect to network shares.

Step 4: Check Deny Policies

  1. Double-click on “Deny access to this computer from the network” and make sure the user or group you’re trying to connect with is not listed. If they are, remove them by selecting the user or group and clicking Remove.
  2. Similarly, check the “Deny log on locally” policy. Make sure the user or group is not listed here either.

Step 5: Grant Network Access Rights

  1. Still under User Rights Assignment, find “Access this computer from the network”.
  2. Double-click it, then click Add User or Group.
  3. Type in the name of the user or group that needs access (like “Everyone” or specific users), then click OK.

Step 6: Apply and Restart

  1. Once you’ve made the changes, click Apply and OK.
  2. Restart the computer to ensure the changes take effect.

Step 7: Network Connection Failure Test the Connection

Now, try reconnecting to the network share from the other computer. If everything is set up correctly, you should now be able to connect without any issues. If it still doesn’t work, make sure the user account is also part of the local users or administrators group on the machine you’re connecting to. Let me know if you run into any trouble with these steps! It should be a straightforward fix, but every system is a little different.

Related Articles, References, Credits, or External Links

Remote Desktop Services – Connection Errors

Remote Desktop Web Access – Connection Error

Windows RDP: ‘An authentication error has occurred’

KB ID 0001433

Problem

When attempting to RDP to a remote machine;

 

An authentication error has occurred.
The function requested is not supported

Remote computer: {name}
This could be due to CredSSP encryption oracle remediation.

Or you may just see;

 

An authentication error has occurred.
The function requested is not supported

Remote computer: {name}

Solution

This is happening after you have a applied a windows security update it was this security update. It also tells you how to change your GPOs accordingly.

If your business is in Chaos – set it to ‘Vulnerable‘ to get things working, get EVERYTHING patched, then change it to ‘Mitigated‘ or ‘Force Updated‘. (WARNING: any change requires a reboot!).

 ‘Encryption Oracle Remediation’ Policy Is Missing?

Copy these two files from a freshly updated machine;

  • C:\Windows\PolicyDefinitions\CredSsp.admx (Dtd Did Feb 2018)
  • C:\Windows\PolicyDefinitions\en-US\CredSsp.adml (Dtd Feb 2018 – Your local folder may be different i.e. en-GB)

On a DC, navigate to;

  • C:\Windows\SYSVOL\sysvol\<your domain>\Policies\PolicyDefinitions

Rename the current CredSsp.admx to CredSsp.admx.old

Copy the new CredSsp.admx to this folder.

On the same DC navigate to;

  • C:\Windows\SYSVOL\sysvol\<your domain>\Policies\PolicyDefinitions\en-US (or your local language)

Rename the current CredSsp.adml to CredSsp.adml.old

Copy the new CredSsp.adml file to this folder.

Try your group policy again.

If Using a Central Policy Definition Store

You will need to copy the files to the central PolicyDefinitions folder in your Sysvol directory, see the following link;

Setup up a Central ‘PolicyDefinitions’ Store (for ADMX files)

 

Footnote

Don’t Simply Uninstall Windows updates KB41037272. and or KB4103718 – just because something works does not mean that’s what you should do!

Related Articles, References, Credits, or External Links

Windows – Remote Desktop Error ‘An authentication error has occurred. The Local Security Authority cannot be contacted’