It's a damn "hair puller" problem.
It doesn't appear related to new hardware & dongles but more to do with netframework getting/writing the port values.
It appears 3rd party software fixes this so why is the MS stuff so poor after years of this still being an issue. I mean this issue has been around for some time across various OS & hardware platforms.
There are some suggested fixes in
this MS summary of the issue but I have never followed them up nor know how to apply them.