Hyper-v keeps getting disconnected with RS1

Only user but keep getting disconnected since upgrading Pro N to RS1
Any suggestions?

Edit: THOUGHTI found problem. My wifi adaptor on pc had got bridge linked with the hyper-v virtual router and that was confusing things. Also explains why I was getting an internet icon.

Reset wifi and now ok.

EDIT 2: ARRGH - Problem is back

This problem is caused by not having a password assigned to your user. I consider it a bug myself, but others disagree.

The issue is that when you enter Enhanced mode, the standard console reconnects and because there is no password, it automatically signs in, disconnecting you from your enhanced mode.

The bridging is standard when creating an external connection. And yes, it's annoying that the wireless icon is replaced by a wired icon. I reported feedback on it a while back.

This problem is caused by not having a password assigned to your user. I consider it a bug myself, but others disagree.

The issue is that when you enter Enhanced mode, the standard console reconnects and because there is no password, it automatically signs in, disconnecting you from your enhanced mode.

The bridging is standard when creating an external connection. And yes, it's annoying that the wireless icon is replaced by a wired icon. I reported feedback on it a while back.

Thanks - is there any solution to the password problem, or do i just keep reconnecting until it works?

Re, icon - I worked that out in the end as resetting wifi broke the hyper-v internet link?

Edit: have now set a password, and fingers crossed, it seems to be working.

Martin, take a look at this tutorial on our sister site the Eight blog: Hyper-V Virtual Switch Manager

You should not remove the bridge from WiFi adapter manually after you have created an external switch for WiFi adapter! That will be created by Hyper-V Virtual Switch Manageras soon as you create an external switch using WLAN NIC, and will be removed when you remove this switch.

Hyper-V does not recognize wireless NICs, therefore the bridge is needed to present the wireless NIC as Ethernet connection to vm.

This image from above mentioned tutorial:

The vm sees virtual switch it is using as Ethernet connection, regardless if the switch is using LAN or WLAN NIC. In order to host WLAN to "interpret" that, a bridge is needed between WLAN NIC and external Hyper-V switch. All traffic from vm goes through the external switch, which sends this "Ethernet" traffic over the bridge to WLAN NIC.

Kari

Martin, take a look at this tutorial on our sister site the Eight blog: Hyper-V Virtual Switch Manager

You should not remove the bridge from WiFi adapter manually after you have created an external switch for WiFi adapter! That will be created by Hyper-V Virtual Switch Manageras soon as you create an external switch using WLAN NIC, and will be removed when you remove this switch.

Hyper-V does not recognize wireless NICs, therefore the bridge is needed to present the wireless NIC as Ethernet connection to vm.

This image from above mentioned tutorial:

The vm sees virtual switch it is using as Ethernet connection, regardless if the switch is using LAN or WLAN NIC. In order to host WLAN to "interpret" that, a bridge is needed between WLAN NIC and external Hyper-V switch. All traffic from vm goes through the external switch, which sends this "Ethernet" traffic over the bridge to WLAN NIC.

Kari

Thanks - I worked this out in the end but it was fairly easy to fix.

It is a bit of a pain having to use passwords in a vm rather than autologin but it now works without disconnecting all the time. Funny thing is it worked with autologin on 10586. Some things are just a mystery I guess.