← Back to Visual Studio / Code for Command Palette
Silent install command for Visual Studio / Code for Command Palette 1.34.0.0
The exact silent switches the Visual Studio / Code 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 .\15722UsefulApp.WorkspaceLauncherforVSCode_1.34.0.0_x64__s4b834ss2syh6.Msix
Run from the directory containing 15722UsefulApp.WorkspaceLauncherforVSCode_1.34.0.0_x64__s4b834ss2syh6.Msix. Download the installer from the Direct link below first.
| Architecture | Scope | Type | Silent switches | Source |
|---|---|---|---|---|
| x64 | - | 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 Visual Studio / Code for Command Palette?
Visual Studio / Code for Command Palette uses MSIX. After downloading the installer, run: Add-AppxPackage -Path .\15722UsefulApp.WorkspaceLauncherforVSCode_1.34.0.0_x64__s4b834ss2syh6.Msix.
How do I deploy Visual Studio / Code for Command Palette via Intune or Configuration Manager?
Use winget for the cleanest path: winget install --id 15722UsefulApp.WorkspaceLauncherForVSCode --exact 1.34.0.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 Visual Studio / Code for Command Palette install page.