VB-Audio's Forums

Well, that's the error infro from windows log.

Deactivate VB-Virtual-Cable in device manager
- Audacity starts
- SATlive and LevelCheck start
- Windows control for audio starts and shows all devices

Activate VB-Virtual-Cable in device manager
- Audacity does not start
- SATlive and LevelCheck lock during initialization of the IClientCapture Interface
- Windows control for audio takes a long time to start and shows no inputs or outputs ..

Beim Start des Geräts ROOT\MEDIA\0001 ist ein Problem aufgetreten.

Treibername: oem115.inf
Klassen-GUID: {4d36e96c-e325-11ce-bfc1-08002be10318}
Dienst: VBAudioVACMME
Untere Filter:
Obere Filter:
Problem: 0x0
Problemstatus: 0xC00000E5

Strange. never heard about. Let's wait for a second case to get more information.

Hi Vincent

I managed it to work by performing this steps. Please note that my OS uses German language setting, so the translation of labels might not fit exactly.
Not all restarts will be mentioned

- Uninstall again
- Disconnect internet and disabled all protections/scans (I'm just using windows protection/anti virus)
- Restart PC
- Installed VB-virtual-Cable again
- Restart PC
- Problem still occurs
- Connect to internet again
- Run sfc /scannow which finds some problems
- Problem still there
- Entered service configuration
- In windows-audio-service settings I opened the log in page, changed from 'This account to Local System Account and checked Allow data transfer between Service and desktop
- Now I was able to start Audacity, windows audio settup shows all devices, SATlive & LevelCheck start, but trying to start Audio resultet in an error or did not work at.
- Applied the same change to windows-audioendpoint service and a service called waves audio service
- No Change
- Entered Windows-Audio service again, in log-in changed back to This account, select Local Service and set password to 1234
- Restart PC
- HEUREKA all is working as expected
- Restart PC
- All still working
- Modified Settings for windows-audioendpoint service and wave audio service in the same way
- Restart PC
- Still working

What confuses me is that the three services have the local service account selected when I entered them for the first time. Furthermore a problem here should have affected all audio managed by windows, but the problem was clearly related to the vb-virtual-cable

I'm not used to driver programming nor on writing an *.inf file for installation, but my wild guess would be that the vb-cable is assigned to an other account than the other audio drivers....