#Double virtual Xbox controllers

303 messages · Page 1 of 1 (latest)

proven wharf
#

Hello

#

@south magnet @dry prism

#

Nef, pop is experiencing an issue with virtual xbox controllers being duplicated when created via DSX, but i dont know if it's from vPad entierly since he says it also happens with DSX v2 using ViGEm driver.

If you can, guide him how to create debug log files so that you could investigate this please

#

I've also expierenced this in v3.1, but cant replicate

south magnet
#

Are there really 2 virtual x360 devices in device manager?

proven wharf
#

even if he reinstalls, reboots, it keeps creating double vXbox controllers

south magnet
#

That was not my question 😉

tame mural
#

Yeah it adds an extra device in device manager if I got what that poor thing told me (been suffuring it for a while)

dry prism
south magnet
#

Screenshots pls

south magnet
proven wharf
#

@dry prism Device Manager -> View (top) -> Devices by Connection -> Nefarius Virtual Gamepad Emulation Bus G2 -> unpack all and screenshot

south magnet
#

Ideally both cases, DSX v2 and v3

dry prism
#

ok just one moment

south magnet
#

You get two HTrollFace

dry prism
proven wharf
#

So it’s only one

south magnet
# dry prism

The very last node "Xbox HID Controller" is looking weird, right click properties, share all tabs. That looks like the wrong driver

proven wharf
#

Oh dsxAwk

dry prism
south magnet
#

All tabs

dry prism
south magnet
#

I have never seen this before, no clue what that is and where it came from, but 99% sure that is the cause of your problems

#

Get rid of it and it will be fine

#

Post the file C:\Windows\INF\oem16.inf here as attachment

proven wharf
#

“Uninstall device” right?

south magnet
#

Usually but I wonder if that works

proven wharf
#

Hmm from march 28th

south magnet
#

Share the file first I'd say

proven wharf
#

This “driver”

south magnet
#

Provider and Manufacturer is "Xbox", that could be an official Microsoft division although IDK if they use something else than Microsoft for their in house driver packages

dry prism
south magnet
#

Maybe it came with another MS tool or via Windows Update

tame mural
#

Wouldn't everyone have gotten it if so ?

proven wharf
#

Windows 24H2 I heard broke so much stuff

south magnet
#

This is very new and looks official, probably came via Windows Update

%ManufacturerName% = XboxGameControllerDriver, NTamd64.10.0...22000 ; amd64/arm64, Windows 11 21H2
#

So yeah, not "my" bug, folks 😉

proven wharf
#

I need to see if I have the same

#

Sec

south magnet
#

Games now probably "see" the XInput device exposed by xusb22.sys and by xinputhid.sys so from your system's point of view you have 2 xbox controllers that originate from the same device

#

I guess this was a compatibility effort for Win11, games and old controllers but with harsh side-effects

proven wharf
#

Well that’s annoying, you’ll have to adjust for this?

tame mural
south magnet
#

No? What am I supposed to do about it KEKW

tame mural
#

Definitely not the same

south magnet
#

These names are auto generated

#

And system unique

#

You need to check the INF name in your device in device manager

proven wharf
#

You can check what file from this

image0.jpg
tame mural
south magnet
tame mural
#

My events for this "device" are empty anyway, without infos

proven wharf
#

Zzzz I’m stuck here cuz of this shitty internet lol

IMG_3537.jpg
south magnet
#

@dry prism also pls toss the file C:\Windows\System32\drivers\XboxGameController.sys or zip it if Discord refuses

proven wharf
#

i seem to be normal here

image.png
south magnet
#

It is

dry prism
south magnet
#

Claims to be from Microsoft

image.png
proven wharf
#

it had an original file name

south magnet
#

Someone forgot to change the DDK sample project name tho hehe

proven wharf
#

xbgc.sys

south magnet
#

That doesn't mean much, that is just a string in the resource file

proven wharf
#

oh i know, just a clue for investigation

dry prism
#

so should i for now leave everything alone or do you want me to remove anything?

south magnet
#

You can right click Update driver on the device if it offers you that and I can guide you through a workaround for the time being

#

Share a screenshot what you see each step and I tell you what to click

dry prism
#

this?

proven wharf
#

Update Driver -> Browse My Computer for Drivers -> Let me Pick from available drivers -> uncheck show compatible drivers -> this is at least mine

image.png
south magnet
proven wharf
#

