NewApp Digest
search bot

installation issue

Microsoft fixes Windows Server 2016 security update failures
Winsage
June 18, 2026

Microsoft fixes Windows Server 2016 security update failures

Microsoft resolved an installation issue affecting the June 2026 security updates (KB5094122) on Windows Server 2016 systems that had not previously installed the KB5087537 update, which was a prerequisite. Users had encountered 0x80070002 or FILENOTFOUND errors. Microsoft acknowledged the problem and confirmed that affected devices should no longer experience installation failures for the June 2026 update. Additionally, Microsoft fixed a similar issue with the May 2026 Windows 11 security update (KB5089549) that resulted in 0x800f0922 errors due to insufficient space on the EFI System Partition. They also warned users about potential installation issues with error codes 0x80073712 or 0x800f0993 on devices upgraded to Windows 11 24H2 or 25H2. Furthermore, Microsoft addressed a boot issue for Windows Server 2025 devices after the April 2026 update and a bug affecting installation failures for updates since May 2025 using the Windows Update Standalone Installer (WUSA). Lastly, they are investigating a separate issue preventing third-party applications from launching essential Office programs after the June 2026 updates.
Microsoft fixes Windows update failures linked to WUSA installer
Winsage
June 12, 2026

Microsoft fixes Windows update failures linked to WUSA installer

Microsoft resolved an issue affecting the installation of Windows updates released since May 2025, which primarily impacted users using the Windows Update Standalone Installer (WUSA) from a network share, especially in enterprise environments. The problem was significant for devices running Windows 11 24H2/25H2 and Windows Server 2025, but did not occur when handling a single .msu file or when files were stored locally. In August 2025, Microsoft acknowledged that updates installed using WUSA might fail with error ERRORBADPATHNAME when multiple .msu files were involved. A Known Issue Rollback Group Policy was implemented in September 2025 to mitigate the impact on home and non-managed business devices. The issue was ultimately resolved with cumulative updates released in June 2026 for Windows 11 (KB5079391) and Windows Server 2025 (KB5094125). Microsoft provided a workaround for users experiencing difficulties with prior updates by suggesting they save .msu files locally for installation. Users were also advised to wait at least 15 minutes after installing an .msu file via WUSA before checking the Update History page. Additionally, Microsoft had previously addressed another issue in April 2025 that affected enterprise customers installing security updates via WSUS, which recurred in the August 2025 updates. Microsoft warned customers about potential issues with installing the latest monthly updates on devices upgraded to Windows 11 24H2 or 25H2.
Windows boot partition runs out of space for Microsoft's May security update
Winsage
May 18, 2026

Windows boot partition runs out of space for Microsoft’s May security update

Microsoft has acknowledged a potential issue with its May 2026 security update, which may fail to install properly due to insufficient space in the EFI System Partition (ESP). If the available space in the ESP drops below 10 MB, users may encounter a 0x800f0922 error code, leading to installation failures during the reboot phase. This issue affects Windows 11 versions 25H2 and 24H2. Microsoft has proposed two solutions: a registry edit or a Known Issue Rollback (KIR), which has already propagated to consumer and non-managed business devices. The update addresses several critical Microsoft CVEs, although there have been no reports of active exploitation.
silver Android smartphone
Winsage
April 3, 2026

New out-of-band Windows 11 update fixes March’s installation errors – how to get it

Microsoft faced backlash due to the March non-security preview update (KB5079391) for Windows 11, which caused installation errors for many users. In response, Microsoft paused the initial update and released an out-of-band update (KB5086672) on March 31, 2026, to address these issues. The new update includes all enhancements from the previous update and fixes the installation problems. Users set to receive preview updates will automatically download KB5086672, while others can manually check for it in the Windows Update settings. Users can also manage their preferences for optional preview updates through the Windows Update screen.
Microsoft: Windows bug blocks Microsoft 365 desktop app installs
Winsage
November 17, 2025

Microsoft: Windows bug blocks Microsoft 365 desktop app installs

Microsoft is addressing an issue preventing users from installing Microsoft 365 desktop applications on Windows devices due to misconfigured authentication components. The affected versions are Microsoft 365 desktop apps version 2508 (Build 19127.20358) and version 2507 (Build 19029.20294). Microsoft is working on reconfiguring the authentication components, with a resolution expected to be deployed soon. The issue has been classified as incident OP1186186, indicating a critical service disruption. Additionally, another problem, tracked as MO1176905, is affecting some admins and users by restricting access to various Microsoft 365 services due to a misconfiguration related to Microsoft 365 Group SecurityEnabled settings. Recently, Microsoft resolved a bug related to Microsoft Intune and mitigated a DNS outage that affected global customers.
Microsoft patch Tuesday update fails to install
Winsage
August 14, 2025

Microsoft patch Tuesday update fails to install

Microsoft has acknowledged an issue with its August Patch Tuesday update affecting installations via Windows Server Update Services (WSUS), specifically that the "August 12, 2025 Windows security update for Windows 11, version 24H2, might fail to install with error code 0x80240069 when installed via WSUS." This error complicates update management for organizations using WSUS. Microsoft is working on a resolution for this issue, which will be included in a future Windows update. Administrators can manually install the patch or use a provided group policy as a workaround. There is currently no timeline for when the installation issue will be resolved.
Microsoft reiterates it may never truly be able to fix Windows Update 0x80070643 error
Winsage
July 13, 2025

Microsoft reiterates it may never truly be able to fix Windows Update 0x80070643 error

In April, Microsoft released dynamic updates for Windows 10, including KB5057589, which was intended for the Windows Recovery Environment (WinRE). Users faced issues with the 0x80070643 error code despite having sufficient disk space. Microsoft decided not to reoffer this update to users who installed it and promised a more reliable update. In July 2025, Microsoft released a new WinRE update, KB5063523, which automatically applies the Safe OS Dynamic Update (KB5062691) to enhance recovery features. This update resolves the previous installation issue, although the error code may still appear. Additional dynamic updates released on July 8, 2025, include KB5062682, KB5062787, KB5062788, KB5062691, KB5062689, and KB5062692, all aimed at improving Windows setup and recovery environments. These updates will be automatically downloaded and installed via Windows Update.
Microsoft confirms Windows 11 KB5044284 / KB5046617 can't install new updates
Winsage
December 27, 2024

Microsoft confirms Windows 11 KB5044284 / KB5046617 can’t install new updates

Microsoft has acknowledged an issue affecting users of Windows 11 version 24H2 who installed the OS using external media like CDs or USB drives. Users may be unable to install security updates released during the October 2024 (KB5044284) and November 2024 (KB5046617) Patch Tuesdays if they used external media for installation. This issue does not affect installations via Windows Update or the Update Catalog. The problem arises when the installation media includes the October or November security updates. Microsoft recommends avoiding installations with these updates and instead using media that includes the December 2024 monthly security update or later. Microsoft is investigating the issue and will provide further updates.
Search