VediramVediramSupport

Updates & Uninstall

How Deck upgrades, how to uninstall it cleanly, and what happens to user data

Upgrades

Deck uses a Windows Installer major upgrade. Installing a newer MSI over an existing installation automatically removes the old version and installs the new one in a single transaction:

msiexec /i VediramDeckSetup-1.9.0-x64.msi ALLUSERS=1 /qn
  • User data is preserved. Profiles, the add-in inventory, metrics, and crash history live in %LOCALAPPDATA%\Vediram\Deck\deck.db, which the installer does not touch. The database migrates its schema automatically on first launch of the new version if needed.
  • Downgrades are blocked. Installing an older version over a newer one fails with: "A newer version of Vediram Deck is already installed." To move back a version you must uninstall first.
  • Keep the scope consistent. Upgrade a per-machine install with ALLUSERS=1 and a per-user install without it. Mixing scopes results in two parallel installations rather than an upgrade.

Pin fleet deployments to explicit stable version URLs so upgrades roll out only when you publish the new version to your management tool - not automatically. Deck has no built-in auto-updater.

Uninstall

With the original MSI

msiexec /x VediramDeckSetup-1.8.0-x64.msi /qn

By product code

If you don't have the MSI on hand, uninstall by the product's code. The UpgradeCode is stable (F8A3B2C1-4D5E-6F78-9A0B-1C2D3E4F5A6B); resolve the current ProductCode from it:

$p = Get-CimInstance Win32_Product -Filter "Name LIKE 'Vediram Deck%'"
if ($p) { msiexec /x $($p.IdentifyingNumber) /qn }

Interactively

Uninstall Vediram Deck from Settings → Apps → Installed apps (per-user installs appear for the current user; per-machine installs appear for administrators).

What uninstall removes - and what it leaves

ItemRemoved on uninstall?
Application binaries (...\Vediram\Deck)Yes
Start-menu shortcutYes
Auto-start entry (HKCU\...\Run\VediramDeck)Yes, if Deck was set to start with Windows
User data folder (%LOCALAPPDATA%\Vediram\Deck, incl. deck.db and logs)No - left in place
Office add-in LoadBehavior values written by DeckNo - the last-activated profile's state remains

Two consequences matter for administrators:

  1. Add-in state persists after removal. Uninstalling Deck does not revert add-ins to their pre-Deck state. If you need that, activate the Original profile before uninstalling. See Profiles.
  2. Reinstalling reuses existing data. Because the data folder survives, a reinstall picks up the previous profiles and history. To start clean, delete the data folder after uninstall: 
    Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Vediram\Deck"

Removing policy

Uninstalling the client does not remove Group Policy settings. To stop managing a machine, also unlink or remove the Deck GPO and let policy refresh, or delete the SOFTWARE\Policies\Vediram\Deck keys. See Group Policy Setup.

Enterprise DeploymentGroup Policy Setup