Standard System Devices -> HID Game Controller

#

then i think redo emulation via DSX

#

go Native then back to Xbox to see what happens in Device Manager

#

as before, it should look like this

image.png
south magnet
dry prism
#

Thanks guys you are the best, I think its fixed

proven wharf
#

After selecting middle one, and reboot, pop claiming it's now operating as normal

south magnet
#

😉

dry prism
#

any idea what caused that issue as i dont remember doing anything except updating windows

south magnet
#

Probably came via Windows Update, new 200 IQ move from Microsoft

#

There's an option to disallow pulling drivers from Windows Update but IDK where in their fucked up UI it would be or if they haven't broken that since

dry prism
#

maybe that?

#

i found a guide with several suggestions

south magnet
#

Yes

dry prism
#

Thank you again, learn something new everyday

proven wharf
#

I would still keep it as automatic as these things that happen are quite rare and can be identifiable/fixed

#

@south magnet I think it could be a good idea to add some detection for this if Microsoft tries replacing old working stuff with new shit

#

At least to identify

tame mural
#

Could also check for "overclock" drivers and say " nuh huh, you're on your own buddy "

south magnet
proven wharf
#

Idk, you know more of how these devices operate and how they’re detected

south magnet
#

Well what do you expect is the question, to have a mechanism to notify the user or to silently change it automatically?

proven wharf
#

Hmm

#

I have a question, if the x360 is replaced with vXbox One emulation, do we need to worry about this as well?

south magnet
#

Nope

proven wharf
#

Like is Xbox one controllers the same behavior in the OS?

south magnet
#

As of the time of writing they're fine

proven wharf
#

Hmm, well the best course of action is replacing x360 with One and call it a day

#

More modern I guess

south magnet
#

For most, yes. Leaving the x360 option in mainly for old ass weird games that 0.5% of the people have that do need an x360 for some reason. But othwerwise I agree

tame mural
#

Some games don't support Xbox One controllers tho, or it just Xbox One controller features they don't ?

south magnet
#

Technically every game that is coded right (haha, see where the problems hide?) has no clue if you use an x360 or XBONE, should all work the same

#

Exceptions are engines that are "too smart" and deliberatly look for specific controller devices properties instead of just letting an API do the work

proven wharf
#

Hmm then definitely not a replace, but an addition

south magnet
#

Also ofc. games that support the trigger vibrations need to take into account that that feature only exists on XBONE and forward

tame mural
#

Xbox emu could just have a subsection then (like vDS Audio or Audioless)

south magnet
proven wharf
#

Am waiting on you to add Xbox One emulation dsxGunRobbery

south magnet
#

I thought I delegated that to @tame mural HTrollFace

tame mural
proven wharf
tame mural
#

I mean main subsection instead of a drop-down

south magnet
#

Once it exists XBONE emu can be made the new default

#

They can coexist so there is no need to force a complete replacement

proven wharf
#

Also I think you should let me know when you plan on doing an update for vPad because the code for vDS with audio looks for a higher version than the current public one, if not ready, can cause issues for users

south magnet
#

Yes that is not good, I plan to add a feature flag API to the SDK so DSX doesn't need to fiddle with version numbers

proven wharf
#

That would be even better

south magnet
#

The next update is gonna be huge again, am afraid pepe_naruto

proven wharf
#

Basically like an output report

#

Smart

south magnet
#

I've solved similar challenges for customers in the past

proven wharf
#

Once I’m back in the states, can focus back again on DSX

#

We need to step it up tbh

south magnet
#

I also have more good news about that but everything in due time aPES_SaxophoneSunglasses

tame mural
south magnet
proven wharf
#

Ah that firmware being old

south magnet
#

Last time we tried to "fix" it everything got worse so this needs its own careful implementation, tests and rollout

#

Cuz just changing some numbers is not enough to satisfy the FW changes

proven wharf
south magnet
proven wharf
#

back to this topic again

#

it seems Microsoft is at fault here regarding this new weird driver

#

some users are even facing BSOD because of it

tame mural
south magnet
#

When the Intern gets push permissions to Windows Update

#

I did similar oopsies too but almost 10 years ago and am one guy and not a trillion dollar company

image.png
#

Someone recycled an old project, even forgot to rename some stuff, probably only tested it on one machine with one controller and in the spirit of "agile" published it as "good enough"

tame mural
south magnet
#

