Rdp Windows 10 2004

Posted on |



Microsoft has released Windows 10 Build 19043.899 (21H1) to Windows insiders in the beta channel.

  1. Rdp Patcher Windows 10 2004
  2. Enable Rdp Windows 10 Home 2004
  3. Multiple Rdp Windows 10 2004
  4. Windows 10 2004 Rdp Problems
  5. Rdp Wrapper Windows 10 2004 Github

How to Fix RDP Wrapper Issue in Windows 10 2004, windows 10, remote desktop, tutorial, How to run multiple REMOTE DESKTOP USERS WITHOUT LOG OFF, remote access, termserv.dll, remote desktop connection, microsoft windows (operating system), rdp gratis windows, rdp wrapper, rdp windows 10, rdp windows, version 2004, vcloudpoint zero client, vcloudpoint installation, vcloudpoint, desktop, remote. MDT version 8456 supports Windows 10, version 2004 and earlier operating systems, including Windows Server 2019. There is currently an issue that causes MDT to incorrectly detect that UEFI is present in Windows 10, version 2004. This issue is currently under investigation. For the latest information about MDT, see the MDT release notes. How to Fix RDP Wrapper Issue in Windows 10 2004, windows 10, remote desktop, tutorial, How to run multiple REMOTE DESKTOP USERS WITHOUT LOG OFF, remote access, termserv.dll, remote desktop connection, microsoft windows (operating system), rdp gratis windows, rdp wrapper, rdp windows 10, rdp windows, version 2004, vcloudpoint zero client, vcloudpoint installation, vcloudpoint, desktop, remote. We fixed an issue that prevents Windows from activating Windows 10, version 2004 using the OA 3.0 key after installing KB4598291. We fixed an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.

2004

Releasing Windows 10 Build 19043.899 (21H1) to Beta Channel

