It doesn't detect my xbox wireless adapter

[jeregon1]

I run the script while having my xbox one controller connected via the 2.4GHz dongle and the script didn't detect the dongle although it did detect the controller.

• It's the official Wireless adapter that came with the controller
• The dongle is plugged directly into the laptop
• I don't know how to check if the Xbox accessories driver is installed but I have the Xbox accessories app and the controller firmware is up to date. And the Device manager entry drivers seem to be up to date

The only entries for Xbox things in the Device manager are:

And this may be of help too:

[socalit]

Thanks for reporting this. I’ve just pushed an updated version of the script (v1.0.1) that expands detection for the Xbox Wireless Adapter.

Some official adapters report different PIDs (like 02E6, 02F9, 091E, etc.), and the old version only checked for two of them. Because of that, the script detected your controller but didn’t recognize the dongle even though it was working.

What to do:

Download the latest release (v1.0.1) here:
https://github.com/socalit/Windows11-Xbox-Controller-Wake/releases/latest

Run Option 2 – Console-style sleep setup again
(You don’t need to redo auto login unless you want to.)

The dongle should now appear correctly in the detection section.

Your controller wake should already work, but this update removes the false warning and officially recognizes more Xbox Wireless Adapter models.

If it still doesn’t detect your dongle, just let me know your Hardware IDs from Device Manager and I’ll add support for your PID in the next update.

[jeregon1]

I've got bad and very good news:

1. After updating the script to v1.0.1 it still doesn't detect my dongle, but checking the Hardware ID it had a known ID:

so it should've been identified in the first place with the previous script version.

2. Looking into the script I found this is presumably the line that checks the existance of a dongle:

wmic path Win32_PnPEntity get DeviceID /format:list 2^>nul ^| findstr /I "VID_045E&PID_02E6 VID_045E&PID_02F9 VID_045E&PID_02FE VID_045E&PID_091E VID_045E&PID_0B05"

I've tried running that line in an Admin Command Prompt but I've got the error Invalid XSL format (or) file name. so then I've just run wmic path Win32_PnPEntity get DeviceID /format:list, I've looked through the long list of device IDs and I've found my dongle succesfully:
DeviceID=USB\VID_045E&PID_02FE\136337

So I've changed that line in the script to match exactly my dongle's deviceID from VID_045E&PID_02FE to VID_045E&PID_02FE and then it's succesfully detected my dongle and applied the tweaks.

I sincerely don't know why all my deviceIDs have & instead of just & so I'm not submitting a PR because I don't know if it's an anomaly or what. Maybe it would be good to check for both styles (with and without the amp; part).

Hope I helped!

[socalit]

Thanks for the detailed write-up. This is a real bug, and you diagnosed it correctly.

What you’re seeing (& showing up as &) is WMIC output escaping. When the older script used wmic ... /format:list, some systems end up returning HTML-escaped strings, which breaks a simple findstr match (and in your case, /format:list is also triggering the “Invalid XSL format” error).

I fixed this in v1.0.2 by:

Avoiding the fragile wmic /format:list path that can throw the XSL error.

Matching the PID values instead of depending on the raw VID_045E&PID_xxxx string, so the & vs & issue no longer matters.

Can you try v1.0.2 and confirm it detects your adapter without any manual edits? If it does, I’ll add a note to the README / release notes crediting your report and explaining the WMIC escaping behavior.

Either way, your findings absolutely helped thank you.

[jeregon1]

So, I tried v1.0.2 in Admin Command Prompt as well as in pwsh. I just ran option 6, which didn't generate any report, but it just wrote on the terminal the whole script i presume, and then option 7 (exit) got stuck in a loop and ended kind of abruptly.

Here's the output for option 6:

============================================================
       UNIVERSAL DONGLE WAKE COMPATIBILITY CHECK
============================================================

This checks what Windows can actually arm for wake.
If your 2.4 GHz dongle is NOT in wake_from_any / wake_programmable,
Windows cannot enable wake for it by script.

A report will be saved as: wake-report.txt

Press any key to run the scan...
$ErrorActionPreference = 'SilentlyContinue'

function Get-WakeList([string]$which) {
  $out =
Invalid Parameters -- try "/?" for help
  if(-not $out) { return @() }
  return $out | Where-Object { $_ -and $_.Trim() -ne "" }
}

function Get-DeviceByName([string]$name) {
  # Prefer Get-PnpDevice (best on Win10/11), fallback to CIM.
  $d = Get-PnpDevice -FriendlyName $name -ErrorAction SilentlyContinue | Select-Object -First 1
  if($d) { return $d }

  $safe = $name.Replace("'","''")
  $d2 = Get-CimInstance Win32_PnPEntity -Filter ("Name='{0}'" -f $safe) -ErrorAction SilentlyContinue | Select-Object -First 1
  return $d2
}

