If you use DSX regularly to configure your PS5 DualSense controller on a Windows PC, opening the application manually every time can become repetitive. Setting it to launch automatically when you sign in to Windows can save a step and make your controller setup easier to manage.
There are a few ways to do this, depending on the DSX version you have installed. Start with the application’s own settings, then try Windows startup options if necessary.
Important: DSX does not need administrator permissions simply because it launches at startup. Only use elevated permissions if a specific feature or documented requirement calls for them.
Method 1: Check DSX’s Built-In Startup Settings
The simplest option is to use a startup setting provided by your installed version of DSX, if one is available.
- Open DSX.
- Go to its settings or preferences.
- Look for an option such as Run at Startup, Launch on Startup, or a similar setting.
- Enable it if available.
- If the application offers a start-minimized option, enable that too if you prefer not to see the main window every time you sign in.
- Restart Windows or sign out and sign back in to test the setting.
The exact names and availability of these options depend on the DSX version. Do not assume every version includes a built-in startup toggle or a system-tray option.
If DSX launches successfully, you can stop here. There is no need to create a second startup entry.
Method 2: Add DSX to the Windows Startup Folder
Windows has a Startup folder that can launch applications when a user signs in. This is a useful alternative when DSX does not offer a built-in startup setting.
Step 1: Open the Startup Folder
Press Win + R to open the Run dialog.
Enter:
shell:startup
Press Enter. Windows opens the Startup folder for your current user account.
Step 2: Create a DSX Shortcut
Find the DSX application shortcut in the Start menu or locate its installed executable.
If you already have a shortcut, you can copy it into the Startup folder. If you have only the executable, create a shortcut to it and place that shortcut in the folder.
Avoid moving the original executable itself.
Step 3: Test the Startup Entry
Sign out of Windows and sign back in, or restart the PC.
Check whether DSX opens automatically. If it does, the setup is complete.
If nothing happens, verify that the shortcut points to the correct executable and that Windows has not disabled the startup entry.
Note: A Startup folder shortcut normally launches the application with the current user’s permissions. It does not automatically bypass User Account Control (UAC) or grant administrator access.
Method 3: Use Windows Task Scheduler
Task Scheduler provides more control over when an application launches. It is useful if a regular startup shortcut fails or if you need to configure a particular launch condition.
Start with a standard task that runs when you sign in. Do not enable elevated permissions unless DSX or a required feature genuinely needs them.
Step 1: Open Task Scheduler
- Open the Windows Start menu.
- Search for Task Scheduler.
- Open the application.
- In the Actions panel, select Create Basic Task.
Step 2: Name the Task
Enter a name such as DSX Startup.
Add a description if you want, then select Next.
Step 3: Choose the Trigger
Select When I log on and continue.
This starts the task when you sign in to Windows, rather than whenever the computer is powered on before anyone logs in.
Step 4: Choose the Action
Select Start a program.
Browse to the DSX executable and select it. If the application requires specific command-line arguments, use the information provided by its documentation rather than guessing.
Continue through the wizard.
Step 5: Finish and Test
Complete the task setup, then sign out and sign back in to Windows.
If DSX launches, the task is working.
If it fails, open Task Scheduler, find your task, and inspect its properties and Last Run Result. Check the executable path before changing permissions.
Should You Select “Run With Highest Privileges”?
Only when necessary.
The option is available in the task’s Properties window under the General tab. Enabling it requests elevated execution for the task, which can increase the security impact of an incorrectly configured task.
Do not use it merely to make DSX start automatically. If a specific feature requires elevation, check the application’s documentation and configure the task accordingly. Depending on the account and security configuration, Windows may still require appropriate credentials or permissions.
How to Make DSX Start Minimized
If DSX launches automatically but its window appears over your desktop, check whether your version provides a Start Minimized or similar option.
If it does, enable it and test the behavior after signing in again.
Not every DSX version supports minimizing to the system tray, and a standard Windows shortcut does not guarantee that an application will start minimized. Avoid adding command-line switches unless they are documented for your installed version.
Troubleshooting DSX Startup Problems
DSX Does Not Launch at Sign-In
Check the startup method you used.
For the Startup folder, open shell:startup and verify that the shortcut is present.
For Task Scheduler, confirm that the task is enabled, the trigger is set to When I log on, and the executable path is correct.
Also check whether you have moved, updated, or reinstalled DSX since creating the startup entry.
Task Scheduler Says the Task Ran, but DSX Does Not Appear
A task can start without producing the visible result you expected.
Check the task’s action and executable path. Make sure you selected the actual application executable rather than an unrelated file or an outdated shortcut.
If DSX is already running in the background, check the system tray and Task Manager before creating additional startup tasks.
Windows Shows a UAC Prompt
A regular startup shortcut does not bypass UAC. If you are using Task Scheduler, check whether you enabled elevated execution unnecessarily.
Do not disable UAC across Windows just to automate DSX. If the application genuinely requires elevation for a particular function, use a documented approach and understand the security implications.
DSX Opens, but the Controller Is Not Detected
Startup automation and controller detection are separate issues.
If DSX opens normally but cannot detect the DualSense, check the USB or Bluetooth connection, the DSX version, and any relevant controller software or drivers.
A startup task cannot repair a broken controller connection.
DSX Starts More Than Once
You may have enabled the application’s own startup option and also created a Startup folder shortcut or scheduled task.
Check the available startup entries and remove the redundant one. Keep a single method unless your setup has a specific reason to use more than one.
The Startup Setting Disappeared After an Update
Application updates can change settings or installation paths. Reopen DSX’s settings and verify whether the startup option still exists.
If you use Task Scheduler or the Startup folder, check that the executable path still points to the installed version.
Do You Need DSX to Run at Startup?
Not necessarily.
If you use the DualSense directly with games that support it, DSX may not need to run at all. If you use DSX for profiles, remapping, or supported virtual-controller features, automatic startup may be convenient.
Choose the simplest setup that works for your games. Starting DSX automatically does not guarantee that every game will use its output or that all controller features will work.
Frequently Asked Questions
Does DSX need administrator rights at startup?
Not in every setup. Whether elevation is needed depends on the application version and the feature being used. Test normal startup first.
Is Task Scheduler better than the Startup folder?
Task Scheduler provides more control over triggers and execution settings. The Startup folder is simpler and may be enough for a normal application launch.
Will DSX start before I sign in to Windows?
The methods in this guide launch DSX at user sign-in. Starting an application before a user logs in is a different configuration and is generally unnecessary for a personal controller setup.
Can DSX start minimized?
That depends on the installed version. Check for a built-in option rather than assuming a generic Windows shortcut can force minimized startup.
What if I no longer want DSX to launch automatically?
Disable the application’s startup setting, remove its shortcut from the Startup folder, or disable the scheduled task you created. You do not need to uninstall DSX to stop it from launching at sign-in.
Final Checklist
Before finishing, confirm that:
- DSX launches successfully when opened manually.
- You have enabled only one startup method.
- The shortcut or task points to the correct executable.
- DSX starts after you sign in to Windows.
- Elevated permissions are enabled only if actually needed.
- Your controller works after DSX launches.
With the startup entry configured and tested, DSX can open automatically whenever you sign in, without requiring you to launch it manually each time.