Author Topic: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)  (Read 27544 times)

0 Members and 1 Guest are viewing this topic.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #15 on: December 08, 2020, 04:48:13 PM »
Windows Insider Preview Build 19042.685 Released to the Beta and Preview Builds (20H2):  Announcing Windows 10 Insider Preview Build 19042.685 (20H2) | Windows Insider Blog.

This security update includes quality improvements. Key changes include:
  • We fixed a security vulnerability by preventing applications that run as a SYSTEM account from printing to “FILE:” ports. To address this issue in the future, make sure your applications or services run as a specific user or service account.
  • Security updates to Microsoft Edge Legacy, the Microsoft Graphics Component, Windows Media, Windows Fundamentals, and Windows Virtualization.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #16 on: January 12, 2021, 06:01:40 PM »
Windows Insider Preview Build 19042.746 Released to the Beta and Preview Builds (20H2):  Releasing Windows 10 Build 19042.746 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.

This security update includes quality improvements. Key changes include:
  • We fixed a security vulnerability issue with HTTPS-based intranet servers. After installing this update, HTTPS-based intranet servers cannot, by default, use a user proxy to detect updates. Scans using these servers will fail if you have not configured a system proxy on the clients. If you must use a user proxy, you must configure the behavior using the policy “Allow user proxy to be used as a fallback if detection using system proxy fails.” To ensure the highest levels of security, also use Windows Server Update Services (WSUS) Transport Layer Security (TLS) certificate pinning on all devices. This change does not affect customers who are using HTTP WSUS servers. For more information, see Changes to scans, improved security for Windows devices.
  • Addresses a security bypass vulnerability that exists in the way the Printer Remote Procedure Call (RPC) binding handles authentication for the remote Winspool interface. For more information, see KB4599464.
  • Security updates to Windows App Platform and Frameworks, Windows Media, Windows Fundamentals, Windows Cryptography, Windows Virtualization, Windows Peripherals, and Windows Hybrid Storage Services.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #17 on: January 21, 2021, 08:45:50 PM »
Windows Insider Build 19042.782 (20H2) (KB4598291) Released to Beta and Release Preview Channels:  Releasing Windows 10 Build 19042.782 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.

This update includes the following fixes and improvements:
  • 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 (domain\username).
  • 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.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #18 on: January 26, 2021, 05:51:32 PM »
Windows Insider Build 120.2212.2020.0 Released to Beta Channel:  Releasing Windows Feature Experience Pack 120.2212.2020.0 to the Beta Channel | Windows Insider Blog.

The update is the Windows Feature Experience Pack, in particular, improving the reliability of screen snipping experience, especially with apps that access the clipboard often.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #19 on: February 02, 2021, 09:07:45 PM »
Windows Insider Build 19042.789 (20H2) Released to Beta and Release Preview Channels:  Releasing Windows 10 Build 19042.789 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.

This update includes all the fixes in 20H2 Build 19042.782 plus the following additional fixes:
  • 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.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #20 on: February 09, 2021, 04:38:56 PM »
Windows Insider Build 19042.804 (20H2) Released to Beta and Release Preview Channels:  Releasing Windows 10 Build 19042.804 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.

This security update includes quality improvements and the following key changes:
  • We fixed a possible elevation of privilege vulnerability in the win32k component.
  • We fixed an issue that might damage the file system of some devices and prevent them from starting up after running chkdsk /f.
  • We fixed a security vulnerability by preventing applications that run as a SYSTEM account from printing to “FILE:” ports. To address this issue in the future, make sure your applications or services run as a specific user or service account.
  • Security updates to the Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Cloud Infrastructure, Windows Management, Windows Authentication, Windows Fundamentals, Windows Cryptography, Windows Virtualization, Windows Core Networking, and Windows Hybrid Cloud Networking.
For more information about the resolved security vulnerabilities, please refer to the new Security Update Guide website.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #21 on: February 17, 2021, 08:47:29 PM »
Windows Insider Build 20H2 Build 19042.844 (KB4601382) Released to the Beta Release Preview Channels and Windows 10 Insider Preview Build 19043.844 (21H1) Releasing Windows 10 Build 19042.844 (20H2) to Beta and Release Preview Channels | Windows Insider Blog.  See the blog post for the very long list of fixes and improvements.

and

