← Back to Colors for Command Palette
Silent install command for Colors for Command Palette 0.10.0
The exact silent switches the Colors for Command Palette installer accepts, plus a one-line command you can paste into a script, Intune Win32 app, or Configuration Manager package.
One-line silent install (x64)
Add-AppxPackage -Path .\JiriPolasek.ColorsforCommandPalette_0.10.0.0_x64__15b1mzc2p8w76.Msix
Run from the directory containing JiriPolasek.ColorsforCommandPalette_0.10.0.0_x64__15b1mzc2p8w76.Msix. Download the installer from the Direct link below first.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x64 | - | MSIX | none required | Inherently silent |
| arm64 | - | MSIX | none required | Inherently silent |
- Declared by publisher means the switches come straight from the winget manifest the publisher (or community maintainer) submitted to microsoft/winget-pkgs.
- Default for {type} means the manifest doesn't specify silent switches, so the framework's standard switches are shown (e.g.
/Sfor NSIS,/quiet /norestartfor MSI).
Frequently asked questions
What is the silent install command for Colors for Command Palette?
Colors for Command Palette uses MSIX. After downloading the installer, run: Add-AppxPackage -Path .\JiriPolasek.ColorsforCommandPalette_0.10.0.0_x64__15b1mzc2p8w76.Msix.
How do I deploy Colors for Command Palette via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id JiriPolasek.ColorsforCommandPalette --exact 0.10.0 --silent --accept-package-agreements --accept-source-agreements. If winget isn't viable in your environment, package the publisher's installer directly using the silent switches above.
Prefer the winget route? See the full Colors for Command Palette install page.