Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Xbox PC Toolbox application is in preview. Please reach out to your Xbox contact if you would like to find out more.
What are the known issues, dependencies and limitations?
Known Issues
Getting an error on the installed required tools screen, when trying to install XboxPC Device Manager, Microsoft.Powershell.* or Microsoft.Windows.Developer
- Work-around: Delete those module's directories from here and try again: %onedrive%/Documents/PowerShell/Modules/
- Cause: OneDrive sometimes interferes with the installation of PowerShell modules.
- Can't fix it since it is OneDrive related. We are exploring alternatives with the PowerShell team for the modules to install in another directory.
Kex_exchange_identification: read: Connection reset. Connection reset by xx.xx.xx.xx port 22. Press any key to continue:
- This is an OpenSSH error. Most common fix is restarting the server, in this case the target device.
- Another option is checking if your device is correctly configured on a private network profile, because if not, the firewall might be closing the connection.
- One more thing can be a corrupted known_hosts file in your local device.
- Cannot fix since it is OpenSSH specific, not related to our code.
winget Microsoft PowerShell 7.5 failed (0x8A150049)
- Work-around: Uninstall PowerShell 7.6 (comes with Visual Studio 2026)
- Cause: It is newer than the one we tried to install, but the install still fails for some reason.
- Will be fixed by public release.
Domain joined target devices are currently limited to password-based authentication for OpenSSH connections instead of the preferred key-based authentication. This only affects Domain Joined, Windows Pro devices.
- This known issue has the workaround and cause explained in a prior section in the document.
- Cannot fix since this is OpenSSH Windows + AAD specific, not related to our code. We are following up with the respective teams. They have some improvements in their roadmap for next year.
Getting an error for Winget commands like Winget search failed to run
- Work-around: A reboot of your target device is recommended. This is also being investigated with the winget team.
Dependencies and limitations
- Internet access is required on both devices during setup
- Devices must share the same local network and be able to ping each other
- Acquisition of the Xbox PC Toolbox application is currently only available in the RETAIL sandbox. Ensure that your devices are in the RETAIL sandbox when trying to download the application from the MS Store on Windows.
- Only devices running Windows 10 or Windows 11, Home or Pro editions are supported
- Physical access to both devices is required during setup
- Administrator level access is required on both devices to execute setup steps
- Azure Active Drectory(AAD) joined target devices are not supported.
How do I find device connection information?
After finalizing the initial pairing process on the target remote device using the Xbox PC Toolbox, the connection details will be displayed in the Testing Device Screen
Alternatively, use a PS terminal on the target device:
# Open a PowerShell 7 terminal
$env:ComputerName # Device name
$env:Username # Username
ipconfig # IP address
How do I verify configuration changes in the devices?
Use Device State Configuration (DSC) and PowerShell to test configurations:
# Open a PowerShell 7 terminal on the DevPC
dsc config test -f "$env:LOCALAPPDATA\XboxPCDeviceManager\config\devPC.dsc.yaml"
# Network (usable on either device)
dsc config test -f "$env:LOCALAPPDATA\XboxPCDeviceManager\config\network.dsc.yaml"
# Open a PowerShell 7 terminal on TargetDevice
dsc config test -f "$env:LOCALAPPDATA\XboxPCDeviceManager\config\targetDevice.dsc.yaml"
Alternatively, check system configuration changes on Windows Setting for each device.
How do I verify and change the sandbox?
Your sandbox configuration should be set to "RETAIL" in order for the tools to function properly, as they will download dependencies that aren't accessible from a sandbox environment. To verify the current configuration, run xblpcsandbox /get on a terminal. If the mode is not set to RETAIL, execute the following command to switch it:
XblPCSandbox.exe RETAIL
How do I select a specific network adapter for the secure channel setup?
During the setup on either device, the Xbox PC Toolbox will provide the option to chose which network adapter to use
How can I report a problem?
From the Xbox PC Toolbox App Title Bar, select the Send Feedback button (to the left of the Minimize button), and then select Report a Problem as shown in the following screenshot:
When reporting issues, please include:
- Operating System version (Windows 10/11 build)
- PowerShell version (
$PSVersionTable) for Xbox Device Management PowerShell Module issues - Network configuration (Wi-Fi/Ethernet, corporate/home)
- Error messages (exact text)
- Steps to reproduce
- Which tool was being used (Xbox PC Toolbox, Xbox Device Management PowerShell Module, wdRemote, or wdEndpoint)
- Preview version you're using
What's the difference between Xbox Device Management PowerShell Module (XDM) and wdRemote/wdEndpoint?
Xbox Device Management PowerShell Module (XDM) sets up secure communication channels. wdRemote/wdEndpoint handle game deployment and launching over those channels.
Do I need both Xbox Device Management PowerShell Module (XDM) and wdRemote/wdEndpoint?
Yes. Xbox Device Management PowerShell Module (XDM) establishes the connection, then wdRemote/wdEndPoint tools perform game deployment and execution.
Why run wdEndpoint as Administrator the first time?
Required to create/store certificates and bind HTTPS URL. Subsequent runs don't need elevation.
Can I deploy multiple games to the same target device?
Yes! Deploy to different directories and launch as needed.
What happens if the network connection drops during deployment?
wdRemote will show an error. Simply retry the deployment command once connectivity is restored.
Is all communication encrypted?
Yes! This preview ensures all communication between development PC and target device is encrypted.
Which tool should I use for what task?
- Use Xbox PC Toolbox for provisioning and acquiring devices remotely including secure channel setup, installing dependencies and device configuration
- Test connectivity with Xbox PC Toolbox before deploying games
- Used XDM-enabled remote sessions and PowerShell remoting to execute commands on the target device
- Use wdRemote/wdEndpoint for game deployment, testing and termination
Can I use these tools with any Windows game?
Yes! These tools work with any Windows executable, not just GDK games.
What network ports do these tools use?
- Xbox Device Management PowerShell Module (XDM): SSH (port 22)
- wdEndpoint: HTTPS (port 4275)