beta will expire 10 october?

Hi, I just downloaded the beta version as the reguar windows does not work well on my laptop, and when I run the beta it says it will expire on the 10th October (5 days). Is this because you are releasing soon?
Should I get a license or something? I’m looking to use it for a big project (i used the mac version way back in 2010 and it was great)!
Thanks! :slight_smile:

Hi. It’s probably not a sign of impending regular release. With the beta releases, L&L has disabled the normal licensing system. In its place, and to make sure that people aren’t using an older version of the beta that may contain bugs that are fixed in later versions, they have set up an expiration date. After the expiration date, you can no longer run that version of the beta – you have to download and update to the next version of the beta. They normally make the next beta version available a couple of days before the expiration – sometimes it’s a little shorter, sometimes it’s a little longer, but they have always put out a new version (so far) before the expiration date hits.

Make a note on your calendar to start checking for a new version (or check here on the forums – the users will normally see the new release and start making forum posts about it before the official notice goes out) so that you have time to download and update.

There are two main schools of thought on how to upgrade between beta versions:

  1. Use the automatic updater within Scrivener. Just open Scrivener, check for new updates, and accept the prompts to install the new beta version. Scrivener will do the rest and preserve all of your settings. (Note: if you go past the expiration date, the older beta version will no longer open and you will not be able to use this method – meaning that you might lose any settings customizations you have made.)

  2. Manually download the updated version. Using the about-to-expire beta version, save your various settings to disk (outside of the Scrivener installation directory) and then uninstall the about-to-expire version. Now, install the new version (some people like to reboot Windows before doing this), fire it up, and import your settings. You can do this after the current beta version has expired, as long as you have your settings saved – the manual uninstall and reinstall will wipe out your settings otherwise.

Two things to keep in mind no matter which method you use:

  • It’s probably a good idea to save a copy of your settings as a backup just in case you have to uninstall and reinstall for whatever reason.
  • Never store your saved settings or your Scrivener project files in the installation directory for Scrivener!

Once they actually put out the release version, they’ll re-enabled the normal licensing code, and the new version will become a regular 30-day trial. At that point, you can go ahead and get your license and put it in. You can get a license for 1.9.x right now if you really want – it includes a free upgrade to 3.0 – but you won’t be able to use it with the beta. Either way, you’ll have time – once they finally announce the release.

Thank you so much for this response!

It is very clear and I really appreciate your taking the time to explain everything (especially re. the save locations!)


By the way, the current version is valid till 15/10, not 10/10!


This is not strictly correct. There is a very simple way to upgrade this way if you go past the expiry date. Simply change the system date to before the expiry date, launch Scrivener and update, then change the system date back. A little fiddly, takes a couple of minutes but much faster and easier than alternatives.

I don’t generally make a habit of encouraging people to perform non-standard procedures to their machines that have the potential to cause other unforeseen side effects if they are not fully aware of the risks. Yes, most of the time setting your system clock back is benign. When it’s not, it’s catastrophic.

Given that files are dated the developers do ‘not’ condone changing the date of ones computer as this can cause corruption of ones files due to how backups are also dated. The best advise would be to follow Devinganger’s advice or steps. It’s not really that difficult to just pop in or open the program to check for updates.

The other item I would also suggest is that the OP check their computers date as ‘my’ version shows and exp of 15 Oct.

It is always prudent, regardless of being in Beta or updating, to make a backup of your settings. Under options there is a save options to a file choice and you can then load options from a file.

I’d hardly call changing date/time a ‘non-standard’ procedure. Provided the most basic precautions (no open files, other programs) are taken it’s a pretty standard process.

In 30+ years in IT I’ve never had an issue with a quick date/time change for the purpose of resetting an ‘expired’ beta back to allow an update. I’ve also done it for other specific tasks though always with planning and basic precaution.

All that said, I always have ample backups so if I had a total idiot moment there’s a way back.