Destiny 2 – Solo Mode on Windows 10

Solo Mode on Windows 10 Enabling

Solo mode allows you to load into solo patrol zones, solo strikes, black armory forges, and most traditionally matchmade activities as a fireteam of just one.

Notably, it does not work in Crucible or Gambit. There may be other modes that never load up as well, and you’ll discover this if you’re stuck in the matchmaking / “finding guardians” step for a very long time.

How it Works?

• This script configures Windows Firewall to block a handful of ports used to communicate with Destiny 2 servers. It blocks both inbound (to your computer) and outbound (from your computer) communications on both UDP and TCP protocols.
• The behavior of this script can be replicated by configuring your home router to block the same ports. You can use this router-based blocking method if you feel uncomfortable running this script.
• The behavior of this script is enabled by standard Windows 10 features, and there is no third-party code in use.

Before You Begin

Make sure Windows Firewall / Windows Defender is enabled: https://support.microsoft.com/en-us/help/4028544/windows-10-turn-windows-defender-firewall-on-or-off
Make sure Windows is configured to show file extensions: https://support.microsoft.com/en-us/help/4479981/windows-10-common-file-name-extensions

Creating and Running the Script

1. Create new “text document” on your desktop titled destiny-solo.ps1. Make sure you remove the .txt file extension.
2. Paste the script from the code box below into your new file.
3. Alt-tab back into Destiny 2, or open the game if not already running.
4. Ensure you are in orbit / not in an activity.
5. Alt-tab, right click the script, and select Run with Powershell.
6. The script may ask you to verify permissions; it needs to run as administrator. Press Y or A to accept.
7. The script will run in a blue window and display 4 sets of ports that are now blocked.
8. Pop back over to Destiny 2 and enjoy solo strikes, solo patrols, tower visits, etc.

<# This code requests administrator permissions so that the script can modify your Windows Firewall rules as needed #>
if (!([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] “Administrator”)) { Start-Process powershell.exe “-NoProfile -ExecutionPolicy Bypass -File `”$PSCommandPath`”” -Verb RunAs; exit }

<# These four commands create sets of blocked ports, both inbound and outbound #>
New-NetFirewallRule -DisplayName “Destiny2-Solo-1” -Direction Outbound -LocalPort 1935,3097,3478-3480 -Protocol TCP -Action Block
New-NetFirewallRule -DisplayName “Destiny2-Solo-2” -Direction Outbound -LocalPort 1935,3097,3478-3480 -Protocol UDP -Action Block
New-NetFirewallRule -DisplayName “Destiny2-Solo-3” -Direction Inbound -LocalPort 1935,3097,3478-3480 -Protocol TCP -Action Block
New-NetFirewallRule -DisplayName “Destiny2-Solo-4” -Direction Inbound -LocalPort 1935,3097,3478-3480 -Protocol UDP -Action Block

<# This writes a message and waits for user input to resume the script. In this way, the script pauses while ports are blocked #>
Write-Host “Destiny 2 Solo mode activated. Press Enter to deactivate solo mode.”
Read-Host

<# Once user input is detected, the script resumes and removes the port blocks, restoring things to how they were prior to running #>
Remove-NetFirewallRule -DisplayName “Destiny2-Solo-1”
Remove-NetFirewallRule -DisplayName “Destiny2-Solo-2”
Remove-NetFirewallRule -DisplayName “Destiny2-Solo-3”
Remove-NetFirewallRule -DisplayName “Destiny2-Solo-4”

Troubleshooting

• You won’t be able to login to Destiny 2 if the script is running. Instead, you’ll want to launch the script after you are in orbit.
• If you can’t find an option to Run with Powershell when right clicking on the script, double check that you’ve enabled file extension visibility https://support.microsoft.com/en-us/help/4479981/windows-10-common-file-name-extensions in Windows, and that the file extension on the script is .ps1
• The destiny-solo.ps1 script will stay open until you focus it’s window and press the Enter key. You may need to press Enter a few times. Destiny 2 will stay in solo mode until you close the script in this way.