Pixel users report workplace and school Wi-Fi connectivity issues after November update

Google Pixel users are reporting a new bug that’s causing enterprise Wi-Fi connectivity issues, and I’m now officially running out of fingers on both hands to count all the bugs and glitches that have surfaced since Google’s November 2026 update. The update has seemingly broken wireless charging for some, cameras for others, and it’s even causing screensavers to stay unusually bright at night, among a slew of other issues.

The latest addition to that list is a connectivity bug that’s preventing Pixel users from being able to connect to their workplace or school’s Wi-Fi.

Complaints about the issue have made their way to the Google Support forum and Reddit, with users reporting similar problems across generations, with only the November update in common. According to the support post, users are losing WPA2-Enterprise PEAP/MSCHAPv2 (used by organizations to securely connect users to Wi-Fi) connectivity immediately following the November update. Devices that haven’t updated to the latest build remain unaffected.

After repeatedly trying to establish a connection, the affected devices reportedly show “Saved/Connection failure” errors, leaving users unable to connect to their school or workplace’s Wi-Fi.

One user reiterated the claim that only devices running the November update are affected:

It’s ridiculous that my old Android tablet can connect, but a practically new Pixel 10a can’t. It stopped working after the November update was installed overnight.

A different user claimed that factory resetting their Pixel fixed the issue, but only temporarily:

Im having the same issue on my pixel 11 pro i tried everything and nothing worked. Then i finally did a factory reset on my phone and it worked for about a week and as of today it wont connect again.

Users have also reported issues across different enterprise Wi-Fi protocols, including PEAP/MSCHAPv2 authentication and Windows Network Policy Server.

Although there appears to be no temporary fix for now, there still is good news: Google is aware of the issue. In a Reddit reply, the company’s official Pixel Community account confirmed that it had reached out to a few affected users to gather more information about the issue. It didn’t say what was causing the problem and it didn’t share a timeline for a fix either.

Note that regular home Wi-Fi connectivity remains unaffected. We’ll keep track of the situation and push an update once we learn more.