Briefly
On March 10, 2026 Microsoft released patch KB5079473 for Windows 11 (versions 24H2 and 25H2). After installation, reports of system failures began appearing on Microsoft’s official forum: frequent reboots (every 10–20 minutes), freezes, and errors with codes ATTEMPTED_WRITE_TO_READONLY_MEMORY (0xBE) and 0x800704b3. In some cases applications stop launching, including Microsoft Office.
Who is reporting and what to watch for
The information comes mostly from Microsoft’s official support forum and user reports via Feedback Hub. There is not yet a single large-scale statement from Microsoft about the cause, but the number of reports indicates a systemic issue rather than isolated coincidences.
"After installing the patch the computer started rebooting every 15 minutes — working with documents became impossible."
— Oleksiy, IT administrator, Microsoft forum user
What Microsoft advises
Microsoft support recommends temporarily pausing updates or uninstalling the problematic patch through Windows Update settings. The company also encourages submitting reports through the Feedback Hub so engineers can reproduce the issue and speed up the release of a fix.
"If you notice instability after the update, pause updates or uninstall the relevant update and submit a report through Feedback Hub."
— Microsoft Support
Practical steps for users
To minimize risks to work or critical services, act by priority:
1) Temporarily pause updates: Settings > Windows Update > Pause updates. This is a simple first step that will protect other machines on the network.
2) Uninstall the update (if already installed): Windows Update > Update history > Uninstall updates — find KB5079473 and remove it. For businesses — perform this on a test machine before a widespread response.
3) Submit a detailed report: Feedback Hub — include logs, screenshots and the times of failures. This will speed up Microsoft engineers’ work.
4) Controls for organizations: IT departments should disable automatic updates on critical systems and conduct a driver inventory — analysts suggest the issue may be related to a driver conflict or a kernel-level module.
Context and what’s next
Amid talk about Windows 12 with AI and the new Xbox mode, it’s important not to trade basic stability for promising features. For Ukraine, stability is not just convenience: it is working documents, volunteers’ information exchange, and business processes of defense enterprises. Therefore the priority is testing and a conservative approach to updates.
Conclusion
Until Microsoft issues an official fix, the smartest course of action is to pause updates on critical machines, restore functionality by removing KB5079473 where necessary, and send detailed reports via Feedback Hub. This is not about fear, but about responsibility: technical stability today is the foundation of digital security tomorrow. Whether Microsoft’s engineers will turn these signals into a quick fix depends on the volume and quality of feedback from users and organizations.