$wakeFromAny = Get-WakeList "wake_from_any"
$wakeProgrammable = Get-WakeList "wake_programmable"
$wakeArmed = Get-WakeList "wake_armed"

if($LogPath) {
  "wake_from_any:" | Out-File -FilePath $LogPath -Encoding UTF8
  $wakeFromAny | Out-File -FilePath $LogPath -Append -Encoding UTF8
  "" | Out-File -FilePath $LogPath -Append -Encoding UTF8
  "wake_programmable:" | Out-File -FilePath $LogPath -Append -Encoding UTF8
  $wakeProgrammable | Out-File -FilePath $LogPath -Append -Encoding UTF8
  "" | Out-File -FilePath $LogPath -Append -Encoding UTF8
  "wake_armed:" | Out-File -FilePath $LogPath -Append -Encoding UTF8
  $wakeArmed | Out-File -FilePath $LogPath -Append -Encoding UTF8
}

Write-Host "============================================================"
Write-Host "                UNIVERSAL WAKE REPORT"
Write-Host "============================================================"
Write-Host ""
Write-Host ("Report saved to: {0}" -f $LogPath)
Write-Host ""

Write-Host "Wake-from-any devices (can be armed):"
if($wakeFromAny.Count -eq 0) { Write-Host "  (none reported)" } else { $wakeFromAny | ForEach-Object { Write-Host ("  - " + $_) } }
Write-Host ""
Write-Host "Wake-programmable devices (driver/firmware may allow):"
if($wakeProgrammable.Count -eq 0) { Write-Host "  (none reported)" } else { $wakeProgrammable | ForEach-Object { Write-Host ("  - " + $_) } }
Write-Host ""
Write-Host "Wake-armed devices (currently enabled):"
if($wakeArmed.Count -eq 0) { Write-Host "  (none armed)" } else { $wakeArmed | ForEach-Object { Write-Host ("  - " + $_) } }

Write-Host ""
Write-Host "Resolved device IDs (flags likely USB dongles):"
Write-Host "  [USB-WAKE-OK] = USB device that Windows says can wake the PC"
Write-Host "  [BT/RADIO]    = Bluetooth stack/radio (wake behavior varies)"
Write-Host "  [OTHER]       = other bus/class device"
Write-Host ""

foreach($n in $wakeFromAny) {
  $d = Get-DeviceByName $n
  if($null -eq $d) {
    Write-Host ("[UNRESOLVED] " + $n)
    continue
  }

  $id = $d.InstanceId
  if(-not $id) { $id = $d.DeviceID }

  $cls = $d.Class
  if(-not $cls) { $cls = $d.PNPClass }

  $tag = "OTHER"
  if($id -like "USB\VID_*") { $tag = "USB-WAKE-OK" }
  elseif($id -like "BTH*" -or $id -like "Bluetooth*") { $tag = "BT/RADIO" }

  Write-Host ("[{0}] {1}" -f $tag, $n)
  if($id)  { Write-Host ("     ID:    {0}" -f $id) }
  if($cls) { Write-Host ("     Class: {0}" -f $cls) }
}

Write-Host ""
Write-Host "------------------------------------------------------------"
Write-Host "Interpretation:"
Write-Host " - If your wireless dongle/receiver does NOT show up under"
Write-Host "   wake_from_any, Windows cannot arm it for wake by script."
Write-Host " - If it DOES show up (especially flagged USB-WAKE-OK), you can"
Write-Host "   enable wake using powercfg -deviceenablewake ""<device name>"""
Write-Host "------------------------------------------------------------"
At C:\Users\jesus\AppData\Local\Temp\wake_check_3118730858.ps1:1 char:23
+ param([string]$LogPath
+                       ~
Missing ')' in function parameter list.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordExcepti
   on
    + FullyQualifiedErrorId : MissingEndParenthesisInFunctionParameterList


[OK] Report saved to: C:\Users\jesus\Downloads\wake-report.txt

Press any key to return to main menu...

And for option 7:

============================================================
          DISABLING MODERN STANDBY (PREFER S3 SLEEP)
============================================================

Applying PlatformAoAcOverride = 0 ...

******  B A T C H   R E C U R S I O N  exceeds STACK limits ******
Recursion Count=299, Stack Usage=90 percent
******       B A T C H   PROCESSING IS   A B O R T E D      ******

Edit:
I've tried taking the option 6 powershell script out of the cmd script into a ps1 script removing the "echo" and ^ characters and it's worked, so there must be some issue I don't understand.

I've tried fixing it with AI and it turns out it only lacked some ^ characters to escape ), & and <,>. I'm going to create a PR for this but I can't assure this will work for everyone.