None
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 11, version 21H2, see its update history page.**Note **Follow [@WindowsUpdate]() to find out when new content is published to the Windows release health dashboard.

**Tip: **Looking for this month’s video? It’s now in the Windows 11, version 22H2 article.

## Highlights

* This update addresses security issues for your Windows operating system.

## Improvements

This security update includes improvements that were a part of update KB5026436 (released May 23, 2023). When you install this KB:

* This update addresses a known issue that affects 32-bit apps that are [large address aware]() and use the [CopyFile API](). You might have issues when you save, copy, or attach files. If you use some commercial or enterprise security software that uses extended file attributes, this issue will likely affect you. For Microsoft Office apps, this issue only affects the 32-bit versions. You might receive the error, “Document not saved.”
* This update addresses a compatibility issue. The issue occurs because of unsupported use of the registry.
* This update addresses an issue that affects the Windows Kernel. This issue is related to CVE-2023-32019. To learn more, see KB5028407.
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 [Security Update Guide]() website and the [June 2023 Security Updates]().

### Windows 11 servicing stack update – 22000.2000

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

**Applies to**| **Symptom**| **Workaround**
—|—|—
All users| After installing this or later updates, Windows devices with some third-party UI customization apps might not start up. These third-party apps might cause errors with explorer.exe that might repeat multiple times in a loop. The known affected third-party UI customization apps are ExplorerPatcher and StartAllBack. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device.| We recommend uninstalling any third-party UI customization app before installing this or later updates to prevent this issue. If your Windows device is already experiencing this issue, you might need to contact customer support for the developer of the app you are using. If you are using StartAllBack, you might be able to prevent this issue by updating to the latest version (v3.5.6 or later).We are presently investigating and will provide more information when it is available.

## How to get this update

**Before installing this update**Microsoft 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](). **Install this update****Release Channel**| **Available**| **Next Step**
—|—|—
Windows Update and Microsoft Update| Yes| None. This update will be downloaded and installed automatically from Windows Update.
Windows Update for Business| Yes| None. This update will be downloaded and installed automatically from Windows Update in accordance with configured policies.
Microsoft Update Catalog| Yes| To get the standalone package for this update, go to the [Microsoft Update Catalog]() website.
Windows Server Update Services (WSUS)| Yes| This update will automatically sync with WSUS if you configure **Products and Classifications** as follows:**Product**: Windows 11**Classification**: Security Updates

**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 5027223](). For a list of the files that are provided in the servicing stack update, download the [file information for the SSU – version 22000.2000]().Read More