Looking through the INF again I believe that the X360 controllers are included was an unintentional side-effect due to this line

; XInputHid
%DeviceDescriptionHid% = XInputHid,HID\VID_045E&UP:0001_U:0005

This ID match is way too broad, it matches every HID device with a Microsoft Vendor Id.... So I predict more and more crash reports will pop up soon

proven wharf
#

fokin microsoft

#

i had GPT inspect both inf and sys files

south magnet
#

Since this driver is apparently made for some USB device compatibility but it gets loaded onto Bluetooth devices too because of that line

proven wharf
#

it told me that the .inf file was an invidia gpu driver lol

south magnet
#

I mean.... why even waste the time 😅

proven wharf
#

well to investigate

south magnet
#

What was your promt/question?

proven wharf
tame mural
#

I'll rather ask *CatGPT about this cursed driver 😉 (might have insights)

south magnet
#

So it didn't even read it but just did a search with the (randomly generated) filename PES2_Derp

proven wharf
#

oh wotfok

#

i thought it inspected it

south magnet
#

Assuming you actually uploaded Pops file and not your own

#

You uploaded the wrong file, didn't you?

proven wharf
#

it did inspect the .sys file tho

image.png
proven wharf
south magnet
#

I highly doubt ChatGPT comes with a disassembler so any binary you give it is just random results based on some loose string matches

proven wharf
#

after he did the driver remove, and using device cleanup, he's actually back to normal now

south magnet
#

Am not surprised

proven wharf
#

force uninstalling oem16.inf

south magnet
#

This is le epic fail

HID\VID_045E&UP:0001_U:0005
proven wharf
#

i swear these devs

#

and then we get blamed for these issues

south magnet
#

But sure, ISVs are the problem with driver code quality KEKW

south magnet
proven wharf
#

well at least we got to the bottom of it

proven wharf
#

well we come to you because you have the most experience in these situations

#

or insight

south magnet
#

I am just teasing, I found this adventure quite interesting

#

Windows Update ThisIsFine

proven wharf
#

it's weird that not everyone is affected

#

in those threads by users, some have said going to windows beta solved their issue

south magnet
#

There has to be a reason for drivers getting pulled by WU, typically if a device runs fine with the stock drivers, it doesn't always conclude that "newer" means "more compatible"

proven wharf
#

hopefully they spotted the issue early on, and stopped pushing that driver update

south magnet
#

So maybe using some Xbox affiliated app triggered it

#

Yeah also maybe they already got the telemetry and rolled it back

tame mural
#

But isn't it like old ? Pop getting it only recently is even odder

proven wharf
#

which .inf file did you inspect nef? the one i downloaded from the previous chat above by pop is nvidia when inspecting it

south magnet
#

The driver creation and signing dates are not proof when it was actually published

south magnet
proven wharf
#

fokin AI taking over

south magnet
south magnet
#

Why am I always right

tame mural
#

#BadBot astrosad

proven wharf
#

okay waiting for GPT to inspect

#

any reason this can happen?

#

pop has this, even after doing device cleanup, these entries still show up @south magnet

tame mural
#

His install is still cursed ? 😮

dry prism
#

Im thinking i should reinstall OS

proven wharf
#

it's always the best option

#

its why windows is so shit

#

always needs a re-install every 6 months or so

#

no more than a year, or you will be running in circles

tame mural
#

So like Android then ?

south magnet
proven wharf
#

Device Cleanup tool

south magnet
#

Then do it properly? Topkek IDK always worked for me

dry prism
#

i deleted them

Screenshot_2025-05-17_163012.png
proven wharf
#

i mean i never saw ghost entries in device manager

#

but if normal, then oh well

south magnet
proven wharf
#

ohh these are hidden

south magnet
proven wharf
#

wtf i never knew there was a hidden option for device manager

south magnet
#

Always has been

proven wharf
#

ah just saw it

south magnet
#

DevMan also doesn't show all devices that exist for a machine

dry prism
south magnet
#

Delete them, done. Ez gg

#

Everything under USB and HID enumerators

proven wharf
#

these enttries look normal

#

same on my laptop/PC

#

so can be ignored

#

@dry prism You're back to normal operations, and can close this case

south magnet
#

It doesn't matter, those are all "currently absent" devices

#

Leave them or delete them, doesn't matter

proven wharf
#

then back to blaming you dsxTopkek

