For managed Windows deployments of Warp, use the vendor download page or the official Windows installation docs as the package source. Warp currently documents Windows 11/10 builds for both x64 and ARM64, with a command-line install path available as winget install Warp.Warp when Windows Package Manager is intentionally used.

If you stage Warp outside that package manager, keep architecture selection explicit in your package naming and detection rules because the public download page exposes separate Windows x64 and Windows ARM64 installer choices. Treat first-run sign-in/team enrollment as user context, not as part of a device-level silent install validation; a successful deployment check should confirm the Warp application is installed and launchable without assuming the target user has already signed in.

Official source context: Warp documents Windows installation in its installation and setup guide and publishes the Windows x64/ARM64 downloads from warp.dev/download.

For managed Windows deployments of Warp, use the vendor download page or the official Windows installation docs as the package source. Warp currently documents Windows 11/10 builds for both x64 and ARM64, with a command-line install path available as winget install Warp.Warp when Windows Package Manager is intentionally used.

If you stage Warp outside that package manager, keep architecture selection explicit in your package naming and detection rules because the public download page exposes separate Windows x64 and Windows ARM64 installer choices. Treat first-run sign-in/team enrollment as user context, not as part of a device-level silent install validation; a successful deployment check should confirm the Warp application is installed and launchable without assuming the target user has already signed in.

Official source context: Warp documents Windows installation in its installation and setup guide and publishes the Windows x64/ARM64 downloads from warp.dev/download.