Forum Discussion
[server 25314] External SET Team to Internal after Reboot.
After communicating with the Microsoft team, I was given a minimal workaround and managed to get SET Switch to work.
1.when BSOD or GSOD occurs on Intel i350, etc., it occurs when Virtual Machine Pool is enabled, so it is necessary to disable VMP.
Using e1r.sys and may occur on NICs where VMq is supported
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmsmp\Parameters BelowTenGigVmqEnabled 0
2.if Host Network Service is running, SET Switch is set to Internal due to HNS problem.
Disable HNS (this workaround is not possible when using containers).
With the above two methods, we were able to create a SET Switch and confirm that the SET Switch still works after rebooting.
Now I just hope that the Microsoft Team will fix the problem.
This is only a workaround and not an answer.
I can confirm that there are two separate issues that is related to this. The BSOD bug related to VMQ support, and the HNS Service/SET Switch issue.
As brichan mentioned the workarounds are not a final solution. When there is an update available to official fixes I will post here. Thank you everybody for reporting this issue.