Hello there
Can you provide the Tools install logs which hopefully the repair will have generated?
These might help understand why the vmxnet3 driver was not installing or being reinstalled.
They are usually located in the following locations:
%temp%/vminst.log
%temp%/vmmsi.log
C:\windows\temp\vminst.log
C:\windows\INF\seupapi.dev.log
Also with OS in-place upgrades we have seen issues with drivers and Tools functionality being lost . The general recommended practice is to create a new VM with the later OS instead.
Having stated that, customers often do this. When issues like this occur, it is because during the OS upgrade process the plug and play drivers will be reinstalled. This means that the installation data the Tools installer caches in the registry can become stale and incorrect. That leads to repair breaking and possibly Tools upgrades to the next newer version not working correctly.
To workaround this issue, it ls probably simplest to uninstall the Tools and install again as new,
This type of issue, I have just fixed and should be much improved in the next release of Tools.