Hi guys,it happened yesterday and today again, when I start ASE it says it's not activated. The activation works fine, but I wonder why? I installed Squawkbox 4 recently which reinstalled the simconnect client. I run ASE on a secondary PC. Can that be issue? How can I solve it? I won't be able to activate ASE again after a short while this way.ThanksFedeP.S. Running build 572.

Hi,Different hardware or switching between ASA and ASE can cause this. Also our latest Beta Build may help you in this area.

No Jim, sorry, maybe I didn't express correctly. There is no different hardware. I have my usual setup which has been running for a year: FS PC + ASE PC. That's it. It's always worked, it started yesterday telling me it wasn't activated, asking for an activation. I only use ASE. The latest build has some bugs I wouldn't want to see here, the build I'm using runs fine for me. that's just ok. It's always worked perfectly, so why would it stop now? Is it maybe related to the simconnect client I installed yesterday as per SB4 installation? Should I reinstall ASE from scratch?ThanksFede

Yesterday I experienced something similar in mid-flight. All of a sudden FS9 (fullscreen) returned to desktop (not CTD), asking me to reactivate ASE. FS continued running in the background. I had to click "OK" and I could return to FS carrying on with my flight. Strange...I didn't fumble about with anything like simconnect or whatever. I didn't switch between ASE and ASA either.

FWIW, after install of 625, got the reactivation screen - hadn't happened with any other versions after initial install.

Well, if I had installed the new build it wouldn't have been so strange to me. I don't even remember what happened the previous times after install. I never touched ASE folders' or installation. Even the simconnect install shouldn't have bothered ASE, but I don't know where this activation file is (if it exists, maybe it's even on the server?). I'm starting it again now, let's see what happens..Cheers

Today the same. Flying from EDDH to USSS. After 3:20 hrs inflight my PC reverted to desktop, indicating that ASE is either not activated or the license key is invalid. Press OK to activate.After pressing this darn thing "thank you for activation" and so on. I could go back to FS9 and landed as usual. Really strange.

For what it's worth, today seems to be fine...I'm keeping my fingers crossed, just in case, you know :)Jim, may it be something on the server end? I mean, I don't know how this activation works is detail, but it seems to be running remotely (that would explain why you need to activate it again and again if you run it on two Pc's). Maybe some corrupted data on your end? Not blaming anyone here, just thinking out loud.Cheers

All,We have been working on the activation\licence verification system because as system hardware and user habits have changed we needed to adjust our system.B625 was the first attempt and we knew and documented that upon the initial running a user would be asked to re-activate. That was normal and expected.At this time, please be testing B629 for those that wish.It's not at the key server end, that we know for sure!

OK, after upgrading to B629 I did a flight from UNNT to RJBB. 5:49 hours in Level-D's 767. No request for reactivation. So obviously that did it.By the way - I really like the new option to set the altitude when the upper visibility should be reached when using the visibility smoothing. One more reason not to fumble around with your fsuipc settings.

Recently made some hardware changes in my pc, and it will not accept my Key (ASA) or (ASE) at all? Should i remove everything and start over?

Hi,No, you should e-mail me your purchase information so that I may look up your key information on the key server!

Ok Jim email sent. TY :D

Hello, Installed B629 and it requested ActivationActivation was OK and B629 running without problems.Have a nice day.

Hi,One initial activation is expected and normal.