south magnet
#

Y'all are incompetent and don't know watcha doing, stop fiddling with tools you don't understand and everything is fine thumbsup TrollFace

proven wharf
#

okay as you said, microsoft is noob, and we gonna have more cases of this sooner or later

image.png
tame mural
south magnet
#

Shock and horror, GPT says the same things as me 7049pepesnogee

tame mural
#

Yeah, now that is worrying

dry prism
#

i will see if they come back again and keep you updated

south magnet
#

They will and that's fine. That is how Windows works. Nothing to worry here

#

Absent devices will remain in the registry. It. Is. Normal.

tame mural
#

This won't be complicated to explain users like at all /s

south magnet
tame mural
proven wharf
#

its simple to fix, but have to guide the user which sucks

tame mural
#

Glad that ticket is here then

south magnet
#

Make guide. Link it to all future cases. Done

tame mural
#

Yep

proven wharf
#

Steps to fix

  1. Open terminal as administrator
  2. List drivers with this command: pnputil /enum-drivers > drivers.txt
  3. Type pwd and navigate to that path to find the text file. You can just copy paste the response into the file explorer.
  4. Open the driver.txt file and search for 1.14.20.740 (this is problematic driver version). Take note of the driver file name. For me it was oem72.inf, for other user it was oem74.inf, for you it may be different.
  5. Uninstall the driver by running the command: pnputil /delete-driver driverName.inf /uninstall /force, replacing the "driverName.inf" with what you got from the previous step
  6. Restart computer and reconnect your Xbox controller. It should now work.
tame mural
#

Well, Pali, your call to lock it down whenever you feel like it 6484peeposalute

proven wharf
#

the problem is the user identifying the issue, like for pop it was semi-working

south magnet
#

Do we still have someone who has exported the complete driver package before you nuked it?

proven wharf
#

Nope it was nuked lol

#

but i think, it can be reinstalled again and driver manually picked for vXbox?

south magnet
#

Well we don't know why it landed on the system to begin with so.... PES2_Shrug

#

Easiest thing would be to add it to legacinator but without the driver files to actually test I wouldn't just make a blind update release

proven wharf
#

i can install it

image.png
#

ah digital signature issue

image.png
south magnet
#

No you can not 🙂

proven wharf
#

well that's annoying

south magnet
#

Welp

south magnet
#

Your call

dry prism
#

I didn't disable that after what Pali said

tame mural
#

Good luck walking down the memory lane for the "repeat whatever caused it" Pop...

south magnet
#

There is also a "search for new driver via Windows Update" option you can choose on each device but it feels to never really reliably do anything

dry prism
#

I have no Idea except it was probably an update within a few weeks ago or so when I noticed it happening

tame mural
south magnet
# dry prism

Go through this and choose all the topmost options IIRC

tame mural
dry prism
south magnet
#

Not this device, leave that alone

#

Wrong device

dry prism
south magnet
#

KB5058486 is at fault

proven wharf
#

Noobs

south magnet
#

Windows 11 Insider Preview Build 26120.4151 (Beta Channel)

tame mural
#

Better late than never to address it...

#

Fonckin MS

south magnet
#

Well it's not really addressed. It's acknowledged KEKW

#

I came across KB5058486 on accident today cuz it got installed last night on my Dev VM too and since then it boot looped with UNSUPPORTED PROCESSOR error. Had to uninstall it

tame mural
#

Oof

proven wharf
#

Make an announcement in the server with everyone tag plz

#

So DSX isn’t blamed by noob stuff

tame mural
#

Ok, copy pasting the link and pic ?

proven wharf
#

Well no, needs to be more descriptive about how it can effect

#

@south magnet was telling him to post it since he knows the technical stuff

tame mural
#

As you wish 😊

south magnet
#

Who, what

#

Sry, am confused, who does what

tame mural
#

I think Pali wants you to do a tldr PSA to everyone about it

south magnet
#

Oh, right, can do that

south magnet
#

I can't find this driver via searching the public MS update catalogue, so I assume the package was really part of the updated package itself, not pulled by the "new device detected" mechanism

#

This could in turn mean that MS can pull and fix it easier; if it is not in the "general" update pool, only Windows Insiders in that particular time frame got it installed and if they publish a hotfix or pull that update, you can't grab it even on accident anymore

proven wharf
south magnet
#

We need another insider that recently ruined their machine TrollFace