Virtual-device names describe software-created adapters and endpoints, not a single driver class or universal download. Windows features, hypervisors, GPU/audio packages, and companion applications can each create different devices. Hyper-V and Windows Sandbox have edition and hardware prerequisites; WSL installation and networking behavior depend on the selected WSL version and Windows release. Identify the exact device instance and owning feature or application before servicing it. Several vendor family names below are retained as search routes only: unless an exact official product page lists that endpoint, the name does not promise that a vendor currently ships such a package.
A virtual device driver lets a piece of software impersonate real hardware convincingly enough that Windows, and the programs running on it, treat it exactly like the physical thing. A virtual network adapter carries traffic between your PC and a virtual machine as if a real cable were plugged in; a virtual audio endpoint accepts a program's sound and routes it somewhere else instead of a speaker; a loopback adapter gives the networking stack an address to talk to itself. In each case the driver is the shim that makes the illusion complete.
What sets this category apart is that the driver usually does not come from a chip vendor. It is installed by the software that needs it, whether that is a Windows optional feature like Hyper-V, a developer tool like the Windows Subsystem for Linux, or a streaming utility that wants a spare audio channel. The driver's lifecycle is tied to that parent program, so it is created when you enable the feature and removed when you uninstall it, and it must stay in step with the version of the host that made it.
Because these devices are software, their most common failures are configuration problems, orphaned leftovers, and version drift between a driver and its host, rather than the hardware faults you see elsewhere.
Expanded guide insight
The practical virtual devices context
Virtual devices are software-made hardware entries used by VPNs, virtual machines, audio routing, and Windows itself. The key question is which installed feature owns the device.
Show hidden devices to audit old entries.
Driver Provider helps identify the app that owns a device.
Uninstalling the owning app is safer than deleting its device blindly.
Take care: Do not remove Microsoft in-box virtual devices such as WAN Miniports just because they look unfamiliar.
Fast checks for common virtual devices problems
What you see
Likely area to check
Safe first move
An unfamiliar network adapter appears
A VPN, VM, or older app created a virtual device
Match the provider to installed software first
VPN connection fails
The adapter binding or owning app is damaged
Use the VPN provider’s repair or reinstall path
Audio routes to the wrong device
A virtual endpoint became the default
Select the intended output in Sound settings
Start with the lowest-risk check that matches what you see, then return to the detailed sections below if it does not resolve the issue.
Identify your exact device first
In Device Manager, choose Show hidden devices from the View menu so dormant virtual adapters and endpoints become visible.
Read the device name closely; virtual entries usually carry words like Virtual, Hyper-V, Loopback, WAN Miniport, or a utility's brand name.
Trace each virtual device back to the software that created it, since that program, not a vendor, is what you will update or repair.
Check installed Windows features and apps to see whether Hyper-V, WSL, or Windows Sandbox is available and enabled; availability depends on Windows edition, release, hardware, and policy.
In Network Connections, look for adapters with no matching physical port, a strong sign they are software-defined.
For virtual audio, open Sound settings and note endpoints that do not correspond to a real speaker or headset.
10/11 only where the exact Corsair product/app lists it
Exact endpoint and driver-provider names
Scan the list first, then open the family that matches your hardware for the full reference.
Reference coverage summarizes the Windows releases discussed in this catalog; it is not certified compatibility. Confirm the exact device or PC model, hardware revision, current Windows release, and current package requirements on the publisher source before making a change.
Reference coverage: Eligible 10/11 Pro, Enterprise, or Education editions with Hyper-V requirements met
Hyper-V creates virtual network adapters for virtual machines and virtual switches; names and lifecycle depend on the configuration. Hyper-V is not available as a host feature on every Windows edition, and Microsoft documents processor, firmware-virtualization, and security requirements. Service it as part of Windows and Hyper-V rather than downloading a standalone adapter package.
How you recognize it
Hyper-V-related adapter shown when the platform and a virtual network are configured
Bound to a Hyper-V virtual switch
Installed by enabling the Hyper-V optional feature; serviced by Windows Update.
Reference coverage: Eligible 10/11 Pro, Enterprise, or Education editions with Hyper-V requirements met
This route covers the Hyper-V virtual switch and extensibility model, not a standalone extension download. Hyper-V Manager configures switches; third-party switch extensions, if installed, come from their own publisher and must document compatibility with the host release. Availability depends on edition, hardware, policy, and enabled Hyper-V components.
How you recognize it
Configured in Hyper-V Manager
Extension entries, if any, identify their own publisher
External switches bind to a selected physical NIC
Managed through Hyper-V Manager and Windows features, not a standalone driver.
Reference coverage: 10/11 releases supported by the selected WSL installation method
WSL networking is provisioned by the selected WSL version and Windows configuration; adapter names and architecture can differ, including mirrored networking on supported Windows 11 systems. This route is not a standalone adapter download. Follow Microsoft's current WSL install and networking documentation for the host release.
How you recognize it
WSL is installed and its version/configuration is known
Networking entries may be named for WSL, Hyper-V, or the current architecture
Created by the Windows Subsystem for Linux; update WSL to service it.
Reference coverage: 10/11 Pro, Enterprise, or Education editions only; current Sandbox prerequisites apply
Windows Sandbox is an optional disposable environment available only on editions and systems listed by Microsoft's install documentation. Its virtualized devices belong to the Windows feature and are not standalone downloads. Required Windows build, architecture, memory, storage, and firmware virtualization must be checked against the current prerequisite page.
How you recognize it
Associated with an enabled Windows Sandbox feature on an eligible edition
Created for Sandbox sessions
Requires documented virtualization prerequisites
Provided by the Windows Sandbox optional feature and Windows Update.
Reference coverage: Use only on releases covered by the applicable Microsoft procedure
Microsoft documents a KM-Test loopback adapter for specific testing and troubleshooting procedures. Installation steps and naming can vary by Windows release, and it should not be added merely as general network maintenance. Use the exact Microsoft procedure for the intended scenario; there is no standalone download.
How you recognize it
Exact Microsoft procedure calls for a loopback adapter
Adapter name is confirmed after installation
Has no matching physical network port
Inbox virtual adapter added via Device Manager's legacy hardware wizard.
Reference coverage: 10/11 only with compatible Wi-Fi hardware, driver, and feature support
Windows and a compatible wireless driver can expose Wi-Fi Direct virtual interfaces for supported features. Their presence and naming depend on the physical adapter, driver model, Windows release, and active feature; Mobile hotspot behavior alone does not prove a particular adapter name. Service the physical wireless stack using the PC or adapter maker's applicable package.
How you recognize it
Exact virtual-adapter name and physical Wi-Fi adapter
Compatible wireless driver and active feature
No standalone virtual-adapter download; exact behavior depends on Windows, physical Wi-Fi hardware, its driver, and the active feature.
Reference coverage: 10/11 only where an exact NVIDIA product/package lists it
This retained route name is a search label for an NVIDIA-named virtual endpoint, not a promise that every graphics package installs one or that it supports a particular broadcast feature. Read the device's hardware ID and driver provider, then consult the exact NVIDIA product and package notes. Service it with the owning package only after that relationship is established.
How you recognize it
Exact Device Manager name, hardware ID, and driver provider
Owning NVIDIA application or package identified from official documentation
Search label only; no fetched NVIDIA document established a universal endpoint, owner, streaming purpose, or service package.
Reference coverage: 10/11 only where an exact AMD product/package lists it
This retained family name is a search label, not evidence that current AMD graphics software creates a generically named virtual audio or display endpoint. Identify the exact Device Manager name, provider, and hardware ID, and use the applicable AMD or system-maker package notes. Do not reinstall a graphics package merely from this route name.
How you recognize it
Exact endpoint name, provider, and hardware ID
Owning AMD feature confirmed by official product documentation
Search label only; no fetched AMD document established this generic endpoint, its purpose, or a family-wide service package.
Reference coverage: 10/11 only where the system or Intel package lists it
This retained route name is a search label; Intel's general graphics download page does not by itself substantiate a generically named virtual display endpoint or a wireless-display/capture purpose. Identify the exact endpoint and owning feature, then use the PC maker's model page or an Intel document that explicitly lists it.
How you recognize it
Exact Device Manager name, hardware ID, and provider
Owning system or Intel feature confirmed on an exact product page
Search label only; no fetched Intel document established this generic virtual endpoint or a wireless-display/capture purpose.
Reference coverage: 10/11 only where the exact PC/board audio package lists it
This retained route name is a search label, not a Realtek-wide package claim. OEM audio stacks can add software endpoints under different names and from different companion vendors. Check the endpoint provider and the exact PC or motherboard audio package before attributing it to Realtek or changing a driver.
How you recognize it
Exact endpoint name and provider in Device Manager or Sound settings
Owning OEM audio package documented for the exact system
Search label only; no fetched Realtek or OEM document established a family-wide virtual endpoint.
Reference coverage: 10/11 only where an exact ASUS product page lists the utility
This retained route name is a search label. ASUS has multiple product-specific audio utilities, and the general download center does not establish that a particular board creates this mixer. Search the exact PC, motherboard, headset, or capture product and install only a documented utility for that model.
How you recognize it
Exact ASUS product model
Utility and endpoint names listed on that product's support page
Search label only; the general ASUS selector does not establish a mixer, broadcast purpose, or supported product.
Reference coverage: 10/11 only where an exact MSI product page lists the utility
This retained route name is a support-search label, not a named universal MSI package. Identify the exact device provider and owning MSI application, then check that model's support page. Do not assume an unknown virtual device should be removed merely because an MSI application is installed.
How you recognize it
Exact Device Manager name and provider
Owning MSI application documented for the exact product
Search label only; no fetched MSI document established one generic virtual device or service application.
Reference coverage: 10/11 only where an exact Gigabyte product page lists it
This retained route name is a search label, not evidence of a Gigabyte-wide virtual-device package. Identify the exact provider and parent application, then use the board or system revision's support page. Removing an unidentified hidden device can break a still-installed feature, so establish ownership first.
How you recognize it
Exact device name, provider, and parent application
Board/system model and revision support page lists the utility
Search label only; no fetched Gigabyte document established a generic endpoint, purpose, or maintenance path.
Reference coverage: 10/11 only where the exact Corsair product/app lists it
This retained route name is a search label. Corsair peripherals and applications vary, and a general downloads page does not prove that an exact product installs a virtual endpoint. Identify the endpoint provider and owning Corsair product or app, then follow that product's documentation for repair or removal.
How you recognize it
Exact endpoint and driver-provider names
Owning Corsair product/application confirmed on its support page
Search label only; no fetched Corsair document established a family-wide endpoint, mixer purpose, or service package.
Device Driver Guide does not host, mirror, or alter driver files. The official-source citations below are maintained separately from this reference material and never point to third-party mirrors.
Where the correct package usually comes from
For virtual devices created by Windows itself, there is nothing to download. Enable the relevant feature in Turn Windows features on or off, and Windows Update maintains the driver as part of the platform. Trying to source a standalone file for a Hyper-V adapter or a WSL network device is a mistake, because those components are versioned with Windows and cannot be swapped independently.
For virtual devices created by an application, the source is that application. Update, repair, or reinstall the host software from the company that makes it, and the bundled virtual driver comes along with it. When the virtual endpoint is a feature of real hardware, such as a GPU that offers a virtual display or an audio chip that exposes an extra output, the correct package is the ordinary driver for that hardware from the chip maker's own support site.
Official sources and citations
These links serve two different purposes. A manufacturer support selector helps you find an exact model, but does not prove that a package or feature exists for every product in a family. Claim-specific documents explain the cited technology, requirement, lifecycle, or bounded package example. In either case, check the publisher domain, exact model and hardware revision, operating-system release, supported-products list, and package notes before making a change.
Microsoft Lifecycle: Lifecycle documentation for Windows 10 Home and Pro; separately governed editions and servicing channels can have different dates.
Realtek: Use this publisher-maintained page to match the exact Realtek model and operating-system release before selecting a package.
Device Driver Guide is an independent reference, not a repair or technical-support service. It does not host or mirror installers and receives no payment for these links. A named-model package example applies only to the systems and operating systems on that publisher page; it is not a recommendation to install the package across a family. Report a moved or incorrect link through the correction form.
Virtual Devices reference tables
Who owns each virtual device
Virtual device
What created it
How to service it
Hyper-V virtual Ethernet
The Hyper-V feature
Update Windows; manage the switch in Hyper-V Manager
WSL network adapter
The Windows Subsystem for Linux
Update WSL, then reboot
Windows Sandbox devices
The Sandbox feature
Windows Update maintains them with the feature
Wi-Fi Direct virtual adapter
The wireless stack
Update the physical Wi-Fi adapter driver
GPU virtual audio or display
The graphics driver
Update or reinstall the GPU driver
Vendor utility virtual device
A motherboard or peripheral app
Repair or reinstall that application
Which parent creates each kind of virtual device and how you actually service it.
Do not chase a standalone driver here
Tempting action
Why it fails
Correct move
Download a Hyper-V adapter driver
Component is versioned with Windows
Toggle the feature or update Windows
Update only the bundled virtual driver
It drifts out of sync with its host
Update the host application as a whole
Run a driver updater on an endpoint
It misreads software as stale hardware
Leave it; refresh the parent if broken
Reinstall a GPU audio endpoint alone
The endpoint is part of the GPU package
Reinstall the graphics driver
Delete an in-use virtual adapter
The host recreates it or breaks
Close the VM or stream first
Why standalone driver files are the wrong instinct for software devices, with the correct move instead.
Cleaning up orphaned virtual devices
Step
Action
Why
1
Show hidden devices in Device Manager
Dormant and orphaned entries stay invisible otherwise
2
Confirm no app or feature still owns it
Removing a live adapter breaks its host
3
Uninstall the orphaned entry by hand
Clears IP and DNS conflicts it can cause
4
Reboot and recheck hidden devices
Confirms it did not return
5
Rebuild host networking if needed
May restore the configuration you cleared
A safe order for finding and removing leftover software adapters after an app is gone.
When updating helps, and when it does not
Do not update a virtual device on its own; update its host instead. If Hyper-V networking misbehaves, service Windows; if a WSL adapter breaks, update WSL; if a streaming tool's virtual mixer stops working, update that tool. Chasing a standalone driver for a software device usually does more harm than good because the driver is not meant to move independently of the program that installed it.
There is rarely a routine cadence here at all. Leave working virtual devices alone and act only when something breaks or when the host software's own release notes call for an update. The one exception is a hardware-backed virtual endpoint, which follows the same modest update schedule as the GPU or audio driver that provides it.
Before you install anything
Identify which application or Windows feature owns the virtual device before you touch anything.
Save any host-application configuration, such as virtual switch settings or audio routing, so you can rebuild it if needed.
Create a System Restore point, since feature and hypervisor changes can affect networking broadly.
Close virtual machines and streaming sessions that depend on the device so it is not in use during the change.
Note existing virtual adapters in Device Manager with hidden devices shown, so you can spot new duplicates afterward.
How to update virtual devices drivers
1
Identify what created the virtual device
In Device Manager, note the exact virtual device name and category. Most virtual adapters and endpoints are created by a host application or a Windows feature, so determine the parent software before making changes.
2
Enable the relevant Windows feature when documented
Follow Microsoft's current installation page for the exact feature and Windows edition. Hyper-V, WSL, and Windows Sandbox have different installation paths and prerequisites; do not assume all are enabled through the same dialog.
3
Update the host application, not a standalone driver
If a hypervisor or utility created the device, update or repair that application from its official source. Virtual-device drivers are usually bundled with their host and must stay in sync with it.
4
Service only a confirmed owning package
If exact product documentation ties the endpoint to a GPU, audio, or companion package, follow that publisher's model-specific repair or update instructions. A similar brand name alone is not enough.
5
Confirm documented virtualization prerequisites
If a virtual-machine feature fails to start, compare the Windows edition, host hardware, firmware virtualization, memory, storage, and security prerequisites in that feature's current Microsoft and PC-maker documentation before changing firmware.
Confirm the install actually worked
Reopen Device Manager and confirm the virtual device is present with no warning icon after the host is updated.
Start the dependent workflow, such as booting a VM or opening a stream, and confirm it reaches the network or plays audio.
In Network Connections, check that the virtual adapter has a sensible address and no conflict with another interface.
For virtual audio, play a test sound to the endpoint and confirm it arrives where you expect.
Show hidden devices again and confirm no orphaned duplicate of the adapter was left behind.
Undoing a bad virtual devices install
If a host update broke a virtual device, the first move is to repair or reinstall that host rather than the driver alone. Most hypervisors, developer tools, and utilities offer a repair option that recreates their virtual devices cleanly, and a full uninstall followed by a fresh install clears out corrupted state.
When a Windows feature is at fault, turn the feature off in Turn Windows features on or off, reboot, then turn it back on to force Windows to register a fresh copy of its virtual devices. For leftover or duplicate adapters, show hidden devices in Device Manager and uninstall the orphaned entries by hand.
If networking as a whole is disturbed, a System Restore point taken before the change is the surest way back, after which you rebuild the host application's configuration.
Uninstalling an application often leaves its virtual adapter behind, and the orphan can cause IP or DNS conflicts until removed with hidden devices shown.
Disabling hardware virtualization in Bios/Uefi, or a security feature that blocks it, stops virtual machines from starting even when the adapters look fine.
Duplicate virtual audio endpoints send sound to the wrong place, which looks like a driver fault but is really a routing choice.
Automated driver updaters misread software adapters as outdated hardware and try to replace components that must match their host.
A mismatch between a host application and its bundled virtual driver, after updating only one of them, breaks the feature.
Recreating a Hyper-V external switch on the wrong physical adapter cuts the host's own network access.
Mistakes to avoid with virtual devices
Hunting for a standalone driver file for a Hyper-V or WSL adapter that is versioned with Windows.
Updating only the bundled virtual driver and letting it drift out of sync with its host application.
Uninstalling an app without removing its leftover adapter, which then causes IP or DNS conflicts.
Disabling hardware virtualization in firmware, so VMs will not start even though the adapters look fine.
Binding a Hyper-V external switch to the wrong NIC and cutting the host's own network.
Letting a driver updater replace software endpoints that must match their host application.
Blaming a driver when a duplicate virtual audio endpoint is really just the wrong default device.
Situations readers arrive with
I uninstalled a VPN app but my internet is flaky and I still see its adapter listed.
The app left an orphaned virtual adapter that can cause IP or DNS conflicts. In Device Manager choose Show hidden devices, confirm no running app owns it, then uninstall the orphaned entry and reboot. If networking is still off, rebuild your connection settings afterward.
My virtual machines suddenly refuse to start with a virtualization error, though nothing looks wrong.
This is usually a firmware or security setting, not the virtual adapters. Enter Bios or Uefi and enable Intel VT-x or AMD-V, and check whether a Windows security feature is blocking virtualization. Update the OEM chipset driver, then reboot and retry.
After a Windows update, my WSL Linux environment can no longer reach the internet.
The WSL virtual adapter is serviced by WSL itself, so do not look for a driver. Update WSL to the current version, restart the WSL service, and reboot. That usually re-registers the adapter and may restore networking.
My streaming software's virtual audio channel disappeared after I updated my graphics driver.
If the endpoint came from the GPU package, reinstalling or repairing the graphics driver refreshes it. If it came from a separate streaming utility, update or repair that utility instead. Then set the correct default device in Sound settings so audio routes where you expect.
I set up a Hyper-V external switch and now the host itself has no network.
The external switch was likely bound to the wrong physical adapter, which redirects the host's own connection. In Hyper-V Manager, recreate the external switch on the correct NIC, confirm the physical adapter driver is current, and reboot after the change.
Symptom-by-symptom troubleshooting
Hyper-V virtual switch cannot reach the network
In Hyper-V Manager, recreate the external virtual switch bound to your physical adapter, and make sure the physical NIC driver is current. Reboot after changing the switch type.
Virtual machine will not start with a virtualization error
Check the hypervisor's documented error and host requirements, including Windows edition, processor features, firmware virtualization, and interactions with other virtualization-based features. Use the PC maker's firmware instructions rather than changing an assumed setting name.
A leftover virtual adapter remains after uninstalling software
Open Device Manager, choose Show hidden devices from the View menu, and uninstall the orphaned adapter. If it returns, run the host application's repair or clean-uninstall option.
Virtual audio device produces no sound
Identify the endpoint's provider and owning application first, then check routing in Sound settings. Repair or update a package only when its exact documentation confirms ownership and applicability.
WSL networking stopped working after an update
Check Microsoft's WSL status, update, and networking guidance for your installed WSL and Windows versions before resetting anything. Adapter names and networking modes differ by configuration, so do not hunt for a standalone driver.
Duplicate virtual adapters cause IP or DNS conflicts
Disable adapters you do not use in Network Connections, and remove duplicates via Device Manager with hidden devices shown. Reconfigure the host application's networking afterward.
Loopback adapter is missing for a test setup
Use Device Manager's Add legacy hardware wizard to install the Microsoft KM-Test Loopback Adapter, then assign it a static address as needed for your scenario.
Frequently asked questions
Do virtual devices need their own downloadable drivers?
Usually not. Most virtual adapters and endpoints are created by a Windows feature or a host application and are serviced by Windows Update or that application. Standalone driver files are the exception, not the rule.
Where does the Hyper-V virtual adapter come from?
It appears when you enable the Hyper-V optional feature in Windows. There is no separate driver to download; Windows Update maintains the component along with the platform.
Did my GPU create a virtual audio or display device?
Do not infer that from a brand-like endpoint name. Check the device provider, hardware ID, installed applications, and exact GPU or system documentation. Service the graphics package only if that evidence identifies it as the owner.
Why do I see leftover virtual adapters after removing an app?
Some applications do not fully remove their virtual adapters. Show hidden devices in Device Manager and uninstall the orphaned entries, or use the app's clean-uninstall option.
How do I enable virtualization so VMs will run?
Use the hypervisor's host-requirement page and your PC maker's firmware instructions. Required Windows edition, processor support, firmware setting names, and interactions with other virtualization-based features vary by system.
Can automatic driver updaters manage virtual devices?
We advise against them. They can misidentify software adapters and try to replace components that must remain in sync with their host application, which can break virtualization or audio routing.
Is a virtual network adapter a security risk?
By itself, no more than the software that created it. Keep the host application and Windows updated, remove adapters you no longer use, and download software only from official sources.
Terms used on this page
Hypervisor
Software such as Hyper-V that runs virtual machines and creates the virtual devices they use.
Virtual switch
A software network bridge that connects virtual machines to each other and to a physical adapter.
Loopback adapter
A virtual network interface used for testing that lets the PC send traffic to itself.
Endpoint
A named audio input or output; a virtual one exists in software rather than as a physical jack.
Optional feature
A Windows component you enable on demand, which registers and services its own virtual devices.
Device Driver Guide stores a local consent preference to remember your choice. Replit Project Analytics may measure visits and selected site interactions. These local choices do not turn hosting analytics on or off. Custom events exclude form entries and other free-form content. No advertising scripts are active. Read the Cookie Policy.
