The images in this article were generated with artificial intelligence. How we publish
Microsoft has stopped the distribution of an optional Windows 11 update after several teams began to fail when installing it with a recurring error. The update in question, identified as KB5079391, was offered as a preview with changes and improvements - including Smart App Control settings, screen optimizations and Windows related corrections Hello Fingerprint and Windows recovery on ARM64 devices running apps x64 - but some users started to see that the installation did not advance due to the known error 0x80073712.
The failure is manifested when the system tries to download or apply the package files and Windows Update returns a message indicating that files are missing or that there are problems with the components needed to complete the update. In view of the repetition of these failures, Microsoft decided to temporarily limit the availability of the package to prevent more equipment from being affected while investigating the root of the problem. The official note and update details can be found in the Microsoft support sheet: KB5079391, and the status platform of Windows versions offers context on incidents and deployments: Windows Release Health.

That an optional cumulative preview is paused is not extraordinary, but it is a nuisance for administrators and users who wanted to test the news before they reach the entire machine park. Microsoft has not announced a specific date for an arrangement, although it is most likely that it will publish a corrected version before the next round of scheduled updates (the well-known Patch Tuesday) so that the changes can be reviewed in test environments before their mass distribution.
This episode is added to a streak of recent issues related to Windows updates: in March Microsoft had to publish an emergency correction for a failure that was preventing you from logging into Microsoft accounts in several applications such as Teams, Edge and OneDrive. In addition, out-of-cycle updates have been launched from the month patch to solve Bluetooth device visibility problems and other point corrections in business environments with hotpatch, as well as guides to solve access to C disk: in some Samsung laptops affected by a defective version of the brand connectivity software. The sum of these incidents recalls that the operational system updates, although necessary, can introduce unexpected regressions.

If you meet the 0x80073712 error when trying to install KB5079391, the situation has two ways: in many cases the deployment pause itself will prevent Windows Update from trying to offer you the update again, so no immediate action will be necessary. If you are in a critical environment or manage several teams, it is recommended to follow the official Microsoft status and support pages and wait for the revised version. For individual users who prefer to try a repair, there are maintenance procedures that help to recover the Windows component store - tools such as DISM and SFC - and Windows Update problem resolution utilities can be useful; Microsoft publishes diagnostic and repair guides in its technical documentation and support pages.
In any case, it is appropriate to keep calm and prioritize stability: if your computer works properly and does not depend on a specific function included in the preview, it is wise to wait for Microsoft to confirm the correction and resume the deployment. To follow the evolution of this incidence and know the corrected version when available, see the KB note linked above and the Windows status page. To continue covering news and analysis on Windows updates, you can read specialized media that often track these stops and patches, such as BleepingComputer: bleepingcomputer.com.
In summary: Microsoft has temporarily paused the distribution of KB5079391 for a problem that causes the error 0x80073712 on some equipment. There is no exact date for the solution, and the safest for most users is to wait for official correction, while advanced administrators and users can rely on Microsoft diagnostic tools and guides to mitigate the problem if necessary.
Related
More news on the same subject.

Four Plex2Shell CVE allows remote execution and mining and proxy backdoor deployment
In recent days, an increase in attacks has been confirmed that take advantage of a chain of failures in Plex Media Server - nicknamed "Plex2Shell" by researchers - to run code r...

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...

Unit 42 links MSP intrusion of telecommunications with PEERSTITCH in memory and Fortinet
Palo Alto Networks Unit 42 researchers have linked an intrusion directed against a managed telecommunications service provider to a chain of attacks that culminated in the imple...