Windows 10 Insider Preview Build 19043.844 (21H1) Released to Insiders in the Beta Channel only who are interested in moving up to 21H1:  Announcing Windows 10 Insider Preview Build 19043.844 (21H1) | Windows Insider Blog.

This Build is being released to build to Insiders in the Beta Channel via the “seeker” experience in Windows Update. This means Insiders in the Beta Channel will need to go to Settings > Update & Security > Windows Update and choose to download and install 21H1.  The Build includes all of the fixes and improvements of Build 19042.844, referenced above, as well as the new features referenced in Introducing the next feature update to Windows 10, version 21H1 | Windows Experience Blog.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #22 on: February 24, 2021, 04:07:33 PM »
Windows Inside Preview Build 21322 Released to Insiders on the Preview Channel:  Announcing Windows 10 Insider Preview Build 21322 | Windows Insider Blog.

Fixes
  • We fixed an issue where if you tried to access an Azure Active Directory (AAD) joined device via Remote Desktop (RDP), it would fail after updating to recent Dev Channel builds.
  • We fixed an issue that could result in your PC bugchecking when switching between users.
  • We fixed an issue that could result in deleted files unexpectedly remaining visible on the desktop until the desktop was refreshed.
  • [News and interests] We fixed an issue where the taskbar button might show no content after the primary monitor was changed.
  • [News and interests] We fixed an issue where news and interests would continue to refresh content in the background even when the screen was turned off, consuming resources.
  • [News and interests] We fixed multiple issues impacting performance and reliability.
  • We fixed an issue with the new “Paste as plain text” option in clipboard history where clipboard history didn’t close after it was used, inconsistent with the normal paste behavior.
  • We fixed an issue that could result in erroneous torn write errors being logged.
  • We fixed an issue that could result in delayed audio playback on certain devices in the last few builds.
  • We fixed an issue where if you changed the calendar format multiple times under Settings > Date & Time > Region, the enumerated values of the other data formats may not be correct.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #23 on: March 02, 2021, 08:55:08 PM »
Update to Releasing Windows 10 Build 19042.844 (20H2) to Beta and Release Preview Channels | Windows Insider Blog:

Quote
UPDATE 3/2: 21H1 is now being offered as a recommended update to all Windows Insiders in the Beta Channel. Insiders who previously didn’t choose to install 21H1 will now automatically receive 21H1 in the Beta Channel.

Hello Windows Insiders, today we are announcing Windows 10 version 21H1 as the next feature update for Windows 10. As part of today’s announcement, we’re also releasing 21H1 Build 19043.844 (KB4601382) to the Beta Channel.

We are releasing this build to the Beta Channel via our “seeker” experience in Windows Update. This means Insiders in the Beta Channel will need to go to Settings > Update & Security > Windows Update and choose to download and install 21H1.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #24 on: March 09, 2021, 05:58:49 PM »
Windows Insider Preview Build 19043-867 (21H1) Released to Insiders in the Beta Channel:  Releasing Windows 10 Build 19043.867 (21H1) to Beta Channel | Windows Insider Blog.

This is a security update and quality improvement update with the following key changes:
  • We fixed an elevation of privilege security vulnerability documented in CVE-2021-1640 related to print jobs submitted to “FILE:” ports. After installing Windows updates from March 9, 2021 and later, print jobs that are in a pending state before restarting the print spooler service or restarting the OS will remain in an error state. Manually delete the affected print jobs and resubmit them to the print queue when the print spooler service is online.
  • Security updates to the Windows Shell, Windows Fundamentals, Windows Management, Windows Apps, Windows User Account Control (UAC), Windows Virtualization, Windows Kernel, the Microsoft Graphics Component, Internet Explorer, Microsoft Edge Legacy, and Windows Media.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #25 on: March 15, 2021, 11:51:51 PM »
Windows Insider Preview Build 19043.899 Released to the Beta Channel:  Releasing Windows 10 Build 19043.899 (21H1) to Beta Channel | Windows Insider Blog.

