The software giant confirmed that the problem – which meant that university Wi-Fi networks (and those at other educational establishments) failed to work for some students – was caused by patches KB5032288 and KB5033375.
The latter is the cumulative update for December in Windows 11, and the former is the preview version of that upgrade (unsurprisingly, as they are essentially the same thing).
The good news is that the solution came alongside the confirmation of the bug.
Microsoft got in touch with us directly to point out the fix, with the company also announcing on its release health status dashboard: “This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster.”
Analysis: A swiftly delivered save
It’s great to see Microsoft move quickly with the fix here, as this was a pretty nasty issue for those students affected. It seems that it was mainly universities, businesses, and public Wi-Fi networks where this gremlin struck, with Microsoft telling us that it’s “not likely to occur on home networks” (though that doesn’t rule out the possibility completely).
At any rate, you don’t have to do anything to cure these Wi-Fi blues. The Known Issue Rollback means that Microsoft is rolling back the problematic part of the update, while leaving the rest of it in place (to redeploy that faulty bit at a later date, when it’s fixed up and no longer causing Wi-Fi woes).
The catch is that the issue rollback takes a bit of time to filter through to everyone, up to 24 hours as noted. However, that announcement was made late in the day yesterday, and all affected users should have the fix in around the next five hours or so, all being well. If you’re getting impatient, as Microsoft advises, you can try a reboot to surface the fix.
That’s the KB5030310 update, which we should note is a preview update for those using Windows 11 22H2. (Folks can get the upgrade, and Copilot plus other goodies, by ensuring that they have chosen the option to ‘Get the latest updates as soon as they’re available’ in Windows Update).
As Windows Latest reports, some users who have installed KB5030310 (with the mentioned option to get the latest features activated) have run into some fairly nasty gremlins.
That includes reports of File Explorer – the central part of the Windows 11 interface that lets you work with folders and files on the desktop – becoming more prone to buggy behavior, and running noticeably slower in general. (Including sluggishness rendering the actual interface which sounds jarring indeed, as mentioned on Reddit).
Other folks are complaining about weirdness with the search box in the taskbar, with it failing to work, or the magnifying glass icon not rendering properly (in fact it’s shown as a letter ‘C’, oddly).
More worryingly, Windows Latest brings our attention to system crashes post-update, and black screens (the latter aren’t complete lock-ups, at least in some reported cases, and can be escaped from by bringing up the Task Manager).
Another bigger glitch here affects those who are using AMD graphics cards, and running the latest driver – apparently, KB5030310 doesn’t play nice with the Adrenalin driver 23.9.3. Every time the PC is restarted, those AMD GPU owners are telling us that their settings are being reset, which is going to get pretty old, pretty fast.
Analysis: The perils of previews
That’s a fair old raft of problems, then, some of which are going to be unpleasant to be visited on your PC. However, this is a preview update, and Microsoft is still working on the functionality therein – so it’s hardly unexpected to see flaws popping up. In fact, it’s very much expected, and of course, we get glitches on finished updates for Windows 11, not just those still officially in testing.
Unfortunately, if you want to get the latest features like Copilot straight away – as per the aforementioned toggle – via a preview release, then you have to be aware that you’re running some level of additional risk for encountering bugs.
What’s a bit more baffling is despite the reports coming in via Reddit and Microsoft’s Feedback Hub that Windows Latest has highlighted here, Microsoft still doesn’t see anything wrong.
In the support document for KB5030310, the company states: “Microsoft is not currently aware of any issues with this update.”
There may, however, be investigations underway regarding the reports of the various glitches covered above, so we might hear soon enough from Microsoft as to what’s going on with these apparent issues (and how widespread they might be, perhaps).
Windows 11’s latest cumulative update has been triggering a whole heap of problems going by a bunch of online reports, including causing havoc for PC gamers in some cases.
This is KB5030219, the compulsory update for September that was released last week and piped to Windows 11 22H2 systems.
Windows Latest spotted a catalog of reported gremlins in the works with KB5030219, and that includes the update causing Blue Screen of Death (BSoD) crashes.
On top of that, readers have reported instances of system slowdown to Windows Latest following the installation of KB5030219, and network connection problems, with internet access apparently failing for some post-installation.
There are also reports of PCs failing to start entirely after the update, which is very worrying of course – there’s nothing worse than your system failing to boot after applying an ‘upgrade.’
Another report on Reddit, on the official thread introducing KB5030219, complains about a problem where the Start menu (and search functionality) fails to work for some folks.
That Reddit thread contains quite a number of other issues, including various performance problems (like a very slow right-click menu) and tabs in File Explorer disappearing due to KB5030219, as well as some weird audio glitches. Oh, and installation failures, with the update failing to complete in some cases (a continued problem with Windows 11 cumulative updates for some folks).
And on top of that, as mentioned, PC gamers have been hit here. Windows Latest highlights some apparent performance glitches with Starfield, and a post on Microsoft’s own Feedback Hub claims the Game Pass version of Starfield is experiencing TDR (timeout detection and recovery) errors and crashes.
“After removing the update, the Starfield game ran normally,” the affected gamer observes.
However, Windows Latest further notes that it’s not sure if these Starfield performance issues could be related to Nvidia’s most recent GeForce driver, or to this Windows 11 cumulative update.
One Redditor certainly lays the blame at Microsoft’s door, saying: “It’s definitely a Windows update issue for me because I didn’t update my GeForce driver (I use the studio driver that is still at v536.99) but stupid me did the Windows update and now my PC is exhibiting all kinds of intermittent internet connection problems, lags, slow application startups, etc.”
Another Redditor claims: “Yes! I thought it was the new Nvidia driver I had installed at first, but then rolled it back and [the] issue [performance problem in Starfield] was still present. I then uninstalled update KB5030219 and issue was completely gone. Reinstalled the latest Nvidia driver again and it was fine. Not sure what they broke with that Windows update, but I won’t be reinstalling it until it has been addressed.”
Other reports from PC gamers include Ratchet & Clank: Rift Apart misfiring with crashes and freezes.
Analysis: Return of the timeouts (sadly)
This is a surprisingly lengthy laundry list of serious issues across the board, really. We expect some rockiness to be experienced with any new patch, true, but this kind of level of apparent chaos is a poor show from Microsoft. The range of the glitches, and the performance hits in many cases – for gaming, and operation within the Windows 11 environment in general – make for a truly worrying state of affairs.
What doesn’t help is there’s no admission from Microsoft that there’s anything amiss here, at least not yet. In the supporting bumph for KB5030219, Microsoft simply states that it is “not currently aware of any issues with this update” and leaves it at that.
What’s extra disappointing for us here is that TDR errors were resolved in July, with the cumulative update for that month – so to see them apparently making a return already is a bit of a blow, to say the least.
Hopefully, Microsoft will be investigating the many outlined issues here, because clearly, something has gone awry with KB5030219 – to see this much disgruntled chatter around an update, and such a wide-ranging set of apparent problems, is definitely concerning.
As Neowin spotted, there are complaints on Reddit that KB5027215 installs very slowly. One Redditor reports: “Only unusual thing that I noticed which others might have experienced is the long ‘cleaning up’ process post-update/pre-login on the reboot. That happens if you reboot for the cumulative update and the NET update at the same time.”
There are some other reports in that thread regarding the cumulative update for June completely failing to install (with the usual garbage error messages that mean nothing). Those instances are backed up by other users on Microsoft’s Feedback Hub.
There are also a couple of reports (from Redditors) that KB5027215 is causing more serious trouble, and in one case, it bricked the PC, and in another, Windows Update got stuck in a loop checking for updates.
Analysis: Be careful drawing conclusions
We must be careful about how much we read into reports of bricking devices, of course, when they are scattered findings. To illustrate this, in the above linked Reddit thread, there’s a complaint of a Windows 10 laptop going wonky post-update, with its charger no longer recognized, but it turns out that the cumulative update wasn’t to blame in this case.
In actual fact, it was a Dell firmware update pushed alongside patch KB5027215 which messed up the notebook’s charging functionality. So, while the initial reaction was to rage at the update – unsurprisingly – after investigation, KB5027215 was innocent here.
That said, the blame for pushing the new firmware directly to the laptop can be laid at the feet of Windows Update, which really shouldn’t be running that kind of firmware update automatically, in the background, without the user knowing. (It was not an update piped directly from Dell). So, this is still an issue Microsoft (indirectly) caused.
At any rate, the hints of serious trouble around KB5027215 may lead the cautious to pause this update for the time being, and that could be a wise decision. Hopefully Microsoft will investigate the issues flagged here, and any necessary fixes can be applied in a timely manner. The downside being that you’ll be left without those security measures brought in by KB5027215, of course.
Windows 11 is causing trouble for some users with AMD graphics cards, thanks to antics involving installing an outdated driver for Team Red’s GPUs.
What’s happening here is that Windows Update is going ahead with an automatic driver ‘update’ that actually installs an older graphics driver.
Windows Latest explains that it has received reports from readers, and via its forums, complaining about the issue, and also there’s a post on Reddit with some affected Windows 11 users making their feelings known, too.
Those hit by the glitch get an error message from AMD’s Adrenalin software informing them: “Windows Update may have automatically replaced your AMD Graphics driver. Hence, the version of AMD Software you have launched is not compatible with your currently installed AMD Graphics driver.”
In other words, Windows 11 has installed a Universal Windows Platform (UWP) driver, but this is an old version and incompatible with the AMD Adrenalin suite.
The good news is that it’s easy enough to fix this problem, as we’ll discuss next.
Analysis: A fairly easy fix – but don’t forget the extra step
The cure, fortunately, is relatively simple. You need to download the latest AMD Adrenalin driver for starters – then uninstall the current driver, and reinstall the new AMD driver. (Some also advise disconnecting from the internet while uninstalling and reinstalling the graphics driver in this way).
The next and very important step to take is to turn off Windows Update’s automatic graphics driver updates, to avoid this happening again. To do that, in the search box (taskbar), type ‘Device installation settings’ and click on this when it pops up in the panel above.
You’ll be presented with a question asking if you want to use automatic downloads for hardware manufacturers’ apps, to which you should reply ‘no’ (even though it says your device may not work as expected – don’t worry about that). Then click ‘Save Changes’ and the automatic graphics driver update will no longer happen. (If you don’t do this, you might find that Windows 11 changes the driver again, even after you’ve reverted it – and so on, ad nauseum, until Microsoft sorts out whatever the issue is here.)
Why is this happening? Good question, it’s a bit of an odd one. There’s clearly been a mistake somewhere at Microsoft, or maybe something has gone awry with the driver supplied by AMD. Hopefully, the situation will be rectified soon enough, but at least you can cure the problem manually as described above.