Conflict between Chrome and Hyper-V default switch
up vote
0
down vote
favorite
I have a strange problem: for the long time I have received error ERR_NETWORK_CHANGED in Chrome and Chrome-based browsers (e.g. Opera). At the beginning I suspected Bitdefender firewall and VirtualBox private network adapters. Finally I have figured out that the source of the problem is a new "Default Switch" feature in Windows10 1709. This switch is visible in Network Connections as Unindentified Network and is a cause of trouble. When I disable this switch network adapter the error dissapears.
What is the problem?
- The Default Switch is enabled even if hypervisor is disabled at boot
(BCD setting: hypervisorlaunchtype off). - When I remove adapter connected to Default Switch, it is recreated at the next boot.
- If I disable this adapter, Windows10 creates another "Default Switch".
I teach different courses about network/Windows/Linux technologies so uinstalling Hyper-V nor VirtualBox is not an option.
Is it possible to configure Windows10 networking to prevent this problem?
My initial idea to solve this problem is to create PS script that runs at logon and logoff disabling/enabling DefaultSwitch adapter. So far I am not able to discover the Hyper-V hypervisor state (on/off). PS cmdlet Get-WindowsOptionalFeature Hyper-v -online informs only that Hyper-V is enabled or disabled, but not about its current state (on/off).
networking windows-10 google-chrome hyper-v
asked Nov 8 at 8:22
WojtekTM
12
add a comment |
up vote
0
down vote
favorite
I have a strange problem: for the long time I have received error ERR_NETWORK_CHANGED in Chrome and Chrome-based browsers (e.g. Opera). At the beginning I suspected Bitdefender firewall and VirtualBox private network adapters. Finally I have figured out that the source of the problem is a new "Default Switch" feature in Windows10 1709. This switch is visible in Network Connections as Unindentified Network and is a cause of trouble. When I disable this switch network adapter the error dissapears.
What is the problem?
- The Default Switch is enabled even if hypervisor is disabled at boot
(BCD setting: hypervisorlaunchtype off). - When I remove adapter connected to Default Switch, it is recreated at the next boot.
- If I disable this adapter, Windows10 creates another "Default Switch".
I teach different courses about network/Windows/Linux technologies so uinstalling Hyper-V nor VirtualBox is not an option.
Is it possible to configure Windows10 networking to prevent this problem?
My initial idea to solve this problem is to create PS script that runs at logon and logoff disabling/enabling DefaultSwitch adapter. So far I am not able to discover the Hyper-V hypervisor state (on/off). PS cmdlet Get-WindowsOptionalFeature Hyper-v -online informs only that Hyper-V is enabled or disabled, but not about its current state (on/off).
networking windows-10 google-chrome hyper-v
asked Nov 8 at 8:22
WojtekTM
12
It shouldn't appear as Unidentified Network. Try to remove the Hyper-V feature, reboot, re-enable and reboot.
– harrymc
Nov 8 at 9:06
It did not resolve problem. I uninstalled antyvirus, reboot, hyper-v, reboot twice, installed hyper-v, reboot , installed, result is the same. Maybe shoud I clear Hyper-V configuration the other way? @harrymc - what is the state/configuration of your default switch?
– WojtekTM
Nov 8 at 10:20
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a strange problem: for the long time I have received error ERR_NETWORK_CHANGED in Chrome and Chrome-based browsers (e.g. Opera). At the beginning I suspected Bitdefender firewall and VirtualBox private network adapters. Finally I have figured out that the source of the problem is a new "Default Switch" feature in Windows10 1709. This switch is visible in Network Connections as Unindentified Network and is a cause of trouble. When I disable this switch network adapter the error dissapears.
What is the problem?
- The Default Switch is enabled even if hypervisor is disabled at boot
(BCD setting: hypervisorlaunchtype off). - When I remove adapter connected to Default Switch, it is recreated at the next boot.
- If I disable this adapter, Windows10 creates another "Default Switch".
I teach different courses about network/Windows/Linux technologies so uinstalling Hyper-V nor VirtualBox is not an option.
Is it possible to configure Windows10 networking to prevent this problem?
My initial idea to solve this problem is to create PS script that runs at logon and logoff disabling/enabling DefaultSwitch adapter. So far I am not able to discover the Hyper-V hypervisor state (on/off). PS cmdlet Get-WindowsOptionalFeature Hyper-v -online informs only that Hyper-V is enabled or disabled, but not about its current state (on/off).
networking windows-10 google-chrome hyper-v
asked Nov 8 at 8:22
WojtekTM
12
I have a strange problem: for the long time I have received error ERR_NETWORK_CHANGED in Chrome and Chrome-based browsers (e.g. Opera). At the beginning I suspected Bitdefender firewall and VirtualBox private network adapters. Finally I have figured out that the source of the problem is a new "Default Switch" feature in Windows10 1709. This switch is visible in Network Connections as Unindentified Network and is a cause of trouble. When I disable this switch network adapter the error dissapears.
What is the problem?
- The Default Switch is enabled even if hypervisor is disabled at boot
(BCD setting: hypervisorlaunchtype off). - When I remove adapter connected to Default Switch, it is recreated at the next boot.
- If I disable this adapter, Windows10 creates another "Default Switch".
I teach different courses about network/Windows/Linux technologies so uinstalling Hyper-V nor VirtualBox is not an option.
Is it possible to configure Windows10 networking to prevent this problem?
My initial idea to solve this problem is to create PS script that runs at logon and logoff disabling/enabling DefaultSwitch adapter. So far I am not able to discover the Hyper-V hypervisor state (on/off). PS cmdlet Get-WindowsOptionalFeature Hyper-v -online informs only that Hyper-V is enabled or disabled, but not about its current state (on/off).
networking windows-10 google-chrome hyper-v
networking windows-10 google-chrome hyper-v
asked Nov 8 at 8:22
WojtekTM
12
asked Nov 8 at 8:22
WojtekTM
12
asked Nov 8 at 8:22
WojtekTM
12
asked Nov 8 at 8:22
WojtekTM
12
asked Nov 8 at 8:22
WojtekTM
12
12
It shouldn't appear as Unidentified Network. Try to remove the Hyper-V feature, reboot, re-enable and reboot.
– harrymc
Nov 8 at 9:06
It did not resolve problem. I uninstalled antyvirus, reboot, hyper-v, reboot twice, installed hyper-v, reboot , installed, result is the same. Maybe shoud I clear Hyper-V configuration the other way? @harrymc - what is the state/configuration of your default switch?
– WojtekTM
Nov 8 at 10:20
add a comment |
It shouldn't appear as Unidentified Network. Try to remove the Hyper-V feature, reboot, re-enable and reboot.
– harrymc
Nov 8 at 9:06
It did not resolve problem. I uninstalled antyvirus, reboot, hyper-v, reboot twice, installed hyper-v, reboot , installed, result is the same. Maybe shoud I clear Hyper-V configuration the other way? @harrymc - what is the state/configuration of your default switch?
– WojtekTM
Nov 8 at 10:20
It shouldn't appear as Unidentified Network. Try to remove the Hyper-V feature, reboot, re-enable and reboot.
– harrymc
Nov 8 at 9:06
It shouldn't appear as Unidentified Network. Try to remove the Hyper-V feature, reboot, re-enable and reboot.
– harrymc
Nov 8 at 9:06
It did not resolve problem. I uninstalled antyvirus, reboot, hyper-v, reboot twice, installed hyper-v, reboot , installed, result is the same. Maybe shoud I clear Hyper-V configuration the other way? @harrymc - what is the state/configuration of your default switch?
– WojtekTM
Nov 8 at 10:20
It did not resolve problem. I uninstalled antyvirus, reboot, hyper-v, reboot twice, installed hyper-v, reboot , installed, result is the same. Maybe shoud I clear Hyper-V configuration the other way? @harrymc - what is the state/configuration of your default switch?
– WojtekTM
Nov 8 at 10:20
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
I have finally discovered that there is a bug in Windows 10.
If you had configured NAT in Hyper-V with *-NetNat cmdlet before you installed Windows10 1709 (with new DefaultSwitch feature), your configuration of DefaultSwitch will be broken.
Advices given by MS staff on MS support forums are useless, as disabling and enabling Hyper-V feature (with multiple reboots in between) does not reset Hyper-V configuration. It is also not possible to configure DefaultSwitch manually.
15 Nov '18 Update:
I have found blog entry: [ https://mikefrobbins.com/2018/11/08/managing-the-hyper-v-default-switch-in-windows-10-version-1709-and-higher-with-powershell/#comment-39379 ] . Author suggests setting high metric on both IPv4 and IPv6 protocols of DefaultSwitch adapter:
Get-NetIPInterface -InterfaceAlias 'vEthernet (Default Switch)' | Set-NetIPInterface -InterfaceMetric 5000 -PassThru
It does not resolve problem (DefaultSwitch still does not work), however I can use browsers without ERR_NETWORK_CHANGE errors.
As no one in Microsoft knows how to repair their DefaultSwitch, probably the only complete solution is to make a clean install of 1809.
answered Nov 9 at 7:23
WojtekTM
12
New contributor
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
I have finally discovered that there is a bug in Windows 10.
If you had configured NAT in Hyper-V with *-NetNat cmdlet before you installed Windows10 1709 (with new DefaultSwitch feature), your configuration of DefaultSwitch will be broken.
Advices given by MS staff on MS support forums are useless, as disabling and enabling Hyper-V feature (with multiple reboots in between) does not reset Hyper-V configuration. It is also not possible to configure DefaultSwitch manually.
15 Nov '18 Update:
I have found blog entry: [ https://mikefrobbins.com/2018/11/08/managing-the-hyper-v-default-switch-in-windows-10-version-1709-and-higher-with-powershell/#comment-39379 ] . Author suggests setting high metric on both IPv4 and IPv6 protocols of DefaultSwitch adapter:
Get-NetIPInterface -InterfaceAlias 'vEthernet (Default Switch)' | Set-NetIPInterface -InterfaceMetric 5000 -PassThru
It does not resolve problem (DefaultSwitch still does not work), however I can use browsers without ERR_NETWORK_CHANGE errors.
As no one in Microsoft knows how to repair their DefaultSwitch, probably the only complete solution is to make a clean install of 1809.
answered Nov 9 at 7:23
WojtekTM
12
New contributor
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
accepted
I have finally discovered that there is a bug in Windows 10.
If you had configured NAT in Hyper-V with *-NetNat cmdlet before you installed Windows10 1709 (with new DefaultSwitch feature), your configuration of DefaultSwitch will be broken.
Advices given by MS staff on MS support forums are useless, as disabling and enabling Hyper-V feature (with multiple reboots in between) does not reset Hyper-V configuration. It is also not possible to configure DefaultSwitch manually.
15 Nov '18 Update:
I have found blog entry: [ https://mikefrobbins.com/2018/11/08/managing-the-hyper-v-default-switch-in-windows-10-version-1709-and-higher-with-powershell/#comment-39379 ] . Author suggests setting high metric on both IPv4 and IPv6 protocols of DefaultSwitch adapter:
Get-NetIPInterface -InterfaceAlias 'vEthernet (Default Switch)' | Set-NetIPInterface -InterfaceMetric 5000 -PassThru
It does not resolve problem (DefaultSwitch still does not work), however I can use browsers without ERR_NETWORK_CHANGE errors.
As no one in Microsoft knows how to repair their DefaultSwitch, probably the only complete solution is to make a clean install of 1809.
answered Nov 9 at 7:23
WojtekTM
12
New contributor
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I have finally discovered that there is a bug in Windows 10.
If you had configured NAT in Hyper-V with *-NetNat cmdlet before you installed Windows10 1709 (with new DefaultSwitch feature), your configuration of DefaultSwitch will be broken.
Advices given by MS staff on MS support forums are useless, as disabling and enabling Hyper-V feature (with multiple reboots in between) does not reset Hyper-V configuration. It is also not possible to configure DefaultSwitch manually.
15 Nov '18 Update:
I have found blog entry: [ https://mikefrobbins.com/2018/11/08/managing-the-hyper-v-default-switch-in-windows-10-version-1709-and-higher-with-powershell/#comment-39379 ] . Author suggests setting high metric on both IPv4 and IPv6 protocols of DefaultSwitch adapter:
Get-NetIPInterface -InterfaceAlias 'vEthernet (Default Switch)' | Set-NetIPInterface -InterfaceMetric 5000 -PassThru
It does not resolve problem (DefaultSwitch still does not work), however I can use browsers without ERR_NETWORK_CHANGE errors.
As no one in Microsoft knows how to repair their DefaultSwitch, probably the only complete solution is to make a clean install of 1809.
answered Nov 9 at 7:23
WojtekTM
12
New contributor
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have finally discovered that there is a bug in Windows 10.
If you had configured NAT in Hyper-V with *-NetNat cmdlet before you installed Windows10 1709 (with new DefaultSwitch feature), your configuration of DefaultSwitch will be broken.
Advices given by MS staff on MS support forums are useless, as disabling and enabling Hyper-V feature (with multiple reboots in between) does not reset Hyper-V configuration. It is also not possible to configure DefaultSwitch manually.
15 Nov '18 Update:
I have found blog entry: [ https://mikefrobbins.com/2018/11/08/managing-the-hyper-v-default-switch-in-windows-10-version-1709-and-higher-with-powershell/#comment-39379 ] . Author suggests setting high metric on both IPv4 and IPv6 protocols of DefaultSwitch adapter:
Get-NetIPInterface -InterfaceAlias 'vEthernet (Default Switch)' | Set-NetIPInterface -InterfaceMetric 5000 -PassThru
It does not resolve problem (DefaultSwitch still does not work), however I can use browsers without ERR_NETWORK_CHANGE errors.
As no one in Microsoft knows how to repair their DefaultSwitch, probably the only complete solution is to make a clean install of 1809.
answered Nov 9 at 7:23
WojtekTM
12
New contributor
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 3 hours ago
answered Nov 9 at 7:23
WojtekTM
12
New contributor
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 9 at 7:23
WojtekTM
12
answered Nov 9 at 7:23
WojtekTM
12
12
New contributor
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
WojtekTM is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1373707%2fconflict-between-chrome-and-hyper-v-default-switch%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
It shouldn't appear as Unidentified Network. Try to remove the Hyper-V feature, reboot, re-enable and reboot.
– harrymc
Nov 8 at 9:06
It did not resolve problem. I uninstalled antyvirus, reboot, hyper-v, reboot twice, installed hyper-v, reboot , installed, result is the same. Maybe shoud I clear Hyper-V configuration the other way? @harrymc - what is the state/configuration of your default switch?
– WojtekTM
Nov 8 at 10:20