It’s surprising and disappointing that it’s even necessary to ask, considering that it’s such a major issue that’s been discussed so prominently in the forums, but I have to ask as it’s not even mentioned in the changelog:
Does it address the very well known issue that affects people who installed the problematic v2.2.258, whereby that specific version wiped out settings and history, in such a way that every subsequent version installed on a such a machine (i.e. one which had v2.2.258 at some point) also wipes out settings and history?
Does this new version have a proper fix for that major issue so that it is safe to install on such an affected machine?
Sorry for the issue you experienced with version 2.2.258 that was released in October of 2020. Version 2.2.258 was released for two days and no users were ever asked to update via an update alert.
Of course it’s still unacceptable that any version could cause user settings to be lost and I apologize.
You can see in our change list (click the link below) that version 2.2.258 was released on October 6, then the fix was released two days later on October 8. On the change list we also link so the fix for the problem that we posted here in the forum. GlassWire Software Version Changes List
I don’t see any solution offered in your reply. As you are well aware, installing v2.2.260 over v2.2.258 doesn’t solve anything, so why you try to point me to a so-called “solution” in the v2.2.260 changelog is a mystery.
So you’re saying that people who installed v2.2.258 are now SOL? Because, as you know, every time any version is installed now, the problem is repeated again, causing major hassle.
Your comments about no users being asked to update is rather tone-deaf and actually quite insulting. I installed a non-beta, public release that you made available on your website. It was because of people like me installing that version and then posting details of the bug that you were able to make changes for v2.2.260 to avoid the problem for other people. But you’ve since never solved the problem in any subsequent release to reverse what v2.2.258 did on machines like mine that it was installed on.
So GlassWire screwed up my installation with the publicly-released version v2.2.258 and now you offer no solution to get my installation back on track. You expect me to just put up with having a GlassWire installation that gets affected in the same way every time a new version is released.
You guys have washed your hands of this and are not prepared to fix installs that have been broken by v2.2.258. Wow.
Okey. There is quite an improvement.
Now the the control process is not running indifintely into a loop and using 6% of one of my high end cpu.
And so the improvements tôt je database engine made the job. It doesn’t give a null value anymore when it encounters a problem.
Now it just crashes as it supposed to be.
Still a lot of crashes though but we are on the right road now. The database was one of the big problem which seems to be now more or less resolved.
Do you want the crash dumps ?