{Degraded, ProtocolVersion} on some vmnetworkadapters on 2016 hyperv host


  • Hi.

    I have some question's about keeping my vm's integration services up-to-date on hyper-v 2016.

    After migrating my vm's from a 2012 r2 cluster to a new 2016 cluster my vm's networkadapters shows status {Degraded, ProtocolVersion}

    what i found so far about this is that your vm's integration services version doesn't match your hyper-v hosts version.

    I cant find which version a windows 2012 r2 guest's running on hyper-v 2016 should have.

    My current version is "6.3.9600.18398" which is the latest version running on a 2012 r2 hyper-v host. But is that the latest version for a windows 2012 r2 guest running on 2016 hyper-v? I have tried updating through windows update but there doesn't seem to be any newer versions there.

    /regards Jorgen


    Friday, March 24, 2017 2:04 PM

All replies

  • Hi Sir,

    I tried to installed a new windows 2012R2 and imported a 2012R2 server which residing at 2012R2 hyper-v host .

    The network adapters of both VMs in powershell show {degraded,protocolversion} , but it doesn't show it in hyper-v console :


    Now , I'm waiting for the windows update to finish latest updates installation .

    I'll keep you updated .

    Thanks for your understanding . 


    Now , windows update made some changes (nod1 is not installed windows update , nod2 installed some windows updates ) :

    But VM NIC still show "Degraded" . 


    Best Regards,


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

    Monday, March 27, 2017 11:25 AM