New
#270
Yes, there usually is. Our issue now, in your case we cannot use the PowerShell's excellent Hyper-V cmdlets to completely remove the traces of old switches because as far as Hyper-V and PowerShell are concerned, there aren't any.
You could check the Event log at the moment of getting that error message in Virtual Switch Manager. Tip: Your last screenshot about the error seems to be named as create-switch-error01.png, check the date created time of that file to see about which log entries you should check in your events, just before the date created time of that file.