KB5014699 Windows 10 21H2, 21H1 19044.1766, 19043.1766 update rolled out

CU June 2022 patch Tuesday update KB5014699 for Windows 10 21H2, 21H1 changes, bug fixes, direct download link, and ways to install.


Windows 10 is obtaining the security patches for June 2022 laden with necessary bug fixes. KB5014699 is the cumulative update for Windows 10 21H2, 21H1, and 20H2. This patch increases the Windows Version to 19044.1766, 19043.1766, and 19042.1766 respectively.

Full name of this patch is – 2022-06 Cumulative Update for Windows 10 for x64-based System (KB5014699). Let’s see what changes and improvements this release brings.

KB5014699 Windows 10 changes, fixes, known issues, and direct download link

Here is the changelog –

Bug fixes and changes

Windows Server, version 20H2

Remark: Use EKB KB4562830 to update to Windows Server, version 20H2.

This security update comprises improvements that were a part of update KB 5014023 (released June 2, 2022) and also addresses the following issues:

  • Addresses an elevation of privilege (EOP) vulnerability under CVE-2022-30154 for the Microsoft File Server Shadow Copy Agent Service. To become protected and functional, you must install the June 14, 2022 or later Windows update on both the application server and the file server. The application server runs the Volume Shadow Copy Service (VSS)-aware application that stores data on the remote Server Message Block 3.0 (or higher) shares on a file server. The file server hosts the file shares. If you don’t install the update on both machine roles, backup operations carried out by applications, which previously worked, might fail. For such failure scenarios, the Microsoft File Server Shadow Copy Agent Service will log FileShareShadowCopyAgent event 1013 on the file server. For more information, see KB5015527.

To see the details of security vulnerabilities, go to June 2022 Security Updates guide and release note.

See – Direct Download link KB5003791 Windows 10 21H2 enablement package.

Known issues


Symptoms Workaround
In the situation when you have installed the edition using a custom ISO image or custom offline media there will be a drawback regarding the browser Microsoft Edge. The legacy version of this app will be eliminated but the Chromium version browser will not be installed. The fault occurs when the ISO images or custom offline media are created by slipstreaming this update into the image without having installed the copy of standalone Servicing Stack Update 29/03/2021 or later.

Attention – In case, you have added outright to Windows Update to obtain updates the system would not have been not affected. Windows Update for Business is an instance.

Suppose you want to deal with this mess, first of all, slipstream SSU dated 29/03/2021 or further into the custom offline media or ISO image. Moreover, slipstream the CU means Cumulative Update. So, you will have to extract the SSU from the blend of SSU and LCU for Windows 10 v20H2 and v2004. Extract the SSU using the steps –

Extract the cab from the MSU through this command line (via the package for KB5014699 as an instance): expand Windows10.0-KB5014699-x64.msu /f:Windows10.0-KB5014699-x64.cab <destination path>

Unpack the Servicing Stack Update from the earlier extracted cab via this command line: expand Windows10.0-KB5014699-x64.cab /f:* <destination path>

You will then get the SSU cab, in this instance named SSU-19042.1766-x64.cab. Slipstream this file into your offline image initially, then the LCU aka Latest Cumulative Update

Subsequent to installing the 21/06/2021 patch named KB5003690), you might not fail to receive the 06/07/2021 patch (KB5004945) or next. However, you will confront the error code – PSFX_E_MATCHING_BINARY_MISSING. To see more go to – KB5005322.
Once acquiring this update, an authentication drawback occurs when connecting to devices in an untrusted domain through Remote Desktop. The glitch is that connections might fail to authenticate through smart card authentication. Oppositely, an error is thrown saying- “Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials.”. Otherwise, you may also encounter the error “The login attempt failed” in red. This issue is corrected through KIR aka Known Issue Rollback. Please remember that it might take upto 24 hours for the fix to propagate automatically to non-managed personal devices and non-managed business devices. Although, you can restart to lessen the time. Enterprise-managed users should download and install a special Group Policy (gpedit) from the below link –

1.   Windows Server 2022

2.   Windows 10 2004, Windows 10 20H2, Windows 10 21H1, Windows 10 21H2

Snip & Sketch app might fail to take a screenshot and open via the keyboard shortcut (Windows key+shift+S). This problem starts after installing KB5010342 (08/02/2022) and later updates. A team is looking into it and will provide an update when more information is available.

How to download KB5014699 and install

Prior to receiving the patch make sure to have the latest SSU version on your device. Now follow any of the methods –

Way-1: Directly through Windows update

  1. Press – Winkey.
  2. Type – updates.
  3. Hit – Enter.
  4. Click on Check for updates.
  5. To download KB5014699, give some time to the system. Once completed, you will see Restart now option; click this.
  6. Windows will deploy the update automatically after a few restarts.

Way-2: Manually via Microsoft update catalog

  1. Click KB 5014699 direct download link.
  2. Once you reach the Microsoft update catalog website, look for the file suitable to your computer specifications.
  3. Click on Download.
  4. A page will appear, click on the Standalone file’s link.
  5. After downloading is completed, double click on the .msu file and select Yes on the prompt.
  6. KB 5014699 will be installed successfully.

That’s all!!

Sharing is caring    Share Whatsapp

Topics:  Windows update
About Sunita
Love to play with Windows 11 and 10. Suggestion - Going for Registry change or system files edit then remember to take a backup or create a restore point before Starting.