Windows 10 20H2

Perhaps it is something to be thankful for. One step forward, two steps backward isn't really progress. Even when you don't like the conditions, predictability is an underrated blessing.

 

February 24, 2021—KB4601382 (OS Builds 19041.844 and 19042.844) Preview

Before installing this update

Prerequisite:

Starting with this release, Microsoft will combine the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). To utilize this improvement, install the most recent standalone SSU ( KB4598481) before installing this LCU. If you install this LCU before installing KB4598481, you might encounter error 0x800f0823 – CBS_E_NEW_SERVICING_STACK_REQUIRED. Close the error message and install the recommended SSU.

Known issues for KB4601382

• If you use the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows input of Furigana characters, you may not get the correct Furigana characters. You may have to enter the furigana characters manually. We are working on a solution and will provide an update in one of the next versions.
• If you have problems with the installation and receive the error message 0x800f0988 , Ben's fix will also help here .
• Problems that are currently still open or that have already been resolved are always updated on this page .

Problems resolved by KB4601382

• The highlights:
• Windows Hello multi-camera support to set the default as an external camera when there are both external and internal Windows Hello cameras.
• Windows Defender Application Guard performance improvements, including optimization of the scenario times when opening documents.
• We fixed an issue that caused a delay of a minute or more when you open an Office document using Microsoft Defender Application Guard (WDAG). This occurs when you try to open a file using a Universal Naming Convention (UNC) path or a Server Message Block (SMB) share link.
• We have improved Robocopy's performance when copying files that are over 400MB in total.
• We fixed an issue that caused a WDAG container to use almost 1 GB of memory when the container is idle.
• Windows Management Instrumentation (WMI) Group Policy Service (GPSVC) update performance has been improved to support remote work scenarios.
• We fixed an issue that resulted in changes that the Active Directory (AD) administrator makes to user or computer group membership being slow to propagate. Although the access token is eventually updated, these changes will not be reflected when the administrator uses gpresult / r or gpresult / h to generate a report.

• We fixed an issue with a memory leak in Internet Explorer 11 that occurs when using the Chinese language pack.
• We fixed an issue with certain COM + calling policies causing blocking in certain applications.
• Fixed an issue that prevented certain Win32 applications from opening as a different user when using the Runas
• We fixed an issue displaying unexpected screens during Windows Out of Box Experience (OOBE).
• We have fixed a problem that can lead to a deadlock if a COM server delivers an event to several subscribers in parallel.
• We fixed an issue in Advanced Display Settings showing the incorrect available refresh rates for HDR (High Dynamic Range) displays.
• Fixed an issue that could prevent certain CAD applications from opening when those applications rely on OpenGL.
• We fixed an issue where video playback could flicker when rendering on certain low latency monitors.
• Fixed an issue that sometimes prevented strings from being entered into the Input Method Editor (IME).
• We fixed an issue where resources are being drained because the Desktop Windows Manager (DWM) is leaking handles and virtual memory in Remote Desktop sessions.
• We fixed an issue with a stop error that occurs on startup.
• We fixed an issue that can delay the deployment of a Windows Hello for Business (WHfB) Certificate Trust when opening the Settings-> Accounts-> Sign-in Options page.
• We fixed an issue that could sometimes result in some keyboard keys not working, e.g. B. the Home key, the Ctrl key, or the left arrow key. This problem occurs when you set the Japanese IME input mode to Kana.
• We removed the history of previously used images from a user account's profile.
• We fixed an issue where the wrong language is displayed on a console after changing the system locale.
• We fixed an issue resulting in the Windows Remote Management (WinRM) host process stop working when formatting messages from a PowerShell plugin.

