Microsoft rolled out a Windows 10 update to Insiders in the Beta and Release Preview Channels yesterday. The update brings PCs to build 19042.789 and includes several fixes. The build also includes all fixes that came in Windows 10 build 19042.782.
Here are the fixes in build 19042.789, as found on a Microsoft blog post:
- We fixed an issue with Microsoft Exchange accounts and some Surface Hub devices that occurs after updating to Windows 10, version 20H2. The message, “Something went wrong” appears, and the error code is 0x80131500.
- We fixed an issue with Windows Update scans that occurs when an authenticated proxy is used as a fallback for the sync service after the previous proxy setting fails.
- We fixed an issue that causes an update from Windows 10, version 1703 to Windows 10, version 20H2 to fail on a Surface Hub device. The message “Getting ready…” remains on the screen indefinitely.
In case you haven’t grabbed build 19042.782 in the past, here are the fixes originally in that build that are also in build 19042.789.
- We updated the default values for the following Internet Explorer registry keys:
- svcKBFWLink = ” ” (empty string)
- svcKBNumber = ” ” (empty string)
svcUpdateVersion = 11.0.1000.
In addition, these values will no longer be updated automatically.
We enabled administrators to disable standalone Internet Explorer using a Group Policy while continuing to use Microsoft Edge’s IE Mode.
- We enabled you to configure certain policies that support Microsoft Edge IE Mode using mobile device management (MDM).
- We fixed an issue in the Universal C Run-time Library (UCRT) that causes printf() to incorrectly round floating point values.
- We fixed an issue that displays a User Account Control (UAC) dialog box unexpectedly when you turn on speech recognition.
- We fixed an issue that fails to notify the target application when you select the Copy link command on the Share menu.
- We fixed an issue that causes the 64-bit fmod() and remainder() functions to damage the Floating Point Unit (FPU) stack.
- We fixed an issue that causes a stop error or causes a device to stop responding when you play a game in full-screen or tablet mode.
- We fixed an issue with using Ctrl+Caps Lock and Alt+Caps Lock to switch to Hiragana or Katakana mode respectively after upgrading to Windows 10, version 2004.
- We fixed an issue that prevents you from opening a document that is on the Windows desktop and generates the error, “The directory name is invalid.” This issue occurs after changing the desktop location in the Location tab of the Desktop Properties dialog box (File Explorer -> This PC -> Desktop).
- We fixed an issue that creates duplicate cloud provider folders in the File Explorer navigation pane.
- We fixed an issue that occurs when the Mandatory Profile check box is selected when you copy a user profile.
- We fixed an issue that might cause the Alt+Tab order to change unexpectedly and cause you to switch to the wrong window.
- We fixed an issue that prevents ImmGetCompositionString() from returning the white space for furigana when using the Japanese Input Method Editor (IME).
- We fixed an issue with some special key combinations used in DaYi, Yi, and Array IMEs that might cause an application to stop working.
- We fixed an issue that displays a blank lock screen after a device wakes up from Hibernate.
- We corrected historical daylight savings time (DST) information for the Palestinian Authority.
- We added support for serial number control using the registry.
- We fixed an issue that incorrectly deactivates some Windows 10 Education devices after upgrading to Windows 10, version 2004.
- We fixed an issue that causes the upload of diagnostic logs to a management service, such as Microsoft Intune, to fail. The failure occurs because of a network time-out on a slow network.
- We displayed a notification to a user when an administrator signs in to an MDM service, such as Microsoft Intune, to find the location of a managed device.
- We fixed an issue that prevents users from using their smart card credentials when the user hint is the domain credential name (domainusername).
- We fixed an issue in which using local Service for User (S4U) affects Data Protection API (DPAPI) credential keys and causes users to sign out unexpectedly.
- We fixed an issue that causes the silent mode deployment of BitLocker to fail with the error 0x80310001. This issue occurs when deploying BitLocker encryption to Hybrid Azure Active Directory (Azure AD) joined devices.
- We fixed an issue that might cause a black screen to appear 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 might cause systems that use BitLocker to stop working with the error 0x120 (BITLOCKER_FATAL_ERROR).
- We fixed an issue that causes a device to stop working when deploying Microsoft Endpoint Configuration Manager if AppLocker is enabled on the device.
- We fixed an issue that cause the LSASS.exe process to leak memory on a server that is under a heavy authentication load when Kerberos Armoring (Flexible Authentication Secure Tunneling (FAST)) is enabled.
- We fixed an issue that causes LSASS.exe to stop working because of a race condition that results in a double free error in Schannel. The exception code is c0000374, and the Event Log displays Schannel event 36888, fatal error code 20, and error state 960. This issue occurs after installing Windows updates from September 2020 and later.
- We fixed a memory leak issue that occurs when you authenticate a client certificate on servers that are configured as domain controllers.
- We fixed an issue with Virtual Interrupt Notification Assert (VINA) interrupts.
- We fixed an issue with HTTP caching that interferes with kiosk mode that targets Azure AD groups.
- We fixed an issue that occurs when a Volume Shadow Copy Service (VSS) snapshot triggers on virtual machines (VM) that contain Resilient File System (ReFS) volumes. The triggered VSS snapshot fails with a time-out and prevents access to the ReFS volume for 30 minutes.
- We fixed an issue that incorrectly logs Extensible Storage Engine Technology (ESENT) event 642 in the Application Event Log.
- We fixed an issue with Administrative Template settings you configure using a Group Policy Object (GPO). When you change the value of the policy settings to NOT CONFIGURED, the system fails to remove the previous settings. This issue is most noticeable with roaming user profiles.
- We fixed an issue that might cause a deadlock in Windows Virtual Desktop when a user disconnects before a driver fully loads
- We fixed an issue that fails to show Extract all on the shortcut menu when you right-click an online-only ZIP file.
- We updated the process for enrolling in online speech recognition. If you are already enrolled, you will see a message that asks you to review the new settings. If you choose not to contribute your speech data for human review, you can still use online speech recognition. The new settings contain one button to turn on online speech recognition and another button that turns on the collection of your voice clips. If you turn on the collection of your voice clips, you can turn it off at any time using the same button in the new settings page.
- We fixed an issue that prevents the Start menu, Cortana, and tiles pinned to the Taskbar from opening. This issue occurs when an administrator copies an existing profile that has the Mandatory Profile check box selected.
You can grab the latest build from Windows Update now if you’re in the Release Preview or Beta Channels.
This post was written by Sean Endicott and was first posted to WindowsCentral
Do you find this article helpful? Your Friend might too. So, please Share it with them using the Share button above.
Will you like to get notified when I post new updates? Then Follow me on any of my social media handles: Google News, Telegram, WhatsApp, Twitter, Facebook, Pinterest.
You can also drop your email address below if you wish to be notified by mail.