Latest / The Windows Podcast with Fexingo: Microsoft, PC, and Enterprise Windows Conversations / Windows 11 Is Forcing Enterprises to Rethink Wi-Fi
Transcript
- Lucas: So if you’re an IT admin managing a fleet of Windows 11 machines, you may have noticed something weird happening after the 24H2 update — devices randomly dropping Wi-Fi, especially on older access points. Luna: We’ve been getting messages about this for weeks. Some people thought it was a bad driver update, but it seems deeper. Lucas: It is. The core issue is that Windows 11 24H2 introduced a new Wi-Fi driver stack to support Wi-Fi 7 — the newest standard. But in doing so, Microsoft changed how the OS negotiates connections with older access points, particularly those running 802.11ac, or Wi-Fi 5. Luna: And enterprise environments are full of those. Most corporate offices deployed Wi-Fi 5 access points in the last five to seven years, and they’re not exactly cheap to rip out. Lucas: Right. So what happens is the new stack tries to enable Wi-Fi 7 features like multi-link operation — even when the access point doesn’t support it. That causes negotiation failures, and the device either disconnects and reconnects, or it falls back to a slower mode inconsistently. Luna: And we’re not talking about a small subset of devices. I’ve seen reports from IT admins saying up to 15 percent of their fleet started having connectivity issues right after the 24H2 update. Lucas: That’s huge. For a company with five thousand laptops, that’s seven hundred fifty devices with spotty Wi-Fi. Help desk tickets spike, productivity drops, and the immediate fix is usually a driver rollback — which Microsoft has made harder in 24H2. Luna: Wait — they made driver rollbacks harder? Lucas: Yeah. In previous versions, you could go into Device Manager, find the Wi-Fi adapter, and select 'Roll Back Driver'. In 24H2, if the driver is part of the Windows Update-managed stack, the rollback option is greyed out. Microsoft wants you using the signed driver from the update. Luna: So IT admins have to either block the update altogether — which is its own headache — or find the old driver from the OEM’s site and sideload it. Lucas: Exactly. And that’s not sustainable for a large enterprise. Plus, Microsoft is deprecating older Wi-Fi protocols. They’ve already announced that Windows 11 will drop support for WPA2-TKIP and 802.11n in future releases. So the message is clear: upgrade your infrastructure or deal with increasing breakage. Luna: And that ties into something you mentioned earlier — the cost. A single enterprise-grade Wi-Fi 6 or 6E access point can run three to five hundred dollars. For a campus with a hundred access points, that’s thirty to fifty grand, plus installation. Lucas: Right. And that’s just hardware. There’s also the time to test and redeploy. IT admins I’ve talked to say they’re planning to skip Wi-Fi 6 entirely and go straight to Wi-Fi 7, but those access points are still expensive and availability is spotty. So they’re stuck. Lucas: Now, there is a workaround. You can use Group Policy to disable the new Wi-Fi 7 features. Microsoft published a policy called 'Disable Wifi7' — yes, that’s the actual name — which forces the driver to behave more like the old stack. Luna: Okay, but that’s a band-aid. And it means you’re not getting any of the benefits of Wi-Fi 7 if your hardware does support it. Lucas: Exactly. It’s a stopgap while you plan the upgrade. But the bigger point here is that Microsoft is using the Windows update mechanism to push hardware compatibility forward — whether enterprises are ready or not. Luna: And that’s been a theme across a lot of our recent episodes — forced upgrades, deprecation, end of support. It feels like Microsoft is tightening the screws. Lucas: They are. And look, I get their perspective. Maintaining backward compatibility for decade-old Wi-Fi standards is costly and holds back innovation. But the way they’re doing it — silently changing the driver stack in a feature update — catches enterprises off guard. Luna: Speaking of catching people off guard — we should mention that conversations like this, where we dig into real-world IT problems, only happen because this podcast is listener-supported. A couple of dollars a month is genuinely what keeps these going. If today’s tech conversation gave you something usable, you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, it really does make a difference. Helps us stay independent and keep digging into these niche but critical topics. Luna: Alright, back to the Wi-Fi mess. One thing I want to explore — what about the testing process? How are enterprises supposed to catch this before it hits production? Lucas: Great question. The standard advice is to pilot the update in a test ring with representative hardware. But the problem is that the Wi-Fi issue doesn’t show up on every access point. It depends on the specific chipset, firmware version, and even the channel configuration. So you might test with three different access points and see no issues, then deploy to production and hit problems on a fourth model. Luna: So it’s hard to reproduce consistently. That’s a nightmare for QA. Lucas: It really is. I spoke with a network engineer at a mid-size financial services firm. They have about two hundred access points from a major vendor, all Wi-Fi 5. After 24H2, they saw intermittent disconnects on about twenty percent of their devices — but only in one wing of the building. They traced it to a specific access point model that had a slightly different firmware. Luna: So they had to either update the firmware on that model — which took two weeks to get approved — or block 24H2 on devices that connected to that wing. Lucas: Exactly. And the workaround they landed on was using Group Policy to disable Wi-Fi 7 features, which solved it for that model but also disabled it for their newer access points that could have benefited. Luna: That’s the kind of trade-off IT admins hate — a global policy that penalizes your modern hardware. Lucas: Yeah. And Microsoft hasn’t officially acknowledged this as a bug. They’ve published the Group Policy workaround, but there’s no patch scheduled as of June 2026. So enterprises are left to manage it themselves until the next feature update, which might change the stack again. Luna: What about Wi-Fi 6E? Does it affect those networks too? Lucas: Generally, no. The new stack works well with Wi-Fi 6 and 6E because those standards share more protocol features with Wi-Fi 7. The breakage is specifically with Wi-Fi 5 and older. But some users have reported issues with Wi-Fi 6 access points that have certain Qualcomm chipsets — it’s not as widespread, but it’s happening. Lucas: So the takeaway for IT admins is: if you’re starting your 24H2 rollout, first inventory your access point models and firmware. Then test with the specific hardware you have, not just a generic setup. And be ready to apply the 'Disable Wifi7' policy if you see issues. Luna: And if you’re in the middle of a rollout and already seeing problems, roll back the driver using the OEM’s installer — not the built-in rollback — and then plan your upgrade path. Lucas: Right. And maybe use this as a forcing function to start budgeting for Wi-Fi 6E or 7. Because Microsoft is not going to reverse this direction. Every future update will lean further into the new stack. Luna: It’s one of those quiet changes that ends up costing companies real money and real time. Not a flashy topic, but essential. Lucas: Exactly. And we’ll keep tracking it. If you’ve got your own Wi-Fi war stories after the 24H2 update, let us know — we might do a follow-up.