• We fixed an issue in the Windows Management Instrumentation (WMI) service causing a heap leak every time security settings are applied to WMI namespace permissions.
• We fixed an issue with screen rendering after opening games with certain hardware configurations.
• We have improved the startup times for applications with roaming settings when User Experience Virtualization (UE-V) is enabled.
• We fixed an issue where a principal on a trusted MIT realm cannot obtain a Kerberos service ticket from Active Directory Domain Controllers (DC). This occurs on devices that have installed Windows Updates that contain CVE-2020-17049 protections and have PerfromTicketSignature configured to 1 or higher. These updates were released between November 10, 2020 and December 8, 2020. The ticket purchase also fails with the "KRB_GENERIC_ERROR" error if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without specifying the USER_NO_AUTH_DATA_REQUIRED flag.
• We fixed high memory and CPU usage in Microsoft Defender for Endpoint.
• We have improved the functionality of the Data Loss Prevention and Insider Risk Management solution in Microsoft 365 Endpoints.
• We fixed an issue that displays an error when you try to open an untrusted webpage with Microsoft Edge or open an untrusted Microsoft Office document. The error is: "WDAG Report - Container: Error: 0x80070003, Ext-Fehler: 0x00000001". This problem occurs after installing the .NET update KB4565627.
• We fixed an issue preventing wevtutil from parsing an XML file.
• We fixed an issue that does not report an error when the Elliptic Curve Digital Signature Algorithm (ECDSA) generates invalid keys of 163 bytes instead of 165 bytes.
• We've added support for using the new Chromium-based Microsoft Edge as a dedicated Access Single Kiosk app. You can now also customize a breakout key sequence for single app kiosks. For more information, see Configure Microsoft Edge Kiosk Mode.
• Fixed an issue with User Datagram Protocol (UDP) broadcast packets that are larger than the Maximum Transmission Unit (MTU). Devices that receive these packets discard them because the checksum is not valid.
• A problem has been fixed in which the WinHTTP AutoProxy service does not adhere to the value for the maximum Time To Live (TTL) in the PAC (Proxy Auto-Configuration) file. This prevents the cached file from being dynamically updated.
• We have improved the ability of the WinHTTP Web Proxy Auto-Discovery Service to ignore invalid Web Proxy Auto-Discovery Protocol (WPAD) URLs returned by the Dynamic Host Configuration Protocol (DHCP) server.
• We have displayed the correct Envelope media type as the selectable output paper type for Universal Print queues.
• We stopped displaying a random paper size for a printer when it is using the Microsoft Internet Printing Protocol (IPP) Class Driver.
• We've enabled Windows to get updated printer functionality 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-feed direction on certain printers.
• We fixed an issue that could cause the IKEEXT service to intermittently stop working.
• We fixed an issue that could prevent a Non-Volatile Memory Express (NVMe) device from going into the correct power state.
• We fixed an issue that can cause stop error 7E in sys on servers running Network File System (NFS) service.
• We fixed an issue that was preventing the User Profile Service from reliably detecting a slow or fast connection.
• Fixed an issue that caused a metadata lock conflict when using working folders.
  We added a new dfslogkey as described below:
• Keypath: HKEY_LOCAL_MACHINE / SOFTWARE / MICROSOFT / dfslog.
  The RootShareAcquireSuccessEvent has the following possible values:

• Default value = 1; activates the protocol.
• Any value other than 1; deactivates the protocol.
• If this key does not exist, it will be created automatically. For a change to dfslog / RootShareAcquireSuccessEvent in the registry to take effect, you must restart the DFSN service.

​

• We have updated the Open Mobile Alliance (OMA) Device Management (DM) synchronization protocol by adding a check-in reason for requests from the client to the server. The check-in reason enables the Mobile Device Management (MDM) service to make better decisions about synchronization sessions. With this change, the OMA-DM service must negotiate a protocol version of 4.0 with the Windows OMA-DM client.
• We disabled token binding in Windows Internet (WinINet) by default.
• We fixed an issue that could prevent the correct furigana characters from being displayed in applications that automatically allow furigana characters to be entered. You may have to enter the furigana characters manually. This problem occurs when you use the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in these applications.
• support.microsoft.com/

Direct download link CU (Cumulative Update) - KB4601382


February 24, 2021-KB4601554 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, and Windows Server, version 20H2

Direct download link Dotnetfx48 CU
http://download.windowsupdate.com/d..._2d34ab16fa8501aa0bd9738d1b8f76024f88d421.msu

 

Is 20H2 finally safe to use without any issues? I would have to upgrade anyways since 1909 wont be supported anymore in May and since 20H1 was a major update i would have to reinstall Windows to do so.

 

Will it ever be safe? If it worked yeasterday it doensn't mean it will work tomorrow.

The latest Windows 10 update is causing new issues for some users Windowslatest - March 8, 2021

The latest update for Windows 10 is reportedly causing issues with the system backup tool called 'File History' for a small subset of users. In addition to backup issues, users are also finding that the update breaks their webcam, crashes apps, and fails to install in some cases.

 

Computers (including smartphones) have never been, and will never be, safe to use. They are inherently unsafe and forever will be for as long as people are born evil and live their lives in an environment with other evil people where being evil is viewed as acceptable behavior. I mean, just look around... we have entire industries thriving financially because people live in places where being evil is viewed as normal, acceptable and expected behavior.

 

It doesnt sound too bad compared to past problems.

I grown to accept Windows 10 of what it is a trash OS that we're stuck with if you want to use Windows. They need to stop making major useless updates every 6 months and go back to the old ways but that wont happen. I usually hold off upgrading as long as possible that why stayed with 1909.

 

Will never ever happen. They need to make small changes so they can implement new ways to try grab info from your system. @Mr. Fox I had to smile when I saw this one Enjoy!

 

Windows 10 KB5000802 (March) update is crashing PCs with BSOD

