Vb Audio Virtual Cable Install -
Installing VB-Audio Virtual Cable is a straightforward process that effectively turns your computer into a digital patch bay, allowing you to route audio between applications without physical cables. Installation Steps
To ensure a clean setup, follow these sequential instructions: Download the Package : Visit the official VB-Audio website and download the VB-CABLE Driver Extract All Files : Right-click the downloaded ZIP folder and select Extract All
. It is critical to extract the files into a regular folder on your local disk; the installer will not function correctly if run directly from inside the ZIP folder. Run as Administrator Open the extracted folder. VBCABLE_Setup_x64.exe (for 64-bit systems) or VBCABLE_Setup.exe (for 32-bit systems). Right-click the file and select Run as administrator
. This step is mandatory for the driver to register correctly with the Windows kernel. Install the Driver : Click the Install Driver button in the setup window. Mandatory Restart : Once the installation is complete, restart your computer
. Skipping this step is the most common cause of audio issues or the driver not appearing in your sound settings. Post-Installation Verification
After your system reboots, you should verify the installation: Windows Sound Settings (Win + I > System > Sound). tab, you should see CABLE Input tab, you should see CABLE Output Common Use Cases Discord/Streaming
: Route specific game audio or music to Discord by setting the application output to "CABLE Input" and Discord's input device to "CABLE Output". OBS Integration
: Use the virtual cable to separate audio tracks in OBS, allowing you to record game sound while excluding music or voice chat. Combining Sources
: You can use the "Listen to this device" feature in the Windows Sound Control Panel to bridge your physical microphone and the virtual cable, merging them into a single stream for recording apps. VB-Audio Virtual Apps
It was a Tuesday evening, the kind where the rain taps insistently against the windowpane, signaling that it is the perfect weather for staying indoors and fixing the unfixable. For Mark, a budding streamer and amateur podcaster, "fixing the unfixable" usually meant wrestling with audio settings until his eyes crossed.
Mark had a dream: he wanted to play a suspenseful horror game on stream, letting his friends hear the terrifying game audio through his microphone, while simultaneously listening to their voices in his headset, and—here was the kicker—recording a crystal-clear track of just the game audio for a highlight reel later.
If you have ever looked at the Windows Sound Control Panel, you know this is akin to asking a toaster to perform open-heart surgery. Mark’s current setup was a chaotic mess of feedback loops. If he turned on "Stereo Mix," his friends would hear themselves talking, resulting in a cacophony of screeching echoes. If he turned it off, they couldn't hear the game.
"It’s impossible," Mark muttered, staring at the green bars of his volume mixer that jumped erratically with every notification ping.
Then, a notification popped up in his chat from a viewer named AudioWizard99: "You need a virtual cable. Google VB-Audio. It’s the duct tape of the internet."
Mark was skeptical. He liked hardware. He could hold a cable in his hand. A "virtual" cable sounded like something that required a degree in computer science to understand. But desperation is a powerful motivator. He opened his browser and navigated to the VB-Audio Software website.
The Download
The website was utilitarian, looking like a relic from the early 2000s, which strangely gave Mark a sense of security. No flashy ads, no bloatware—just the promise of a driver. He scrolled down past the donation requests (which he bookmarked for later; if this worked, they deserved a coffee) and found the download link.
He clicked the zip file. It downloaded instantly. Mark extracted the folder. Inside, it looked surprisingly sparse. There was a readme file, a license agreement, and a setup application.
He double-clicked VBCABLE_Setup_x64.
A User Account Control window flashed, asking for permission to make changes. Mark hesitated. Installing audio drivers was serious business. If this went wrong, he might be staring at a silent computer for the next three hours. He took a deep breath and clicked "Yes."
The installation window popped up. It was stark. No "Next, Next, Finish" wizard here. Just a simple interface showing the install path and a button that read Install Driver.
Mark hovered the mouse over the button. "Here goes nothing." vb audio virtual cable install
He clicked. The text box below began to populate with lines of code.
Copying files...
Registering DLL...
Creating registry keys...
For a moment, the screen flickered. The audio on his PC cut out—the comforting hum of his computer fans vanishing from his headset. Silence. Panic seized Mark’s chest. Then, a chime. The audio returned.
Installation completed successfully.
Mark clicked "Exit." The program vanished.
The Ghost in the Machine
Mark sat back. He looked at his desktop. Nothing had changed. There were no new icons, no new taskbar applets. Had it done anything?
He right-clicked the speaker icon in his taskbar and selected "Sounds." He navigated to the Playback tab. Usually, this list was short: "Speakers (Realtek)" and "Headset Earphone."
Now, there was a third entry. It was grayed out, sitting stoically among the hardware: CABLE Input (VB-Audio Virtual Cable).
He switched to the Recording tab. There, alongside his physical microphone, sat CABLE Output (VB-Audio Virtual Cable).
"It’s real," Mark whispered. He felt like he had just discovered a secret passage in his own house. The program had indeed installed a "virtual cable." But now came the hard part: wiring the house without burning it down.
The Patchwork
The concept was simple, yet mind-bending. The "CABLE Input" was a speaker. The "CABLE Output" was a microphone. Whatever sound you fed into the Input came out of the Output.
Mark opened his game, Phasmophobia. He went into the game’s audio settings. He left the output device as his default headphones so he could hear, but he wanted the stream to hear it too. This was the bottleneck.
He opened OBS Studio, his streaming software. This was where the magic had to happen.
-
The Desktop Audio: In OBS, under Audio Settings, he saw the "Desktop Audio" device. Usually, this was set to "Default." Mark changed it to CABLE Input (VB-Audio Virtual Cable).
- Logic check: Now, OBS was listening to the cable, not his headphones.
-
The Windows Sound: He went back to the Windows Sound Control Panel. He set the "CABLE Input" as the Default Playback Device.
- Logic check: Now, Windows was playing all computer sounds (game, discord pings, system alerts) into the cable.
-
The Monitor: But wait—if Windows is playing sound into the cable, and OBS is listening to the cable, Mark can’t hear anything. He had just deafened himself.
This was the tripping point. Mark stared at the screen. He needed to duplicate the signal. He needed to hear it, and the stream needed to hear it.
He went back into the Windows Sound Control Panel, to the Playback tab. He right-clicked CABLE Input and looked for a "Listen" tab, but realized that was for inputs. He needed a different approach.
He remembered the "Stereo Mix" trick but applied it to the Virtual Cable. No, that was too messy. Then he remembered the Audio Output Capture in OBS.
He decided to route it backwards.
- Windows Default Output: Set back to his physical Headset.
- Game Output: Set to his physical Headset.
"I’m overcomplicating it," Mark muttered. He deleted the sources in OBS and started fresh. The Desktop Audio: In OBS, under Audio Settings,
- Step 1: He opened the Windows Volume Mixer. He right-clicked the speaker icon and opened "Volume Mixer."
- Step 2: In OBS, he added a new source: Audio Output Capture. He selected CABLE Input (VB-Audio Virtual Cable).
- Step 3: He went to the game settings. He set the game’s audio output device to CABLE Input (VB-Audio Virtual Cable).
Now the game was screaming into the Cable. OBS was listening to the Cable.
But again, the silence. Mark couldn't hear the game.
"The 'Listen' tab!" he snapped his fingers. He went to the Sound Control Panel, Recording tab. He right-clicked CABLE Output. He went to the Listen tab. He checked the box "Listen to this device." Then, under "Playback through this device," he selected his physical Headset.
He hit Apply.
Suddenly, the ghostly whispers of the Phasmophobia menu music whispered into his ears. The audio traveled: Game -> Virtual Cable -> OBS (for the stream) AND (via the Listen tab) -> Mark’s Headset.
It was a digital triangle of audio routing.
The Moment of Truth
Mark hit "Start Streaming." He switched to his phone to check the stream latency. He walked his character into a dark room in the game. A ghost jumped out, screaming.
Mark screamed. The game screamed.
He looked at his phone. The stream had captured the game audio perfectly, crisp and isolated from his voice. His friends in Discord, set to a separate hardware output, were laughing at his reaction.
"Wait," Mark said aloud. He spoke into his mic. "Can you guys hear the game?"
"No," his friend Dave replied over Discord. "We only hear you. We don't hear the scary music."
Mark groaned. He had isolated the game audio so well that Discord couldn't hear it. He wanted his friends to hear the game and the stream to hear the game.
He needed a splitter. Or... another cable.
He went back to the VB-Audio website. There it was: VB-Audio Virtual Cable was free. But Hi-Fi Cable was also available. He briefly considered downloading a second one, but his brain was tired of routing.
There was a simpler way. OBS has a feature called "Monitor and Output."
Mark went into OBS Audio Mixer. He clicked the settings cog on the "Audio Output Capture" (which was his Virtual Cable). He went to Advanced Audio Properties. Under "Audio Monitoring," he changed it from "Monitor Off" to "Monitor and Output."
Then, in Windows Sound Settings, he set his Headset to listen to the OBS Monitor output (which was a separate stream).
Actually, Mark realized the "Listen to this device" trick he did earlier did work for him hearing it. The issue was Discord.
He decided to use the physical mixer he had ignored for months. No, that was too analog.
The Final Configuration
Mark realized he needed to merge the streams. He set the Windows Default Output back to his Headset.
He set the Game Output to CABLE Input.
He went into Discord Voice & Video settings. He set the Input Device to CABLE Output.
Now, Discord was listening to the Virtual Cable.
OBS was also listening to the Virtual Cable.
And Mark? Mark went back to the Sound Control Panel, Recording Tab, right-clicked CABLE Output, went to the Listen tab, and selected his Headset.
It was the ultimate daisy chain.
- Game screams into Cable.
- Discord hears Cable.
- OBS hears Cable.
- Mark hears Cable.
Mark tested it. "Testing, one, two."
His friends heard him. They heard the game music.
He checked the stream. The audio levels were bouncing. He checked his local recording. Game audio on track 1, Microphone on track 2.
It was glorious. It was clean. It was professional.
The Aftermath
Mark leaned back in his chair. The rain was still tapping against the window, but inside, the storm had passed. He looked at the humble little volume control for "CABLE Input" in his taskbar. It sat there, a silent sentinel, bridging the gap between hardware and software.
He had spent three hours installing a driver that took five seconds to set up, and two hours and fifty-five minutes learning how to drive the signal. But now, he was the master of his audio domain.
He typed a message to AudioWizard99 in his chat: "It worked. You are a genius. This cable is invisible, but it holds my whole setup together."
Mark didn't just install a virtual cable that night; he installed a new way of thinking. He realized that in the digital world, you don't need a hardware store to build a bridge—you just need the right driver and a little bit of patience.
And, he noted with a smile, he should probably donate to those French developers. They had earned it.
Step 3: Verify Installation
After restart:
-
Right-click the speaker icon in your taskbar → "Sounds" (or go to Sound Settings).
-
Click the "Playback" tab – you should see:
✅ "CABLE Input" (VB-Audio Virtual Cable)
-
Click the "Recording" tab – you should see:
✅ "CABLE Output" (VB-Audio Virtual Cable)
If both appear, the installation succeeded.
Common Issues & Fixes
| Problem | Solution |
|---------|----------|
| "Driver not signed" error | Disable driver signature enforcement (Windows 10/11) or install in Test Mode. |
| No sound / cable not working | Restart PC; then re-run installer as admin and click "Install Driver" again. |
| Audio crackling or latency | Increase buffer size in app settings or use ASIO via VB-Cable ASIO Bridge. |
| Can't find CABLE Input/Output | Check "Show Disabled Devices" in Sound panel (right-click empty area). |
Part 3: How to Use It (The Setup)
Here is the most common use case: Playing Computer Audio through a Zoom call (or OBS).
1. The Source (Sending Audio)
You want your computer sounds (Music/Game) to go "into" the cable.
- Open your Sound Settings (Playback devices).
- Set "CABLE Input (VB-Audio Virtual Cable)" as your Default Playback Device.
- Result: Your computer is now playing audio into the virtual cable.
2. The Destination (Receiving Audio)
Now, you need Zoom/OBS to "listen" to that cable.
- Open Zoom/OBS settings.
- Go to Audio settings -> Microphone.
- Select "CABLE Output (VB-Audio Virtual Cable)" as your Microphone input.
- Result: Zoom/OBS is now "hearing" the audio you piped in earlier.
3. Listening to Yourself (Monitoring)
If you do the above, you will stop hearing audio through your real speakers. To hear the audio while also sending it to the cable, you have two options: Logic check: Now, OBS was listening to the
- Option A: Don't set the Cable as your "Default Device" globally. Instead, go into the specific app (like Spotify or VLC) and change its output device specifically to the Cable, leaving your speakers as the default.
- Option B: Use the "Listen" tab in Windows Sound Control Panel to "Listen to this device" on the CABLE Output, playing it through your real speakers (this can cause echo loops if not careful).
3. Close All Audio Applications
This is the most common source of "Installation Failed" errors. Before starting:
- Close your web browser (Chrome, Firefox, Edge).
- Close music players (Spotify, iTunes, VLC).
- Close DAWs (Audacity, FL Studio, Ableton, Reaper).
- Close communication apps (Discord, Zoom, Slack, Teams).
Why? Windows locks audio drivers when an app is using them. If the installer tries to replace a locked driver, it will crash.
Before you begin:
- Close all audio applications: Close your web browser, Spotify, Discord, OBS, DAWs (like Ableton or FL Studio), and games. Open files using your microphone or speakers can block the installer.
- Disable antivirus temporarily (if needed): Some aggressive antivirus programs flag kernel-mode drivers as suspicious. VB Audio is safe, but you may need to add an exception or pause real-time protection during the install.
- Right-click and "Run as Administrator": You must have administrative privileges on your PC.
