Wifi coming back from hibernate?

[goodintentions]

I've been updating my i5 sp3 to the latest everything since yesterday. So far, I really like how well made this thing is. Visual studio is working great on it.

One thing I've noticed is coming back from hibernate even though WiFi is connected there's no internet. I have to disconnect and reconnect to get it working again.

It's not that much of a hassle, but anyone know how I can resolve this?

 

[goodintentions]

Bump.

 

[ctitanic]

You need to disable Hyper-V to fix this issue.

 

[JimB]

No solution for this problem. you'll need to create a task scheduler event, triggering this custom event filter:

<QueryList>
<Query Id="0" Path="System">
<Select Path="System">*[System[Provider[@Name='Microsoft-Windows-Power-Troubleshooter'] and (Level=4 or Level=0) and (EventID=1)]]</Select>
</Query>
</QueryList>

Create this .cmd in a text file and execute:

netsh int set int wi-fi disabled
netsh int set int wi-fi enabled

 

[ctitanic]

Again, the user has Visual Studio installed and that enables Hyper-V. Once Hyper-V is enabled the Wifi will fail when coming back from Hibernation, it's a known issue.

 

[JimB]

I also have visual studio installed and hyper v is disabled so there are other factors causing this.

 

[ctitanic]

I also have visual studio installed and hyper v is disabled so there are other factors causing this.

Are you sure?
Try this

bcdedit /set hypervisorlaunchtype off

Restart and check if you still have the issue.

 

[JimB]

Just did the above command, rebooted and same issue. wifi showing connected yet not working.

 

[goodintentions]

Disabling hyper-v solved this issue for me. Many thanks.

 

[ctitanic]

Just did the above command, rebooted and same issue. wifi showing connected yet not working.

Are you using the last Wifi Driver?

 

[JimB]

Yes, 15.68.3066.135 10/29/2014 Marvell Semiconductor. Inc.

 

[ctitanic]

Yes, 15.68.3066.135 10/29/2014 Marvell Semiconductor. Inc.

What router are you using? If it's a dual band are you using the same SSID? If that's the case, try using different SSID?