Blue Screens when printing in win32kfull.sys
Users of Windows 10 version 1909, 2004 or 20H2 should urgently activate the update delay for 7 days and I recommend that administrators in managed enterprise environments should not release the march 2021 updates like KB5000802 without extensive tests. I got massive feedback, that these updates are causing blue screens in win32kfull.sys during printing. Its reported for update KB5000802 (2004/20H2)as well for update KB5000808 (v1909). A workaround to test is to uninstall the printer driver and reinstall it, to solve the printing bsod issue. Here is the first message from my German blog.

We have the problem that after today’s updates several W10 (1909,2004,20H2) – clients go into a BlueScreen when printing especially to Kyocera printers.

win32kfull.sys is probably reported in the BSOD.

Causing update KB5000802 + KB5000808

Good old Microsoft did it again......

 

And to make it complete, good old Microsoft offered Windows 10 KB4589212 (Intel Microcode) update for AMD systems http://forum.notebookreview.com/thr...nd-announcements.826887/page-84#post-11083082

Yeah, welcome to patch Tuesday HELL. Microsoft never ceases to disappoint

 

Windows 10 emergency updates released to fix printing crashes
http://forum.notebookreview.com/thr...nd-announcements.826887/page-84#post-11084214

• KB5001567 for Win10 v2004/20H2

 

I have noticed that in reverting back to Win 10 2004 build, that I still get the same number of crashes as I did when I tried out 20H2, though will slightly less frequency. It all seemed like placebo going back to 2004 initially, however is there some aspect or part of 20H2 that is stuck in the 2004 model? I dont know what keeps causing the VLTMRG crashes, but I distinctly remember it all started when I tried the 20H2 build.

 

20H2 is in short same OS version as 20H1. With focused on bug and performance fixes, LOOL
What's New in Windows 10's October 2020 Update (20H2)

 

Maybe sticking with 1909 wont be so bad after all lol

Still going upgrade to Pro whenever i feel like it

 

I hear that alot.

 

Just upgraded to 20H2 build, so far all good. I had some issues with file explorer crashing on 1909 which required it to be restarted almost everyday, so far it's all good on this build. And it's snappy smooth.

 

March 29, 2021—KB5000842 (OS Builds 19041.906 and 19042.906) Preview

KB5000842 update highlights
With the KB5000842 monthly release preview update, Microsoft addresses an issue that might cause systems running Windows 10 2004 to stop responding during hybrid shutdowns.

This cumulative update also fixes bugs causing devices to stop working and generating 0xC9 error codes, and heap leak triggering high memory consumption in explorer.exe.

Microsoft also addressed a Windows activation issue impacting Windows 10, version 2004 systems after installing last month's KB4598291 preview update that fixed device deactivation and freezing issues.

Last but not least, the update removes the out-of-support Microsoft Edge Legacy and installs the new Microsoft Edge. Microsoft announced last month that the Windows 10 April updates will remove Edge Legacy permanently.

Other highlights included in this update:

• 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.
  
  
• Addresses 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.
  
  
• Informs users when a child account in the Family Safety plan has administrative privileges.
  
  
• Updates an issue that causes a device to stop working if you delete files or folders that OneDrive syncs.
  
  
• Addresses 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.
  

What's changed in KB5000842
The KB5000842 Windows 10 cumulative update is considered optional, and it will not be deployed automatically given that it is a preview update.

To install it manually, you have to go to Settings > Update & Security > Windows Update and 'Check for updates.' You’ll then be able to download and install the update by going to the 'Optional updates available' area.

The update can also be downloaded manually from the Microsoft Catalog. After installing it, Windows 10 2004 will be updated to build 19041.906, while Windows 10 20H2 will be upgraded to build 19042.906.

Microsoft advises customers who encounter "0x800f0823 – CBS_E_NEW_SERVICING_STACK_REQUIRED" errors when installing the KB5000842 update to close the message, install the last standalone SSU ( KB4598481), and retry the installation process.

Here is the complete list of key quality improvements and fixes delivered with this update:

• Addresses an issue with zoom that occurs when using Microsoft Edge IE Mode on devices that use multiple high-DPI monitors.
  
  
• Allows administrators to use a Group Policy to enable extended keyboard shortcuts, including Ctrl+S, for users in Microsoft Edge IE Mode.
  
  
• Addresses an issue that prevents the icon for a Toast collection from appearing in the Action Center if the icon file’s URI contains spaces.
  
  
• Addresses an issue that makes high dynamic range (HDR) screens appear much darker than expected.
  
  
• Addresses an issue that causes video playback to be out of sync in duplicate mode when you use multiple monitors.
  
  
• Addresses 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.
  
  
• Addresses an issue that prevents users from adjusting or turning off the touchpad because of administrative settings.
  
  
• Addresses a window rendering issue that causes content in a window to flash frequently when FlipEx is used.
  
  
• Addresses a window rendering issue that causes content in a window to flash frequently when multi-plane overlay (MPO) is used.
  
  
• Addresses an issue with Japanese input that occurs after focus changes between boxes in Microsoft Edge.
  
  
• Addresses an issue that displays nothing or shows “Computing Filters” indefinitely when you filter File Explorer search results.
  
  
• Addresses an issue that makes the split layout unavailable for the touch keyboard when you rotate a device to portrait mode.
  
  
• Addresses an issue that prevents you from closing Toast Notifications using the Close button on touchscreen devices.
  
  
• Updates the Volgograd, Russia time zone from UTC+4 to UTC+3.
  
  
• Adds a new time zone, UTC+2:00 Juba, for the Republic of South Sudan.
  
  
• Addresses 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.
  
  
• Addresses an issue that causes PowerShell-based monitors to stop working when you enable transcription on the systems.
  
  
• Addresses an issue that stops BranchCache from working if you activate Windows using Cloud Solution Provider (CSP) license.
  

