Sending a power off packet to an Xbox Series Controller

Question

Sending a power off packet to an Xbox Series Controller

magrega 56

Hi! I am makeing a C# pet project with which I want to power off my xbox controller on a certain trigger.

I've discovered that I can use WriteFile to send data to \.\XboxGIP handle from C# code.

I've managed to send a Led command as per doc but I still don't understand why a power off packet doesn't come through.

I am sending these bytes to the handle to dim the LED backlight:

Opening \\.\XboxGIP for manual frame...
Manual Write frame (23B): 
7E-ED-82-C6-8B-DA-00-00-0A-20-00-00-03-00-00-00-00-00-00-00-00-01-05   
WriteFile OK (23B written)

As you can see, I prefix the command with my controller ID otherwise I get Not_Connected error. I send the power off packet the same way as per docs:
7E-ED-82-C6-8B-DA-00-00-05-20-00-00-01-00-00-00-00-00-00-00-04-00-00

I tried moving the 04 byte around but it made no difference. Could you at least confirm that it is possible to do with the \.\XboxGIP handle to power off a controller?

Opening \\.\XboxGIP for manual frame...
  Manual Write frame (23B): 7E-ED-82-C6-8B-DA-00-00-05-20-00-00-01-00-00-00-00-00-00-00-01-00-00
  WriteFile FAILED (error 87)
Failed to send manual frame to \\.\XboxGIP.

Is it supported? How can I do this any other way?

I managed to send 05 20 01 01 04 over a usb cable and the controller turned off so I assume that xboxgip.sys does allow that. Am I just not sending the correct message?

0 comments

2 answers

Your answer

Answer 1

Jack Dang (WICLOUD CORPORATION) 16,515 Microsoft External Staff Moderator

Hi @magrega ,

Thanks for reaching out.

The issue looks to be the packet format you are sending to \\.\XboxGIP.

According to the GIP USB Set Device State documentation, the command format is:

05 20 <sequence> 01 04

The 04 value for Off is correct, but the buffer you posted does not match this command format. It is padded to 23 bytes, and it uses 00 as the sequence id, which is reserved. That is the most likely reason for ERROR_INVALID_PARAMETER (87).

So the direct answer is:

Yes, 04 is the correct device state value for Off.
No, the 23-byte buffer you posted does not match the documented command.
If you want to test the raw command, use a non-zero sequence value, for example 05 20 01 01 04.

There is also an important limitation here: there is no documented public API that guarantees powering off the controller through \\.\XboxGIP.

The closest official API reference is IGameInputDevice::PowerOff(), which states that the method was never implemented, was removed in GameInput v1, and has no equivalent in the current API surface.

So even if the controller supports the Off command at the protocol level, there is no supported Windows API that guarantees user-mode writes to \\.\XboxGIP will work for this scenario.

Hope this helps! If my answer was useful to you, I would greatly appreciate it if you could follow the instructions here so others with the same problem can benefit as well.

magrega 56 Reputation points

2026-04-10T10:54:56.9166667+00:00

The raw packet form is not sent to the .\Xboxgip. It's wrapped in a certain frame which I don't understand fully yet. The LED command worked only when sent in a manner I specified in the post. Raw as-is commands work only when sent with Bus Hound directly to the controller plugged in with a usb cable
Jack Dang (WICLOUD CORPORATION) 16,515 Reputation points Microsoft External Staff Moderator

2026-04-13T04:23:15.5966667+00:00
Hi @magrega ,

Thanks for the clarification.

If the raw 05 20 01 01 04 packet only works when sent directly over USB with Bus Hound, but the LED command only works through your wrapped \\.\XboxGIP format, then those are clearly two different transport paths.

So I would not expect the raw USB packet to work unchanged through \\.\XboxGIP. The 04 value itself does not look like the problem. The more likely issue is one of these:

the outer \\.\XboxGIP wrapper format is not correct for the power-off command,

the outer frame has additional length, sequence, or metadata requirements that differ from the LED command, or

the regular \\.\XboxGIP write path simply does not allow this operation even though the device supports it over raw USB.

The ERROR_INVALID_PARAMETER (87) result is also more consistent with an invalid \\.\XboxGIP frame than with an invalid Off opcode. Since your LED command works only with the wrapped format, the power-off command would likely need that same wrapper structure, with the embedded payload changed to 05 20 <non-zero sequence> 01 04.

As an additional data point, there is some community reverse-engineering here: https://github.com/Leclowndu93150/xbpoweroff. That research suggests xboxgip.sys may handle LED control and power-off differently, with LED control going through the regular \\.\XboxGIP write path and power-off using a separate undocumented administrative control path instead. This is not official Microsoft documentation, and I cannot validate or recommend it as a supported solution, but it does line up with what you are seeing.

This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watchout for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

From the supported API side, IGameInputDevice::PowerOff() was never implemented, was removed in GameInput v1, and has no replacement. So there is still no documented or supported Windows API that guarantees controller power-off through \\.\XboxGIP.

Answer 2

Powering off an Xbox Series controller from an app is not supported through any documented or supported API in the Microsoft gaming stack.

Specifically:

The legacy GameInput IGameInputDevice::PowerOff method was never implemented (always returned E_NOTIMPL) and was removed in GameInput v1. The documentation explicitly states that no replacement exists in the current API surface, so there is no supported way to programmatically power off a controller via GameInput.
The behavior observed by reverse‑engineering packets to \\.XboxGIP or over USB is not documented or guaranteed, and there is no official contract that such packets must be accepted or continue to work. That path is not a supported mechanism for powering off the controller.

So, while it may be possible to discover packets that appear to turn off the controller in some configurations, doing so relies on undocumented behavior and is outside the supported API surface. From the platform perspective, sending a “power off” command to an Xbox Series controller from an app is not supported.

References:

IGameInputDevice::PowerOff

Share via

Sending a power off packet to an Xbox Series Controller

2 answers

Your answer