Wi-fi stopped working after upgrading to iOS 17.0.1

Found the solution. One of my Fritzbox Accesspoints, which I ised for all IOS devices, was an older model. The WiFi module and the (latest) software installed on it didn’t work with IOS 17.01 (it worked fine with all previous IOS versions)

After I switched off this accespoint and used two more modern accesspoints. The problem was over….Now ask AVM ic they can solve tje problem

the following worked for my iPhone SE 2022 after upgrade from 16.1 to17.1. Now several other actions were taken prior to this such as disabling my vpn and several forced resets.

Solution 5. Turn Off/On Wi-Fi Assist

Some users have reported that disable and re-enable Wi-Fi Assist seems to help solve the Wi-Fi connection issue in iOS 16, 17. Go to Settings > Tap Cellular > Disable Wi-Fi Assist and turn it on again after a few seconds.

Hi. After an hour on the phone with Apple support their only solution was to factory reset my phone like it was new out of the box. So far this seems to have worked. Once the phone turned back on to the welcome screen I was finally able to log back into my WiFi network. I am still waiting for my iCloud backup to download. I will reply with any updates. Hopefully this fixes the issue.

PROBLEM SOLVED!

After downloading 17.0.1, two iPhones in one household, had service annd connectivity interruptions in WiFi. WiFi source is a WOW cable modem. Since the modem offers 5.0G and 2.4G settings we’ve always used the 5.0G. Months ago we had trouble with our LG Smart TV 17“scrolling” to find a signal while watching. We learned the best WiFi setting was 2.4G for that and no longer have scrolling issues, the same now applies to our iPhones! Switch off the 5.0G and load the 2.4G and “voilà” no more connectivity issues, DONE!

I had the exact same issue - pages slow to load across multiple wifis.

a fix that seems to have worked for me since yesterday:

I went into Wi-Fi, clicked on my Wi-Fi name (the “i” button), switched off “Private Wi-Fi Address” and then switched it back on again, then switched off Wi-Fi and switched it back on again.

I updated my iPhone 12 Pro Max last night to iOS 17.4.1 and just had this issue. Workarounds did NOT work. What actually worked for me IMMEDIATELY was going to General - About - Name and changing the name on my phone because it had been changed back to “iPhone”.

Maybe this will help others if their phone’s “name” has been changed after an update.

I tried this but some apps still wouldn't load, Then I turned off "Private Wifi Address" for my internet providers too which appeared in the Edit section and finally it worked! May want to try this.

***FIXED***

Forgot the WiFi network

Remove !ALL! VPN profiles, and configurations on your iPhone.

P.S. Was fixed on SE 2022, iOS 17.1

P.P.S Works for a cellular network too.

Enjoy ;)

I have a similar problem, documented in both Apple Feedback Assistant FB13192022, and this thread on Apple Developer Forum. Please file your own ticket via Feedback Assistant if you can and refer back if you could. My observations:

I have this same issue with the public release of iOS 17.0 with an iPhone 12. I cannot use certificate-based 802.1x authentication with work's wifi. My regular home WPA2 pre-shared key network works fine. As a odd curiosity, I also cannot use the 802.1x cert protected "XFINITY" public hotspot, but the lower-case "xfinitywifi" (no encryption) public hotspot network is OK.

If I try to go into settings->wifi while the cert-based network is trying to connect, the whole phone slows to a crawl, or Settings crashes. It could take 4 or 5 tries to turn wifi off, each "try" being 30 seconds. The phone heats up while this happens. Almost seems like something is retrying in a tight loop then a timeout.

Only workaround seems to be to use a non-cert-based network, or use cellular service.

--

One more observation -- both of these "bad" networks involve physical access points serving multiple SSIDs using different encryption methods. Is there some race condition bouncing between the virtual SSIDs?

--

Confirmed NOT fixed in 17.0.1.

Aha! That was the missing piece that I didn’t think of. The DHCP lease expiry, wish I had thought of that earlier.

On our corporate network, we had found that Private Wi-Fi Address had been toggled on for some devices during iOS 17 install, and InTune had not overridden this. Toggling this only sometimes cleared the issue. With two devices that were logged in to iCloud with the same AppleID, I think the affected settings synced between the two (good and bad).

Switching to Ethernet from wifi worked for my iPad. Perhaps this reset something in the network and forced a DHCP renewal.

Luckily, we found that 17.0.3 solved the issue for all of our remaining affected devices. Let’s hope that 17.1 is the cure for the rest of you!

I had this problem with both my cell and internet connections.

It turned out, somehow, my VPN connected to all my services, and blocked my connection. I have no idea how that spontaneously happened (which makes me think it was not spontaneous!)

So, if you have this issue, check your VPN!

This issue was resolved for med after upgrading to 17.0.3 this morning

I would still check to see if “Private wifi address” is turned on when you look at the connected network. Tap on the “i” icon and turn it off if it’s on, then try surfing.

Would suggest you guys to delete vpn profile if itself available on your ios device. Forget network. Turn off your router and on back. Then try connecting back to your network. It works for me.

This worked!!!!! I removed the VPN app and everything went back to normal. I had tried everything else--thank you!!!!!!!!