How to delete hyper-v virtual switch extensions adapters from device managerRemove hyper-v virtual switch extensions adapters from device managerWhere do all the little vEthernet (Default Switch) come from?Hyper-V extensible virtual switch disables networkVirtual Machine on Hyper-V Server Manager is goneHow to access device manager in Hyper-V Server 2008 R2?Hyper-V Missing Virtual Server From Hyper-V Manager ListHyper-V Manager - How do I Connect to Hyper-V Server using different credentialsHyper-v Virtual Network Switch ConfigurationHow to create a virtual switch with Hyper-VRemove hyper-v virtual switch extensions adapters from device managerHyper-v Manager, 1 External Switch, 2 Private switch on cento7 vm, cannot ping internetHyper-V cluster - physical or virtual network adapters for nodes?

Rotated Position of Integers

Did airlines fly their aircraft slower in response to oil prices in the 1970s?

Why don't I have ground wiring on any of my outlets?

How to properly maintain eye contact with people that have distinctive facial features?

How can I stop my presentation being derailed by audience questions?

Is there a rule that prohibits us from using 2 possessives in a row?

Beginner's snake game using PyGame

Is there any Biblical Basis for 400 years of silence between Old and New Testament?

Why is there a need to modify system call tables in Linux?

How can a single Member of the House block a Congressional bill?

Are there mythical creatures in the world of Game of Thrones?

What are the problems in teaching guitar via Skype?

What is the intuition behind uniform continuity?

Why would Lupin kill Pettigrew?

The oldest tradition stopped before it got back to him

What does the wifi amplifier exactly amplify?

Why were the Night's Watch required to be celibate?

What if you don't bring your credit card or debit for incidentals?

Explain Ant-Man's "not it" scene from Avengers: Endgame

How to detach yourself from a character you're going to kill?

Does nuclear propulsion applied to military ships fall under civil or military nuclear power?

Why is Colorado so different politically from nearby states?

Are grass strips more dangerous than tarmac?

Infinitely many hats



How to delete hyper-v virtual switch extensions adapters from device manager


Remove hyper-v virtual switch extensions adapters from device managerWhere do all the little vEthernet (Default Switch) come from?Hyper-V extensible virtual switch disables networkVirtual Machine on Hyper-V Server Manager is goneHow to access device manager in Hyper-V Server 2008 R2?Hyper-V Missing Virtual Server From Hyper-V Manager ListHyper-V Manager - How do I Connect to Hyper-V Server using different credentialsHyper-v Virtual Network Switch ConfigurationHow to create a virtual switch with Hyper-VRemove hyper-v virtual switch extensions adapters from device managerHyper-v Manager, 1 External Switch, 2 Private switch on cento7 vm, cannot ping internetHyper-V cluster - physical or virtual network adapters for nodes?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








15















How to clean that hyper-v mess?



I just want to delete all of them.