• Addresses 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.
  
  
• Addresses an issue that prevents App-V applications from opening and generates error 0xc0000225.
  
  
• Addresses an issue in which some machines enrolled with an MDM service fail to sync if the device manufacturer's name contains a reserved character.
  
  
• Addresses 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.
  
  
• Addresses 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.
  
  
• Addresses an issue with credential roaming that occurs when Windows Hello for Business is enabled.
  
  
• Addresses an issue that prevents performance monitoring tools from displaying logged data for single instance counter objects.
  
  
• Addresses 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.
  
  
• Addresses an issue that causes a black screen or delays signing in to a Hybrid Azure Active Directory joined machine while the machine attempts to connect to login.microsoftonline.com.
  
  
• Addresses an issue with 7.1 channel audio technology.
  
  
• Addresses an issue that turns on Caps lock unexpectedly when using RemoteApp.
  
  
• Enables Windows to retrieve updated printer capabilities to ensure that users have the proper set of selectable print options.
  
  
• Updates support for hole punch and stapling locations for print jobs with long edge first paper feed direction on certain printers.
  

• Addresses an issue with high memory usage when performing XSLT transforms using MSXLM6.
  
  
• Addresses an issue that prevents Server Message Block 1 (SMB1) clients from accessing the SMB share after restarting the LanmanServer service.
  
  
• Addresses 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.
  
  
• Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  
  
• Addresses 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.
  
  
• Addresses an issue to allow our enterprise partners to work with the Microsoft Support program to create customized mitigations.
  
  
• Addresses an issue that causes Remote Desktop sessions to end unexpectedly.
  
  
• Addresses 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.
  
  
• Addresses an issue that prevents you from specifying up to 255 columns when you use the Jet Text installable indexed sequential access method (IISAM) format.

Direct download link: KB5000842

Enjoy

 

Does anyone know if hibernation is working in 20H2? I recently upgraded to 20H1 when it was finally marked as "business ready", but found hibernation was broke. Or is there a fix for hibernation not working?

 

what kind of computer are you using, Primes (a desktop or laptop PC)?
post specs of your computer here after running either HWInfo or Speccy

I'm still running Win10 v2004/20H1 (build 19041.906) on a Toshiba Satellite C55Dt-A laptop and hibernation appears to be working fine on it but the situation may be different for other laptop models or other laptop brands.

 

I always hibernate. works perfectly fine.

 

I know bruh

KB5001330 [Manual Download] Windows 10 21H1, 20H2 and 2004 Security Patch April 13, 2021

Known issues with KB5001330

• If you have problems with the installation and get the error message 0x800f0988 , Ben's fix can definitely help.
• System and user certificates may be lost when upgrading a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices are only affected if they have already installed a Latest Cumulative Update (LCU) released on September 16, 2020 or higher and then proceed with the update to a later version of Windows 10 from media or an installation source that does not contain an LCU released on October 13, 2020 or later. Workaround: go back to the previous version.
• If you use the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters into an app that automatically allows you to enter Furigana characters, you may not get the correct Furigana characters. You may have to enter the furigana characters manually. We work on a solution
• As always, you can find all outstanding problems in our overview , which we are constantly updating

Problems fixed by KB5001330

• Addresses an issue in which a principal on a trusted MIT realm cannot obtain a Kerberos service ticket from Active Directory Domain Controllers (DC). This occurs on devices that have installed Windows Updates that contain CVE-2020-17049 protections and have PerfromTicketSignature configured to 1 or higher. These updates were released between November 10, 2020 and December 8, 2020. The ticket purchase also fails with the "KRB_GENERIC_ERROR" error if callers submit a PAC-less Ticket Granting Ticket (TGT) as an evidence ticket without specifying the USER_NO_AUTH_DATA_REQUIRED flag.
• Addresses an issue with security vulnerabilities identified by a security researcher. Due to these security vulnerabilities, this and all future Windows updates will no longer contain the RemoteFX vGPU function. For more information about the vulnerability and how to resolve it, see CVE-2020-1036 and KB4570006. Secure vGPU alternatives are available via Discrete Device Assignment (DDA) in Windows Server LTSC versions (Windows Server 2016 and Windows Server 2019) and Windows Server SAC versions (Windows Server, version 1803 and later versions).
• Addresses a potential elevation of privilege in the way Azure Active Directory web login 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, Windows AI Platform, Windows Kernel, Windows Virtualization, and Windows Media.
• You can find the individual list of CVE vulnerabilities on this page msrc.microsoft.com/update-guide/
• support.microsoft