The update includes the following long list of fixes:
  • We fixed an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
  • We enabled administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
  • We fixed an issue that prevents the icon for a Toast collection from appearing in the Action Center if the icon file’s URI contains spaces.
  • We fixed an issue that makes high dynamic range (HDR) screens appear much darker than expected.
  • We fixed an issue that causes video playback to be out of sync in duplicate mode when you use multiple monitors.
  • We fixed an issue that might cause applications to stop working while you type Japanese characters using the Microsoft Japanese Input Method Editor (IME) in compatibility mode.
  • We fixed an issue that might cause a device to stop responding during hybrid shutdown.
  • We fixed an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
  • We fixed a window rendering issue that causes content in a window to flash frequently when FlipEx is used.
  • We fixed a window rendering issue that causes content in a window to flash frequently when multi-plane overlay (MPO) is used.
  • We fixed an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge.
  • We fixed an issue that displays nothing or shows “Computing Filters” indefinitely when you filter File Explorer search results.
  • We fixed an issue that makes the split layout unavailable for the touch keyboard when you rotate a device to portrait mode.
  • We informed users when a child account in the Family Safety plan has administrative privileges.
  • We fixed an issue that prevents you from closing Toast Notifications using the Close button on touchscreen devices.
  • We fixed an issue with a heap leak that might cause explorer.exe to consume high amounts of memory.
  • We updated the Volgograd, Russia time zone from UTC+4 to UTC+3.
  • We added a new time zone, UTC+2:00 Juba, for the Republic of South Sudan.
  • We fixed an issue with the Windows Event Log Forwarding client, which returns the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client selects the client’s certificate only if the Network Service has read permissions for the private key.
  • We fixed an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
  • We fixed an issue that stops BranchCache from working if you activate Windows using Cloud Solution Provider (CSP) license.
  • We fixed an issue that prevents Windows 10 Home edition devices from upgrading to the Windows 10 Pro Education edition using mobile device management (MDM) services such as Microsoft Intune.
  • We fixed an issue that prevents App-V applications from opening and generates error 0xc0000225.
  • We fixed an issue in which some machines enrolled with an MDM service fail to sync if the device manufacturer’s name contains a reserved character.
  • We fixed an issue with using a configuration service provider (CSP) policy to configure a custom setting for Audit Other Logon/Logoff events. The custom setting fails to take effect.
  • We fixed an issue that causes a system to stop working when no Trusted Platform Module (TPM) is present in the system. The error code in TpmTasks.dll!TrackTPMStateChanges is c0000005.
  • We fixed an issue that causes multiple instances of exe to run on a system when AppLocker is enabled and the system is not on the internet.
  • We fixed an issue with credential roaming when Windows Hello for Business is enabled.
  • We fixed an issue that prevents performance monitoring tools from displaying logged data for single instance counter objects.
  • We fixed an issue that prevents the Chromium-based Microsoft Edge from working. This issue occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
  • We fixed an issue that might cause a black screen 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 causes the system to stop working and generates error code 0xC9.
  • We fixed an issue with 7.1 channel audio technology.
  • We fixed an issue that turns on Caps lock unexpectedly when using RemoteApp. 31259510
  • We enabled Windows to retrieve updated printer capabilities to ensure that users have the proper set of selectable print options.
  • We updated support for hole punch and stapling locations for print jobs with long edge first paper feed direction on certain printers.
  • We fixed an issue with high memory usage when performing XSLT transforms using MSXLM6.
  • We fixed an issue that might cause File Explorer and other applications to stop responding for several minutes. This issue occurs after a client reconnects to the corporate network and attempts to use mapped drives to access file shares on the corporate network.
  • We fixed an issue that prevents Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  • We fixed an issue that might cause the cluster network interface to stop working for a short time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system might not detect that the NIC is working and the NIC remains in a failed status.
  • We fixed an issue with signing in to a device that is in the current domain by using the default user profile of a device that is in a different, but trusted domain. The profile service of the current domain cannot retrieve the default user profile from the trusted domain and uses the local default user profile instead.
  • We fixed an issue that causes a device to stop working if you delete files or folders that OneDrive syncs.
  • We fixed an issue that prevents Windows from activating Windows 10, version 2004 using the OA 3.0 key after installing KB4598291.
  • We fixed an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • We removed the Microsoft Edge Legacy desktop application that is out of support and installs the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release.
  • We fixed an issue that prevents users from using the Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • We fixed an issue to allow our enterprise partners to work with the Microsoft Support program to create customized mitigations.
  • We fixed an issue that might cause a blue screen when attempting to print to certain printers using some apps and might generate the error, APC_INDEX_MISMATCH.
  • We fixed an issue with an HTTP Keep-Alive connection in Azure Front Door. After completing a previous request and response to keep the connection open, Azure Front Door will try to reuse the connection. After an idle timeout, a race condition might occur that closes the Transmission Control Protocol (TCP) connection. As a result, the client might fail with an invalid server response.
  • We fixed an issue that causes Remote Desktop sessions to end unexpectedly.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #26 on: March 25, 2021, 05:03:47 PM »
