On my system, I was able to install over the old version, without stopping the older version, without any issues.
Version 1.2.61b automatically stopped and uninstalled the previous version before installing the new one.
As I stated previously, it stopped the service on install, removed the old version etc etc. However, it wouldn’t start. I had no services running other than ESET, GlassWire and Process Explorer (Oh, and Chrome). I have never been able to get it to restart automatically without issue after upgrade.
I just had to do a completely clean install and thus, all my past data is gone and now setting rules once more. Makes me want to avoid ever upgrading the software.
@JMSolo Please email our helpdesk https://www.glasswire.com/contact/ with a link to this thread so I can give some instructions so we can collect logs and see why this is happening for you.
It is not required to do a clean wipe and install with every upgrade, we think that would be bad and I think our users would be mad at us! I hope we can fix this for you!
It’s true, my CPU is overclocked. Hence the ‘K’ Would an overclocked system really cause this type of issue?
Geez, I sounded like a jerk there… sorry bout my bad filter @Remah, just really curious how this would result in the behavior I am experiencing with a simple upgrade. No other softwares have faced this issues on my system during an upgrade. I am curious, is there a way to get others with an overclocked system to speak out?
Overclocking changes timings and can produce subtle and unusual issues.
Are CPU core temperatures well below the spec: Maximum operating temperature 67.4°C?
Do you have have the latest chipset drivers?
One way to virtually eliminate overclocking as a cause of the problem is to run the install while the CPU is at the stock speed. If you still have the problem then it is more likely to be something else.
Yes, I keep everything current… temps are never an issue as the most intensive apps I run are Atom.io, Plex Media Server and Illustrator. Temps usually sit around 42°C. Never go higher than 65 or I have an alert shut down the process… unless I am doing it intentionally.
It’s Intel Panther Point Z77, Intel Ivy Bridge motherboard chipset as well… but don’t know how relevant that would be to the problem.
I could try tempering the beast and see if that matters. Good idea!
Over many years supporting systems, I’ve seen many problems disappear when overclocking is scaled back. In one case, the reduction was only 1-2% to get a Windows .NET application to run properly. Admittedly, it is much less likely today because there is much better motherboard support for overclocking.
You might check if other overclockers with the same motherboard/CPU combination have had unusual software problems.
I would, but I wouldn’t know where to start. This is the only application I have had issues with. But I am going to attempt your suggestion once I am not running anything.
Updated
Thanks loads to GlassWire, the new Beta works splendidly. Installed over the past release and the services installed and started right up without error.