Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Find information on known issues and the servicing status for Windows 10, version 1607 and Windows Server 2016. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Current status as of May 2, 2025
On October 13, 2026, Windows 10 LTSB 2016 will reach end of support. After this date, devices running this version will no longer receive security updates containing protections from the latest security threats. Check out the Microsoft lifecycle website and Lifecycle FAQ - Windows for more information.
On January 12, 2027, Windows Server 2016 will reach end of support. For more information about servicing timelines, see the Windows Server 2016 lifecycle page.
To learn about the latest version of Windows 11, see the Windows 11 release information page. For Windows Server, see the Windows Server release information page.
Known issues
See open issues, content updated in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).
| Summary | Originating update | Status | Last updated |
|---|---|---|---|
| Issues occur when using Microsoft Changjie Input Method Only devices using Traditional Chinese are affected. Reverting to the previous IME version prevents the issue. | OS Build 14393.8246 KB5062560 2025-07-08 | Confirmed | 2025-07-11 09:14 PT |
| Apps that acquire or set Active Directory Forest Trust Information might have issues Apps using Microsoft .NET to acquire or set Forest Trust Information might fail, close, or you might receive an error. | OS Build 14393.4886 KB5009546 2022-01-11 | Mitigated | 2022-02-07 15:36 PT |
| Windows Presentation Foundation (WPF) apps might close, or you may receive an error Microsoft and third-party applications which use the .Net UI framework called WPF might have issues. | OS Build 14393.4225 KB4601318 2021-02-09 | Mitigated | 2021-02-11 20:41 PT |
Issue details
July 2025
Issues occur when using Microsoft Changjie Input Method
| Status | Originating update | History |
|---|---|---|
| Confirmed | OS Build 14393.8246 KB5062560 2025-07-08 | Last updated: 2025-07-11, 09:14 PT Opened: 2025-07-11, 08:52 PT |
Following installation of the July 2025 Windows security updates (KB5062560), there might be issues when using the Microsoft Changjie IME (input method editor) for Traditional Chinese.
This issue only affects devices where Traditional Chinese is a preferred or common language or input method, and specifically where Changjie IME is used. Reported symptoms include:
- inability to form or select words after typing the full composition (associate phrase window)
- spacebar or blank key not responding
- incorrect or distorted word outputs
- the conversion candidate window fails to display properly
Microsoft Changjie is an IME that is included in Windows and available in currently supported versions.
Workaround: Windows IME supports a compatibility setting that allows using the previous version of an IME instead. Employing this option should help resolve this issue.
To revert to old version of the Microsoft Changjie IME, follow these steps:
- Open the Language & region setting. This can be accomplished by opening the Settings app, selecting Time & Language, then Language & Regions. You can also open the start menu and type "language" and select the top result.
- If Traditional Chinese is used on this device, the Chinese (Traditional) option will appear near the top. Select the three dots next to Chinese (Traditional) to open a menu and select Language Options.
- Under Keyboards, select the three dots next to Microsoft Changjie and select Keyboard Options from the menu.
- Under Compatibility, set the "Use previous version of Microsoft Changjie" option to On. Then select OK.
Next steps: We are working on a resolution and will provide more information when it is available.
Affected platforms:
- Client: Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
- Server: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2016
February 2022
Apps that acquire or set Active Directory Forest Trust Information might have issues
| Status | Originating update | History |
|---|---|---|
| Mitigated | OS Build 14393.4886 KB5009546 2022-01-11 | Last updated: 2022-02-07, 15:36 PT Opened: 2022-02-04, 16:57 PT |
After installing updates released January 11, 2022 or later, apps using Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might fail, close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. Note for developers: Affected apps use the System.DirectoryServices API.
Next Steps: This issue was resolved in the out-of-band update for the version of .NET Framework used by the app. Note: These out-of-band updates are not available from Windows Update and will not install automatically. To get the standalone package, search for the KB number for your version of Windows and .NET Framework in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog.
For instructions on how to install this update for your operating system, see the KB articles listed below:
- Windows Server 2022:
- .NET Framework 4.8 KB5011258
- Windows Server 2019:
- Windows Server 2016:
- Windows Server 2012 R2:
- Windows Server 2012:
Affected platforms:
- Client: None
- Server: Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
February 2021
Windows Presentation Foundation (WPF) apps might close, or you may receive an error
| Status | Originating update | History |
|---|---|---|
| Mitigated | OS Build 14393.4225 KB4601318 2021-02-09 | Last updated: 2021-02-11, 20:41 PT Opened: 2021-02-11, 17:49 PT |
After installing KB4601318, Windows Presentation Foundation (WPF) apps might close, or you may receive an error similar to:
Exception Info: System.NullReferenceException at System.Windows.Interop.HwndMouseInputProvider.HasCustomChrome(System.Windows.Interop.HwndSource, RECT ByRef)
at System.Windows.Interop.HwndMouseInputProvider.GetEffectiveClientRect(IntPtr)
at System.Windows.Interop.HwndMouseInputProvider.PossiblyDeactivate(IntPtr, Boolean)
at System.Windows.Interop.HwndMouseInputProvider.Dispose()
This occurs when disposing an HwndSource whose RootVisual is null, a situation that arises in Visual Studio when docking or splitting windows, and could arise in other apps.
Affected platforms:
- Client: Windows 10, version 1803; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
- Server: Windows Server, version 1803; Windows Server 2016
Workaround: To mitigate this issue when using Microsoft Visual Studio, update to the latest version. This issue is resolved starting with the following releases:
- Visual Studio 2019 version 16.9 Preview 4
- Visual Studio 2019 version 16.8.5
- Visual Studio 2019 version 16.7.12
- Visual Studio 2017 version 15.9.33
Developers can mitigate this issue in their own apps by setting two AppContext switches using one of the methods described in AppContext Class (System) under the heading “AppContext for library consumers”. The switches are named Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix and Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix; both should be set to “true”. The first switch avoids the crash, but re-introduces the issue addressed in this update. The second switch is currently ignored, but will be recognized in a future .NET update that addresses the issue for the null-reference crash; it restores the behavior originally intended to be addressed in this update.
For example, using the app.config file method to apply the workaround at application scope:
<AppContextSwitchOverrides value="Switch.System.Windows.Interop.MouseInput.OptOutOfMoveToChromedWindowFix=true; Switch.System.Windows.Interop.MouseInput.DoNotOptOutOfMoveToChromedWindowFix=true " />
Next steps: We are working on a resolution and will provide an update in an upcoming release.
Report a problem with Windows updates
To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.
Need help with Windows updates?
Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.
For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.
View this site in your language
This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.