Hello Windows Insiders, today we’re releasing 21H1 Build 19043.899 (KB5000842) to the Beta Channel for those Insiders who are on 21H1. This update includes the following improvements:

  • We fixed an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
  • We enabled administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
  • We fixed an issue that prevents the icon for a Toast collection from appearing in the Action Center if the icon file’s URI contains spaces.
  • We fixed an issue that makes high dynamic range (HDR) screens appear much darker than expected.
  • We fixed an issue that causes video playback to be out of sync in duplicate mode when you use multiple monitors.
  • We fixed an issue that might cause applications to stop working while you type Japanese characters using the Microsoft Japanese Input Method Editor (IME) in compatibility mode.
  • We fixed an issue that might cause a device to stop responding during hybrid shutdown.
  • We fixed an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
  • We fixed a window rendering issue that causes content in a window to flash frequently when FlipEx is used.
  • We fixed a window rendering issue that causes content in a window to flash frequently when multi-plane overlay (MPO) is used.
  • We fixed an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge.
  • We fixed an issue that displays nothing or shows “Computing Filters” indefinitely when you filter File Explorer search results.
  • We fixed an issue that makes the split layout unavailable for the touch keyboard when you rotate a device to portrait mode.
  • We informed users when a child account in the Family Safety plan has administrative privileges.
  • We fixed an issue that prevents you from closing Toast Notifications using the Close button on touchscreen devices.
  • We fixed an issue with a heap leak that might cause explorer.exe to consume high amounts of memory.
  • We updated the Volgograd, Russia time zone from UTC+4 to UTC+3.
  • We added a new time zone, UTC+2:00 Juba, for the Republic of South Sudan.
  • We fixed an issue with the Windows Event Log Forwarding client, which returns the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client selects the client’s certificate only if the Network Service has read permissions for the private key.
  • We fixed an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
  • We fixed an issue that stops BranchCache from working if you activate Windows using Cloud Solution Provider (CSP) license.
  • We fixed an issue that prevents Windows 10 Home edition devices from upgrading to the Windows 10 Pro Education edition using mobile device management (MDM) services such as Microsoft Intune.
  • We fixed an issue that prevents App-V applications from opening and generates error 0xc0000225.
  • We fixed an issue in which some machines enrolled with an MDM service fail to sync if the device manufacturer’s name contains a reserved character.
  • We fixed an issue with using a configuration service provider (CSP) policy to configure a custom setting for Audit Other Logon/Logoff events. The custom setting fails to take effect.
  • We fixed an issue that causes a system to stop working when no Trusted Platform Module (TPM) is present in the system. The error code in TpmTasks.dll!TrackTPMStateChanges is c0000005.
  • We fixed an issue that causes multiple instances of exe to run on a system when AppLocker is enabled and the system is not on the internet.
  • We fixed an issue with credential roaming when Windows Hello for Business is enabled.
  • We fixed an issue that prevents performance monitoring tools from displaying logged data for single instance counter objects.
  • We fixed an issue that prevents the Chromium-based Microsoft Edge from working. This issue occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
  • We fixed an issue that might cause a black screen or delay signing in to Hybrid Azure Active Directory joined machines. Additionally, there is no access to login.microsoftonline.com.
  • We fixed an issue that causes the system to stop working and generates error code 0xC9.
  • We fixed an issue with 7.1 channel audio technology.
  • We fixed an issue that turns on Caps lock unexpectedly when using RemoteApp. 31259510
  • We enabled Windows to retrieve updated printer capabilities to ensure that users have the proper set of selectable print options.
  • We updated support for hole punch and stapling locations for print jobs with long edge first paper feed direction on certain printers.
  • We fixed an issue with high memory usage when performing XSLT transforms using MSXLM6.
  • We fixed an issue that might cause File Explorer and other applications to stop responding for several minutes. This issue occurs after a client reconnects to the corporate network and attempts to use mapped drives to access file shares on the corporate network.
  • We fixed an issue that prevents Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  • We fixed an issue that might cause the cluster network interface to stop working for a short time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system might not detect that the NIC is working and the NIC remains in a failed status.
  • We fixed an issue with signing in to a device that is in the current domain by using the default user profile of a device that is in a different, but trusted domain. The profile service of the current domain cannot retrieve the default user profile from the trusted domain and uses the local default user profile instead.
  • We fixed an issue that causes a device to stop working if you delete files or folders that OneDrive syncs.
  • We fixed an issue that prevents Windows from activating Windows 10, version 2004 using the OA 3.0 key after installing KB4598291.
  • We fixed an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • We removed the Microsoft Edge Legacy desktop application that is out of support and installs the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release.
  • We fixed an issue that prevents users from using the Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • We fixed an issue to allow our enterprise partners to work with the Microsoft Support program to create customized mitigations.
  • We fixed an issue that might cause a blue screen when attempting to print to certain printers using some apps and might generate the error, APC_INDEX_MISMATCH.
  • We fixed an issue with an HTTP Keep-Alive connection in Azure Front Door. After completing a previous request and response to keep the connection open, Azure Front Door will try to reuse the connection. After an idle timeout, a race condition might occur that closes the Transmission Control Protocol (TCP) connection. As a result, the client might fail with an invalid server response.
  • We fixed an issue that causes Remote Desktop sessions to end unexpectedly.

Releasing Windows 10 Build 19043.899 (21H1) to Beta Channel

Intro
As you might know the RDP protocol in Windows 10 consists of different type of codecs (both proprietary and standardized video compression codecs). They belong to a broader set of technologies also known as RemoteFX. There are currently 2 type of codec configurations possible in Windows 10:

  • A combination of different codecs, one optimized for text and one for moving graphics (like video content)
  • The full screen AVC video codec

You can configure them with policies and check which configuration you are using by checking Event ID 162 in the following eventlog location:

Rdp Patcher Windows 10 2004

Applications and Services Logs -> Microsoft -> Windows -> RemoteDesktopServices-RdpCoreTS -> Operational

  • Initial profile 2 means you are using the codec combination
  • Initial profile 2048 means you are using the full screen AVC codec

Both configurations gives a good out-of-the-box experience with a high level of quality. The full screen AVC codec implementation is pretty neat because they managed to leverage hardware encoders that normally only supports 4:2:0 encoding to reach a 4:4:4 quality level. While 4:2:0 compression is ideal for video content, 4:4:4 quality is needed to make text and still images sharp without blurry side affects. The full screen AVC codec implementation operates best when encoding can be done in hardware (GPU), it can however work with software based encoding (emulated GPU) but that will result in increased CPU utilization. Good to know is that the new HTML5 based web client always leverages the full screen AVC codec implementation.

