Windows CLI installation command returns 404

[Abdallah-Alwarawreh]

Describe the bug
the installation script for windows gives 404

To Reproduce
run the command in the docs
powershell -Command "irm https://get.daytona.io/windows | iex"
and it would return

PS C:\Users\user\Documents\testing> irm https://get.daytona.io/windows | iex
irm : The remote server returned an error: (404) Not Found.
At line:1 char:1
+ irm https://get.daytona.io/windows | iex
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Going to the "https://get.daytona.io/windows" link gives a 404

[anandmishrapersonal]

The issue seems to be caused by an invalid Windows install URL in the documentation.

The command:

powershell -Command "irm https://get.daytona.io/windows | iex"

fails because https://get.daytona.io/windows returns 404 Not Found (confirmed both via PowerShell and browser). This looks like an outdated or incorrect endpoint rather than a client-side issue.

Workaround (until fixed):
Install the Daytona CLI on Windows by downloading the binary directly from the official download endpoint and adding it to PATH.

$dir = "$Env:LOCALAPPDATA\daytona\bin"
New-Item -ItemType Directory -Force -Path $dir | Out-Null
Invoke-WebRequest -Uri "https://download.daytona.io/daytona/latest/daytona-windows-amd64.exe"
-OutFile "$dir\daytona.exe"
[Environment]::SetEnvironmentVariable(
"Path",
"$dir;" + [Environment]::GetEnvironmentVariable("Path", "User"),
"User"
)

Open a new terminal and verify:

daytona --version

My Suggestion is Either update the docs to point to the correct Windows installer URL or add a redirect/script at get.daytona.io/windows similar to macOS/Linux.

[Abdallah-Alwarawreh]

Gotta love when someone responds with AI slop!

At least put some effort when responding, check if it even works lmao