Gamepad 0 could not create the requested DualSense USB/audio controller

The attached logs identify Vibepollo 2.0.1 (66e169c325da) and report DualSense USB/audio transport is not installed at host startup, before controller attachment. That message does not distinguish a missing driver from an unavailable or incompatible transport. The installer's “Reusing” message checks interface presence; it does not establish that runtime attachment succeeds. The separate haptics executable is not required for this composite backend.

Could you reproduce on the October 29 nightly and share:

1. The exact host version/commit and fresh startup line beginning DualSense USB/audio transport is, followed by the first controller-attachment error (if any).
2. These read-only PowerShell query results:

Get-CimInstance Win32_SystemDriver -Filter "Name='usbip2_ude'" |
  Select-Object Name, State, Started
Get-CimInstance Win32_PnPEntity -Filter "Service='usbip2_ude'" |
  Select-Object Name, Status, ConfigManagerErrorCode
Get-Item "$env:windir\System32\drivers\usbip2_ude.sys" -ErrorAction SilentlyContinue |
  Select-Object -ExpandProperty VersionInfo |
  Select-Object FileVersion, ProductVersion

Please mention if a query returns nothing. Share only these lines/results, with personal paths or identifiers redacted; another full crash bundle is not needed. This will help separate transport availability from client waveform negotiation without guessing at the cause.

Current version 2.0.2-nightly.d20261029.r.1.a8ef56b07f39

[2026-10-30 01:01:35.434]: Info: Vibepollo virtual gamepad driver is available (up to 16 controllers; offers Xbox Series, Xbox One, DualSense, DualShock 4, Switch Pro, Steam Controller) [2026-10-30 01:01:35.434]: Info: DualSense USB/audio transport is not installed [2026-10-30 01:01:35.434]: Debug: Gamepad usbip_ds5 is unavailable (gamepads.usbip-not-available) [2026-10-30 01:03:39.977]: Error: Couldn't attach composite DualSense USB gamepad 0 [2026-10-30 01:03:39.977]: Error: Gamepad 0 could not create the requested DualSense USB/audio controller

PS C:\Users\xxxx\Downloads> .\test.ps1

Name State Started

usbip2_ude Running True USBip 3.X Emulated Host Controller

Thanks—the October 29 nightly confirmation is useful. One correction to my earlier diagnostic: mixing different objects in the default table could hide the status/version fields, and the hardcoded driver path can miss DriverStore-isolated installations. The “USBip 3.X” display name alone does not identify the installed version or prove it is wrong.

Please run this in PowerShell and paste the counts and named fields. It only reads local device inventory; instance IDs are used locally for matching but are not printed. No reinstall or driver change is requested.

try {
    $nodes = @(Get-CimInstance Win32_PnPEntity `
        -Filter "Service='usbip2_ude'" -ErrorAction Stop)
    "USB/IP PnP entries: $($nodes.Count)"
    $nodes | Format-List Name, Status, ConfigManagerErrorCode

    $drivers = @(Get-CimInstance Win32_PnPSignedDriver -ErrorAction Stop |
        Where-Object { $nodes.DeviceID -contains $_.DeviceID })
    "USB/IP signed driver records: $($drivers.Count)"
    $drivers | Format-List DeviceName, DriverVersion
} catch {
    'USB/IP inventory query failed: HRESULT=0x{0:X8}' -f $_.Exception.HResult
}

This should distinguish reported PnP problems from the installed package version. It still will not prove that Vibepollo can open the interface or complete its compatibility probe, so no root cause or production fix is established yet. Please omit any unexpected personal information.

My bad, I had stock version of USB/IP installed when I was messing with it few months ago, I have removed it, then I run Vibepollo installer again and now everything works flawlessly.

Unfortunately there is no controller audio at any client still, should it be present?