I have a clean install on an HP ML350 G10 server of Windows 2019 standard now that it was re-released.
The HP SPP worked fine to get all drivers loaded since 2019 isn't supported yet for the intelligent provisioning process.
Server activated, all four network card work fine. No bangs in device manager, all devices have drivers loaded and are recognized.
I've added the Hyper-V role, that goes fine.
Then trying to add an adapter to the hyper-v switch, it fails. Ultimately the error is that it can't find a file. This is trying to get the adapter installed via the GUI. So I dropped to powershell, tried to create it there, same error.
Tried every network card, same error.
Removed Hyper-V role, re-added it, same error.
Removed Hyper-V role, then when I added it, tried to add the interface to the network switch during the GUI install of the Hyper-V role. It didn't give an error, but when the install was done and system rebooted, there was nothing for the hyper-v switch.
And trying manually via GUI or powershell still does the same thing.
I'm not allowing the management operating system to share the adapter, although I tried with letting that happen and the result is the same.
Some of the things I've seen for older OS's like 2012 and 2016 said to remove the "Hyper-v Extensible Virtual Switch" from the bindings on the cards first then try again, but that won't uninstall. I get an error 0x80071779
I've removed and reinstalled the drivers, and a few different versions of the drivers, including the ones it finds automatically when I just went to the network card properties and told it to find drivers to update as well as the current and previous versions
on HP's website for this adapter.
Anyone else see this? It always comes back to "Error applying virtual switch properties changes. Failed while adding virtual ethernet switch connections." The details show the GUID of the adapter, with the final text, "The system
cannot find the file specified." and an error code of 0x80070002
Another post mentioned they solved something similar on an earlier windows build by disabling internet connection sharing - that's already disabled.
Another post mentioned antivirus causing this in a previous Windows server build - but this is a clean windows install, no antivirus is installed here.
One of the joys of playing with a new server build right at release...
Just in case it WAS something that was corrupted from the original install, I nuked it, reinstalled clean from scratch, and the problem persists.
I wish I had another spare server I could test this with to see if it's a bug with Windows, or simply some incompatibility with HP. But since other people have had this issue since 2012, I'm guessing there's just something I will have to wait to get
updated with by MS or by HP.
I made the mistake of posting the question on spiceworks and got people "instructing" about everything EXCEPT the actual problem. It's a bit like posting on an auto forum about a brake issue, and people "answer" complaining about the color of your car...
Since I have a business continuity device on this network I have no qualms about deploying 2019 this early for a Hyper-V role, as I can spin up any of its guests within minutes if something happens, so no complaining that "you shouldn't use 2019 in
production until after the first service pack," or other such. Let's please try to stick with the actual technical issue. I prefer to NOT have to deploy a 3+ year old OS on a brand new server now if I don't have to.
Thanks for any guesses...
John
John