Pixel owners are reporting that the November 2026 update has stopped their phones from joining workplace and school Wi-Fi. Home networks are not affected, according to the reports, and Google says it is looking into it.
The complaints sit in a thread on Google’s Pixel support forum and a post on the GooglePixel subreddit. Users there say they lost WPA2-Enterprise connections that use PEAP with MSCHAPv2 right after installing the update. That is the sign-in method many offices and universities use, where you type a username and password rather than a shared Wi-Fi key.
After repeated attempts, affected phones, as users describe in the Reddit thread, show a “Saved/Connection failure” message. The reports come from several Pixel generations, and the one thing they share is the November build. People who have not yet installed it say their phones connect normally. One user wrote that an older Android tablet still joins the network while a nearly new Pixel 10a cannot. Some also mention trouble on networks that authenticate through Windows Network Policy Server.
The reports name phones across the range. The forum thread is titled for the Pixel 8, one commenter says a Pixel 10a lost the connection, and another says a Pixel 11 Pro did. The Pixel 11 Pro owner wrote that they tried everything and only a factory reset helped, and that it worked for about a week before the connection failed again. That makes this look like something in the update rather than in any one phone’s saved settings.
No clean fix has turned up. Google’s official Pixel Community account answered on Reddit that it had contacted a few affected users to collect more information. It did not name a cause, a fix date, the number of people affected or the builds involved.
Home Wi-Fi is unaffected, so the people hit hardest are staff and students who depend on managed networks and cannot easily switch to another sign-in method, since that choice belongs to the network’s administrator rather than to the phone’s owner.
For anyone checking their own phone, the pattern in the reports is consistent: the failure begins right after the November build installs, it only touches enterprise-style networks that ask for a username and password, and a phone that has not yet taken the update keeps connecting as before.
This is one of several faults people have tied to the November build, alongside charging, camera and screensaver complaints. Anyone who relies on enterprise Wi-Fi and has not yet taken the update may want to hold off on the update until Google responds.
Google’s reply on Reddit is the only official word so far.
