virtualbox.org

I updated 3 hosts to 4.3.0 release and on three different VMs Windows became unactivated and had to be reactivated. Anyone else have this issue? Was there enough of a change in the VM "hardware" presentation to trigger the reactivation?

To me it seems like the network adapter has changed - properly the Bridge version, but not sure.