Manual download of KB5001330

• As a note once again: An SSU , if available, is now integrated in the update. So no longer has to be installed separately.
• windows10.0-kb5001330-x64.msu

A sidenote...
KB5001330 affects Windows installations from custom offline media windowsreport.com | today

• KB5001330 is this Patch Tuesday's security update for Windows 10 v20H2 and v2004.
• It has been reported that KB5001330 may affect users that have Windows installed from custom installation media.
• Devices that connect directly to Windows Update to receive updates are not affected.
• Read more about this security update, and decide whether to update your PC or not.

 

The usual....

KB5001330 Windows Update is reportedly causing performance drop in games, failed installs and bootloops
http://forum.notebookreview.com/thr...nd-announcements.826887/page-91#post-11090109

 

KB5001391 (v1904x.962) beta LCU

• How to add "Install CAB" Context Menu in Windows 10

Spoiler: Changelog

Anyone testing out the very latest versions of Windows 10 has a new bug-fixing patch to install. With the release of the KB5001391 update, fixes and changes introduced to the Dev channel now make their way to the Beta and Release Preview channels.

This latest patch sees Microsoft taking Windows 10 20H2 up to build 19042.962 and Windows 10 21H1 up to build 19043.962. It includes a large number of bug fixes, and addresses problems with a profile-related Group Policy, and fixes an issue that caused soaring memory usage by the lsass.exe process, as well as high CPU usage that led to system lockups.

See also:

Advertisement

• Microsoft fixes Windows 10's drive corrupting NTFS denial of service vulnerability
• KB5001330 update for Windows 10 is causing performance problems and other issues
• Microsoft issues KB5001330 and KB5001337 updates for Windows 10, killing off legacy Edge

In addition to a fairly large number of bug fixes, the patch also introduces News and Interests on the taskbar for a wider range of users. The KB5001391 update is gradually building up to general availability for all users; when this happens, it will be an optional "C" release.

In a post on the Windows Insider Blog, Microsoft shares more details about the changes included with the latest update:

• 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 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 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 accidentally 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.

 

Yeah, nice see the Beta patch race continue. I wonder what new bugs will be implemented Remember new patches always come with new code that can will screw up. And with the latest fix (KIR) you have to let Microsoft have full access to your computer's data... Yeah, use of Known Issue Rollback help them to keep their Telelmetry Spy-box enabled.

Here’s Microsoft's Official Fix For Windows 10 KB5001330 Gaming Slowdowns and BSODs

How To Determine If This Fix Is Actually Applied
This is a bit of a different scenario, however, as it took a couple weeks for Microsoft to acknowledge the issue, by which time there were plenty of complaints from gamers. Your best bet is to reboot your PC, and hopefully your problems go away. However, it takes some digging to find out if your PC actually has the fix in place, because it does not show up in Windows Update.

One of Bleeping Computer's readers figured out where it is hiding in the system Registry. Bear in mind that you can break things by mucking around in the Registry, but if you are comfortable with the risks and want to see if the fix is in place, type regedit in taskbar search field and click on Registry Editor. Then navigate to:


If the above entry exists (sorry we had to post an image due to long text strings occasionally breaking web pages), the fix has been applied. Otherwise, you will have to wait a little bit longer—it should be applied within 24 hours.

 

Disabling Windows 10 experiments blocks Known Issue Rollback fixes
http://forum.notebookreview.com/thr...nd-announcements.826887/page-93#post-11092561

-----------------------------------------------------------------

New Official Guinea pig version out...

Windows 10 20H2 KB5001391 Cumulative Update Preview Released bleepingcomputer.com

Microsoft has released the optional KB5001391 Preview cumulative update for Windows 10 2004 and Windows 10 20H2.

 

Well that explains why i had to roll back multiple times

 

And now you know how to do before you use their Rollback fix next time. Be yoo sure, not the first or neither last time we will see new awful buggy patches from Redmond

Windows 10 update fixes a critical bug that could mess up backups windowslatest.com - April 29, 2021

With the February update, Microsoft broke two features - Intel webcams for some users and File History (backup tool). While Microsoft acknowledged problems with webcams in a post on Feedback Hub, the company never admitted issues with Windows 10’s built-in backup feature.

 

KB5003173 for 2004/20H2 released (build 1904x.985)
https://betanews.com/2021/05/12/mic...mulative-update-for-windows-10-20h2-and-2004/

 

