Windows 10: KB5012599

Old_hand · Apr 19, 2022

Well, I've had a lot of advice about this one and previous KBs not installing. All else failed, so I Reinstalled Win 10 with a lot of problems! After problematic April Downloads.. It's almost impossible to clear out "Software Distribution" entirely because Windows is still trying to Install this rogue. As for DISM, nothing happens! This was the situation before I Reinstalled. A load of "Stack"s were Installed.

:)

Brink · Apr 19, 2022

KB5012599 Windows 10 19042.1645, 19043.1645, 19044.1645 Win Update

Ghot · Apr 19, 2022

KB5012599 Windows 10 19042.1645, 19043.1645, 19044.1645 Win Update

Someone greased this update. Took only 8 minutes. *Smile

Brink · Apr 19, 2022

KB5012599 Windows 10 19042.1645, 19043.1645, 19044.1645

April 12, 2022 - KB5012599 (OS Builds 19042.1645, 19043.1645, and 19044.1645)

3/15/22
IMPORTANT Windows 10, version 20H2 will reach end of service on May 10, 2022 for devices running the Home, Pro, Pro Education, and Pro for Workstations editions. After May 10, 2022, these devices will no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows 10 or Windows 11.
We will continue to service the following editions: Enterprise, IoT Enterprise, Windows on Surface Hub, and Windows Server, version 20H2.

UPDATED 01/11/22
REMINDER Windows 10, version 2004 reached end of servicing on December 14, 2021. To continue receiving security and quality updates, Microsoft recommends that you update to the latest version of Windows 10.
To update to one of the newer versions of Windows 10, we recommend that you use the appropriate Enablement Package KB (EKB). Using the EKB makes updating faster and easier and requires a single restart. To find the EKB for a specific OS, go to the Improvements section and click or tap the OS name to expand the collapsible section.

11/17/20
For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. For an overview of Windows 10, version 20H2, see its update history page.

Note Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

Highlights

Updates security for your Windows operating system.

Improvements

Note To view the list of addressed issues, click or tap the OS name to expand the collapsible section.

Windows 10, version 21H2

Important: Use EKB KB5003791 to update to Windows 10, version 21H2.

This security update includes quality improvements. Key changes include:

This build includes all the improvements from Windows 10, version 20H2.

No additional issues were documented for this release.

Windows 10, version 21H1

Important: Use EKB KB5000736 to update to Windows 10, version 21H1.

This security update includes quality improvements. Key changes include:

This build includes all the improvements from Windows 10, version 20H2.

No additional issues were documented for this release.

Windows 10, version 20H2

Important: Use EKB KB4562830 to update to Windows 10, version 20H2.

This security update includes improvements that were a part of update KB5011543 (released March 22, 2022) and also addresses the following issues:

Addresses an issue that causes a Denial of Service vulnerability on Cluster Shared Volumes (CSV). For more information, see CVE-2020-26784.

If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.

For more information about security vulnerabilities, please refer to the new Security Update Guide website and the April 2022 Security Updates.

Windows 10 servicing stack update - 19042.1613, 19043.1613, and 19044.1613

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

Known issues in this update

[table][tr][td]Symptom[/td] [td]Workaround[/td] [/tr] [tr][td]Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.[/td] [td]To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU:

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

Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>

You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU.

If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.[/td] [/tr] [tr][td]After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING".[/td] [td]For more information and a workaround, see KB5005322.[/td] [/tr] [tr][td]After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red.[/td] [td]This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to non-managed personal devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files:

Windows Server 2022

Windows 10, version 2004, Windows 10, version 20H2, Windows 10, version 21H1, and Windows 10, version 21H2

Important Verify that you are using the correct Group Policy for your version of Windows.[/td] [/tr] [tr][td]After installing the Windows updates released January 11, 2022 or later Windows versions on an affected version of Windows, recovery discs (CD or DVD) created by using the Backup and Restore (Windows 7) app in Control Panel might be unable to start. Recovery discs that were created by using the Backup and Restore (Windows 7) app on devices which have installed Windows updates released before January 11, 2022 are not affected by this issue and should start as expected. Note No third-party backup or recovery apps are currently known to be affected by this issue[/td] [td]We are working on a resolution and will provide an update in an upcoming release.[/td] [/tr] [/table]

How to get this update

Before installing this update

Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

Prerequisite:

For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog:

If your devices do not have the May 11, 2021 update (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260).

Install this update

[table][tr][td]Release Channel[/td] [td]Available[/td] [td]Next Step[/td] [/tr] [tr][td]Windows Update and Microsoft Update[/td] [td]Yes[/td] [td]None. This update will be downloaded and installed automatically from Windows Update.[/td] [/tr] [tr][td]Windows Update for Business[/td] [td]Yes[/td] [td]None. This update will be downloaded and installed automatically from Windows Update in accordance with configured policies.[/td] [/tr] [tr][td]Microsoft Update Catalog[/td] [td]Yes[/td] [td]To get the standalone package for this update, go to the Microsoft Update Catalog website.[/td] [/tr] [tr][td]Windows Server Update Services (WSUS)[/td] [td]Yes[/td] [td]This update will automatically sync with WSUS if you configure Products and Classifications as follows: Product: Windows 10, version 1903 and later Classification: Security Updates[/td] [/tr] [/table]

If you want to remove the LCU

To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.

Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

File information

For a list of the files that are provided in this update, download the file information for cumulative update 5012599.

For a list of the files that are provided in the servicing stack update, download the file information for the SSU - version 19042.1613, 19043.1613, and 19044.1613.
Click to expand...

Source: https://support.microsoft.com/en-us/...e-589ba81ac2f5

Direct download links for KB5012599 MSU file from Microsoft Update Catalog:

Download KB5012599 MSU for Windows 10 v20H2, v21H1, and v21H2 32-bit (x86) - 312.4 MB

Download KB5012599 MSU for Windows 10 v20H2, v21H1, and v21H2 64-bit (x64) - 661.4 MB

Download KB5012599 MSU for Windows 10 v20H2, v21H1, and v21H2 ARM64 - 692.6 MB

UUP Dump:

32-bit ISO download: Select language for Feature update to Windows 10, version 21H2 (19044.1645) x86 - UUP dump

64-bit ISO download: Select language for Feature update to Windows 10, version 21H2 (19044.1645) amd64 - UUP dump

ARM64 ISO download: Select language for Feature update to Windows 10, version 21H2 (19044.1645) arm64 - UUP dump

UUP Dump - Download Windows Insider ISO Tutorial | Windows 11 Forum

Windows 10: KB5012599

KB5012599

KB5012599

KB5012599

KB5012599 - Similar Threads - KB5012599

KB5011831 and KB5012599 failed with error 0x8007000d

KB5011831 and KB5012599 failed with error 0x8007000d

KB5011831 and KB5012599 failed with error 0x8007000d

DISM error 14098 and Windows update failing to install KB5012599

DISM error 14098 and Windows update failing to install KB5012599

DISM error 14098 and Windows update failing to install KB5012599

KB5012599

KB5012599

KB5012599