(v)GPU
You might have heard that RemoteFX vGPU has been deprecated in Server 2019. Times have changed and GPU virtualization technologies have matured making the API intercept based technologies (like RemoteFX vGPU was) a legacy technology. But no need to get sad about this, because we will get something nice in return: GPU Partitioning or GPU-P for short. It’s still under development but sounds very promising. With this technology multiple virtual machines can leverage the GPU directly (even load balance across multiple GPU’s) and by leveraging the GPU directly Microsoft can move away from the man in the middle role where they needed to maintain the API intercept driver to support new graphic standards. For now we can only leverage the GPU directly by using DDA (GPU pass through) or use GPU virtualization technologies from other vendors.

Windows Virtual Desktop (WVD)
The new GPU-P technology also opens the door for Microsoft to implement this on Azure, which would be a very welcome feature for WVD (the new RDS infrastructure and multi-session Windows 10 edition hosted on Azure). Hopefully Microsoft will not be supporting the GPU-P technology only in Azure like they do with the new multi-session Windows 10 for WVD edition, this will really isolate this technology preventing broader use cases. I don’t think they will be doing this because they pull away RemoteFX vGPU and should provide an alternative for it.

Enable Rdp Windows 10 Home 2004

What happened in a year time with the RDP protocol
With almost every new Windows 10 build the RDP graphics stack is updated, there is not much information you can find about such improvements, but they are certainly there.

While doing some investigation on different Windows 10 builds I noticed the protocol version is matched with the client to enable support for the latest features (both client and servers side). You can find this version numbers in the same eventlog as described in the intro. They look like this:

The client supports version 0xA0400 of the RDP graphics protocol (Build 1709)
The client supports version 0xA0600 of the RDP graphics protocol (Build 1809)

Some of the improvements in the RDP protocol are:

  • Screen regions and content are better classified (to make optimal use of the right codec and compression algorithm)
  • Webcam redirection improvements leveraging H.264
  • Down-scaling for 4K resolutions
  • GPU-P technology (announced) the AVC codec will also benefit from this

Multiple Rdp Windows 10 2004

Time for a test!
I decided to do a simple test using Remote Display Analyzer to look at the improvements and changes Microsoft made to the RDP protocol in a year time. To do this I used 2 different Windows 10 builds: The 1709 and 1809 build (without updates) this will give more a less an indication of the improvements in a year time frame.
Remote Display Analyzer now also supports WVD, but I did not use it in this test because the current WVD private preview only has its RD gateways in the US and it doesn’t make much sense to let traffic flow across the globe. Will do some more testing with WVD later when it’s GA. To check the differences in the RDP protocol between the Windows 10 builds I performed the following test:

  • A direct RDP connection to both builds
  • Connection over LAN using a Windows 10 1809 client
  • Used the out-of-the-box RDP configuration on both builds
  • Both builds running on the same infrastructure
  • The test consists of playing a short video (not full screen) and scrolling some text. Exactly the same has been done on both builds
  • Please note that this was a manual test and it’s always better to automate such tests (I recommend REX analytics for this)
  • This results come without warranty of any kind and are based on my own observations using my own infrastructure. This is only to give you an indication of the differences I observed while performing this test

Windows 10 2004 Rdp Problems

The results are below:

On the left you see the results of running the test on the 1709 build and on the right the results of running the exact same test on the 1809 build. I observed the following:

Rdp Wrapper Windows 10 2004 Github

  • The 1809 build used less bandwidth (almost half) while I didn’t perceived a noticeable difference in frame quality. The send frames are more or less identical
  • The reported “available bandwidth detected” is different across the builds, I’m not sure what the reason for this is, the value of this counter looks a bit inconsistent so I’m not relying to much on this one
  • Overall my perceived user experience on the 1809 build was better (more fluid and snappier screen updates)

Conclusion
While you don’t hear much about it, Microsoft still makes improvements in their remote graphics stack and they should be doing this because it’s one of the most critical success factors of the upcoming WVD platform. The 1809 build performed much better on the LAN then the 1709 build, the lower bandwidth is also great news for WAN scenarios. I’m expecting more protocol improvements inline or shortly after the WVD release, I will certainly keep an eye out on this and will write a new blog post when more information is (publicly) available. Thanks for reading!