iOS 13 Hotspot not working after update

I updated iphone X to ios 13.2 last night 29 oct 2019. There is critical hotspot bug with this update . Not able to connect my laptop with personal hotspot

We have ~500 users on iPhones of varies models: 6S, 7, and 8. Since the release of 13 there have been reported hotspot issues with no common denominator on the model. One user could have a 7 on 13.1.3 and the hotspot works, but another user with same model/ios it doesn't. Many techs have spent a lot of time troubleshooting/trying different options. Still not resolved for the users having the problem

I have the personal hotspot on/off button enabled but still had issues using hotspot on iPhone. Usind a windows computer.

ipconfig /release and ipconfig/renew did not work for me.

However when I followed Sailor Steve's suggestion, the personal hotspot option was grayed out and I enabled it and hotspot started working fine.

Thank you Sailor Steve. It is a big help. Looks like this happened after upgrade of iOS.

I signed out of iCloud and signed back in now my hotspot is working again

I have what looks like the same issue.

No problem connecting to other networks. Problems only since updating iPhone SE to iOS 13.

I have followed all the steps in the link provided, to no avail.

Here are the wifi log entries:

Tue Oct 22 13:04:40.958 <kernel> parseRSNIE: groupCipherType = 5 pairwiseCipherType = 5 authSel = 2
Tue Oct 22 13:04:40.958 <kernel> initWithInterfaceAndIE: _myMacAddress <OBSCURED>
Tue Oct 22 13:04:40.958 <kernel> setPMK: PMK SET!
Tue Oct 22 13:04:43.623 <kernel> Unexpected payload found for message 9, dataLen 0
Tue Oct 22 13:04:43.623 <kernel> en0: Terminating supplicant.
Tue Oct 22 13:04:43.623 <kernel> RSNSupplicant: Releasing authenticator for 00:00:00:00:00:00
Tue Oct 22 13:04:43.833 <kernel> parseRSNIE: groupCipherType = 5 pairwiseCipherType = 5 authSel = 2
Tue Oct 22 13:04:43.833 <kernel> initWithInterfaceAndIE: _myMacAddress <OBSCURED>
Tue Oct 22 13:04:43.833 <kernel> setPMK: PMK SET!
Tue Oct 22 13:04:46.421 <kernel> Unexpected payload found for message 9, dataLen 0
Tue Oct 22 13:04:46.421 <kernel> en0: Terminating supplicant.
Tue Oct 22 13:04:46.421 <kernel> RSNSupplicant: Releasing authenticator for 00:00:00:00:00:00

Hey there, my name is Gabriel, We have similar problem here, since we upgraded our iPhone to the iOS 13. where Personal Hot Spot and our VPN on Windows 10 OS still work fine, says all connected however, it will not let us access any part of our internal network, therefore we haven't been able to access network drives, outlook email etc.

For the record none of the previous responses worked for us, We have done extensive troubleshooting and concluded that is all related to the upgrade of the iOS 13. in our iPhone 8. If we Use the same phone model still with an older iOS 12 works without any problems at all, in fact we have used other phone brands and work also without any troubles.

Common Apple!! do something good to your community. Thank you in advance.

Gabs

Yep, I've been using mobile hotspot on my iphone to connect my macbook pro without any problems for about a year. I did a recent ios update (the iphone is now 13.3.1 and my mac can see my phone in the drop down but 80% of the time it wont connect - it tries and then fails. I have to deleted it from my Network, so it has to find it again, I put in the password and this sometimes works but not always. It's incredibly frustrating. If I'm working on the hoof and need to quickly send a document I've been working on to someone not being able to tether to my hotspot can have serious financial consequences. I've literally tried everything. My network provider is EE on 4G VoLTE - whatever that means. It can flip to 3G if 4G isn't available. I've just asked the guys who run and sort out all our issues with Macs at work, MacXperts, to see if they come up with anything. If they do, I'll post again.

Please try to release the IP and renew again.

hotspot will work.

Go to command prompt, then

ipconfig /release

ipconfig /renew

my team is using chrome books, so they cannot use the refresh reconfig commands. different OS. No workarounds. We have tried tethering. Doesn't work. Tried my personal android and works seamlessly.

I have the same problem. I can get it to work sometimes, but it is WAY more trouble than it used to be. I use for a couple of smart TVs and a couple of Amazon echos (rarely more than one at a time). Before, I would just turn on the TV and the hotspot. After a couple minutes, I would be good to go. Now I have to hunt for the hotspot signal and log in EVERY single time, and half the time, the signal isn't even there. It is really an ordeal and totally hit and miss. Once connected, it is fine, but the trick is getting connected in the first place. Obviously, this is something they screwed up in 13, as it worked fine before.

I’m in the exact same boat! My hotspot will not connect to my sons Kindle Fire...trouble shooting after hours and still no fix 😭 was working fine until the 13.1 update 😤😤😤😤 About to get an Android

Yeah no kidding same here. I can be streaming a show or trying to download something and when I get a snapchat it knocks me off. It’s ridiculous and very frustrating. I’m not going to restart my phone and clear my cache or toggle it off and on every time I want WiFi. It worked fine before. Never had problems. I’d love a swift resolution to this which is going to be another update.

You'd think some expert would show up on here that could explain what would be causing the problem that an IP Address release and renew can fix? Almost has to be a problem with the initial pairing or something? That is fixed on the reset? My 101 knowledge level though isn't high enough to know the specifics involved.