Problem on win11 23H2

VB-Cable A & B, HIFI-Cable, ASIO Bridge
Post Reply
TomyN
Posts: 6
Joined: Tue Jan 13, 2026 8:33 pm

Problem on win11 23H2

Post by TomyN »

Hi,

I've been using vb-virtual cable for a long time without any problem.
Now I tried to use it on my new laptop running win11 23H2, where it locks applications when trying to start capture (via wsaapi or waveInXX functions).
The error log reports
0001 Exception Thread: ID=12600; Name=MAIN; Wait Chain=Blocked waiting for ALPC owned by thread [ $0000 / 0 ] -> thread -> ALPC "\RPC Control\AudioClientRpc" -> process: [ $0EF0 / 3824 ] is PID only;

This happens only when the virtual cable is selected as I/O device.
The installation check reports outdated version of either vb-cable or of the checker.
I tried uninstall /reinstall for serveral times without any success.
Vincent Burel
Site Admin
Posts: 2207
Joined: Sun Jan 17, 2010 12:01 pm

Re: Problem on win11 23H2

Post by Vincent Burel »

did you install the latest VB-CABLE package ?

New Package: VBCABLE_Driver_Pack45.zip
(1.29 MB - OCT 2024 / XP to WIN11 32/64 bits/Arm64)

www.vb-cable.com
TomyN
Posts: 6
Joined: Tue Jan 13, 2026 8:33 pm

Re: Problem on win11 23H2

Post by TomyN »

Hi,
I used the installer from the website, which I've downloaded yesterday.

Filecreation (as reported by windows) and version
vbaudio_cable64_win10.sys 08.10.2024 - 10.0.10011.16384
Vincent Burel
Site Admin
Posts: 2207
Joined: Sun Jan 17, 2010 12:01 pm

Re: Problem on win11 23H2

Post by Vincent Burel »

ok, there is no problem with this package and win11.
Could you post a screenshot of your Windows Device Manager, section "Audio, Video and Game Controllers" ?
TomyN
Posts: 6
Joined: Tue Jan 13, 2026 8:33 pm

Re: Problem on win11 23H2

Post by TomyN »

44pnbM80v00FJOva.png
44pnbM80v00FJOva.png (43.7 KiB) Viewed 28 times
TomyN
Posts: 6
Joined: Tue Jan 13, 2026 8:33 pm

Re: Problem on win11 23H2

Post by TomyN »

Did some more Tests:
- Seems to work when accessed via ASIO4ALL / ASIO

Because we're facing the problem with our products, I tried audacity.
With vb-virtual-cable installed, audacitry freezes in the welcome screen, after removing vb-virtual-cable it stars without any problem.
Vincent Burel
Site Admin
Posts: 2207
Joined: Sun Jan 17, 2010 12:01 pm

Re: Problem on win11 23H2

Post by Vincent Burel »

All seems to be ok in your device manager.
we have no problem reported with audacity too (that is used for our validation test btw).

Generally speaking we have no case report of application freezing with VB-CABLE, you may give more screenshot to explain the context more precisely (to le me see what's happening exactly).
TomyN
Posts: 6
Joined: Tue Jan 13, 2026 8:33 pm

Re: Problem on win11 23H2

Post by TomyN »

- Removed VB-Virtual-Cable completely ( uninstaller + device manager)
- Restartet pc
- Start Audacity -> works
- Exit Audacity
- Run VB-Virtual-Cable Installer (x64) (reports. OS: win10 in installer window, but machine runs win11).
- Installer shows success message + opens VB website
- Restart pc
- Start Audacity
- Audacity Intro window (just showing the icon and the audacitiy string) stays ..... and stays .... and stays ......
TomyN
Posts: 6
Joined: Tue Jan 13, 2026 8:33 pm

Re: Problem on win11 23H2

Post by TomyN »

Beschreibung
A problem caused this program to stop interacting with Windows.
Pfad der fehlerhaften Anwendung: C:\Program Files\Audacity\Audacity.exe

Problemsignatur
Problemereignisame: AppHangXProcB1
Application Name: Audacity.exe
Application Version: 3.7.7.0
Application Timestamp: 693aece5
Hang Signature: 79d6
Hang Type: 134217856
Waiting on Application Name: svchost.exe:AudioClientRpc
Waiting on Application Version: 0.0.0.0
Betriebsystemversion: 10.0.22631.2.0.0.256.48
Gebietsschema-ID: 1031
Additional Hang Signature 1: 79d6322b4e7ffbf57a4052f1f2c12c91
Additional Hang Signature 2: 5341
Additional Hang Signature 3: 5341c2ece500fb1f1e7b48e9a1e4af68
Additional Hang Signature 4: 79d6
Additional Hang Signature 5: 79d6322b4e7ffbf57a4052f1f2c12c91
Additional Hang Signature 6: 5341
Additional Hang Signature 7: 5341c2ece500fb1f1e7b48e9a1e4af68

Post Reply