Microsoft updated the optional update, the KB 4580364 again. This increases the new build number to Windows 10 20H2 19042.610, or Windows 10 2004 19041.610.
- Introducing “Discuss Now” in the Windows 10 Taskbar Earlier this year, we introduced ourselves in Skype. With “Discuss Now” it’s easy to stay connected with people for free in just two clicks, and each call can take up to 24 hours. Today, we’re happy to announce that we’re going to extend this feature in Windows 10 by bringing the meeting directly to the taskbar now. Over the nextfew weeks, you can easily set up a video call and reach friends and family members in no time by clicking the “Discuss Now” icon in the notification area of the taskbar. No registration or downloads required.
- Updates an issue that causes a device to stop responding after using a pen for several hours.
Known issues with this update
Users of the Microsoft Input Method Editor (IME) for Japanese or Chinese languages may experience problems trying to perform various tasks. You may have problems typing, get unexpected results, or you may not be able to type text.
For more information about the issues, problem bypass steps, and the issues that are currently being resolved, see KB4564002
- We fixed an issue when using Group Policy preferences to configure the home page in Internet Explorer.
- We’ve given administrators the option to use Group Policy to enable the Save Target As option for users in Microsoft Edge IE mode.
- We fixed an issue with untrusted URL navigation from Internet Explorer 11 by opening it in the Microsoft Defender Application Guard with Microsoft Edge.
- We fixed an issue that occurs when using the full suite of developer tools in Microsoft Edge for remote debugging on a Windows 10 device.
- We fixed an issue where nothing appears on the screen for five minutes or more during the Remote Desktop Protocol (RDP) session.
- We’ve fixed an issue that prevents certain Windows Virtual Desktop (WVD) users from searching for files using File Explorer.
- We fixed an issue that causes a device to stop responding after using a pen for several hours.
- We fixed an issue that causes an application to temporarily stop responding, causing additional z-order operations that affect a window’s Topmost property.
- We’ve fixed an issue that may cause DDE applications to stop working.
- We fixed an issue that causes the ImmGetCompositionString() function to return the full-width hiragana when using the Microsoft Input Method Editor (IME) for Japanese, rather than returning the katakana in half width.
- We’ve fixed an issue that occurs when you first sign in to an account or unlock an existing user session using Remote Desktop Services (RDS). If you enter an incorrect password, the current keyboard layout unexpectedly changes to the system’s default keyboard layout. This change in the keyboard layout can cause additional logon attempts to fail or result in account lockouts in domains with low account lockout thresholds.
- We fixed an issue that shows the wrong CPU frequency for certain processors.
- We have fixed a performance issue that occurs when PowerShell reads the registry to verify that the ScriptBlockLogging registry key is included in the registry.
- We’ve fixed an issue where the time offset of the time format returned by the exe OS Get localdatetime/ value command is randomly changed.
- We fixed an issue that prevents Microsoft User Experience Virtualization (UE-V) from assigning Microsoft Outlook signatures.
- We fixed an issue that prevents devices connected with Hybrid Azure Active Directory from updating portal information when a device name or version of Windows changes.
- We’ve fixed an issue that might prevent the Smart Cards for Windows service from starting.
- We’ve added a new Microsoft Event Tracing for Windows (ETW) provider called Microsoft Antimalware UacScan. This ETW provider reports the details of the context for each user account control (UAC) request in the ETW provider’s manifest.
- We fixed an issue with Virtual Private Network (VPN) connections that use a secured password (EAP-MSCHAP v2) to authenticate and have enabled the “Automatically use my Windows logon user name and password” property. When you connect to this type of VPN, an authentication dialog incorrectly prompts you for your credentials.
- We now view recovery partitions in the Diskpart utility.
- We fixed an issue that causes stop error 0xd1 in sys. This problem occurs when certain arrays are moved from one cluster node to another.
- We fixed an issue that causes the IAutomaticUpdatesResults::get_LastInstallationSuccessDate method to return 1601/01/01 if there are no active updates.
- We’ve added support for the Transport Layer Security (TLS) 1.1 and 1.2 protocols when connecting to SQL Server through the data providers in Windows Defender Application Control (WDAC).
- We fixed a problem with SQL Server that can cause performance issues if you configure a Linked Server provider to load outside the process.
- We have fixed an issue that can affect Windows performance and prevent lanmanServer service from starting if third-party software uses LanmanServer Custom File System Controls (FSCTL).
- We fixed a deduplication issue that causes long waits for Resilient File System (ReFS) Cluster Shared Volumes (CSV).
- We fixed an issue that might prevent some applications from behaving correctly. This occurs when you publish them as Remote Application Integrated Locally (RAIL) applications using Remote Desktop Services (RDS) and change the docking for an AppBar.
- We fixed a problem with a deadlock in the Transmission Control Protocol /Internet Protocol (TCPIP) driver that causes the operating system to stop working or to stop responding.
- We fixed an issue that causes the Routing and Remote Access Service (RRAS) to stop responding on new connections. However, RRAS continues to work for existing connections.
- Fixed an issue that causes the RRAS administrator to stop responding randomly to Microsoft Management Console (MMC) when you perform administrative tasks or at startup.
- We fixed an issue when starting Windows Subsystem for Linux 2 (WSL2) on ARM64 devices that occurs after installing KB4579311.
- In addition to the fixed problems, which were already corrected in the *.608, there was also:
- We fixed an issue that caused the Docker pull operation to fail. This problem occurs because of a code integrity (CI) policy that blocks the import of a Windows container image.