Home » Tech News » Microsoft » Windows » Microsoft Cumulative Update For Windows 10 Insider Fixed Printer Issues

Microsoft Cumulative Update For Windows 10 Insider Fixed Printer Issues

Windows 10 Insider Program

Microsoft has made further improvements and released a new version for the cumulative update KB5000842. The update is available for Windows insiders in the beta and release preview channel and is intended to fix other printer problems.

Only last week Microsoft released the cumulative update KB5000842, now a revision for Windows 10 21H1, 20H2 and 2004 will follow. The new version numbers are 19043.906, 19042.906 and 19041.906. Microsoft has not yet communicated much about the changes compared to the version released on March 16. The only new addition is a bug fix for the graphic printer problems that many Windows users noticed after Patch Day March.

Fixes printer problems

Microsoft writes about this in the release notes: “We have fixed a problem in which the graphical content of a document cannot be printed after installing the March 9, 2021 update.” The update brings a long list of bug fixes. This is the preview, as the final update, these changes should appear on April Patch Day. We translated the release notes for the preview using Deepl. This update contains the following improvements:

Earlier: Microsoft Windows 10 Insider Preview Build 21343 – Improvement, Fixes, Issues

Cumulative update KB5000842 from March 25th

  • We fixed a zoom issue that occurs when using Microsoft Edge IE mode on devices that use multiple high DPI monitors.
  • We made it possible for administrators to use Group Policy to enable advanced keyboard shortcuts, including Ctrl + S, for users in Microsoft Edge IE mode.
  • We fixed an issue that prevented the icon for a Toast Collection from appearing in the Action Center when the URI of the icon file contains spaces.
  • We fixed an issue that could make high dynamic range (HDR) screens appear much darker than expected.
  • We fixed an issue resulting in duplicate mode video playback out of sync when using multiple monitors.
  • We fixed an issue that could cause applications to stop working while entering Japanese characters using the Microsoft Japanese Input Method Editor (IME) in Compatibility Mode.
  • We fixed an issue that could cause a device to become unresponsive during the hybrid shutdown.
  • We fixed an issue preventing users from customizing or turning off the touchpad due to administrative settings.
  • We fixed a window rendering issue that caused content in a window to blink frequently when using FlipEx.
  • We fixed an issue with the display of windows where the contents of a window would often blink when using Multi-Plane-Overlay (MPO).
  • We fixed an issue with Japanese input that occurs when switching focus between fields in Microsoft Edge Legacy.
  • We fixed an issue where filtering search results in File Explorer resulted in nothing or “Computing Filters” showing indefinitely.
  • We fixed an issue that prevented the split layout for the touch keyboard from being available when rotating a device to portrait mode.
  • We’ve notified users when a child account in the Family Safety plan has administrative rights.
  • We fixed an issue preventing you from being able to close Toast notifications using the Close button on touchscreen devices.
  • We fixed an issue with a heap leak that could cause explorer.exe to consume large amounts of memory.
  • We have updated the Volgograd, Russia time zone from UTC + 4 to UTC + 3.
  • We have 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 returning the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client only selects the client’s certificate if the network service has read rights for the private key.
  • We fixed an issue causing PowerShell-based monitors to stop working when you enable transcription on the systems.
  • We fixed an issue that could cause BranchCache to stop working when you activate Windows with a Cloud Solution Provider (CSP) license.
  • We fixed an issue preventing Windows 10 Home Edition devices from upgrading to Windows 10 Pro Education Edition using Mobile Device Management (MDM) services such as Microsoft Intune.
  • We fixed an issue preventing App-V applications from opening and producing error 0xc0000225.
  • We fixed an issue where some devices signed in to an MDM service cannot sync if the device manufacturer name contains a reserved character.
  • Fixed an issue with using a Configuration Service Provider (CSP) policy to configure a custom setting to check for other login/logout events. The custom setting will not take effect.
  • Fixed an issue that could cause a system to stop working if there was no Trusted Platform Module (TPM) in the system. The error code in TpmTasks.dll! TrackTPMStateChanges is c0000005.
  • We fixed an issue resulting in multiple instances of appidcertstorecheck.exe running on a system when AppLocker is enabled and the system is not on the internet.
  • We fixed an issue with credentials roaming when Windows Hello for Business is enabled.
  • We fixed an issue that was preventing performance monitoring tools from displaying logged data for individual instance counter objects.
  • We fixed an issue preventing the Chromium-based Microsoft Edge from working. This problem occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled within the virtual environment.
  • We fixed an issue that could cause a black screen or delay in signing in to hybrid Azure Active Directory joined machines. In addition, there is no access to login.microsoftonline.com.
  • We fixed an issue causing the system to stop working and generating error code 0xC9.
  • We fixed an issue with 7.1 channel audio technology.
  • We fixed an issue where Caps Lock locks unexpectedly when using RemoteApp. 31259510
  • We’ve enabled Windows to pull in updated printer capabilities to ensure users have the correct set of print options to choose from.
  • We have updated support for hole punch and stapler positions for long-edge print jobs in the first paper feed direction on certain printers.
  • Fixed an issue with high memory consumption when performing XSLT transformations with MSXLM6.
  • We fixed an issue that could cause File Explorer and other applications to stop responding for several minutes. This problem occurs after a client reconnects to the corporate network and tries to access file shares on the corporate network using mapped drives.
  • We fixed an issue preventing Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  • We fixed an issue that could cause the cluster’s network interface to stop working for a short period of time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system may not recognize that the NIC is working and the NIC may remain in a failed state.
  • We fixed an issue logging into 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 get the default user profile from the trusted domain and instead uses the local default user profile.
  • We fixed an issue that caused a device to stop working when you delete files or folders that OneDrive is syncing.
  • We fixed an issue preventing 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 ensure application and device compatibility for all Windows updates.
  • We removed the legacy Microsoft Edge desktop application, which is no longer supported, and installed the new Microsoft Edge. For more information, see New Microsoft Edge Replaces Microsoft Edge Legacy with the Windows 10 Update Tuesday release in April.
  • We fixed an issue preventing users from using Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • We fixed an issue that allows our corporate partners to work with the Microsoft Support Program to create custom remedial actions.
  • We fixed an issue resulting in remote desktop sessions ending 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 tries to use the connection again. After an idle timeout, a race condition can occur that closes the Transmission Control Protocol (TCP) connection. As a result, the client might fail with an invalid server response.
  • Fixed an issue that could cause a blue screen and the APC_INDEX_MISMATCH error when trying to print to certain printers from some applications.
  • We fixed an issue where the graphical content of a document cannot be printed after installing the March 9, 2021 update.
  • We fixed a zoom issue that occurs when using Microsoft Edge IE mode on devices that use multiple high DPI monitors.
  • We made it possible for administrators to use Group Policy to enable advanced keyboard shortcuts, including Ctrl + S, for users in Microsoft Edge IE mode.
  • We fixed an issue that prevented the icon for a Toast Collection from appearing in the Action Center when the URI of the icon file contains spaces.
  • We fixed an issue that could make high dynamic range (HDR) screens appear much darker than expected.
  • We fixed an issue resulting in duplicate mode video playback out of sync when using multiple monitors.
  • We fixed an issue that could cause applications to stop working while entering Japanese characters using the Microsoft Japanese Input Method Editor (IME) in Compatibility Mode.
  • We fixed an issue that could cause a device to become unresponsive during hybrid shutdown.
  • We fixed an issue preventing users from customizing or turning off the touchpad due to administrative settings.
  • We fixed a window rendering issue that caused content in a window to blink frequently when using FlipEx.
  • We fixed an issue with the display of windows where the contents of a window would often blink when using Multi-Plane-Overlay (MPO).
  • We fixed an issue with Japanese input that occurs when switching focus between fields in Microsoft Edge Legacy.
  • We fixed an issue where filtering search results in File Explorer resulted in nothing or “Computing Filters” showing indefinitely.
  • We fixed an issue that prevented the split layout for the touch keyboard from being available when rotating a device to portrait mode.
  • We’ve notified users when a child account in the Family Safety plan has administrative rights.
  • We fixed an issue preventing you from being able to close Toast notifications using the Close button on touchscreen devices.
  • We fixed an issue with a heap leak that could cause explorer.exe to consume large amounts of memory.
  • We have updated the Volgograd, Russia time zone from UTC + 4 to UTC + 3.
  • We have 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 returning the first matching certificate without checking private key permissions. With this update, the Windows Event Log Forwarding client only selects the client’s certificate if the network service has read rights for the private key.
  • We fixed an issue causing PowerShell-based monitors to stop working when you enable transcription on the systems.
  • We fixed an issue that could cause BranchCache to stop working when you activate Windows with a Cloud Solution Provider (CSP) license.
  • We fixed an issue preventing Windows 10 Home Edition devices from upgrading to Windows 10 Pro Education Edition using Mobile Device Management (MDM) services such as Microsoft Intune.
  • We fixed an issue preventing App-V applications from opening and producing error 0xc0000225.
  • We fixed an issue where some devices signed in to an MDM service cannot sync if the device manufacturer name contains a reserved character.
  • Fixed an issue with using a Configuration Service Provider (CSP) policy to configure a custom setting to check for other login / logout events. The custom setting will not take effect.
  • Fixed an issue that could cause a system to stop working if there was no Trusted Platform Module (TPM) in the system. The error code in TpmTasks.dll! TrackTPMStateChanges is c0000005.
  • We fixed an issue resulting in multiple instances of appidcertstorecheck.exe running on a system when AppLocker is enabled and the system is not on the internet.
  • We fixed an issue with credentials roaming when Windows Hello for Business is enabled.
  • We fixed an issue that was preventing performance monitoring tools from displaying logged data for individual instance counter objects.
  • We fixed an issue preventing the Chromium-based Microsoft Edge from working. This problem occurs when Microsoft Edge is used in combination with Microsoft App-V and fonts are enabled within the virtual environment.
  • We fixed an issue that could cause a black screen or delay in signing in to hybrid Azure Active Directory joined machines. In addition, there is no access to login.microsoftonline.com.
  • We fixed an issue causing the system to stop working and generating error code 0xC9.
  • We fixed an issue with 7.1 channel audio technology.
  • We fixed an issue where Caps Lock locks unexpectedly when using RemoteApp. 31259510
  • We’ve enabled Windows to pull in updated printer capabilities to ensure users have the correct set of print options to choose from.
  • We have updated support for hole punch and stapler positions for long-edge print jobs in the first paper feed direction on certain printers.
  • Fixed an issue with high memory consumption when performing XSLT transformations with MSXLM6.
  • We fixed an issue that could cause File Explorer and other applications to stop responding for several minutes. This problem occurs after a client reconnects to the corporate network and tries to access file shares on the corporate network using mapped drives.
  • We fixed an issue preventing Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  • We fixed an issue that could cause the cluster’s network interface to stop working for a short period of time. As a result, the network interface controller (NIC) is marked as failed. When the network is operational again, the system may not recognize that the NIC is working and the NIC may remain in a failed state.
  • We fixed an issue logging into 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 get the default user profile from the trusted domain and instead uses the local default user profile.
  • We fixed an issue that caused a device to stop working when you delete files or folders that OneDrive is syncing.
  • We fixed an issue preventing 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 ensure application and device compatibility for all Windows updates.
  • We removed the legacy Microsoft Edge desktop application, which is no longer supported, and installed the new Microsoft Edge. For more information, see New Microsoft Edge Replaces Microsoft Edge Legacy with the Windows 10 Update Tuesday release in April.
  • We fixed an issue preventing users from using Remote Desktop Protocol (RDP) to connect to a Windows Server 2019 device that is in Desktop Experience mode.
  • We fixed an issue that allows our corporate partners to work with the Microsoft Support Program to create custom remedial actions.
  • We fixed an issue resulting in remote desktop sessions ending 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 tries to use the connection again. After an idle timeout, a race condition can occur that closes the Transmission Control Protocol (TCP) connection. As a result, the client might fail with an invalid server response.
  • Fixed an issue that could cause a blue screen and the APC_INDEX_MISMATCH error when trying to print to certain printers from some applications.
  • We fixed an issue where the graphical content of a document cannot be printed after installing the March 9, 2021 update.

Web Desk is the news author at Research Snipers which mainly covers Technology News, Microsoft News, Google News, Facebook, Apple, Huawei, Xiaomi, and other tech news and served by Research Snipers Staff and editors.

Leave a Reply

Your email address will not be published. Required fields are marked *