I ran into the same issue. The answer is:
This is known behavior that (sometimes) occurs when you plug in a USB camera
or, apparently, simply have a video card with a video capture port on it.
Here is the URL to KB "FAQ":
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q303302
Microsoft says that this is "By Design" behavior (which means it should have
no impact) but the fact of the matter is that I found this because I was
investigating why my connection to the internet kept dropping.
On my machine, at least, this mysterious Microsoft TV/Video Connection was
set to use an automatic Interface metric, which resulted in it "cutting in
line" before my NIC and was receiving all TCP traffic first. The resultant
xx millisecond delay while the packets were passed down the TCP/IP stack was
just enough to make my NIC think it was disconnected.
Changing the interface metric to "2" for the Microsoft TV/Video Connection
seemed to help a lot. Of course, if you unplug the USB camera and reboot the
device disappears altogether and the crappy connection problem is resolved -
but some of us need to use our USB cameras while we're connected to the
internet!
Shannon Norrell
thewebdood
Ken Wickes said:
I don't remember exactly but I think it is a piece of hardware the
incorrectly identifies itself as a network adapter. You should be able to
ignore it.
--
Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Tom Frass said:
This just popped up in the network area and have no clue
what it is or where it came from? Thansk Tom
