<div>
your very problem?<br />
2016 and 2012 differences :)<br />
<br />
<br />
<a href="https://social.technet.microsoft.com/Forums/lync/en-US/e5ee2072-8264-4477-add6-4fc26408d89b/the-vm-and-host-networking-components-failed-to-negotiate-protocol-version-61?forum=winserverhyperv" rel="ugc nofollow">https://social.technet.microsoft.com/Forums/lync/en-US/e5ee2072-8264-4477-add6-4fc26408d89b/the-vm-and-host-networking-components-failed-to-negotiate-protocol-version-61?forum=winserverhyperv</a>
</div>


<div>
As i know is supported right?<br />
<br />
<a href="https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn792027(v=ws.11)" rel="ugc">https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn792027(v=ws.11)</a><br />
<br />
recently the vm claim auto reboot, checked event log is return that.<br />
<br />
so wondering will the event cause any major problem
</div>


<div>
What else happened when auto-rebooting, maybe update installations? There are no errors that will force a reboot.
</div>


<div>
Not notice much log, beside that. will check out the auto Windows update and revert.
</div>


<div>
HI McKnife, thanks for sharing. we can conclude whether is windows update is causing the windows auto restart. but it may the possibility. so we just turn off windows update and monitor for next few weeks. <br />
<br />
Really appreciate the sharing.
</div>


<div>
<div class="content wysiwyg-content">
Host : Hyper-V Windows Server 2012R2<br />
<br />
Guest OS: Windows Server 2016<br />
<br />
Event Log : &quot;&nbsp;VM and host networking components failed to negotiate protocol version 6.1&quot;<br />
<br />
HI All, Anyone have idea about this? will this cause the server reboot?
</div>
</div>


Host : Hyper-V Windows Server 2012R2

Guest OS: Windows Server 2016

Event Log : " VM and host networking components failed to negotiate protocol version 6.1"

HI All, Anyone have idea about this? will this cause the server reboot?

Windows Server 2016 VM on Micorosoft Hyper-V 2012R2

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.