Windows 11 25H2 bug: Xbox controller randomly loses XInput HID devices — persists after Windows repair

Question

Windows 11 25H2 bug: Xbox controller randomly loses XInput HID devices — persists after Windows repair

MikeZero955 5

I have already submitted a report through Windows Feedback Hub. I am posting here because the issue persists and I want to establish whether other users are affected and whether Microsoft can escalate it to the appropriate Windows device/input-stack team.

During the failure, the Xbox controller remains powered on, but its XInput HID child devices (VID_045E&PID_02FF) disappear even while the parent controller and wireless adapter may still appear present. Restarting Windows temporarily restores input. SFC repairs and an in-place Windows repair did not permanently resolve the issue.

Windows 11 25H2, OS build 26200.9550. The available device and Kernel-PnP logs point to a device-enumeration/input-stack failure, although the root cause is not confirmed.

I tried everything from enabling/disabling and reinstalling the controller and wireless adapter from the device manager and regardless of connecting the controller to USB, the controller stays solid white as if its connected but the input remains unresponsive. The only way to restore again the controller connection is to restart the windows.

Can a Microsoft moderator advise how this can be escalated to the responsible Windows engineering team?

MikeZero955 5 Reputation points

2026-10-15T12:23:38.76+00:00

Hello, I submitted on the feedback hub but unfortunately I haven't received responses yet.

Thanks for clarifying. When the issue occurs, the XInput HID child devices disappear from the list of present devices, rather than simply remaining visible but failing to respond.

The relevant device IDs are:

HID\VID_045E&PID_02FF&IG_00\... — XINPUT-compatible HID device

USB\VID_045E&PID_02FF&IG_00\... — USB Input Device

During the failure, the Xbox controller can remain powered on with a solid white light, and the Xbox Wireless Adapter (USB\VID_045E&PID_02E6) and controller parent device (USB\VID_045E&PID_0B12) have previously remained present. However, the XInput child devices disappear, and the controller stops providing usable input.

I also observed Kernel-PnP Configuration events recording deletion of both PID_02FF child devices. Restarting Windows temporarily restores functionality, but the problem recurs.

The issue has persisted despite SFC repairs and an in-place Windows repair. My Windows version is 11 25H2, OS build 26200.9550.

I haven't established whether the child devices remain as hidden, non-present devices in Device Manager during every occurrence. The confirmed observation is that they disappear from the list of present devices.

Does this pattern suggest a Windows device-enumeration or Xbox input-stack issue, and is there a way to capture diagnostic logs when it happens?
Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-16T13:06:18.2633333+00:00

Hello MikeZero955,

Thanks for replying.

I'm not sure if it will be recorded as an error yet, so it will be hard for us to check what is the event we should be looking for.

Can you please go to "Device manager" > View > Show hidden devices and then reproduce this and see where the child device go?
Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-17T13:05:38.5166667+00:00

Hello MikeZero955,

Just checking in to make sure that you have received my reply. Please let me know if you have any updates.
Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-20T13:09:39.85+00:00

Hello MikeZero955,

It's been a while since I last heard from you. May I know if you still need assistance in this?

Any feedback is appreciated.
MikeZero955 5 Reputation points

2026-10-22T22:02:49.86+00:00

Yes I still need help ! the issue isn't resolved and the feedback hub marks my post as "closed" for an unknown reason and nobody is helping me !
Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-24T13:48:37.44+00:00

Hello MikeZero955,

Can you please refer to my questions above?
Michele Bianchetti 0 Reputation points

2026-11-02T23:11:40.4866667+00:00
I can independently confirm what appears to be the exact same issue, which I've been investigating for several months.

I originally reported it through Windows Feedback Hub on Windows 11 25H2 (build 26200.9168), and it still persists on Windows 11 26H2 (build 26300.9711).

My findings:

After an occasional wireless disconnection, the affected controller reconnects (solid Xbox button) but stops providing input.

The controller disappears from joy.cpl.

The Xbox Wireless Adapter remains functional: a second controller can connect and work normally.

The affected XboxComposite parent device remains present with ProblemCode = 0 and HasProblem = False, but its HID/XInput child device is no longer enumerated.

