KB5043050: Addressing Remote Desktop known issue and other Bug fixes
September 10, 2024—KB5043050 (OS Build 17763.6293)
Highlights
This update addresses security issues for your Windows operating system.
Improvements
This security update includes improvements. Below is a summary of the key issues that this update addresses when you install this KB. If there are new features, it lists them as well. The bold text within the brackets indicates the item or area of the change we are documenting.
- [AppContainer] Printers do not work as you expect when you use them in a restricted setting, like AppContainer.
- [BitLocker] You might not be able to decrypt a BitLocker data drive. This occurs when you move that drive from a newer version of Windows to an older version.
- [Remote Desktop (known issue)] Windows Servers might disrupt Remote Desktop connections across your company. This issue might occur if you use a legacy protocol in the Remote Desktop Gateway. An example protocol is Remote Procedure Call over HTTP. If the issue occurs, it is sporadic, like every 30 minutes. At that point, you lose sessions that you are signed in to. Then you must reconnect to the server. IT admins can track this as an end to the TSGateway service. It stops responding, with the exception code 0xc0000005.
- [Windows Installer] When it repairs an application, the User Account Control (UAC) does not prompt for your credentials. After you install this update, the UAC will prompt for them. Because of this, you must update your automation scripts. Application owners must add the Shield icon. It indicates that the process requires full administrator access. To turn off the UAC prompt, set the HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\Installer\\DisableLUAInRepair registry value to 1. The changes in this update might affect automatic Windows Installer repairs; see Application Resiliency: Unlock the Hidden Features of Windows Installer.
- [Windows Server 2019 (known issue)] Some devices slow down, stop responding, and have high CPU usage. This is most likely to occur with Cryptographic Services. A few companies report that the issue occurs when antivirus software scans the %systemroot%\\system32\\catroot2 folder for Windows updates.