In Device Manager, the ICOM virtual audio driver for RS-BA1 V2 appears under Sound, video and game controllers as a playback and recording endpoint labeled with ICOM or RS-BA1 naming, not under Ports or System devices. The underlying driver package may also register a hidden or non-present entry visible only with Show hidden devices enabled. If you cannot see it there, the virtual audio device is not properly installed, and the RS-BA1 client cannot route received audio to your PC speakers or transmit audio from your microphone.
Mechanism: how the virtual audio driver registers in Windows
RS-BA1 V2 splits its work between two pieces of software. The radio control client handles network traffic to the transceiver. A separate virtual audio driver, installed as part of the RS-BA1 package, creates a software audio endpoint that Windows treats as a real sound card.
Windows organizes hardware by function, not by vendor. Class drivers are grouped by the type of device they expose. An audio endpoint belongs to the audio class, so Windows enumerates it under Sound, video and game controllers. The driver's kernel component may sit in the audio stack, while its installed package registers a multimedia device interface. That interface is what Device Manager reads when it builds the device tree.
The distinction matters because the radio itself connects over the network, not over USB. There is no virtual COM port involved in audio routing. The RS-BA1 virtual audio driver is a software-only sound device, and Windows places software audio devices in the same category as physical sound cards. A common installation registers two endpoints, one for playback and one for recording, because the client must both play received audio and capture microphone audio for transmit.
When the driver is present but not active, Device Manager may hide it. Windows only lists non-present devices when Show hidden devices is enabled from the View menu. A driver that failed to start can appear with a warning overlay in the same audio category.
Plain-language version: Windows files the virtual sound card with your real sound cards, because that is what it pretends to be.
Quantified context: device counts, endpoints, and version scope
A working RS-BA1 V2 installation typically produces two audio endpoints, one playback and one recording. Some builds also register a second pair for a separate radio profile or for the remote-control utility that ships alongside the main client. That means a healthy system may show anywhere from two to four ICOM-labeled audio entries.
Version scope matters. RS-BA1 Version 2 is a distinct product line from the earlier Version 1, and the two have different installer packages. The virtual audio driver is bundled with the RS-BA1 installer rather than distributed as a standalone download in most regions. Consult ICOM's official RS-BA1 documentation for the exact supported Windows versions and any driver signing requirements, because those details change between releases and should not be assumed from memory.
Driver signing is a practical threshold. On 64-bit Windows, an unsigned or improperly signed audio driver will not load, and Device Manager will show the device with a Code 52 or similar signature error. That failure does not move the device to another category; it stays in Sound, video and game controllers but refuses to start.
Endpoint naming is a second threshold. Windows may append a number to duplicate names, so two ICOM endpoints can read as "ICOM Virtual Audio" and "ICOM Virtual Audio 2." The numbering is assigned by enumeration order, not by playback versus recording role, so do not rely on the number to tell you which is which. Check the endpoint's advanced properties to confirm the direction.
Edge cases: when the category looks wrong
Several situations make the driver appear elsewhere or nowhere.
The driver installed but the radio is disconnected: the endpoint shows as not present and disappears unless hidden devices are shown. A Windows feature update reset audio class registrations: the endpoint may vanish from the audio category while the driver package remains listed under a software component node. A third-party virtual cable was installed first and claimed the naming: two vendors' virtual audio devices can coexist, and the ICOM entry may be pushed down the list. The installer was run without elevation: the driver package copies files but never registers the audio interface, so nothing appears in any category. Antivirus blocked the driver's service registration: the device node appears with an error code and no audio function.
The counterintuitive detail is that a correctly installed ICOM virtual audio driver can be entirely absent from the visible device tree while still working. If no application has opened the endpoint since boot, Windows may not have instantiated the device node. Opening the RS-BA1 client forces enumeration, and the entry appears. Technicians who check Device Manager before launching the client sometimes conclude the driver is missing when it is merely dormant.
Misconceptions: where people look and why it fails
The most persistent misconception is that the virtual audio driver belongs under Ports (COM and LPT). That category holds serial and parallel interfaces. Audio endpoints never appear there, regardless of vendor. Some ICOM radios do expose a USB serial interface for CAT control, and that device does appear under Ports, which creates the confusion. The serial CAT interface and the virtual audio driver are separate devices in separate categories.
A second misconception is that the driver lives under System devices because it is a kernel-level component. System devices holds buses, controllers, and firmware interfaces. A kernel audio driver still enumerates as an audio endpoint, so it belongs in the audio category.
A third misconception is that the RS-BA1 client itself appears in Device Manager. Application software does not enumerate as a device. Only the driver package does.
A fourth is that reinstalling the client fixes a missing endpoint. The client and the driver are installed by the same package but register independently. Reinstalling the client without reinstalling or repairing the driver can leave the audio endpoint missing.
Comparison of where similar devices land:
| Device type | Device Manager category | Why |
|---|---|---|
| ICOM virtual audio driver | Sound, video and game controllers | Software audio endpoint |
| USB sound card | Sound, video and game controllers | Physical audio endpoint |
| USB CAT/serial interface | Ports (COM and LPT) | Serial class device |
| Network adapter | Network adapters | NDIS class device |
| Virtual COM port driver | Ports (COM and LPT) | Serial class emulation |
| USB audio codec in a radio | Sound, video and game controllers | Audio class device |
The table shows the pattern: category follows function class, not vendor or connection method.
Practical actions: verify, reveal, and repair
Use these steps in order. Stop when the endpoint appears and the client routes audio.
Launch the RS-BA1 V2 client first, then open Device Manager. This forces enumeration of the dormant endpoint. Expand Sound, video and game controllers and look for ICOM or RS-BA1 naming. Enable Show hidden devices from the View menu to reveal non-present entries. Open the endpoint's properties and read the device status. A Code 10 or Code 52 error indicates a start or signature failure, not a wrong category. If nothing appears, run the RS-BA1 installer again and choose repair, or reinstall with administrator rights. Confirm in Windows Sound settings that the ICOM playback and recording endpoints are enabled and set as the client's audio devices.
Red-flag warnings:
Do not disable driver signature enforcement permanently to force an unsigned audio driver to load. Do not delete the driver package from Device Manager while the client is running; you can orphan the audio route mid-session. Do not assume a Code 10 error means the wrong category; it means the driver failed to start. Do not install a third-party virtual audio cable as a workaround before checking whether the ICOM driver registered at all.
Threshold guidance: give enumeration up to about 30 seconds after launching the client before concluding the endpoint is absent. If the driver shows a signature error, resolve signing rather than moving the device between categories, because Device Manager does not let you reassign a device class by hand.
Limitations: what this guidance cannot settle
Category placement is stable across Windows versions, but endpoint naming, installer behavior, and signing requirements vary by RS-BA1 release and Windows build. ICOM's official documentation is the authority for supported operating systems and installation procedure, and it should be consulted for version-specific steps.
This article cannot diagnose a specific installation. A missing endpoint can stem from installer failure, signing policy, antivirus interference, or a corrupted audio stack, and those causes require different fixes. The category answer is reliable; the repair path is not universal.
If the virtual audio driver is present and starts cleanly but the client still produces no audio, the fault lies in the client's audio device selection or the network link, not in Device Manager category placement. Check those layers before reinstalling anything.