These Virtual Devices (VDev) are provided for Automatic Virtual Machine Activation (AVMA) to communicate with the host. If you view the properties of these devices and check driver details, Hardware IDs or Compatible IDs, they will show the following:vmbus\ No guarantees how long MS will allow it will stay up here, though it’s freely distributed with Hyper-V Server.Īfter installing the IC on OSes older than Windows Server 2012R2, you will still see 2 unknown devices. Hyper-V 2008 here: !AnbqFQxI6C6pio4UYt3Jn_VLbrQs4w Opens a new window Hyper-V 2008 R2 here: !AnbqFQxI6C6pio4TpkS4Yi9Pl0_Ejg Opens a new window I’ve got a copy from Hyper-V 2012 R2 here: !AnbqFQxI6C6pidtRrLfIRLDSHKeYmw Opens a new window Or, if you’ve got a Windows 8/8.1/2012/2012R2 VM/system available with Hyper-V installed you’ll find it in the C:\windows\system32\ folder. Opens a new window ( to extract, you’ll need to mount the ISO, open the x:\sources\install.wim file with something like 7zip, browse to Windows\system32, and extract the vmguest.iso or install Hyper-V Server in a VM to get the vmguest.iso)
You can get the IC from Hyper-V 2012/2012R2 Server, a free download, here: See my blog post here: Opens a new window for the full info: The Integration Components won't help with certain things as Kevin mentioned and you'll still see unknown devices.
