
Why does your Pixel say ‘Saved’ and refuse your work or school Wi-Fi after the November update?
Google’s November Pixel update appears to have broken sign-in on some work and school Wi-Fi networks that use WPA2 Enterprise with PEAP and MSCHAPv2. Phones sit at ‘Saved’ or show ‘Connection failure’ while home Wi-Fi works fine. Google is investigating, there is no confirmed fix or workaround yet, and a factory reset is not the answer.
You badge in at work, your phone sees the office Wi-Fi, and it just sits at ‘Saved’ while your email will not load. Short answer: it is probably not you, and probably not the office network either. Google’s November Pixel update appears to have broken sign-in on some work and school Wi-Fi, and Google is investigating.
There is no confirmed fix yet, so for now: tell IT what you are seeing, and use mobile data for the essentials until a repair update arrives.Why it matters: The reports point to WPA2 Enterprise networks using PEAP and MSCHAPv2 — the kind that ask for a username and often a certificate, which is how most offices and schools run Wi-Fi. Phones show ‘Saved’ or ‘Connection failure’ after repeated tries, while home Wi-Fi works fine. Reports name the Pixel 10a and Pixel 11 Pro across several generations, and some users hit the same wall with Windows Network Policy Server, so no single brand of network gear is to blame.What to do while Google works on it:1.
Test your home Wi-Fi. If it connects fine at home, the problem is only the work or school network.2. Ask IT two questions.
Does their network use WPA2 Enterprise with PEAP and MSCHAPv2, and have they seen other Pixel reports since the November update?3. Stop the delete-and-retry loop. Do not keep deleting and re-adding the network, and do not wipe the phone — neither one fixes this.4.
Use mobile data sparingly. Save it for email and essentials, and watch your data allowance.5. Share details if you are asked.
An official Pixel Community account has replied and the team has asked for logs; your phone model, exact error, and network type all help. Google has named no cause and given no fix date.6. Update promptly when the fix lands.
Install the next Pixel update as soon as Google releases one — that is how the repair reaches you.Common mistake: factory-resetting the phone. It costs hours of setup, and in the one reported case it only helped for about a week before the problem came right back.Ad’s take: I know ‘just wait’ is nobody’s favorite advice, but this one really is on Google to fix, not on you to tinker with. Tell IT, sip your data, and let the update do its job.
Ask AI about this tip
Send this tip to your favorite AI assistant for a plain-language walkthrough, follow-up questions, or help applying it to your device.