Windows Update: New problems encountered, old ones solved

The Windows updates for the August Patchday have some unexpected side effects. However, Microsoft was able to solve older problems.

listen Print view
Windows Updates available: Download

(Image: heise online / dmk)

2 min. read

The updates for Windows that Microsoft distributed on Patchday in August last week are causing unexpected problems on several versions of Windows. Microsoft is working on solutions and out-of-sequence updates. The Redmond-based company has already been able to correct at least one issue.

The good news first: Last week, it became known that the Windows update for Windows 11 24H2 could fail if it was distributed via Windows Server Update Services (WSUS). According to the Windows Release Health note, the developers have solved the problem – if it still occurs, admins should perform a refresh and re-sync with WSUS. Those who have installed the group policy for the Known Issue Rollback (KIR) no longer need it.

Much less pleasing, however: After installing the August updates, attempts to reset or restore affected devices fail. The functions impacted are “System”—”Restore”—”Reset this PC” or “Fix problems using Windows Update,” as well as the RemoteWipe CSP available with the business licenses. The errors occur under Windows 11 23H2, 22H2, Windows 10 22H2, Enterprise LTSC 2021, IoT Enterprise LTSC 2021, Enterprise LTSC 2019, and IoT Enterprise LTSC 2019. The programmers want to follow up with an out-of-band update, i.e., one outside the usual release cycle, to correct this bug – however, Microsoft has not yet given a timetable.

Videos by heise

On Tuesday night of this week, Microsoft also admitted that upgrades with the August patches may fail with the error 0x8007007F. If the installation of the updates is initiated via “Windows Setup” – “Upgrade,” certain client and server upgrade paths may abort with the error. Microsoft mentions upgrades from Windows 10 1809, 21H2, and 22H2 to Windows 11 23H2 and 22H2, as well as from Windows Server 2016 to 2019 or 2022 and from Server 2019 to Server 2022. However, upgrades to the more recent versions Windows 11 24H2 and Windows Server 2025 are not affected, the company adds. Microsoft claims to have corrected this on Friday; those affected should now simply try again.

(dmk)

Don't miss any news – follow us on Facebook, LinkedIn or Mastodon.

This article was originally published in German. It was translated with technical assistance and editorially reviewed before publication.