"Microsoft Hyper-V Network Switch Default Miniport" error 39 RRS feed

  • Question

  • "Microsoft Hyper-V Network Switch Default Miniport" error 39        


    "Microsoft Hyper-V Network Switch Default Miniport"

    I can not uninstall this driver .
    I tried a lot of to uninstall after error 39 but I failed.
    plz help me.

    Detailed information about error

    control panel>device manager>network adapters>Microsoft Hyper-V Network Switch Default Miniport>device status>

    Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

    {Unable to Load Device Driver}
    %hs device driver could not be loaded.
    Error Status was 0x%x

    this is  problem what should I do?

    • Edited by rahulbabriya Sunday, June 28, 2015 9:37 AM asked detailed information
    Saturday, June 27, 2015 11:17 AM


All replies

  • Why do you want to remove it?

    What is the actual problem?

    To enable us to help you better, you need to provide as many details as you can about the problem you are experiencing.

    If you design your question effectively, you can get good information from people who are knowledgeable about the topic and who are happy to help you.

    Prepare your question. Think it through. Hasty-sounding questions get hasty answers, or none at all.

    What troubleshooting have you done so far?

    Asking an effective question will get you help faster read how here

    Suggestions for asking for help on a site.

    Wanikiya and Dyami--Team Zigzag

    Saturday, June 27, 2015 12:09 PM
  • hi plz read my problem first. then ans.
    Sunday, June 28, 2015 9:40 AM
  • hi I had designed my question. plz help!!!!!!!!!!
    Sunday, June 28, 2015 9:42 AM
  • Hi,

    Microsoft hyper-v network switch default miniport is hosted by Hyper-V which is a virtual device

    And responsible for Hyper-V network switch. Code 39 states for Windows cannot load device driver properly, in this case, it might cause bad compatibility of adapter driver and chip set driver after a Windows update recently. You could restore you system to earlier point if this issue happened recently. Also you could try updating all network and chipset driver see if it changes the situation. If you have no idea about when this issue happened and driver update doesn’t help. Refer to edmis_ci’s reply in this thread, try find responsible KB, uninstall it temporarily and please report to us.


    D. Wu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact

    Thursday, July 2, 2015 1:20 AM
  • I just spent hours working on this and found the easy solution: 

    I hope this helps

    Ian Matthews

    Monday, March 12, 2018 8:32 PM