VediramVediramSupport

Crash when switching profiles

profilescrashes

Symptoms

  • Deck becomes unresponsive when activating a profile.
  • An Office application crashes during the live add-in toggle.
  • The profile appears to activate but add-ins don't change state.

Background

Profile activation happens in two phases: a registry write, then an optional live toggle that enables/disables add-ins in running Office apps over COM automation. The live toggle is the phase that interacts with Office, so it's where switch-time problems occur. See Profiles.

Solutions

Activate with Office closed

The registry phase alone is reliable; the live toggle depends on Office being responsive. Close all Office applications, activate the profile (only the registry write runs), then reopen Office - the new profile takes effect on launch.

Disable live toggle

If switching is consistently unstable on a machine, turn the live toggle off so activation only writes the registry. Administrators can enforce this fleet-wide with the DisableLiveToggle policy:

PolicyValue
DisableLiveToggle1

See the Policy Reference. With it set, profile changes take effect the next time the Office app starts.

Check for a problem add-in

Some add-ins don't tolerate being enabled/disabled while Office is running. Check the Crashes page for any add-in flagged during the switch, and consider excluding it - see Crash Analysis.

Clear the database

If activation writes but state doesn't change, the local inventory may be inconsistent:

# Stop Deck first, then:
Remove-Item "$env:LOCALAPPDATA\Vediram\Deck\deck.db"

Restart Deck to re-scan and rebuild.