---
title: "Stardock WinGet Installation Guide"
canonical: "https://support.stardock.com/space/SHC/2813001773/Stardock%20WinGet%20Installation%20Guide"
format: markdown
---
This page provides the **official instructions for installing, updating, and managing Stardock software** using Microsoft’s trusted **Windows Package Manager (WinGet)**.

All Stardock WinGet packages are:

- **Digitally signed by Stardock**
- **Hosted on Stardock’s secure CDN** (`cdn.stardock.us`)
- **Published via Microsoft’s official WinGet repository**

WinGet offers a reliable, script-friendly way for IT administrators and end-users to:

- Install Stardock software silently and consistently
- Automatically check for and apply updates
- Integrate Stardock deployment into enterprise tools such as **Microsoft Intune**, **Endpoint Manager**, or **PowerShell automation**

> 💡 **Why WinGet?**  
> Every installation comes directly from Microsoft’s secure source index and verifies Stardock’s signed binaries automatically. This ensures authenticity, consistency, and reliability across endpoints.

---

> Macro (toc)

## Verify WinGet Availability

WinGet is included by default with:

- Windows 11 (all builds)
- Windows 10, version 22H2 or later

Check by opening **PowerShell** and running:

```
winget --version

```

✅ If a version appears (for example, `1.7.10582`), WinGet is available.

❌ If you get an error (`The term 'winget' is not recognized`):  
Install **App Installer** from the Microsoft Store:  
🔗 [https://apps.microsoft.com/detail/app-installer/9NBLGGH4NNS1](https://apps.microsoft.com/detail/app-installer/9NBLGGH4NNS1) 

After installing, close and reopen PowerShell, then rerun the version check.

---

## Search for Stardock Software

List all Stardock products available via the public WinGet repository:

```
winget search stardock

```

Example output:

```
Name              Id                          Version
--------------------------------------------------------
Fences 6          Stardock.Fences.6            6.0.0.2
Start11 v2        Stardock.Start11.v2          2.5.6.3
Multiplicity 4    StardockSystems.Multiplicity4 4.0.7.2
Groupy 2          Stardock.Groupy.v2           2.3.0.2

```

---

## Install a Stardock Product

Install any Stardock app directly from the trusted Microsoft WinGet source:

```
winget install Stardock.Start11.v2 --accept-source-agreements --accept-package-agreements --silent

```

> 💡 The `--accept-*` flags allow silent, non-interactive installs — ideal for automation or IT deployment.

### Example installs

```
winget install Stardock.Fences.6 --accept-source-agreements --accept-package-agreements --silent
winget install Stardock.Groupy.v2 --accept-source-agreements --accept-package-agreements --silent
winget install StardockSystems.Multiplicity4 --accept-source-agreements --accept-package-agreements --silent

```

---

## Check for Updates

Check whether a new version is available:

```
winget upgrade Stardock.Start11.v2

```

Or list all Stardock packages that can be updated:

```
winget upgrade | findstr Stardock

```

Example output:

```
Name           Id                     Version   Available   Source
------------------------------------------------------------------
Start11 v2     Stardock.Start11.v2    2.5.6.3   2.5.7.0     winget

```

---

## Upgrade to the Latest Version

Update an existing Stardock installation:

```
winget upgrade Stardock.Start11.v2 --accept-source-agreements --accept-package-agreements --silent

```

Or upgrade all Stardock apps in one pass:

```
winget upgrade --all | findstr Stardock

```

---

## Combined One-Liner

To ensure the latest version is always installed:

```
winget upgrade Stardock.Start11.v2 --accept-* --silent `
  || winget install Stardock.Start11.v2 --accept-* --silent

```

If the product is already installed, it upgrades it; if not, it installs it.

---

## Uninstalling (Optional)

To remove a Stardock product:

```
winget uninstall Stardock.Start11.v2

```

---

## ⚠ Note on Installer Exit Codes

Some Stardock installers may return **exit code 9**.  
This is **not an error** — it simply means the installation completed successfully and a **system reboot is required** to finish applying changes.

- **Exit code 0 → Success, no reboot needed**
- **Exit code 9 → Success, reboot required**

If you see code 9 in deployment logs, it can safely be treated as a successful installation.

---

## Quick Reference Summary

| Task | Command | Purpose |
| --- | --- | --- |
| Search Stardock apps | `winget search stardock` | View all available Stardock packages |
| Install | `winget install Stardock.ProductID --accept-* --silent` | Installs product silently |
| Check for update | `winget upgrade Stardock.ProductID` | Shows if a new version exists |
| Upgrade | `winget upgrade Stardock.ProductID --accept-* --silent` | Updates existing install |
| Combined one-liner | `winget upgrade ... |  |
| Uninstall | `winget uninstall Stardock.ProductID` | Removes the app |
| Exit code 9 meaning | “Reboot required (success)” | Not a failure condition |

---

## Notes for IT Administrators

- All Stardock packages are digitally signed and hosted on Stardock’s CDN (`cdn.stardock.us`).
- Packages are published and maintained via Microsoft’s official WinGet repository (`microsoft/winget-pkgs`).
- Installers support silent mode (`/s`) and return standard exit codes (`0` = success, `9` = success + reboot).
- WinGet commands can be scripted or deployed through Intune, Endpoint Manager, or any automation platform.