Windows Insider Build 19042.906 (21H1) Released to Insiders in the Beta Channel:  Releasing Windows 10 Build 19043.906 (21H1) to Beta Channel | Windows Insider Blog.

This update includes all the fixes in 21H1 Build 19043.899 plus the following additional fix:
  • We fixed an issue that fails to print the graphical content in a document after installing the March 9, 2021 update.

In addition


Windows Insider Build 19042.906 (20H2) Released to Insiders in the Release Preview Channel:  Releasing Windows 10 Build 19042.906 (20H2) to Release Preview Channel | Windows Insider Blog.

The update includes a long list of fixes:
  • We fixed an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
  • We enabled administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
  • We fixed an issue that prevents the icon for a Toast collection from appearing in the Action Center if the icon file’s URI contains spaces.
  • We fixed an issue that makes high dynamic range(HDR) screens appear much darker than expected.
  • We fixed an issue that causes video playback to be out of sync in duplicate mode when you use multiple monitors.
  • We fixed an issue that might cause applications to stop working while you type Japanese characters using the Microsoft Japanese Input Method Editor (IME) in compatibility mode.
  • We fixed an issue that might cause a device to stop responding during hybrid shutdown.
  • We fixed an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
  • We fixed a window rendering issue that causes content in a window to flash frequently when FlipEx is used.
  • We fixed a window rendering issue that causes content in a window to flash frequently when multi-plane overlay (MPO) is used.
  • We fixed an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge Legacy.
  • We fixed an issue that displays nothing or shows “Computing Filters” indefinitely when you filter File Explorer search results.
  • We fixed an issue that makes the split layout unavailable for the touch keyboard when you rotate a device to portrait mode.
  • We informed users when a child account in the Family Safety plan has administrative privileges.
  • We fixed an issue that prevents you from closing Toast Notifications using the Close button on touchscreen devices.
  • We fixed an issue with a heap leak that might cause explorer.exe to consume high amounts of memory.
  • We updated the Volgograd, Russia time zone from UTC+4 to UTC+3.
  • We added a new time zone, UTC+2:00 Juba, for the Republic of South Sudan.
  • We fixed an issue with the Windows Event Log Forwarding client, which returns the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client selects the client’s certificate only if the Network Service has read permissions for the private key.
  • We fixed an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
  • We fixed an issue that stops BranchCache from working if you activate Windows using Cloud Solution Provider (CSP) license.
  • We fixed an issue that prevents Windows 10 Home edition devices from upgrading to the Windows 10 Pro Education edition using mobile device management (MDM) services such as Microsoft Intune.
  • We fixed an issue that prevents App-V applications from opening and generates error 0xc0000225.
  • We fixed an issue in which some machines enrolled with an MDM service fail to sync if the device manufacturer’s name contains a reserved character.
  • We fixed an issue with using a configuration service provider (CSP) policy to configure a custom setting for Audit Other Logon/Logoff events. The custom setting fails to take effect.
  • We fixed an issue that causes a system to stop working when no Trusted Platform Module (TPM) is present in the system. The error code in TpmTasks.dll!TrackTPMStateChanges is c0000005.
  • We fixed an issue that causes multiple instances of appidcertstorecheck.exe to run on a system when AppLocker is enabled and the system is not on the internet.
  • We fixed an issue with credential roaming when Windows Hello for Business is enabled.
  • We fixed an issue that prevents performance monitoring tools from displaying logged data for single instance counter objects.
  • We fixed an issue that prevents the Chromium-based Microsoft Edge from working. This issue occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled inside the virtual environment.
  • We fixed an issue that might cause a black screen 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 causes the system to stop working and generates error code 0xC9.
  • We fixed an issue with 7.1 channel audio technology.
  • We fixed an issue that turns on Caps lock unexpectedly when using RemoteApp. 31259510
  • We enabled Windows to retrieve updated printer capabilities to ensure that users have the proper set of selectable print options.
  • We updated support for hole punch and stapling locations for print jobs with long edge first paper feed direction on certain printers.
  • We fixed an issue with high memory usage when performing XSLT transforms using MSXLM6.
  • We fixed an issue that might cause File Explorer and other applications to stop responding for several minutes. This issue occurs after a client reconnects to the corporate network and attempts to use mapped drives to access file shares on the corporate network.
  • We fixed an issue that prevents Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  • We fixed an issue that might cause the cluster network interface to stop working for a short time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system might not detect that the NIC is working and the NIC remains in a failed status.
  • We fixed an issue with signing in to a device that is in the current domain by using the default user profile of a device that is in a different, but trusted domain. The profile service of the current domain cannot retrieve the default user profile from the trusted domain and uses the local default user profile instead.
  • We fixed an issue that causes a device to stop working if you delete files or folders that OneDrive syncs.
  • We fixed an issue that prevents Windows from activating Windows 10, version 2004 using the OA 3.0 key after installing KB4598291.
  • We fixed an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • We removed the Microsoft Edge Legacy desktop application that is out of support and installs the new Microsoft Edge. For more information, see New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release.
  • We fixed an issue that prevents users from using the Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • We fixed an issue to allow our enterprise partners to work with the Microsoft Support program to create customized mitigations.
  • We fixed an issue that causes Remote Desktop sessions to end unexpectedly.
  • We fixed an issue with an HTTP Keep-Alive connection in Azure Front Door. After completing a previous request and response to keep the connection open, Azure Front Door will try to reuse the connection. After an idle timeout, a race condition might occur that closes the Transmission Control Protocol (TCP) connection. As a result, the client might fail with an invalid server response.
  • We fixed an issue that might cause a blue screen when attempting to print to certain printers using some apps and might generate the error, APC_INDEX_MISMATCH.
  • We fixed an issue that fails to print the graphical content in a document after installing the March 9, 2021 update.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #27 on: April 13, 2021, 04:41:09 PM »
