If the hyper-v role is added to a server with a custom LWF installed then the filter is unbound from the physical NIC, bound to the new virtual network adaptor and life is good.
If the LFW is updated by uninstalling and reinstalling then the filter becomes bound to both the physical and virtual NIC?s. How, in this situation, can I prevent the filter from binding to the physical NIC. I am using a custom installer if this can only be achieved through API?s and not configuration or the LWF itself.