This has happened several times. I bought a license for Hazel several years ago but whenever Hazel updates I get the "your trial will end soon" message as if I had not paid for the license. When I open the Hazel license key file the programme recognises me as a paid up user but all of my rules have been erased and I have to start again. Is there a way to get back the rules I had before the update? I hope so as this is very annoying. Thanks.
Are you running any sort of cleaner software like MacKeeper? How are you upgrading? Are you using the in-app updater or doing it manually? Are you uninstalling during this process?
- Launch Console and go to the time of your update and see if there are any log messages that may be applicable. - From your home folder, go to Library/Logs/Hazel. See if there's anything in the SparkleUpdateLog there.
Sorry, I am not sure of the time of the update as I had a message to restart my computer first thing this morning in order to install updates that happened overnight. I've had a look at the console logs for overnight last n night and cannot see anything that pertains to Hazel - though in truth I don't really know what I am looking for.
I have looked in Library/logs but can't see an entry for Hazel there. Sorry I am not being much help.
I have just noticed that Hazel seems to have reset itself some time during today as the message is saying that my trial expires in 13 days and when I go to the info page it says unlicensed, evaluation. What is going on?
Did you check the logs? As for Library/Logs, make sure to look under your home folder, not at the top level of your drive. If you don't see Library, then google as it may be invisible and you'll find instructions on how to reverse that.
I have found library/logs/hazel in my home folder and cannot see anything relevant, but as I said before I do not really know what I am looking for. I can't imagine I am the first person this has happened to, what has been the cause before?
Check the normal system logs as well. Launch Console and look at them there. Look for anything coming from System Preferences around the time this happened.
You're not the first but the reason is different for everyone. Without diagnostics, I can't say which it is.