Q100217: How to resolve the "License not yet valid, may be valid in the future" error message



When installing a nodelocked or floating license, activating a login-based license or when running a program you might encounter the following error message:


"License not yet valid, may be valid in the future"

You may also see the following error when trying to install the license via the FLU:

"An unexpected error occurred"

This error will prevent you from installing the license and/or prevent the program from running.


This error message can happen if the system time of your computer has been changed by a large amount.  

To prevent temporary licenses from being used past their expiration date, the licensing code in our software looks to see if the system time has been changed too much by checking the last-modified timestamp values of system files and directories.


Whilst this does prevent a user from winding back their computer clock to keep using an expired demo license it can trip up users who have previously changed their system date for testing purposes.



The first step to fixing this issue is to make sure your computer has the correct setting for the local date and time. If possible, use the operating systems settings to automatically get the date and time from the internet.  After you correct the date/time setting, applying any pending OS updates and/or rebooting the machine may be enough to fix the issue.


If that doesn't fix the issue then you'll need to search your computer to locate any files or directories with the last modified timestamp ahead of today's date and update them to change the last modified timestamp to the current time.  Once you've fixed all the problematic files and directories you should then be able to install your license and run the program.



If you are still experiencing difficulties please create a support ticket to let us know the exact issue encountered and the troubleshooting steps that have been taken.

For more information on how to open a support request, please refer to this article:

Q100064: How to raise a support ticket


    We're sorry to hear that

    Please tell us why