EDIT: To make the text a bit more detailed

I cannot give you a specific answer to this. But about the other of your links - discussion ended in Windows 11 related problem. I did verify that the Microsoft delivered Windows 11 worked just fine in VMware on that date. It is a DEV version and it seems to change many times a week. I later tried the new install from ISO-file and that worked very well, too, in VMware - however, this isn't really testing VMware, but it is more about if the suggested way to create a correct ISO-file works as it should be ... still talking about Windows 11 from strictly Microsoft sources.

I understand that your case NOW is not about Windows 11.

However, if Network adapters are failing to install, there are many generic reasons why an install in Windows fails. Typically, it is not related to an application, but to a certain Windows instance ... but we don't know for sure.

The generic reasons include:

- versioning. Not sure what the 16 version needs to be with that particular Windows 10 version. Needs to be checked or taken the latest one.

- Windows Feature Upgrades do break applications. This is a Day-One-Problem of Windows 10. Have you done a reinstall AFTER the feature upgrade or any update to make sure?

- Windows Install may be broken. Not sure how to fix that, however, log files or Event Viewer should indicate if the installer itself fails. As for fixing, I'm sure google and microsoft will tell you how. In my cases, the matter has been about an outdated Windows Update resulting in an outdated Install software.

- you have manually tried to correct the situation. See log-files AND Event Viewer to find out, why it failed.

- potentially, any other application can break Windows. This may be far-fetched in this case, but if you have another computer with a vanilla Windows 10, you might want to try it out, for testing, if it isn't useful. This would test at least that your VMware install .exe isn't corrupted.

- failing to install using Run As Administrator during install. Being an Administrator is NOT enough in some cases. (linked into registry matters)

- one way of how Windows gets broken, is to get wrong permissions in registry. No idea, how that might have happened, but that is a possibility, if some installation programs have not behaved correctly

- you may have some security software, which does more than you think. Some anti-virus software may have kind-of stealth fire-walling, which will block network related things. In corporate computers, this might come as a surprise to the user ... information may be shared as need to know -basis.

The above is in no particular order. Personally, I would check Event Viewer first to check for failures.