ssu-19041.1018-x64.cab 1ccff418b596f0b04a6a7beb5d8eff5f7e625d0b 14.58 MiB
windows10.0-kb5001679-x64.cab 6773983c33c19f68c8874e49d90034800a1e938c 35.01 MiB
windows10.0-kb5003214-x64.cab e0eb59c3141d3100f7d5bd2652a8394182e0c63a 558.25 MiB

 

Here is more fun for the Guinea pigs
KB5003214 [manual download] Windows 10 21H1, 20H2 and 2004 1904x.1021 as a non-security update borncity.com May 19, 2021

Microsoft has provided KB 5003214 as an optional non-security update (now referred to as a preview update) for Windows 10 21H1, 20H2 and 2004. The version number makes a big leap compared to the May security update to 19043.1021, 19042.1021 and 19041.1021.

 

nah, I'll skip this one until MS officially announces this in MS blogs with something higher than .1021 (maybe .1022 or greater, then I'll be the "guinea pig" for the revised version)

 

Here is a new guinea pig version with a long nice list of fixed issues and improvements. And higher than .1021

KB5003214 [manual download] Windows 10 21H1, 20H2 and 2004 1904x.1023 as a non-security update

Microsoft yesterday updated the non-security-relevant update (now referred to as preview update) KB 5003214 once again and has now made it available for Windows 10 21H1, 20H2 and 2004. The new version number is 19043.1023, 19042.1023 or 19041.1023.

Known issues for KB5003214

• Currently none known.
• You can read about all outstanding problems here
• Should the error 0x800f0988 appear, you can try it with Ben's script . That has already helped many, even in previous versions. That may (does not have to) be due to the fact that the update cleanup is carried out after a non-security-relevant update.
• The error code 0x800f0922 may be because you have uninstalled Microsoft Edge . If you install it manually and then start the update, it will also run.

Fixed issues and improvements through KB5003214

• We fixed an issue with the just-in-time (JIT) behavior of jscript9.dll.
• We fixed an issue that could prevent users from opening phone apps that are pinned to the system tray. This problem occurs after upgrading to Windows 10 version 2004 and then using the Phone app.
• We fixed an issue preventing certain Win32 apps from opening when using the runas command.
• We fixed an issue preventing certain Win32 apps from opening when the BlockNonAdminUserInstall group policy is enabled.
• We fixed an issue where Progressive Web Application (PWA) icons would appear blank when you pin them to the system tray.
• We fixed an issue where the touch memory would not be properly managed before a session ends.
• We fixed a memory leak in ctfmon.exe that occurs when updating an application that has an editable field.
  Fixed an issue preventing a touch device from functioning as a serial mouse in multiple monitor situations.
• We fixed an issue where the settings page text, “Finish setting up your device”, appears unexpectedly on startup.
• We fixed an issue where items might appear on the desktop after you delete them from the desktop.
• We fixed an issue preventing users from viewing the Mouse Settings page when the group policy for the Settings page visibility is set to showonly: easeofaccess-mousepointer.
• We fixed an issue in Safe Mode preventing users from signing in when web sign-in is enabled.
• We fixed an issue in the Active Directory (AD) admin center that displays an error when it lists many organizational units (OU) or container objects and PowerShell transcription is enabled. The error message is: "Collection was modified after the enumerator was instantiated".
• We fixed an issue resulting in screen readers reporting the wrong UI information. This problem occurs because UI Automation reports inaccurate property information for some controls, such as IsDialog and IsControl.
• We fixed an issue where BitLocker encryption cannot be applied automatically via group policy. This problem occurs with external drives that have an active MBR (Master Boot Record) boot partition.
• We fixed a memory leak in PKU2U that is causing cluster nodes to run out of memory.