Windows Insider Build 19043-928 (20H1) Released to both Beta and Release Preview Channels:  Releasing Windows 10 Build 19043.928 (21H1) to Beta & Release Preview Channels | Windows Insider Blog.

This security update includes quality improvements. Key changes include:
  • We fixed an issue in which a principal in a trusted MIT realm fails to obtain a Kerberos service ticket from Active Directory domain controllers (DC). This occurs on devices that installed Windows Updates that contain CVE-2020-17049 protections and configured PerfromTicketSignature to 1 or higher. These updates were released between November 10, 2020 and December 8, 2020. Ticket acquisition also fails with the error, “KRB_GENERIC_ERROR”, if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without providing the USER_NO_AUTH_DATA_REQUIRED flag.
  • We fixed an issue with security vulnerabilities identified by a security researcher. Because of these security vulnerabilities, this and all future Windows updates will no longer contain the RemoteFX vGPU.  For more information about the vulnerability and its removal, see CVE-2020-1036 and KB4570006. Secure vGPU alternatives are available using Discrete Device Assignment (DDA) in Windows Server LTSC releases (Windows Server 2016 and Windows Server 2019) and Windows Server SAC releases (Windows Server, version 1803 and later versions).
  • We fixed a potential elevation of privilege vulnerability in the way Azure Active Directory web sign-in allows arbitrary browsing from the third-party endpoints used for federated authentication. For more information, see CVE-2021-27092 and Policy CSP – Authentication.
  • Security updates to Windows App Platform and Frameworks, Windows Apps, Windows Input and Composition, Windows Office Media, Windows Fundamentals, Windows Cryptography, the Windows AI Platform, Windows Kernel, Windows Virtualization, Internet Explorer, and Windows Media.
  • We have resolved an issue where some Insiders were getting an 0x800f081f error when attempting to install an early version of KB5000842. If you continue to hit an issue with the final version of KB5000842 update, let us know via Feedback Hub.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #28 on: April 19, 2021, 08:38:36 PM »
Windows Insider build 19043.962.21 (21H1) Released to Insiders on the Beta and Release Preview Channels:  Releasing Windows 10 Build 19043.962 (21H1) to Beta Channel & Release Preview Channels | Windows Insider Blog.

