Microsoft releases Win10 19044.2075 version: fixes the huge amount of bugs

Microsoft today pushed Windows 10 21H2 internal version 19044.2075 (KB5017380) to Windows Preview Experience Channel, mainly to fix several bugs and add five new features, similar to the new version of Win11 22000.1041.

This update includes the following improvements:

• We have turned off Transport Layer Security (TLS) 1.0 and 1.1 by default in Microsoft browsers and applications.
• Added the ability to search for news and interest plugins on the taskbar, which you can set up via Settings > Personalization > Taskbar > News and Interests, or by directly right-clicking on the taskbar and selecting Taskbar Settings.
• News and interests are supported in all taskbar orientations. Either top left or right taskbar will work fine.
• We have introduced the network authentication redirection feature. When you use Remote Desktop, it allows you to authenticate on software and web pages without a password. However, you will need to use Windows Hello or a secure device such as a Fast ID 2.0 (FIDO2) key.
• We introduced the feature that lets you use Azure Active Directory (AD) authentication to log in to Windows using Remote Desktop. You can then use Windows Hello or a secure device, such as a Fast Identity Online 2.0 (FIDO2) key, to remotely log in. It also supports the use of conditional access policies.
• IT House learned that the bug fixes are basically the same as in the latest update to the Win11 Release Preview.
• We fixed an issue that required reinstalling an app if it was not signed by the Microsoft Store.
• We fixed an issue that prevented MSIX updates from being installed from the same URL.
• We have fixed an issue that prevented codec updates from the Microsoft Store.
• We have fixed an issue affecting security key cache credentials and Fast Identity Online 2.0 (FIDO2) authentication. On hybrid domain-connected devices, the system would delete these cached credentials.
• We have fixed an issue that affects network static IPs. This issue caused inconsistent static IP configurations. As a result, NetworkAdapterConfiguration () would occasionally fail.
• We have fixed an issue that affects Desktop Window Manager (DWM) rendering. This issue could cause your device to stop responding in a virtual machine setup when you are using certain video graphics drivers.
• We fixed a rare stopping error that occurs when you change the display mode and multiple displays are in use.
• We fixed an issue affecting graphics drivers that use d3d9on12.dll.
• We have fixed a problem with forcing IE mode tabs to reload in a session.
• We have fixed a problem affecting JavaScript-generated URLs: URLs. when you add these URLs to the Favorites menu in IE mode, they do not work properly.
• We have fixed a problem that affects windows. Open IE mode.
• We have fixed a problem with successfully opening a browser window in IE mode to display a PDF file. Afterward, browsing to other IE mode sites within the same window would fail.
• We have introduced a group policy to enable and disable Microsoft HTML Application (MSHTA) files.
• We have fixed an issue affecting the Microsoft Japanese Input Method Editor (IME). Text conversion fails when using some third-party virtual desktops.
• We have fixed an issue affecting the App-V client service. The service leaks memory when deleting App-V registry nodes.
• We have fixed an issue where the default printer may be changed if the printer is a network printer.
• We have fixed an issue affecting the ProjectionManager. startProjectingAsync API. this issue prevented some regions from connecting to Miracast sinks.
• We have fixed an issue that affects Group Policy objects. As a result, the system may stop working.
• We have fixed an issue that affects the Windows Security Center Application Control (WDAC) path rules.
• We have fixed an issue that may bypass WDAC’s MSHTML and ActiveX rules.
• We have fixed an issue that causes WDAC to log 3091 and 3092 events in audit mode.
• We have fixed an issue that affects Windows Defender Application Control (WDAC). It prevented WDAC from logging .net dynamic code trust validation failures.
• We have fixed an issue that affects WDAC policies. If you enable SecureLaunch on a device, the WDAC policy will not be applied to that device.
• We have fixed an issue that occurs when WDAC policies fail to load. The system logs this failure as an error, but the system should log the failure as a warning.
• We have fixed an issue that affects non-windows devices. It prevented these devices from authenticating. This issue occurs when a user connects to a windows-based remote desktop and authenticates using a smart card.
• We have fixed a problem that sometimes causes explorer.exe to stop working when opened.
• We have fixed a problem affecting the Microsoft Japanese input method when it is active and the input method mode is on. When you insert a dash (-) character using the numeric keypad, IME would insert the wrong dash.
• We fixed an issue that affected the rendering of the search box. It was not rendering correctly if you logged in using table mode.
• We have fixed an issue affecting the FindNextFileNameW () function. It may leak memory.

• We have fixed an issue that affects robot replication. Robocopy could not set the file to the correct modification time when using the / IS an option.
• We have fixed an issue that affects the LanmanWorkstation service. When you mount a network drive, it leaks memory.40366335 Risk Waiting.
• We have fixed an issue that affects roaming user profiles. Some of your settings would not be restored after you logged in or logged out.
• We have fixed a known issue affecting the XML Paper Specification (XPS) viewer. This could prevent you from opening XPS files in some non-English languages. This included some Japanese and Chinese character encoding. This issue affects XPS and Open XPS (OXPS) files.
• We have fixed a known issue that affects Chilean daylight saving time. This issue may affect the time and date used for meetings, applications, tasks, services, transactions, etc.