• We fixed an issue where the Autopilot Reset command would take too long to process after it was sent.
• We fixed an issue that could prevent the Windows Dynamic Host Configuration Protocol (DHCP) server from offering a lease to a DHCPv6 client after the client switched to a different virtual LAN (VLAN).
• We fixed an issue that prevents a task from working properly if you set the task to “Start only when the following network connection is available”.
• We fixed an issue that might display a "Device Removed" error when Direct3D developers use the SetStablePowerState () API in Windows Developer Mode.
• We fixed a bug that could cause video to fail when switching from an external high dynamic range (HDR) display to a built-in non-HDR display.
• We fixed a bug that resulted in the spatial audio effect not being applied to sounds when you enable spatial audio.
• We fixed an issue with noise when you enable Spatial Audio and use Bluetooth USB headphones.
• We fixed an issue with encoding metadata resulting in Free Lossless Audio Codec (FLAC) music files not playing if you change the title, artist, or other metadata.
• We added support for the .hif file extension for High Efficiency Image File (HEIF) images.
• We fixed an issue that could cause a system to stop working when using Remote Desktop to USB redirect an Xbox One controller.
• Fixed an issue that could cause a RemoteApp window to flicker or move to a different area of the screen when using touch or pen input.
• We fixed an issue with the PerfMon API that could cause handle leaks that slow performance.
• Fixed an issue that could cause infinite replication when promoting a new domain controller with the Active Directory Recycle Bin feature enabled.
• We fixed an issue that sporadically prevents the Resource Host Subsystem (RHS) from registering network name resources in the Domain Name System (DNS). As a result, Event ID 1196 appears.
• We fixed an issue with devices configured with the RestrictedGroups, LocalUsersAndGroups, or UserRights policies of Mobile Device Management (MDM). These devices incorrectly continue to receive the policy after you use MDM to remove the configuration profile that contains the policy. As a result, users of the affected devices may have incorrect group memberships and UserRights assignments or other symptoms. This issue occurs after installing Windows updates dated October 29, 2020 and later.
• We fixed an issue preventing users from getting geographic location information even if all the geolocation UI settings are correctly enabled and the device contains a location sensor.
• We fixed an issue where registering a DNS update for an A record and a PTR would fail when updating Azure virtual machines against corporate DNS zones.
• We fixed a timing issue that could result in a RemoteApp temporarily duplicating characters entered on the local keyboard or pasted from the Windows clipboard.
• blogs.windows

 

An update I can't seem to install... Keeps telling me it's corrupt or missing but how?

 

Visit https://www.catalog.update.microsoft.com/Home.aspx and download he relevant update. They have added/appended hashes after underscore to know downloaded file is intact.

 

Those failed as well, failed outright.

Consequently I just went ahead and upgraded to 21H1 to fix it, as I didn't think to keep a 20H2 USB to to an in-place upgrade.

 

Tried running Dism check health using dism gui https://majorgeeks.com/files/details/gui_for_dism.html

 

I have a 5.1 receiver and now speakers for that, and I want to have 5.1 sound as well. I have a MSI GT73 6re laptop, and 3 jack-rca cables running to the receiver yamaha rx-v 520. When I set the 5.1 in windows, the front and center speakers gave sound, but the rear ones look like they sound, but nothing comes through the rear channels. I've seen this problem, but there seems to be no fix for that.

What I've tried: realtek 2.82, 2.81, and the driver provided by the manufacturer.
An in place upgrade.
A "fresh start".

The driver I use now 6.0.8911.1
The only way I could open realtek hd audio manager was to not just update the driver, but install the 2.81, then start "driver booster" and let it work its magic. I don't even understand what is happening, but I'd be glad for a fix.

Also, I have some output from the rear channels when I play a movie with vlc player. Strange thing though that the main volume in windows volume mixer does not affect the rear speakers, but changing the volume in the vlc does affect it. The one in windows is basically every level I set results in the same volume from 1% to 100%. 0% means no sound, everything above is the same. I found no solution for this problem, and I think it is a windows problem, but I cannot tell which version, because I only have 5.1 since a month or so.

 

KB5003637 [manual download] June security update Windows 10 21H1, 20H2 and 2004 1904x.1052

It's Patchday June and with it comes the security update KB 5003637 for Windows 10 21H1, 20H2 and 2004. The new version numbers are 19043.1052, 19042.1052 and 19041.1052.

Known issues with KB5003637

• System and user certificates may be lost when upgrading a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices are only affected if they have already installed a Latest Cumulative Update (LCU) released on September 16, 2020 or later and then proceed with the update to a later version of Windows 10 from media or an installation source that does not contain an LCU released on October 13, 2020 or later. Workaround: go back to the previous version.
• A small group of users have reported lower than expected game performance after installing this update. Most of the users affected by this issue run games in full screen or borderless windowed mode and use two or more monitors.
• If you use the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows you to enter Furigana characters, you may not get the correct Furigana characters. You may have to enter the furigana characters manually.
  - After installing this update, 5.1 Dolby Digital audio playback may contain a high-pitched noise or squeaking noise when using certain audio devices and Windows settings in certain apps. Note: This problem does not occur when using stereo.
• For devices with Windows installations created from custom offline media or custom ISO images, Microsoft Edge Legacy may be removed by this update, but not automatically replaced with the new Microsoft Edge. This issue only occurs when creating custom offline media or ISO images by slipstreaming this update into the image without first installing the stand-alone Servicing Stack Update (SSU) dated March 29, 2021 or later.
• You can read about all outstanding problems here
• Should the error 0x800f0988 appear, you can try it with Ben's script . That has already helped many, even in previous versions.
• The error code 0x800f0922 may be because you have uninstalled Microsoft Edge . If you install it manually and then start the update, it will also run.

Problems fixed by KB5003637

