Repository navigation
[BUG] Webhook and some other settings, alerts and history are lost after 3.2.0.->3.3.0 update #1832
Description
Activity
- changed the title
[-][BUG][/-][+][BUG] Webhook setting is lost after 3.2.0.->3.3.0 update[/+]on Jul 30, 2026 - changed the title
[-][BUG] Webhook setting is lost after 3.2.0.->3.3.0 update[/-][+][BUG] Webhook and some other settings are lost after 3.2.0.->3.3.0 update[/+]on Jul 30, 2026 Also, the "Last 24 hours" -> "Last 4 Hours" after the update.
and no Alerts History. Queries, Deadlocks after the update.
Tabula rasa...- changed the title
[-][BUG] Webhook and some other settings are lost after 3.2.0.->3.3.0 update[/-][+][BUG] Webhook and some other settings, alerts and history are lost after 3.2.0.->3.3.0 update[/+]on Jul 30, 2026 Confirmed, and this is the most serious bug report in a while - thank you for it. Root cause is found. Short version: the 3.3.0 Setup.exe you downloaded installs into the same folder Lite keeps its data in, and re-running Setup over an existing install clears that folder first. Your settings file and the local history database were deleted by the installer. The "Last 4 Hours" detail in your second comment confirmed it: that value is the hardcoded default that only appears when the settings file is missing entirely.
Two things before anything else, in this order:
1. Your webhook URLs are probably still recoverable - but do not press Save in Lite's Settings window until you have copied them out. The URLs are not stored in the settings file; they live in Windows Credential Manager, which the installer never touches. But with the settings file gone, Lite does not load them, shows you empty boxes, and pressing Save writes those empty boxes back - which deletes the stored credentials. So first: Control Panel > Credential Manager > Windows Credentials, look for entries named
PerformanceMonitorLite_TeamsWebhook,_SlackWebhook,_GenericWebhook, and copy the URLs somewhere safe. Then you can re-enter them in Lite normally.2. There is a chance your entire pre-update history survived under a renamed folder. The installer renames the old folder aside before deleting it, and if any file was still locked the delete fails silently. Check with:
dir /a "C:\Users\<you>\AppData\Local\PerformanceMonitorLite.*"If a folder like
PerformanceMonitorLite.a1b2c3...exists, everything is in it - close Lite, copymonitor.duckdb, theconfigfolder, andarchivefrom it back intoC:\Users\<you>\AppData\Local\PerformanceMonitorLite\, and you have your history and settings back.Your server list survived either way - it lives under ProgramData, outside the folder the installer clears - which matches what you reported.
If you can, attach
C:\Users\<you>\AppData\Local\velopack\velopack.log- it is the installer's own log, it survived, and it will show exactly what happened on your machine.The fix (moving Lite's data out of the installer's folder entirely, plus a migration for existing installs) is underway. One thing to carry forward until it ships: upgrade through the app itself (Help > About > install update) rather than by downloading Setup.exe - the in-app path has never had this problem. A full writeup follows when the fix lands.
The fix has landed on dev. What changed:
- Lite's data now lives in
%LOCALAPPDATA%\PerformanceMonitorLite-Data- a folder the installer does not own and can never delete. On the first start of a fixed build, everything found at the old location (settings, the history database, archives, logs) moves across automatically; the move is instant even for a large database, nothing is copied, and nothing in the old folder that belongs to the installer is touched. - The Settings-window hazard from my first comment is gone too: the webhook boxes now load from Credential Manager even when the settings file is missing, so pressing Save can no longer delete surviving credentials.
- The documentation that claimed data was "separate from the executable" has been corrected, and the app now shows a notification when an update is available, steering to the safe in-app path.
One thing that matters for you specifically and for anyone else reading this later: the fix cannot protect the upgrade INTO it. Setup.exe deletes the old folder before a single line of the new version runs. So when the release carrying this ships (it will be in the next regular release; tonight's nightly off dev carries it already), upgrade through the app (Help > About > install update) or by extracting the ZIP - not by running Setup.exe over your existing install. After that one upgrade, the problem is gone for good.
If you did find a
PerformanceMonitorLite.<random>rollback folder or recovered your webhook URLs from Credential Manager per the earlier comment, I would like to hear it either way - it tells me whether the rollback-survivor path is real in practice or just a code path.- Lite's data now lives in
Thank you @erikdarlingdata , btw, the bug with webhook existed earlier, so I have copied it into the text file and now restoring if need.
So I can wait the next release and then will check it again.Good to know you had the webhook URLs stashed in a text file, and the detail that the webhook loss predates this upgrade actually fits the diagnosis: the Settings-save hazard could fire any time the settings file went missing or unreadable, not only after a Setup.exe wipe, so what you saw earlier was most likely the same bug through a different door. Both doors are closed now.
One reminder for the upgrade that carries the fix, since it matters exactly once: go through the app (Help > About > install update) or extract the ZIP over the install, not Setup.exe. After that one upgrade your data lives where no installer can touch it and this whole class of problem is gone.
Closing as fixed for the next release. If anything is missing after you update, comment here and it reopens.
Component
Lite
Performance Monitor Version
3.3.0
SQL Server Version
Azure SQL db
Windows Version
Windows 11
Describe the Bug
I have installed PMLite 3.2.0 and it worked, then detected the version 3.3.0 appeared. I downloaded the Setup and tun it, it wrote the v.3.2.0 already installed and suggested some options, I have selected "Update".
It was installed ok, I go to Settings and see webhook is lost. I.e. no my webhook settings and all by default.
Steps to Reproduce
Install 3.2.0
Then run 3.3.0 Setup.
The webhook settings is lost.
Expected Behavior
The webhook should be kept.
Actual Behavior
The webhook is lost after update to the v3.3.0.
Error Messages / Log Output
Screenshots
No response
Additional Context
No response