Connecting the affected controller via USB to the same PC does not restore input. Connecting that exact controller to another PC via USB works immediately.

Restarting the controller's PnP device, restarting the wireless adapter, restarting XboxGipSvc, and rescanning for hardware changes do not recover it.

Only a full Windows reboot restores normal operation.

I've also reproduced the issue with the Xbox Wireless Adapter connected directly to the PC, ruling out USB-over-IP software as a necessary trigger.

This strongly suggests a failure in the Windows Xbox input/device-enumeration stack rather than an issue with the physical controller or wireless adapter, although the exact cause remains unknown.

I can provide before/after PnP device-tree captures and check whether the missing child devices remain visible as hidden/non-present devices.

Is there a specific ETW trace or diagnostic procedure we could use to identify why the HID/XInput child devices are not recreated?

My original Feedback Hub report: https://aka.ms/AA145hw4

I'd be happy to collaborate on further diagnostics.

2 answers

Your answer

MikeZero955 5 Reputation points

2026-10-15T12:23:38.76+00:00

Hello, I submitted on the feedback hub but unfortunately I haven't received responses yet.

Thanks for clarifying. When the issue occurs, the XInput HID child devices disappear from the list of present devices, rather than simply remaining visible but failing to respond.

The relevant device IDs are:

HID\VID_045E&PID_02FF&IG_00\... — XINPUT-compatible HID device

USB\VID_045E&PID_02FF&IG_00\... — USB Input Device

During the failure, the Xbox controller can remain powered on with a solid white light, and the Xbox Wireless Adapter (USB\VID_045E&PID_02E6) and controller parent device (USB\VID_045E&PID_0B12) have previously remained present. However, the XInput child devices disappear, and the controller stops providing usable input.

I also observed Kernel-PnP Configuration events recording deletion of both PID_02FF child devices. Restarting Windows temporarily restores functionality, but the problem recurs.

The issue has persisted despite SFC repairs and an in-place Windows repair. My Windows version is 11 25H2, OS build 26200.9550.

I haven't established whether the child devices remain as hidden, non-present devices in Device Manager during every occurrence. The confirmed observation is that they disappear from the list of present devices.

Does this pattern suggest a Windows device-enumeration or Xbox input-stack issue, and is there a way to capture diagnostic logs when it happens?
Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-16T13:06:18.2633333+00:00

Hello MikeZero955,

Thanks for replying.

I'm not sure if it will be recorded as an error yet, so it will be hard for us to check what is the event we should be looking for.

Can you please go to "Device manager" > View > Show hidden devices and then reproduce this and see where the child device go?
Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-17T13:05:38.5166667+00:00

Hello MikeZero955,

Just checking in to make sure that you have received my reply. Please let me know if you have any updates.
Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-20T13:09:39.85+00:00

Hello MikeZero955,

It's been a while since I last heard from you. May I know if you still need assistance in this?

Any feedback is appreciated.
MikeZero955 5 Reputation points

2026-10-22T22:02:49.86+00:00

Yes I still need help ! the issue isn't resolved and the feedback hub marks my post as "closed" for an unknown reason and nobody is helping me !
Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-24T13:48:37.44+00:00

Hello MikeZero955,

Can you please refer to my questions above?
Michele Bianchetti 0 Reputation points

2026-11-02T23:11:40.4866667+00:00

I can independently confirm what appears to be the exact same issue, which I've been investigating for several months.

I originally reported it through Windows Feedback Hub on Windows 11 25H2 (build 26200.9168), and it still persists on Windows 11 26H2 (build 26300.9711).

My findings:

After an occasional wireless disconnection, the affected controller reconnects (solid Xbox button) but stops providing input.

The controller disappears from joy.cpl.

The Xbox Wireless Adapter remains functional: a second controller can connect and work normally.

The affected XboxComposite parent device remains present with ProblemCode = 0 and HasProblem = False, but its HID/XInput child device is no longer enumerated.

Connecting the affected controller via USB to the same PC does not restore input. Connecting that exact controller to another PC via USB works immediately.

Restarting the controller's PnP device, restarting the wireless adapter, restarting XboxGipSvc, and rescanning for hardware changes do not recover it.