• Updates to improve security when using input devices such as a mouse, keyboard or pen.
• Updates to improve the security of Windows OLE (compound documents).
• Username and password verification updates.
• Updates to improve security when Windows performs basic operations.
• Updates for storing and managing files.

• The individual explanations for the CVEs will then appear here: msrc.microsoft.com/update-guide

 

More fun... June 11, 2021—KB5004476 (OS Builds 19041.1055, 19042.1055, and 19043.1055) Out-of-band

Direct download link: KB5004476

Enjoy

The reason...

Windows 10 KB5004476 emergency patch released to fix Xbox issues windowslatest.com - June 12, 2021

 

June 21, 2021—KB5003690 (OS Builds 19041.1081, 19042.1081, and 19043.1081) Preview

Download Links for Windows 10 - KB5003690
Windows 10 KB5003690 Direct Download Links: 64-bit and 32-bit (x86).

 

Will try it out in few days.

 

They screwed up again...

June 29, 2021—KB5004760 (OS Builds 19041.1082, 19042.1082, and 19043.1082) Out-of-band

Highlights

• Updates an issue that might prevent you from opening PDFs using Internet Explorer 11 or apps that use the 64-bit version of the WebBrowser control. Additionally, a PDF might render as just a gray background when using the Adobe Acrobat plug-in.

Direct download link: KB5004760

 

I think I should have waited patiently for couple of days before updating.

 

Here is a new one. 3rd OOB patch within one month

July 6, 2021—KB5004945 (OS Builds 19041.1083, 19042.1083, and 19043.1083) Out-of-band

Highlights

• Updates a remote code execution exploit in the Windows Print Spooler service, known as “PrintNightmare”, as documented in CVE-2021-34527.

Direct download link - KB5004945

 

Not again.....

 

Never jump on it once its out. First this....

Microsoft's patch for PrintNightmare vulnerability can be bypassed completely [Update] neowin.com · Jul 7, 2021 · HOT! 28

Security researchers are reporting that Microsoft's fix for the PrintNightmare vulnerability that rolled out to most Windows versions is ineffective, and can let attackers completely bypass it

Then you have the usual behaviour. Double bad. Aka a useless and buggy update as usual. Isn't that correct bro @Mr. Fox

Windows 10 KB5004945 is causing major issues for some users windowslatest.com - July 9, 2021

Microsoft recently started rolling out Windows 10 KB5004945 emergency update to fix the PrintNightmare bug, but it appears to be causing serious problems for the printers of some users out there, according to various reports on social media platforms and our forums.

 

Everyone need to lock down their systems to block the cancer updates and take a chill pill.
"Once you are known as a liar, you will not be taken seriously."

 

from Bleepingcomputer

Microsoft pushes emergency fix for Windows 10 KB5004945 printing issues

Microsoft: PrintNightmare security updates work, start patching!

 

July 13, 2021—KB5004237 (OS Builds 19041.1110, 19042.1110, and 19043.1110)

Known issues with KB5004237

• Prophylactic: If the error 0x800f0988 occurs, you can try it with Ben's script . That has already helped many, even in previous versions.
• If you use the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows you to enter Furigana characters, you may not get the correct Furigana characters. You may have to enter the furigana characters manually.
  Note The affected apps use the ImmGetCompositionString () function.

Problems resolved by KB5004237

• Addresses an issue that can make printing difficult on certain printers. This issue affects several makes and models, but mainly receipt or label printers that connect through a USB port.
• Removes support for the PerformTicketSignature setting and permanently enables enforcement mode for CVE-2020-17049. For more information and steps to enable full protection on domain controller servers, see Manage Kerberos S4U Changes Deployment for CVE-2020-17049 .
• Adds Advanced Encryption Standard (AES) encryption protection for CVE-2021-33757 . For more information, see KB5004605 .
• Fixes a vulnerability where primary update tokens are not strongly encrypted. This issue can result in the token being reusable until the token expires or is renewed. For more information on this issue, see CVE-2021-33779.
• Security updates for Windows apps, Windows administration, Windows basics, Windows authentication, Windows user account control (UAC), operating system security, Windows virtualization, Windows Linux, the Windows kernel, the Microsoft Scripting Engine, the Windows HTML platforms who have favourited Windows MSHTML Platform and Windows Graphics.

Manual download of KB5004237

• Just as a note: SSU and LCU (Latest Cumulative Update) are integrated in the * .msu updates.
• windows10.0-kb5004237-x64.msu

July 13, 2021-KB5003537 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, and Windows Server, version 20H2, and Windows Version 21H1

NDP35-48
http://download.windowsupdate.com/c..._1fbdca72e07a18937ae2c81c032afecbb7fabe45.msu

 

Will wait for few days to release preview or even next month for new patches.

 

Yep

Microsoft's print nightmare continues with malicious driver packages
-
You might run into these bugs after installing KB5004237

http://forum.notebookreview.com/threads/windows-10-21h1.835604/page-7#post-11107085