Microsoft looking into several Windows 11 issues after September 26 (KB5043145) update, rollout halted

Microsoft’s latest September 2024 update, KB5043145, arrived on Windows 11 devices last week. And as we all know, when Microsoft rolls out updates, it can be a toss-up between exciting new features and pulling your hair out because something has gone terribly wrong. Spoiler: This update falls in the “hair-pulling” category for some, and I’m one of the unlucky victims.

First, let’s talk about the fun stuff — what’s new? Microsoft introduced some cool features, like the ability to share local files straight from the taskbar’s search results and tweaked the Delivery Optimization Settings to match the Windows 11 aesthetic. We even got a fancy new lock screen with centralized media controls and some housekeeping on the Start menu for easier user-switching.

But just when we thought the world of Windows was turning into sunshine and rainbows, bam! The gremlins started creeping in. Reports of BSODs (Blue Screen of Death) and its less-popular cousin, GSOD (Green Screen of Death), started flooding Microsoft forums. PCs went from being reliable workhorses to bricks, and I’m here to share my personal “fun” experience with this update’s mess.

Windows 11 BSOD, GSOD, Wi-Fi not working, and more

While some of us were just happy to see the new features, others quickly realized this update had a darker side. Some users, particularly those with Asus TUF A15 (2022) and ROG Strix G17 (2024) laptops, reported constant boot loops and crashes. Microsoft has admitted the problem and is working on it.

Microsoft has received some customer reports of devices restarting multiple times or becoming irresponsive with blue or green screens after trying to install the September 2024 non-security preview Windows update (KB5043145).

Elsewhere, people are also experiencing wireless mouse and keyboard issues alongside Wi-Fi connectivity problems. And guess what? I got hit with one of these beauties. My Wi-Fi decided it had enough of my Monday morning grind and disappeared. Poof! Just like that.

Imagine this: You’re in the middle of a workday, casually browsing, when suddenly, your Wi-Fi connection flatlines. First, I checked my router — everything was fine. Then I noticed the dreaded icon in the system tray, glaring at me like, “Not today!” I’m no stranger to tech troubles, so I sprang into troubleshooting mode, but to my dismay, Wi-Fi settings had simply vanished. No more connection options. Nada.

I dug through network settings, uninstalled and reinstalled Windows updates and drivers, reset network configurations, and even entered the Windows Insider beta program in desperation. Nothing worked. Every time I reinstalled the wireless drivers, I was greeted with a hopeful few seconds of connectivity — only for the drivers to mock me with that yellow exclamation mark in Device Manager again and again. USB tethering to my phone has been the only thing saving the day, and that’s how I’ve been getting my laptop online for now. That’s modern laptops without Ethernet ports for you, am I right?

Microsoft’s knows it’s a hot mess

Luckily, I’m not alone. Other users in the forums are also lamenting their Wi-Fi issues, and Microsoft has finally admitted that things went off the rails. KB5043145 is now recognized as a disaster on multiple fronts, from mouse and keyboard failures to WSL2 being rendered unusable for AMD systems. Oh, and let’s not forget the strange rollback to Windows 10-style right-click context menus for some users. This explains why they’ve reportedly halted the rollout of the botched Windows 11 KB5043145 update.

Microsoft has issued a Known Issue Rollback (KIR) to resolve the reboot problem. The good news? It should automatically propagate to devices, but there’s a catch — it could take up to 24 hours. If you’re lucky, restarting your machine might speed things up. In the meantime, users who are enterprise-managed or tech-savvy can also deploy a special Group Policy fix to handle things manually.

But what about Wi-Fi? Microsoft’s acknowledgment doesn’t mention my issue specifically, so I’m crossing my fingers that they’re working on that too. Until then, I’m rocking USB tethering like it’s 2010.

So, if you haven’t installed this update yet — count yourself lucky. Maybe hold off for a bit, especially if you’re reliant on Wi-Fi for your daily work (which, let’s be honest, is pretty much everyone). If you’ve already installed it and haven’t faced any issues yet, well, consider yourself blessed.

But for the rest of us dealing with the fallout, remember, there’s light at the end of the tunnel — Microsoft is on it (we hope). In the meantime, bookmark that rollback procedure just in case.