Only a full Windows reboot restores normal operation.

I've also reproduced the issue with the Xbox Wireless Adapter connected directly to the PC, ruling out USB-over-IP software as a necessary trigger.

This strongly suggests a failure in the Windows Xbox input/device-enumeration stack rather than an issue with the physical controller or wireless adapter, although the exact cause remains unknown.

I can provide before/after PnP device-tree captures and check whether the missing child devices remain visible as hidden/non-present devices.

Is there a specific ETW trace or diagnostic procedure we could use to identify why the HID/XInput child devices are not recreated?

My original Feedback Hub report: https://aka.ms/AA145hw4

I'd be happy to collaborate on further diagnostics.

Answer 1

Jair 0

I was having trouble with my GameSir controller failing to connect in Xbox mode on Windows. I discovered that the issue was caused by the "GameInput Redist Service," which was forcing the controller to attempt a connection in Switch mode instead of Xbox mode. I disabled this Windows service; it didn't stop the controller from working—in fact, it allowed it to connect normally in Xbox mode, just as it should.

I’m not sure if this will fix the specific problem you’re experiencing, but it’s what solved the issue for me.

Michele Bianchetti 0 Reputation points

2026-11-03T06:31:37.2733333+00:00

Thanks for sharing your findings!

I suspect this is a different issue, though.

In this case, the affected device is an official Microsoft Xbox Wireless Controller connected through the official Xbox Wireless Adapter.

The controller initially works normally. After an occasional wireless disconnect, it reconnects successfully (solid Xbox button), but Windows no longer enumerates its HID/XInput child device.

The "XboxComposite" parent remains present with no reported PnP errors, while the input device disappears from "joy.cpl". Even connecting the affected controller via USB to the same PC does not restore functionality. Only a full Windows reboot does.

This seems more consistent with a failure in the Xbox GIP/PnP device enumeration path than with an incorrect controller mode.

I haven't ruled out GameInput as a contributing factor, but there's currently no evidence that it causes this specific failure.

Did you observe any missing HID/XInput devices in Device Manager, or was your issue limited to the controller connecting in the wrong mode?

Answer 2

Carl-L 24,580 Microsoft External Staff Moderator

Hello MikeZero955,

Welcome to Microsoft Q&A forum.

This is a public forum, so unfortunately moderators don't have the escalation route directly to the engineering team. The Feedback Hub entry you submitted is actually the most direct way to contact them regarding your issue, since any entries will be delivered directly to them.

Just want to check, may I know if when the issue appears, the XInput HID child device appears in the list of device manager or it is hidden?

I'm waiting for your reply.

Carl-L 24,580 Reputation points Microsoft External Staff Moderator

2026-10-15T10:04:25.44+00:00

Hello MikeZero955,

Just checking in to make sure that you have received my reply. Please let me know if you have any updates.
MikeZero955 5 Reputation points

2026-10-20T18:22:12.5033333+00:00

I submitted to the feedback hub but didn't receive any single reply ...
When the issue occurs, the XInput HID child devices disappear from the list of present devices, rather than simply remaining visible but failing to respond.

The relevant device IDs are:

HID\VID_045E&PID_02FF&IG_00\... — XINPUT-compatible HID device

USB\VID_045E&PID_02FF&IG_00\... — USB Input Device

During the failure, the Xbox controller can remain powered on with a solid white light, and the Xbox Wireless Adapter (USB\VID_045E&PID_02E6) and controller parent device (USB\VID_045E&PID_0B12) have previously remained present. However, the XInput child devices disappear, and the controller stops providing usable input.

I also observed Kernel-PnP Configuration events recording deletion of both PID_02FF child devices. Restarting Windows temporarily restores functionality, but the problem recurs.

The issue has persisted despite SFC repairs and an in-place Windows repair. My Windows version is 11 25H2, OS build 26200.9550.

I haven't established whether the child devices remain as hidden, non-present devices in Device Manager during every occurrence. The confirmed observation is that they disappear from the list of present devices.

Does this pattern suggest a Windows device-enumeration or Xbox input-stack issue, and is there a way to capture diagnostic logs when it happens?