Microsoft releases Windows 10 builds 19043.1320, 19042.1320 – here’s what’s new

It’s that time of the month when Microsoft is releasing new optional cumulative updates for Windows 10. Today, the updates are available for all versions of the OS that are supported for consumers, meaning Windows 10 versions 21H1, 20H2, and 2004.

Of course, given the nature of those updates, they all get the exact same bits. If you’re on one of those versions, or if you’re an Insider on Windows 10 version 21H2, you’re going to get KB5006738. For versions 21H2, 21H1, 20H2, and 2004, it brings the build number to 19044.1320, 19043.1320, 19042.1320, and 19041.1320, respectively.

You can manually download it here, and these are the highlights:

Here’s the full list of fixes:

  • Addresses an issue that prevents you from accessing the pre-provisioning page during the out-of-box experience (OOBE). This issue occurs when the credentials page for signing in to Azure Active Directory appears, and you press the Windows key five times.

  • Adds a feature that facilitates certain cross-browser data transfers.
  • Addresses an issue with Assigned Access kiosks that are configured with Microsoft Edge as a kiosk application. These kiosks might sometimes fail to restart Microsoft Edge if users close the browser window.
  • Addresses an issue in which the use of App-V intermittently causes black screens to appear when signing in on the credentials page.
  • Addresses an issue that might prevent subtitles from displaying for certain video apps and streaming video sites.
  • Addresses an issue that prevents Windows 10 virtual private network (VPN) users from connecting to Windows Server 2019 Routing and Remote Access service (RRAS) servers.
  • Addresses an issue that prevents Software-Defined Networking (SDN) virtual machines from working when you configure the Generic Routing Encapsulation (GRE) VPN bandwidth limitation.
  • Addresses a Primary Refresh Token (PRT) update issue that occurs when VPN users sign in using Windows Hello for Business when the VPN connection is offline. Users receive unexpected authentication prompts for online resources that are configured for user sign-in frequency (SIF) in Azure Active Directory-Conditional Access.
  • Addresses an issue that causes Windows to go into BitLocker recovery after a servicing update.
  • Addresses an issue that might cause Kerberos.dll to stop working within the Local Security Authority Subsystem Service (LSASS). This occurs when LSASS processes simultaneous Service for User (S4U) user-to-user (U2U) requests for the same client user.
  • Addresses an issue in Code Integrity that might cause a memory leak.
  • Enhances Microsoft Defender for Endpoint’s ability to identify and intercept ransomware and advanced attacks.
  • Addresses an issue in the OOBE that might cause Windows AutoPilot provisioning to fail.
  • Addresses an issue that prevents Kana input mode users from inserting a question mark (?) using the Shift-0 key combination.
  • Addresses an issue that sometimes causes the lock screen to appear black if you set up slideshow.
  • Addresses a reliability issue with LogonUI.exe, which affects the rendering of the network status text on the credentials screen.
  • Addresses an issue that causes Server Message Block (SMB) Query Directory Requests to fail when the buffer size is large.
  • Addresses a memory leak issue in lsass.exe on domain controllers in the forest root domain that occurs when you have multiple forests and multiple domains in each forest. The SID-Name mapping functions leak memory when a request comes from another domain in the forest and crosses forest boundaries.
  • Addresses an issue with the virtual machine (VM) Load Balancing feature, which ignores a site’s fault domain.
  • Addresses a known issue that might prevent the successful installation of printers using the Internet Printing Protocol (IPP).

There are a few known issues in this update. One is that if you have a custom offline installer, you’ll see that the Edge Legacy browser is removed, but it might not have been replaced by the new Edge. Also, there was an issue with an update in June where there were issues with installing future updates after that. Luckily, there’s a workaround.

As usual, these are optional updates. That means that you’ll be able to find them in Windows Update, but if you don’t, you won’t be forced to take them. These fixes will then be rolled into the Patch Tuesday cumulative update, which is mandatory and will be installed while your PC is idle.

The next major feature update, the Windows 10 November 2021 Update, should be available soon. Given the name, it could arrive as early as next week.

Leave a Comment