Frequently Asked Questions

Yes. DevOps Tools Installer enforces a strict zero-trust pipeline. It fetches official vendor release artifacts over HTTPS only, verifies SHA-256 cryptographic digests, performs Win32 Authenticode (WinVerifyTrust) digital signature checks with a configurable policy (Warn or Block unsigned), tags downloads with Mark-of-the-Web (ZoneId=3) so Microsoft Defender and Windows SmartScreen inspect files normally, and writes an on-disk audit trail to %LOCALAPPDATA%\DevOpsToolsInstaller\logs.

No. We do not distribute third-party executables inside our app binary, nor do we run proxy mirrors. Every download URL in the catalog points directly to official upstream vendor release infrastructure (GitHub Releases, Amazon S3, Azure CDN, HashiCorp Releases). There are zero intermediate proxies or repackaged binaries.

No. The application never executes third-party installers with silent background flags. When an installer (.msi or .exe) runs, it presents its native vendor setup wizard and prompts for standard Windows UAC elevation. You maintain full oversight and interactive consent over what runs on your workstation.

Zero telemetry. The application contains no Google Analytics, no telemetry beacons, no user identifiers, and no background reporting services. All operational events (downloads, signature verifications, policy actions) are logged exclusively to local disk files that never leave your machine.

DevOps Tools Installer supports:

• Windows 11: Build 22000 and higher (full Mica Alt backdrop and Fluent controls).
• Windows 10: Build 19041 and higher (20H1+).
• Architectures: Native x64 (64-bit Intel/AMD) and native ARM64 (Qualcomm Snapdragon).

Built with WinUI 3 via Windows App SDK 2.5.1 and .NET 8.0 self-contained single-file assemblies.

The app provides 12 curated role-based presets (e.g. Kubernetes Starter, DevSecOps Toolkit, Cloud Engineer Essentials, IaC Complete, Observability). You can install an entire stack in 1 click, preview its tools in the catalog, or open it in the Custom Stack Builder.

The Stack Builder features a 2-column composer where you can search 90 catalog tools on the left with keyboard-friendly "+ Add" buttons, reorder and inspect live download estimates on the right, save local presets to custom_stacks.json, and export/import portable JSON stack files for your team.

All files are isolated in user space:

• Downloaded Artifacts: %LOCALAPPDATA%\DevOpsToolsInstaller\Downloads
• Extracted Tool Archives: %LOCALAPPDATA%\DevOpsToolsInstaller\Tools\<tool-id>
• Portable CLI Binaries: %LOCALAPPDATA%\DevOpsToolsInstaller\Tools\bin
• Activity Logs: %LOCALAPPDATA%\DevOpsToolsInstaller\logs

Machine-level directories (Program Files, System32) and Machine PATH (HKLM) are never touched without standard vendor installer elevation.

Navigate to Settings in the application and click "Add to PATH". This registers %LOCALAPPDATA%\DevOpsToolsInstaller\Tools\bin in your User Environment (HKCU\Environment\PATH) with zero administrator rights required. You can also run DevOpsToolsInstaller.exe --fix-path from PowerShell.

Uninstalling Tools: From the "Installed" page (or via --uninstall <id>), the app invokes the vendor's official uninstaller detected via Windows Registry, or cleanly removes extracted directories in Tools\<tool-id> and Tools\bin.

Uninstalling DevOps Tools Installer: The Windows Setup Wizard uninstaller provides an optional prompt: "Remove my downloads, tools, and settings" for a completely clean removal. If installed via WinGet, run winget uninstall DevOpsToolsInstaller.

All downloads write to a companion <filename>.partial file. When the download is retried (in the same session or after restarting the app), the transfer engine sends an HTTP Range request and resumes from the exact byte offset. The file is promoted to its final name only after SHA-256 verification passes. Corrupted partial files are automatically discarded.

The catalog is cryptographically signed with an ECDSA P-256 key at release time. Shipped app versions verify the signature against an embedded pinned public key and fail closed: unsigned, expired, or modified catalogs are refused outright, and the app falls back to the embedded catalog compiled into the binary.

Contributions are welcomed! Fork the repository on GitHub, add your tool specification to catalog/catalog.json, place the official vector SVG logo in src/DevOpsToolsInstaller/Assets/logos/<id>.svg, update catalog/bundles.json if relevant, and open a pull request according to our CONTRIBUTING.md guidelines.