I’m glad it’s fixed for you! We are still working to recreate this problem after install so we can figure out why it happens to some people and not others.
Same issue for me. I’ve just upgraded from v2.2.241 to v2.2.258 and it’s like it’s a fresh install. All my history, all my alerts, etc. are gone. Used the full version installer, and definitely didn’t choose to do a fresh install or to reset the Windows firewall rules.
I’ve done those steps and that has restored the descriptions of my devices on the Things tab, and it has restored the list of alerts on the Alerts tab, which are the things I’m most concerned about. But it didn’t restore the historical data for the Usage or the Graph tabs.
Hi… I was on v2.2.241 and perfoming the upgrade to 2.2.258 wiped out the settings…
I manually just allowed/blocked the required apps so didn’t bother trying the restore method.
As a test I have just tried
2.2.258 full with settings in place… Then installed the 2.2.258 lite over the top and it also wipes out settings…
(Your blog post specifically says it will retain settings)
At least we know how to restore settings now! Hope you manage to get it fixed before too many people get hit by this issue.
I updated the GlassWire Lite Blog post so it’s more clear. It’s correct that your history/settings will change when using GlassWire Lite (the installer even warns about this) but you can switch back to GlassWire Original and all your settings and history should return.
Ah ok… I only tried the lite on one of the laptops (after the full version had already lost most settings on it)…
Ive left the full versions on the other 2 machines and manually reconfigured the settings
Cheers
Sorry, I think my writing was not clear enough so I improved it so nobody is confused in the future. Also we added a warning in the GlassWire Lite installer window itself, but perhaps it’s too easy to miss.
I downloaded via green download button on main page, left all settings on default and same thing happened here as previously reported; settings restored by following instructions above.
@nextdrOp and everyone else, we just released an update that solves this issue.
Sorry for the problem and thanks for your patience while we fixed this. We are thankful that you were willing to report this bug and help us find the problem so quickly.