banner



Windows 10 20H2 build 19042.487 now rolling out in the Beta and Release Channel

Microsoft is today rolling out a new build of the upcoming Windows ten 20H2 release to both the Beta and Release Channel's today. This is the fifth 20H2 build for the Beta Channel, just the first one for the Release Channel. 20H2 is the next big Windows x update that features UI improvements to the Offset menu and notifications UI. It's as well the kickoff version of Windows 10 to take the new Microsoft Border preinstalled past default.

20H2 making its way to the Release Channel means the update is almost set to become. It's probable that we'll see 20H2 begin rolling out sometime in September, meaning we're pretty shut to full general availability.

Today's build includes the following improvements over the previous 20H2 builds:

  • Nosotros stock-still an effect with pinned Add together-ins that cause Microsoft Outlook to become unresponsive.
  • We now provide the ability to sync the Microsoft Border IE Mode unidirectional session cookie when an administrator configures the session cookie.
  • We stock-still an issue with rendering PeerDist-encoded content in Internet Explorer and Microsoft Border.
  • We fixed an issue that might forestall ActiveX content from loading.
  • We stock-still an issue that displays a black screen to Windows Virtual Desktop (WVD) users when they try to sign in.
  • We fixed an result that might cause apps that use the custom text wrapping part to cease working in sure scenarios.
  • We fixed an issue with Offset menu apps and tiles in virtual desktop infrastructure (VDI) environments. The issue occurs after you lot sign in to the VDI environs a second time and use a Remote Desktop User Profile Deejay in a non-persistent virtual desktop pool.
  • We fixed an upshot that generates an fault when printing to a document repository.
  • We stock-still an outcome that prevents Visual Basic 6.0 (VB6) applications from using ListView in OCXafter upgrading to Windows 10, version 1903 and later.
  • We fixed a runtime error that causes VB6 to cease working when duplicate windows messages are sent to WindowProc().
  • Nosotros fixed an issue that causes a terminate fault when the initialization of the graphics adapter fails.
  • We stock-still an issue to reduce the likelihood of missing fonts.
  • We fixed an issue that prevents users from reducing the size of a window in some cases.
  • We fixed an issue that causes the touch keyboard to close when you touch any key.
  • Nosotros stock-still an consequence that adds an unwanted keyboard layout every bit the default after an upgrade or migration even if y'all take already removed the layout.
  • Nosotros fixed an result the prevents applications from closing fifty-fifty though programming code directs them to close.
  • We fixed an issue that causes attempts to take a screenshot of a window using the PrintWindow API to fail.
  • We fixed an event with a memory leak in exe that occurs when you refresh an application that has an editable box.
  • Nosotros fixed an effect that truncates a potential list of characters (candidates) when you type characters in the Simplified Chinese (Pinyin) input method editor (IME). When this happens, Chinese characters practise non appear.
  • We fixed an outcome that prevents the commencement cardinal stroke from beingness recognized correctly in the DataGridView
  • We stock-still an issue that causes an awarding that uses dll to stop working, and the 0xc0000005 (Admission violation) exception appears.
  • We fixed an effect with Dynamic Data Substitution (DDE) that causes a memory leak when multiple clients connect to the same server.
  • We fixed an issue that prevents Cortana Smart lighting from working as expected if you shut down the auto while Fast Shutdown is enabled.
  • Nosotros now provide the ability for Dolby Atmos for Headphones and DTS Headphone: X to be used in 24-fleck mode on devices that back up 24-bit audio.
  • We fixed an issue that prevents the IME user dictionary from being used when leveraging folder redirection with user profiles.
  • Nosotros fixed an issue that causes Microsoft Office applications to close unexpectedly when using a Korean IME.
  • We fixed an effect that displays incorrect binder properties in File Explorer when the path is longer than MAX_PATH.
  • We stock-still an effect with a blurry sign in screen.
  • Nosotros fixed an outcome with Windows Update condign unresponsive when checking for updates.
  • We fixed an event that prevents the correct lock screen from actualization when the post-obit policies are set:
  • Policy "Interactive Logon: Practice not require Ctrl+Alt+Del" set to "Disabled"
  • HKLM\SOFRWARE\Policies\Microsoft\Windows\System
  • DisableLockScreenAppNotifications = 1
  • DisableLogonBackgroundImage = 1
  • We fixed an issue that causes File Explorer to stop working when you browse directories of raw images and other file types.
  • We have improved the tablet experience for convertible or hybrid devices in docked scenarios.
  • We accept improved the user experience of the Windows Hello enrollment pages for face and fingerprint setup.
  • Nosotros forestall accounts from a different tenant from signing in to a Surface Hub device.
  • We accept updated the fourth dimension zone information for the Yukon, Canada.
  • We fixed a stop mistake 0xC2 in sys.
  • Nosotros take stock-still an issue that causes the Issue Viewer Microsoft Management Console (MMC) to stop working when the secondary monitor is above the primary monitor. An out of bounds exception appears.
  • Nosotros have stock-still an issue that prevents the migration of the Windows Remote Management (WinRM) service startup type.
  • Nosotros have fixed an issue with object performance counters.
  • We accept stock-still an issue that prevents Microsoft User Feel Virtualization (UE-V) settings from roaming to enable the signature files that are used for new messages, forwarded messages, and replies.
  • We have fixed an outcome that prevents users from setting the REG_EXPAND_SZkeys in some automated scenarios.
  • We have fixed an event with the EnhancedAppLayerSecurity node in modern device management (MDM) that prevents its setting from beingness applied correctly to customer devices.
  • We have fixed an outcome that causes a memory leak in the exeprocess when the server is under a heavy authentication load and Credential Guard is enabled.
  • We have fixed an issue that might cause a delay of upwards to two minutes when signing in or unlocking a session on Hybrid Azure Active Directory-joined machines.
  • Nosotros accept fixed an consequence that prevents hash signing from working correctly when using the Microsoft Platform Crypto Provider for Trusted Platform Modules (TPM). This event might also touch on networking software, such as virtual private network (VPN) applications.
  • We accept fixed an issue that continues to brandish the previous username hint in the smart card sign in box subsequently a different user has used the automobile with domain credentials.
  • Nosotros have stock-still an issue that causes communication with the TPM to time out and fail.
  • We accept stock-still an issue that sometimes prevents AppLocker from running an application whose publisher rule allows it to run.
  • We have fixed an issue in which AppLocker publisher rules might sometimes foreclose applications from loading software modules; this can cause partial awarding failure.
  • We have fixed an outcome that causes the promotion of a server to a domain controller to fail. This occurs when the Local Security Say-so Subsystem Service (LSASS) procedure is set as Protected Process Light (PPL).
  • Nosotros have stock-still an issue that prevents you from unlocking a device if yous typed a space before the username when you first signed in to the device.
  • We have stock-still an result that causes a organization to stop working and generates a 7E stop lawmaking.
  • We have stock-still an consequence that causes applications to take a long time to open.
  • We take fixed classification failures caused past the wrong User Main Proper noun (UPN).
  • We accept fixed an result in cluster scenarios that causes handles to .vmcx and .vmrs files to become invalid later storage failover. Every bit a consequence, live migration and other virtual machine (VM) maintenance activities fail with STATUS_UNEXPECTED_NETWORK_ERROR.
  • We accept fixed an issue with interrupt targeting that might cause an interrupt to arrive at an wrong processor.
  • We accept fixed an effect that causes delays during shutdown when running the Microsoft Keyboard Filter Service.
  • We accept fixed an issue that causes a machine to request a new IP address after authentication.
  • We fixed an consequence that causes the Background Intelligent Transfer Service (Bits) to download data while a device is in cellular mode without explicit user permission.
  • We fixed an upshot that prevents Always On VPN (AOVPN) from automatically reconnecting when resuming from Sleep or Hide.
  • We fixed an result that causes AOVPN user tunnels to use an incorrect certificate.
  • We fixed an issue with AOVPN that occurs when user and device tunnels are configured to connect to the same endpoint.
  • Nosotros fixed an issue that causes VPN apps to stop working in some cases when they endeavour to enumerate VPN profiles.
  • We stock-still an issue that causes the Optimize Drives dialog to incorrectly written report that previously optimized drives need to be optimized again.
  • We fixed an issue that fails to plough off the host memory buffer (HMB) when you force the shutdown of a device. As a result, solid-state drives (SSDs) do non delete HMB contents.
  • We fixed an issue that prevents apps from downloading an update or opening in sure scenarios.
  • Nosotros stock-still an issue that might cause a stop error (0xC00002E3) at startup. This issue occurs after installing certain Windows Updates that were released on or later on April 21, 2022.
  • We fixed an outcome that might cause end fault 7E in syson servers running the Network File System (NFS) service.
  • We stock-still an issue with Server Message Block (SMB). This issue incorrectly logs the Microsoft-Windows-SMBClient 31013 event in the Microsoft-Windows-SMBClient/Security event log of an SMB client when an SMB server returns STATUS_USER_SESSION_DELETED. This issue occurs when SMB client users or applications open up multiple SMB sessions using the same set of Transmission Control Protocol (TCP) connections on the aforementioned SMB Server. This issue most likely occurs on Remote Desktop Servers.
  • We stock-still an issue that causes SMB to incorrectly apply the original, cached not-Continuous Bachelor handle to a file. This handle becomes invalid after a network error or storage failover. Every bit a result, applications fail with errors such as STATUS_UNEXPECTED_NETWORK_ERROR.
  • We fixed an issue that causes the loss of written data when an application opens a file and writes to the end of the file in a share folder.
  • We fixed an issue with some apps, such every bit Microsoft Excel, that occurs when using the Microsoft Input Method Editor (IME) for Chinese and Japanese languages. You might receive an fault, or the app might stop responding or shut when you attempt to drag using the mouse.

Source: https://www.windowscentral.com/windows-10-20h2-build-19042487-now-rolling-out-beta-and-release-channel

Posted by: johnsonsniters.blogspot.com

0 Response to "Windows 10 20H2 build 19042.487 now rolling out in the Beta and Release Channel"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel