[German]Another small addendum or collective article on known issues that Microsoft confirmed at the beginning of July 2025 for various Windows client versions. These range from broken Emoij search to firewall problems that have not yet been resolved. And Defender also seems to be causing problems.
The details can be found on the Windows Release Health dashboard. The documented issues are briefly addressed below – for details, please consult the support articles for the respective Windows versions.
Changjie problems due to July 2025 update
In various Windows versions, there may be problems using the Microsoft Changjie IME after installing the security updates from July 14, 2025. This is an input method editor for traditional Chinese and is less likely to affect the readers of this blog. It affects all clients from Windows 10 onwards and all servers from Windows Server 2016 onwards. The details can be found in the support article Issues occur when using Microsoft Changjie Input Method.
Update error 0x80070643 due to Windows RE update
It's a problem that has been dragging on for months – I mentioned it at the beginning of May 2025 in the article Windows 10/11/Server 2022: Microsoft says "No more fix for installation error 0x80070643 during WinRE update".
After installing the update KB5057588 for the Windows Recovery Environment from April 2025, users may receive the error message 0x80070643 – ERROR_INSTALL_FAILURE from Windows Update. This affects certain Windows 10 versions and Windows Server 2022.
The Windows Recovery Environment (WinRE) is a recovery environment that can resolve common causes of unbootable operating systems.
According to the support article The April 2025 Windows RE update might show as unsuccessful in Windows Update dated April 11, 2025, the problem was marked as "resolved" on July 8, 2025. The solution states that this error message is incorrect and has no impact on the update or device functionality.
According to Microsoft, the error message occurs when the device installs the WinRE update while another update is in a pending reboot. Although the error message indicates that the update has not been completed, the WinRE update is usually applied successfully after the device restarts.
Windows 10: Emoji search panel broken
According to the support article The Windows Emoji Panel search feature cannot find any results, the security update KB5062554 from July 14, 2025 has corrupted the search in the Emoji Panel of Windows 10 22H2. The Windows Emoji Panel search feature can no longer find any results in Windows 10 version 22H2. The problem is currently being investigated by Microsoft.
Firewall continues to trigger events with warnings
In the blog post Windows 11 24H2: June 2025 Preview Update KB5060829 triggers Firewall Events, I reported that administrators suddenly find entries triggered by the Windows Firewall for Advanced Security in the Windows Event Viewer after installing the preview update in question. Microsoft's advice at the time was that these event entries with the warnings could be ignored. The entries originated from a built-in function that had not yet been fully implemented, Microsoft said.
I remembered that Microsoft had described the problem as solved with the July 2025 update KB5062553 (see Patchday: Windows 10/11 Updates (July 8, 2025)). On July 15, 2025, Microsoft confirmed the problem again in the support article Error events are logged for Windows Firewall for Windows 11 24H2 bestätigt. There you can also read that the solution to the firewall log problem was incorrectly announced in July 2025.
Microsoft Defender VulnerableDriver:WinNT/Winring0 alert
Microsoft has published the support article Microsoft Defender Antivirus alert – VulnerableDriver:WinNT/Winring0 (noticed here). According to this, an alert is triggered by Microsoft Defender under the operating system mentioned, which reports a VulnerableDriver:WinNT/Winring0 detection.
This detection is valid because the WinRing0 driver has been classified as a known vulnerability CVE-2020-14979. The more exciting question is why a VulnerableDriver:WinNT/Winring0 detection has suddenly appeared.
Some games and hardware monitoring applications may be affected. Microsoft mentions tools such as CapFrameX, EVGA Precision X1 (older versions), FanCtrl, HWiNFO, Libre Hardware Monitor, MSI Afterburner, Open Hardware Monitor, OpenRGB, OmenMon, Panorama9, Razer Synapse, SteelSeries Engine, ZenTimings and others. These all use a Winring0 driver. If you use one of these applications and receive a Defender alert, you can add an exclusion for this driver file in Microsoft Defender Antivirus, according to Microsoft.
The July WinRE update KB5063523 broke Defender Offline Scan in Windows 10 22H2 on two different systems.
Has happened before with previous WinRE updates.
The reagentc fix does not work.
Restored the recovery partition from a previous drive image and hid the update,