Windows 10 handles DualSense controllers largely the same way Windows 11 does, native Bluetooth pairing works, but most non-Steam games still won’t recognize a DualSense properly without DSX translating it into a virtual Xbox controller.
Installing Prerequisites
DSX depends on:
- Microsoft .NET 8.0 Desktop Runtime (x64), from Microsoft’s official download page
- Visual C++ Redistributable (2015–2022)
Windows 10 handles these installers identically to Windows 11, no OS-specific quirks here.
Installing DSX
DSX is distributed through Steam:
- Install DSX from its official Steam page
- Let it install like any other Steam app, Steam handles file placement automatically
- If prompted to install ViGEmBus, follow that prompt
Connecting Your DualSense on Windows 10
Wired: connect via USB-C directly to your PC.
Wireless: hold PS and Create/Share together until the lightbar pulses rapidly, then open Windows 10’s Bluetooth settings specifically:
- Go to Start, then Settings
- Click Devices, then Bluetooth & other devices (this menu path differs slightly from Windows 11, where it’s combined into “Bluetooth & devices”)
- Toggle Bluetooth on if it isn’t already
- Click “Add Bluetooth or other device,” choose Bluetooth, and select “Wireless Controller” from the list
Setting Up Your Profile
- Open DSX, go to Profiles, create a new one
- Choose Xbox 360 for broad compatibility, or DualShock 4 for PlayStation-style prompts in supporting games
- Save and assign it to your controller
- Click Start
Preventing Double Inputs
Install HidHide, hide your physical controller under Devices, and whitelist DSX under Applications. This is identical on Windows 10 and 11.
A Note on Windows 10’s Support Timeline
Worth being aware of if you’re still on Windows 10: Microsoft’s mainstream support for Windows 10 has been winding down, with extended security updates available for those who need more time before upgrading. This doesn’t affect DSX directly, DSX itself doesn’t require ongoing Windows 10-specific updates to keep working, but if you’re troubleshooting an issue that seems tied to Windows itself rather than DSX, keep in mind that Windows 10 receives less active development attention from Microsoft going forward than Windows 11 does, so driver-level quirks are somewhat more likely to go unpatched on the OS side.
Why Steam-Based Installation Simplifies Things Here
Older, standalone-distributed versions of controller mapping software sometimes behaved slightly differently across Windows 10 and 11 due to differences in how each OS handled SmartScreen warnings, file permissions, or driver signing requirements for manually downloaded executables. Since DSX installs through Steam, a lot of that OS-version-dependent friction disappears, Steam’s installation process is essentially identical regardless of which Windows version you’re running, which is part of why this guide’s actual setup steps don’t differ much from the Windows 11 version beyond menu navigation. The days of needing separate, detailed instructions per Windows version for basic installation are largely behind us for Steam-distributed software specifically.
Skip the “1ms Polling Rate” Advice
You’ll see this in a lot of guides regardless of Windows version: a claimed setting to force 1000Hz polling for near-zero latency. This doesn’t exist in DSX, its developer has confirmed the app reads input as fast as your connection allows, no manual override available. If latency matters, a wired connection is the real fix, not a hidden toggle.
Windows 10-Specific Troubleshooting
Bluetooth pairing fails repeatedly: Windows 10’s Bluetooth stack has historically been a bit less consistent than Windows 11’s with newer Bluetooth 5.x controllers. If pairing keeps failing, check Device Manager for your Bluetooth adapter and confirm its driver is current, an outdated Bluetooth driver causes more pairing issues on Windows 10 specifically than most other troubleshooting steps address.
DSX installs but Steam shows an error about missing components: Confirm Windows 10 itself is fully updated through Windows Update, some older Windows 10 builds are missing baseline components that newer Steam apps expect.
Controller works but Windows 10 keeps “forgetting” the Bluetooth pairing between sessions: This shows up more often on Windows 10 than 11, and is often tied to a specific Bluetooth adapter’s driver rather than anything DSX controls. Removing the paired device entirely and re-pairing fresh, rather than just reconnecting, tends to resolve this more reliably than troubleshooting the existing pairing.
If You’re Planning to Upgrade to Windows 11
If you’re on Windows 10 now but considering upgrading, it’s worth knowing your DSX setup transfers over cleanly, Steam reinstalls DSX the same way regardless of Windows version, and your saved profiles (stored at C:\Temp\DualSenseX\) aren’t tied to a specific Windows version either. The main practical difference you’ll notice after upgrading is the Bluetooth settings menu path changing slightly, everything else covered in this guide works identically once you’re on Windows 11.
Getting More Help
If you’re running into detection or connection problems beyond installation itself, our Drivers page covers ViGEmBus and HidHide in more depth, and our Troubleshooting guide covers broader issues that apply across both Windows 10 and 11.
Keeping Your Setup Reliable
A few habits help keep things running smoothly on Windows 10 specifically: check Windows Update periodically rather than assuming it’s staying current automatically, since Windows 10 update cadence has shifted over time and it’s easy to fall behind without noticing. If you use multiple Bluetooth devices alongside your DualSense (headphones, mouse, other controllers), periodically removing ones you no longer use from your paired devices list can help avoid the connection quirks that sometimes show up when Windows 10 is juggling a long list of remembered devices.