Microsoft Halts Buggy Windows 11 Update After Installation Errors

Michael Miller · 2026-03-30

So, Microsoft just hit the brakes on a Windows 11 update. You know how these things go—sometimes an update rolls out, and instead of fixing things, it just creates a whole new set of headaches. That's exactly what happened with a recent non-security preview update, which Microsoft has now pulled from distribution. It's not a full-blown security patch, mind you. This was one of those optional preview updates, the kind you might install if you're feeling adventurous and want to test drive some fixes before the general public gets them. But this one came with a nasty bug that triggers a specific error code during installation: 0x80073712. ### What Went Wrong with This Update? That error code might look like random gibberish, but it's actually Windows' way of saying something went seriously wrong with the installation process. Think of it like trying to assemble furniture with missing screws and confusing instructions—the pieces just won't fit together properly. Microsoft hasn't spelled out every single detail about what's broken, but they've confirmed they're investigating the known issue. When a company pulls an update this quickly, you know they've found something that affects enough users to warrant immediate action. Here's what we do know: - The update was labeled KB5079391 - It was a non-security preview update for Windows 11 - The main problem appears during installation - Microsoft has removed it while they investigate  ### Why These Updates Matter (Even Non-Security Ones) You might be thinking, "Well, it's not a security update, so how important could it really be?" That's a fair question, but these preview updates actually serve a crucial purpose in Microsoft's development cycle. They're like test drives for fixes and improvements. Microsoft releases them to a smaller group of users who opt in, gathers feedback, and then refines the updates before pushing them to everyone. When one of these goes wrong, it disrupts that whole feedback loop. What's more concerning is that even non-security updates can contain important stability fixes, performance improvements, or compatibility patches. If you're experiencing issues with certain hardware or software, you might be eagerly awaiting these updates to resolve your problems. ### What Should You Do If You Already Installed It? If you're one of the people who managed to install this update before Microsoft pulled it, don't panic. The issue appears to be with the installation process itself, not necessarily with the update once it's installed. That said, here are a few things to keep in mind: - Monitor your system for any unusual behavior - Check Windows Update for any new patches that might replace this one - Consider creating a system restore point if you haven't recently - Remember that Microsoft will likely release a fixed version soon As one Windows expert put it recently, "These hiccups are part of the modern computing landscape. What matters is how quickly and transparently companies respond." ### The Bigger Picture: Update Quality and Trust This incident touches on something bigger than just one buggy update. It's about the delicate balance between releasing updates quickly and ensuring they're stable. Microsoft, like all tech companies, walks a tightrope here. On one hand, users want timely fixes and new features. On the other hand, nobody wants updates that break their systems. When an update gets pulled like this, it can shake user confidence, even if the company is doing the right thing by addressing the problem promptly. What's encouraging is that Microsoft caught this relatively quickly and took action. In the past, some problematic updates circulated for days or even weeks before being addressed. The faster response time suggests improved monitoring and quality control processes. ### Looking Ahead: What Comes Next? Microsoft will likely release a revised version of this update once they've identified and fixed the installation issue. They might also provide more detailed information about what caused the problem and how they're preventing similar issues in the future. For now, if you were planning to install this update, you'll need to wait a bit longer. Windows Update should no longer offer it to you, but if you do see it listed, it's probably best to hold off until Microsoft gives the all-clear. These situations remind us that technology, for all its advances, still has human beings behind it—and human beings make mistakes. The test isn't whether mistakes happen, but how we respond to them. Microsoft's quick pull of this update suggests they're taking their responsibility seriously, even if it's frustrating for users caught in the middle. Just remember: when it comes to updates, sometimes patience really is a virtue. Waiting a few extra days for a stable version beats dealing with installation errors and potential system issues any day of the week.