Fixes and Improvements
:
  • We fixed an issue that prevents a site from transitioning out of Microsoft Edge IE Mode when expected.
  • We fixed an issue that fails to remove mandatory profiles completely when you sign out when using the “Delete cached copies of roaming profiles” Group Policy.
  • We fixed an issue that causes blank tiles to appear on the Start menu with names such as “ms-resource:AppName” or “ms-resource:appDisplayName”. These blank tiles represent the installed applications and appear for approximately 15 minutes after updating to a newer version of Windows 10. Installing this update prevents these blank tiles from appearing on the Start menu.
  • We fixed an issue with the Microsoft Japanese Input Method Editor (IME) that prevents an app’s custom candidate window from displaying correctly.
  • We are rolling out news and interests on the Windows taskbar to Beta and Release Preview rings. This has been available in the Dev Channel, with on-going improvements based on Insider feedback. News and interests on the taskbar make it easy to stay up to date with information at a glance, and we look forward to hearing what you think.
  • We fixed an issue that occurs when you install inventory applications.
  • We fixed an issue that includes kernel mode rules for .NET applications in Windows Defender Application Control policies. As a result, the generated policies are significantly larger than necessary.
  • We fixed an issue that causes devices to fail Device Health Attestation.
  • We fixed an issue that turns off S Mode when you enable System Guard Secure Launch on a system running Windows 10 in S Mode.
  • We fixed an issue that causes lsass.exe memory usage to grow until the system becomes unusable. This occurs when Transport Layer Security (TLS) resumes a session.
  • We fixed an issue with a race condition between Task Scheduler and the Workstation Service. As a result, users cannot automatically join a hybrid Azure Active Directory (AAD) domain and error 0x80070490 is generated.
  • We fixed an issue that causes Azure Active Directory authentication to fail after signing in on Windows Virtual Desktop machines.
  • We fixed an issue that causes AAD Work Accounts to unexpectedly disappear from certain apps such Microsoft Teams or Microsoft Office.
  • We fixed an issue with a partial Service Connection Point (SCP) configuration that causes dsregcmd.exe to stop working. This issue occurs because of a case-sensitive domain ID name comparison that occurs when joining a hybrid Azure Active Directory domain using single sign-on (SSO).
  • We fixed an issue that accidently triggers hybrid AAD joining when the Group Policy “Register domain-joined computers as devices” is set to DISABLED. For more information, see Post configuration tasks for Hybrid Azure AD join.
  • We added the ability to adjust the amount of idle time before a headset goes to sleep in the Settings app for Windows Mixed Reality.
  • We fixed an issue that might generate a stop error when Docker containers run with process isolation.
  • We fixed an issue that causes automatic enrollment and certificate retrieval to fail with the error, “The parameter is incorrect.”
  • We fixed an issue that might cause Microsoft Defender Application Guard virtual machines to stop responding when Microsoft Defender Application Guard for Office opens a document. This issue might occur on some devices or in drivers that utilize GPU Hardware Accelerated Scheduling.
  • We fixed an issue that prevents some media players from playing content on hybrid devices that are running with dGPU on iGPU displays.
  • We fixed an issue with race conditions that cause high CPU usage. As a result, the system stops working and deadlocks occur.
  • We fixed an issue with a deadlock in the New Technology File System (NTFS).
  • We fixed an issue that causes DWM.exe to stop working in some cases.
  • We fixed an issue that might prevent an application screen from working when using a Remote Desktop ActiveX control that is embedded in an HTML page.
  • We improved the Windows Server Storage Migration Service by:
    • Adding support for migration from NetApp FAS arrays to Windows Servers and clusters.
    • Resolving multiple issues and improving reliability.
    • For more information, see Storage Migration Service overview.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.

Online Corrine

  • The Mystical Rose
  • Administrator
  • Hero Member
  • *****
  • Posts: 20792
  • "Stronger than the past, united in our goal."
    • View Profile
    • Security Garden
Re: Windows Insider Beta Channel Builds for 20H2 (Slow Ring)
« Reply #29 on: April 19, 2021, 09:57:34 PM »
Although the blog post title above indicates Beta Channel and Release Preview Channel, it was actually Build 19042.962 that was released to the Release Preview Channel.  See Releasing Windows 10 Build 19042.962 (20H2) to Release Preview Channel | Windows Insider Blog.

The fixes and improvements appear to be the same.


Take a walk through the "Security Garden" -- Where Everything is Coming up Roses!

Remember - A day without laughter is a day wasted.
May the wind sing to you and the sun rise in your heart.