cgpsmapper key not working on new machine

[whiskeyportal]

So I installed cgpsmapper on a new machine, and it is not recognizing my unlock key. I insert the code and it says that it is accepted, I click OK and then I get a pop-up stating that the code is over a year old and will not be recognized. Attempts to contact Stan haven't yielded any results. This has happened in the past and he has always been very good and getting me a new code right away. Last time it happened, he sent me a code and said that it shouldn't happen again, which it hasn't on that specific machine.
Has anyone else had this issue, and were they able to figure out a work-around?

Thanks

[popej]

Try to set old date on your PC, register and then set back current date. I think this should work.

[whiskeyportal]

edit:
After a few failed attempts I was able to get it to work using this method. Thanks for the help!

[whiskeyportal]

Ok, so that worked, but then the machine had a new VM put on it, and the old build I was using no longer exists, so I was forced to try and re-register cgpsmapper on the new build. I did everything exactly as I did last time, but now cgps is detecting that I changed the date and time and throws up an error.
Any other ideas?
Thanks

[popej]

Have you successfully manipulate time in VM? I think VM can be synchronized to host and restore real time quickly. And you can do opposite - freeze time and date for VM. It will boot always with the same date and stop counting time when suspended. I don't remember details but you should find it in net, at least for VMware.