Reset Purge and Uninstall

Reset, purge, and uninstall

Operation	Effect
Restart DVM	Stop, apply configuration, and start; prerequisite failures abort the sequence.
Reset Config	Reset managed settings/action files; retain traffic and selected database directory.
Reset All	Reset settings and clear active database/backup; retain selected database directory.
Purge Database	Remove obsolete interface records, excluding the primary interface. Their traffic records are lost.
Uninstall	Stop, remove packages, then delete plugin configuration/backups and active database/SQLite companions.

Automatic purge performs the obsolete-interface cleanup when enabled. Virtual interface recreation can leave useful historical records, so consider whether to retain them before enabling removal.

At custom locations, Reset All/uninstall remove known database files while leaving directories outside plugin-owned configuration folders in place. Plugin-owned configuration directories are themselves subject to cleanup. Reset Config retains extra supported files while replacing managed defaults.

Use Service Check for diagnostics. Use Test Configured Actions only when ready for real notifications, Docker operations, VM link changes, and user functions.

Reset All and uninstall also clear owned temporary automation outcome records. They stop safely if required cleanup fails instead of proceeding with dependent deletion. Uninstall removes the owned shutdown hook before removing its helper package. Independent backups must be outside plugin-owned paths.