First of all, I apologize both for my English and if I published this post in the wrong section.
The question is quite summarized in the title.
I specify that the current version of Comodo Firewall used by me is 22.214.171.12436 and that from long time I have activated the Windows Sandbox, without however also having installed the Hyper-V module.
Today I forced the update to the latest version of Windows 10, the new “May 2020 Update v 2004”.
After the successful update process and after rebooting, I found a new network card, called “vEthernet | Hyper-V Virtual Ethernet Adapter” …
This is not a problem!
This a Virtual Machine Platform module in Windows components.
Control Panel → Programs (Programs and Features)-> ‘Turn Windows features on or off’
checkbox name “Virtual Machine Platform” or “Hyper-V Platform” or any other in Windows localizations. Be careful. Some programs can be broken if you delete this checkbox.
Thanks first of all for your intervention and for the suggestion! :-TU
As I said into the lines above, I have not activated the Hyper-V module between the components of Windows, but only Windows Sandbox.
This new network card came out after the “May 2020 Update v 2004” and, from that moment, Comodo Firewall (rightly) detects (automatically) a new network to manage.
I just would like to know if any other user is having my same experience.
In a sense, then, that’s what we wrote here.
In short: “I therefore contacted Microsoft technical support and it was reported to me that, since April 2020, Windows Sandbox has been working properly only by also relying on Hyper-V.”.
As if to say that the April 2020 updates anticipated the definitive changes (with the “creation” of a new virtual network card) from the last and most recent update “May 2020 Update v 2004”.