New DualSense revision (BDM-060) detected through VirtualHere but no input on Windows 11

Hi,

I’m having an issue with a new Sony DualSense controller (BDM-060 revision) in a setup where my older DualSense works correctly.

My streaming setup is:

● Windows 11 gaming PC running Sunshine

● Nvidia Shield running Moonlight

● VirtualHere Server on the Windows PC

● VirtualHere Client on the Nvidia Shield

● DSX installed on the Windows PC

The purpose of VirtualHere in this setup is to use the controller from the Nvidia Shield while streaming through Sunshine/Moonlight, with the controller being available to the Windows PC as if it were locally connected.

Old DualSense

My older DualSense works correctly with this setup.

When using it through the Shield/VirtualHere setup, Windows receives the controller correctly and I can use it with DSX.

New DualSense (BDM-060)

I recently bought a new DualSense, apparently a BDM-060 revision.

The new controller works normally when connected directly to the Windows PC via USB. DSX detects it and the controller itself is therefore working correctly.

The problem only appears when I try to use this new controller through my Nvidia Shield/VirtualHere setup.

VirtualHere/Windows appears to enumerate the controller. Windows identifies it as a DualSense and Steam can sometimes see that a controller is present, but there is no actual controller input.

Most importantly, joy.cpl shows the controller, but no working controller input when tested.

I compared the devices exposed by the old and new controllers in Device Manager. Initially I thought the new controller was missing the HID game-controller interface, but after checking again I confirmed that both controllers expose a HID game-controller interface.

The HID VID/PID is also the same on both controllers:

VID_054C&PID_0CE6

For the new controller, the Hardware IDs shown for the relevant HID device are:

HID\VID_054C&PID_0CE6&REV_0100&MI_03
HID\VID_054C&PID_0CE6&MI_03
HID\VID_054C&UP:0001_U:0005
HID_DEVICE_SYSTEM_GAME
HID_DEVICE_UP:0001_U:0005
HID_DEVICE

Device instance path:

HID\VID_054C&PID_0CE6&MI_03\4&33568155&0&0000

I also found the corresponding USB device/interface:

USB\VID_054C&PID_0CE6&MI_03\3&3a6ad738&1&0003

I tested HidHide as well in case there was some conflict between the HID interfaces, but this made no difference. The new controller was still detected/enumerated but produced no input in joy.cpl.

So, as far as I can tell:

Older DualSense + same Shield/VirtualHere/Windows setup → works

New BDM-060 DualSense + same setup → enumerates, but no input

New BDM-060 connected directly via USB to the Windows PC → works

The particularly strange part is that the old and new controllers appear to use the same Sony VID/PID, and both expose the HID game-controller interface, but they behave differently when used through this setup.

I have also tested Bluetooth separately, but I don’t think that is directly relevant to this issue, since the problem I am trying to diagnose here is specifically the difference between the old and new DualSense hardware when using my VirtualHere setup.

Has anyone tested a BDM-060 DualSense with VirtualHere?

Could something have changed in the USB/HID implementation or descriptors of the newer DualSense hardware revision, despite Sony retaining the same 054C:0CE6 VID/PID?

If useful, I still have both the older working DualSense and the new BDM-060, so I can compare them directly and provide VirtualHere logs, USB/HID descriptors, Device Manager information, or run other tests on both controllers.

Thanks!