And yes, right click -> uninstall does nothing :(



enter image description here



I tried deleting the regedit entries and got a permission denied.



I tried to set permissions to the entries and got a access is denied:



C:> subinacl.exe /subkeyreg HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002 /grant=administrators=F

SYSTEMControlSet001EnumROOTVMS_VSMP002 : new ace for builtinadministrators
HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002 - RegSetKeySecurity Error : 5 Access is denied.


SYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : delete Perm. ACE 2 builtinadministrators
SYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : new ace for builtinadministrators
HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : 2 change(s)
HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Properties - AddAce error : 87 The parameter is incorrect.


HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Properties: 5 : Unable to enumerate subkeys









share|improve this question






























    15















    How to clean that hyper-v mess?



    I just want to delete all of them.



    And yes, right click -> uninstall does nothing :(



    enter image description here



    I tried deleting the regedit entries and got a permission denied.



    I tried to set permissions to the entries and got a access is denied:



    C:> subinacl.exe /subkeyreg HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002 /grant=administrators=F

    SYSTEMControlSet001EnumROOTVMS_VSMP002 : new ace for builtinadministrators
    HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002 - RegSetKeySecurity Error : 5 Access is denied.


    SYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : delete Perm. ACE 2 builtinadministrators
    SYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : new ace for builtinadministrators
    HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : 2 change(s)
    HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Properties - AddAce error : 87 The parameter is incorrect.


    HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Properties: 5 : Unable to enumerate subkeys









    share|improve this question


























      15












      15








      15


      7






      How to clean that hyper-v mess?



      I just want to delete all of them.



      And yes, right click -> uninstall does nothing :(



      enter image description here



      I tried deleting the regedit entries and got a permission denied.



      I tried to set permissions to the entries and got a access is denied:



      C:> subinacl.exe /subkeyreg HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002 /grant=administrators=F

      SYSTEMControlSet001EnumROOTVMS_VSMP002 : new ace for builtinadministrators
      HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002 - RegSetKeySecurity Error : 5 Access is denied.


      SYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : delete Perm. ACE 2 builtinadministrators
      SYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : new ace for builtinadministrators
      HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : 2 change(s)
      HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Properties - AddAce error : 87 The parameter is incorrect.


      HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Properties: 5 : Unable to enumerate subkeys









      share|improve this question
















      How to clean that hyper-v mess?



      I just want to delete all of them.



      And yes, right click -> uninstall does nothing :(



      enter image description here



      I tried deleting the regedit entries and got a permission denied.



      I tried to set permissions to the entries and got a access is denied:



      C:> subinacl.exe /subkeyreg HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002 /grant=administrators=F

      SYSTEMControlSet001EnumROOTVMS_VSMP002 : new ace for builtinadministrators
      HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002 - RegSetKeySecurity Error : 5 Access is denied.


      SYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : delete Perm. ACE 2 builtinadministrators
      SYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : new ace for builtinadministrators
      HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Device Parameters : 2 change(s)
      HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Properties - AddAce error : 87 The parameter is incorrect.


      HKEY_LOCAL_MACHINESYSTEMControlSet001EnumROOTVMS_VSMP002Properties: 5 : Unable to enumerate subkeys






      hyper-v






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 16 at 20:09









      Christopher_G_Lewis

      3,2621727




      3,2621727










      asked Mar 25 '14 at 2:52









      Andre CarlucciAndre Carlucci

      2011411




      2011411




















          5 Answers
          5






          active

          oldest

          votes


















          3














          You want the "remove-vmnetworkadapter" cmdlet in PowerShell. Merely looking at Device Manager will only allow you to add or remove device drivers from "devices" in the machine, where in this case the device is virtual.



          If you want a list of the virtual NICs that are exposed to the management OS (which is what you're showing above) you can use this command:



          Get-VMNetworkAdapter -ManagementOS


          Then you can find the ones that you don't want and delete them with remove-vmnetworkadapter. Once the virtual switch stops reporting them as NICs in the machine, they'll disappear from Device Manager.






          share|improve this answer






























            16














            The nuclear option that works with Windows Core is using netcfg to wipe out all your networking settings and re-initialize the network card drivers.



            #WARNING! DANGER! THIS WILL DELETE ALL YOUR NETWORKING SETTINGS!
            netcfg -d


            That seems to work better than nvspbind.exe or various other PowerShell commands when I really screw up my Hyper-V VMSwitch or LBFOTeam networking settings.






            share|improve this answer


















            • 2





              Incredibly, your command only deleted the virtual adapters and left the real ones untouched. That's as good as it gets.

              – andreszs
              Sep 19 '17 at 22:22






            • 1





              Works on Windows 10 to clean up vEthernet adapters left after Hyper-V uninstalling. Physical cards are up after reboot.

              – Maris B.
              Nov 8 '17 at 9:25











            • worked for me: first removed Win X hyper V then ntcfg -d. great hint!

              – Joe Platano
              Dec 27 '17 at 22:16











            • Great ... this even preserved my TAP-driver and previous installed VirtualBox-HostOnly interface from deletion.

              – cljk
              Mar 23 '18 at 6:11











            • +1 Worked like a charm. Got rid of all the leftover networking bits from other virtualization stuff too.

              – Corin
              Apr 5 '18 at 14:18


















            4














            Following directions from are taken from the article Removing "Stale" Network Adapters in Hyper-V VM by Jeremy Jameson:



            1. Start an administrator command prompt;

            2. Run

              1. set devmgr_show_nonpresent_devices=1

              2. start devmgmt.msc


            3. In newly opened Device Manager "Uninstall" option in context menus worked for me (Win10 Pro).


            Must say I tried the netcfg -d from prior to this, but it had no observable effect. Also I had Hyper-V disabled at the time of this process.






            share|improve this answer




















            • 1





              Accepted answer was not available (it seems like Hyper-V has to be enable) for me but this one did the job while Hyper-V is disabled.

              – Tok'
              Jun 11 '18 at 16:59






            • 1





              @Tok' it's probably good point: I had Hyper-V disabled as well, added it to answer.

              – myf
              Jun 12 '18 at 8:44


















            1














            I solved this by:



            In PowerShell type: netcfg -d



            This WILL DELETE all network adapters AND network SETTINGS!
            Physical adapters will NOT be LOST.
            Then i restored my network settings and created new External Virtual Switches.
            This worked for me fine and fast.



            Windows 10 64bit there.






            share|improve this answer






























              0














              if that doesn't work. right click on the adapter, properties. Click on Configure at the top, on the 3rd tab on Driver. Uninstall the driver and close the mask. the problem should be solved after pressing F5.






              share|improve this answer























                Your Answer








                StackExchange.ready(function()
                var channelOptions =
                tags: "".split(" "),
                id: "2"
                ;
                initTagRenderer("".split(" "), "".split(" "), channelOptions);

                StackExchange.using("externalEditor", function()
                // Have to fire editor after snippets, if snippets enabled
                if (StackExchange.settings.snippets.snippetsEnabled)
                StackExchange.using("snippets", function()
                createEditor();
                );

                else
                createEditor();

                );

                function createEditor()
                StackExchange.prepareEditor(
                heartbeatType: 'answer',
                autoActivateHeartbeat: false,
                convertImagesToLinks: true,
                noModals: true,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: 10,
                bindNavPrevention: true,
                postfix: "",
                imageUploader:
                brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
                contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
                allowUrls: true
                ,
                onDemand: true,
                discardSelector: ".discard-answer"
                ,immediatelyShowMarkdownHelp:true
                );



                );













                draft saved

                draft discarded


















                StackExchange.ready(
                function ()
                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f584316%2fhow-to-delete-hyper-v-virtual-switch-extensions-adapters-from-device-manager%23new-answer', 'question_page');

                );

                Post as a guest















                Required, but never shown

























                5 Answers
                5






                active

                oldest

                votes








                5 Answers
                5






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                3














                You want the "remove-vmnetworkadapter" cmdlet in PowerShell. Merely looking at Device Manager will only allow you to add or remove device drivers from "devices" in the machine, where in this case the device is virtual.



                If you want a list of the virtual NICs that are exposed to the management OS (which is what you're showing above) you can use this command:



                Get-VMNetworkAdapter -ManagementOS


                Then you can find the ones that you don't want and delete them with remove-vmnetworkadapter. Once the virtual switch stops reporting them as NICs in the machine, they'll disappear from Device Manager.






                share|improve this answer



























                  3














                  You want the "remove-vmnetworkadapter" cmdlet in PowerShell. Merely looking at Device Manager will only allow you to add or remove device drivers from "devices" in the machine, where in this case the device is virtual.



                  If you want a list of the virtual NICs that are exposed to the management OS (which is what you're showing above) you can use this command:



                  Get-VMNetworkAdapter -ManagementOS


                  Then you can find the ones that you don't want and delete them with remove-vmnetworkadapter. Once the virtual switch stops reporting them as NICs in the machine, they'll disappear from Device Manager.






                  share|improve this answer

























                    3












                    3








                    3







                    You want the "remove-vmnetworkadapter" cmdlet in PowerShell. Merely looking at Device Manager will only allow you to add or remove device drivers from "devices" in the machine, where in this case the device is virtual.



                    If you want a list of the virtual NICs that are exposed to the management OS (which is what you're showing above) you can use this command:



                    Get-VMNetworkAdapter -ManagementOS


                    Then you can find the ones that you don't want and delete them with remove-vmnetworkadapter. Once the virtual switch stops reporting them as NICs in the machine, they'll disappear from Device Manager.






                    share|improve this answer













                    You want the "remove-vmnetworkadapter" cmdlet in PowerShell. Merely looking at Device Manager will only allow you to add or remove device drivers from "devices" in the machine, where in this case the device is virtual.



                    If you want a list of the virtual NICs that are exposed to the management OS (which is what you're showing above) you can use this command:



                    Get-VMNetworkAdapter -ManagementOS


                    Then you can find the ones that you don't want and delete them with remove-vmnetworkadapter. Once the virtual switch stops reporting them as NICs in the machine, they'll disappear from Device Manager.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Mar 25 '14 at 18:16









                    Jake OshinsJake Oshins

                    5,0081314




                    5,0081314























                        16














                        The nuclear option that works with Windows Core is using netcfg to wipe out all your networking settings and re-initialize the network card drivers.



                        #WARNING! DANGER! THIS WILL DELETE ALL YOUR NETWORKING SETTINGS!
                        netcfg -d


                        That seems to work better than nvspbind.exe or various other PowerShell commands when I really screw up my Hyper-V VMSwitch or LBFOTeam networking settings.






                        share|improve this answer


















                        • 2





                          Incredibly, your command only deleted the virtual adapters and left the real ones untouched. That's as good as it gets.

                          – andreszs
                          Sep 19 '17 at 22:22






                        • 1





                          Works on Windows 10 to clean up vEthernet adapters left after Hyper-V uninstalling. Physical cards are up after reboot.

                          – Maris B.
                          Nov 8 '17 at 9:25











                        • worked for me: first removed Win X hyper V then ntcfg -d. great hint!

                          – Joe Platano
                          Dec 27 '17 at 22:16











                        • Great ... this even preserved my TAP-driver and previous installed VirtualBox-HostOnly interface from deletion.

                          – cljk
                          Mar 23 '18 at 6:11











                        • +1 Worked like a charm. Got rid of all the leftover networking bits from other virtualization stuff too.

                          – Corin
                          Apr 5 '18 at 14:18















                        16














                        The nuclear option that works with Windows Core is using netcfg to wipe out all your networking settings and re-initialize the network card drivers.



                        #WARNING! DANGER! THIS WILL DELETE ALL YOUR NETWORKING SETTINGS!
                        netcfg -d


                        That seems to work better than nvspbind.exe or various other PowerShell commands when I really screw up my Hyper-V VMSwitch or LBFOTeam networking settings.






                        share|improve this answer


















                        • 2





                          Incredibly, your command only deleted the virtual adapters and left the real ones untouched. That's as good as it gets.

                          – andreszs
                          Sep 19 '17 at 22:22






                        • 1





                          Works on Windows 10 to clean up vEthernet adapters left after Hyper-V uninstalling. Physical cards are up after reboot.

                          – Maris B.
                          Nov 8 '17 at 9:25











                        • worked for me: first removed Win X hyper V then ntcfg -d. great hint!

                          – Joe Platano
                          Dec 27 '17 at 22:16











                        • Great ... this even preserved my TAP-driver and previous installed VirtualBox-HostOnly interface from deletion.

                          – cljk
                          Mar 23 '18 at 6:11











                        • +1 Worked like a charm. Got rid of all the leftover networking bits from other virtualization stuff too.

                          – Corin
                          Apr 5 '18 at 14:18













                        16












                        16








                        16







                        The nuclear option that works with Windows Core is using netcfg to wipe out all your networking settings and re-initialize the network card drivers.



                        #WARNING! DANGER! THIS WILL DELETE ALL YOUR NETWORKING SETTINGS!
                        netcfg -d


                        That seems to work better than nvspbind.exe or various other PowerShell commands when I really screw up my Hyper-V VMSwitch or LBFOTeam networking settings.






                        share|improve this answer













                        The nuclear option that works with Windows Core is using netcfg to wipe out all your networking settings and re-initialize the network card drivers.



                        #WARNING! DANGER! THIS WILL DELETE ALL YOUR NETWORKING SETTINGS!
                        netcfg -d


                        That seems to work better than nvspbind.exe or various other PowerShell commands when I really screw up my Hyper-V VMSwitch or LBFOTeam networking settings.







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered Feb 2 '17 at 4:47









                        Greg BrayGreg Bray

                        4,58252647




                        4,58252647







                        • 2





                          Incredibly, your command only deleted the virtual adapters and left the real ones untouched. That's as good as it gets.

                          – andreszs
                          Sep 19 '17 at 22:22






                        • 1





                          Works on Windows 10 to clean up vEthernet adapters left after Hyper-V uninstalling. Physical cards are up after reboot.

                          – Maris B.
                          Nov 8 '17 at 9:25











                        • worked for me: first removed Win X hyper V then ntcfg -d. great hint!

                          – Joe Platano
                          Dec 27 '17 at 22:16











                        • Great ... this even preserved my TAP-driver and previous installed VirtualBox-HostOnly interface from deletion.

                          – cljk
                          Mar 23 '18 at 6:11











                        • +1 Worked like a charm. Got rid of all the leftover networking bits from other virtualization stuff too.

                          – Corin
                          Apr 5 '18 at 14:18












                        • 2





                          Incredibly, your command only deleted the virtual adapters and left the real ones untouched. That's as good as it gets.

                          – andreszs
                          Sep 19 '17 at 22:22






                        • 1





                          Works on Windows 10 to clean up vEthernet adapters left after Hyper-V uninstalling. Physical cards are up after reboot.

                          – Maris B.
                          Nov 8 '17 at 9:25











                        • worked for me: first removed Win X hyper V then ntcfg -d. great hint!

                          – Joe Platano
                          Dec 27 '17 at 22:16











                        • Great ... this even preserved my TAP-driver and previous installed VirtualBox-HostOnly interface from deletion.

                          – cljk
                          Mar 23 '18 at 6:11











                        • +1 Worked like a charm. Got rid of all the leftover networking bits from other virtualization stuff too.

                          – Corin
                          Apr 5 '18 at 14:18







                        2




                        2





                        Incredibly, your command only deleted the virtual adapters and left the real ones untouched. That's as good as it gets.

                        – andreszs
                        Sep 19 '17 at 22:22





                        Incredibly, your command only deleted the virtual adapters and left the real ones untouched. That's as good as it gets.

                        – andreszs
                        Sep 19 '17 at 22:22




                        1




                        1





                        Works on Windows 10 to clean up vEthernet adapters left after Hyper-V uninstalling. Physical cards are up after reboot.

                        – Maris B.
                        Nov 8 '17 at 9:25





                        Works on Windows 10 to clean up vEthernet adapters left after Hyper-V uninstalling. Physical cards are up after reboot.

                        – Maris B.
                        Nov 8 '17 at 9:25













                        worked for me: first removed Win X hyper V then ntcfg -d. great hint!

                        – Joe Platano
                        Dec 27 '17 at 22:16





                        worked for me: first removed Win X hyper V then ntcfg -d. great hint!

                        – Joe Platano
                        Dec 27 '17 at 22:16













                        Great ... this even preserved my TAP-driver and previous installed VirtualBox-HostOnly interface from deletion.

                        – cljk
                        Mar 23 '18 at 6:11





                        Great ... this even preserved my TAP-driver and previous installed VirtualBox-HostOnly interface from deletion.

                        – cljk
                        Mar 23 '18 at 6:11













                        +1 Worked like a charm. Got rid of all the leftover networking bits from other virtualization stuff too.

                        – Corin
                        Apr 5 '18 at 14:18





                        +1 Worked like a charm. Got rid of all the leftover networking bits from other virtualization stuff too.

                        – Corin
                        Apr 5 '18 at 14:18











                        4














                        Following directions from are taken from the article Removing "Stale" Network Adapters in Hyper-V VM by Jeremy Jameson:



                        1. Start an administrator command prompt;

                        2. Run

                          1. set devmgr_show_nonpresent_devices=1

                          2. start devmgmt.msc


                        3. In newly opened Device Manager "Uninstall" option in context menus worked for me (Win10 Pro).


                        Must say I tried the netcfg -d from prior to this, but it had no observable effect. Also I had Hyper-V disabled at the time of this process.






                        share|improve this answer




















                        • 1





                          Accepted answer was not available (it seems like Hyper-V has to be enable) for me but this one did the job while Hyper-V is disabled.

                          – Tok'
                          Jun 11 '18 at 16:59






                        • 1





                          @Tok' it's probably good point: I had Hyper-V disabled as well, added it to answer.

                          – myf
                          Jun 12 '18 at 8:44















                        4














                        Following directions from are taken from the article Removing "Stale" Network Adapters in Hyper-V VM by Jeremy Jameson:



                        1. Start an administrator command prompt;

                        2. Run

                          1. set devmgr_show_nonpresent_devices=1

                          2. start devmgmt.msc


                        3. In newly opened Device Manager "Uninstall" option in context menus worked for me (Win10 Pro).


                        Must say I tried the netcfg -d from prior to this, but it had no observable effect. Also I had Hyper-V disabled at the time of this process.






                        share|improve this answer




















                        • 1





                          Accepted answer was not available (it seems like Hyper-V has to be enable) for me but this one did the job while Hyper-V is disabled.

                          – Tok'
                          Jun 11 '18 at 16:59






                        • 1





                          @Tok' it's probably good point: I had Hyper-V disabled as well, added it to answer.

                          – myf
                          Jun 12 '18 at 8:44













                        4












                        4








                        4







                        Following directions from are taken from the article Removing "Stale" Network Adapters in Hyper-V VM by Jeremy Jameson:



                        1. Start an administrator command prompt;

                        2. Run

                          1. set devmgr_show_nonpresent_devices=1

                          2. start devmgmt.msc


                        3. In newly opened Device Manager "Uninstall" option in context menus worked for me (Win10 Pro).


                        Must say I tried the netcfg -d from prior to this, but it had no observable effect. Also I had Hyper-V disabled at the time of this process.






                        share|improve this answer















                        Following directions from are taken from the article Removing "Stale" Network Adapters in Hyper-V VM by Jeremy Jameson:



                        1. Start an administrator command prompt;

                        2. Run

                          1. set devmgr_show_nonpresent_devices=1

                          2. start devmgmt.msc


                        3. In newly opened Device Manager "Uninstall" option in context menus worked for me (Win10 Pro).


                        Must say I tried the netcfg -d from prior to this, but it had no observable effect. Also I had Hyper-V disabled at the time of this process.







                        share|improve this answer














                        share|improve this answer



                        share|improve this answer








                        edited Jun 12 '18 at 8:42


























                        community wiki





                        2 revs
                        myf








                        • 1





                          Accepted answer was not available (it seems like Hyper-V has to be enable) for me but this one did the job while Hyper-V is disabled.

                          – Tok'
                          Jun 11 '18 at 16:59






                        • 1





                          @Tok' it's probably good point: I had Hyper-V disabled as well, added it to answer.

                          – myf
                          Jun 12 '18 at 8:44












                        • 1





                          Accepted answer was not available (it seems like Hyper-V has to be enable) for me but this one did the job while Hyper-V is disabled.

                          – Tok'
                          Jun 11 '18 at 16:59






                        • 1





                          @Tok' it's probably good point: I had Hyper-V disabled as well, added it to answer.

                          – myf
                          Jun 12 '18 at 8:44







                        1




                        1





                        Accepted answer was not available (it seems like Hyper-V has to be enable) for me but this one did the job while Hyper-V is disabled.

                        – Tok'
                        Jun 11 '18 at 16:59





                        Accepted answer was not available (it seems like Hyper-V has to be enable) for me but this one did the job while Hyper-V is disabled.

                        – Tok'
                        Jun 11 '18 at 16:59




                        1




                        1





                        @Tok' it's probably good point: I had Hyper-V disabled as well, added it to answer.

                        – myf
                        Jun 12 '18 at 8:44





                        @Tok' it's probably good point: I had Hyper-V disabled as well, added it to answer.

                        – myf
                        Jun 12 '18 at 8:44











                        1














                        I solved this by:



                        In PowerShell type: netcfg -d



                        This WILL DELETE all network adapters AND network SETTINGS!
                        Physical adapters will NOT be LOST.
                        Then i restored my network settings and created new External Virtual Switches.
                        This worked for me fine and fast.



                        Windows 10 64bit there.






                        share|improve this answer



























                          1














                          I solved this by:



                          In PowerShell type: netcfg -d



                          This WILL DELETE all network adapters AND network SETTINGS!
                          Physical adapters will NOT be LOST.
                          Then i restored my network settings and created new External Virtual Switches.
                          This worked for me fine and fast.



                          Windows 10 64bit there.






                          share|improve this answer

























                            1












                            1








                            1







                            I solved this by:



                            In PowerShell type: netcfg -d



                            This WILL DELETE all network adapters AND network SETTINGS!
                            Physical adapters will NOT be LOST.
                            Then i restored my network settings and created new External Virtual Switches.
                            This worked for me fine and fast.



                            Windows 10 64bit there.






                            share|improve this answer













                            I solved this by:



                            In PowerShell type: netcfg -d



                            This WILL DELETE all network adapters AND network SETTINGS!
                            Physical adapters will NOT be LOST.
                            Then i restored my network settings and created new External Virtual Switches.
                            This worked for me fine and fast.



                            Windows 10 64bit there.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Nov 22 '17 at 1:18









                            DzintarsDzintars

                            1113




                            1113





















                                0














                                if that doesn't work. right click on the adapter, properties. Click on Configure at the top, on the 3rd tab on Driver. Uninstall the driver and close the mask. the problem should be solved after pressing F5.






                                share|improve this answer



























                                  0














                                  if that doesn't work. right click on the adapter, properties. Click on Configure at the top, on the 3rd tab on Driver. Uninstall the driver and close the mask. the problem should be solved after pressing F5.






                                  share|improve this answer

























                                    0












                                    0








                                    0







                                    if that doesn't work. right click on the adapter, properties. Click on Configure at the top, on the 3rd tab on Driver. Uninstall the driver and close the mask. the problem should be solved after pressing F5.






                                    share|improve this answer













                                    if that doesn't work. right click on the adapter, properties. Click on Configure at the top, on the 3rd tab on Driver. Uninstall the driver and close the mask. the problem should be solved after pressing F5.







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Jan 14 at 20:12









                                    user505263user505263

                                    1




                                    1



























                                        draft saved

                                        draft discarded
















































                                        Thanks for contributing an answer to Server Fault!


                                        • Please be sure to answer the question. Provide details and share your research!

                                        But avoid


                                        • Asking for help, clarification, or responding to other answers.

                                        • Making statements based on opinion; back them up with references or personal experience.

                                        To learn more, see our tips on writing great answers.




                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function ()
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f584316%2fhow-to-delete-hyper-v-virtual-switch-extensions-adapters-from-device-manager%23new-answer', 'question_page');

                                        );

                                        Post as a guest















                                        Required, but never shown





















































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown

































                                        Required, but never shown














                                        Required, but never shown












                                        Required, but never shown







                                        Required, but never shown







                                        Popular posts from this blog

                                        Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

                                        Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

                                        What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company