Win10 update and esellrate + fsdt

[Jonwait]

Hello, to let evryone know, after installing lastest big WIN10 update, P3D V3 and all FSDT add-ons or all using esellrate, needs to reconfirm as it considers the new WIN installation as a new computer.. and evrything is blocked by firewall or antivirus.

Anyway, big pain in the *** when you first start P3D V3 after the update installation.

My 2 cents.
Jonathan.

[virtuali]

Hello, to let evryone know, after installing lastest big WIN10 update, P3D V3 and all FSDT add-ons or all using esellrate, needs to reconfirm as it considers the new WIN installation as a new computer..

We always said, that a reactivation is required when installing new hardware AND when installing Windows so, this is not news or unexpected.

and everything is blocked by firewall or antivirus.

That's not obviously a "bug" of the system. An ONLINE activation, by *definition* requires ONLINE access. The job of a firewall/antivirus is PRECISELY to prevent something to go ONLINE without your permission. If a software could automatically bypass your firewall/antivirus without your intervention, that would defeat the purpose of having a firewall/antivirus in the first place, so you could just uninstall them, if it annoys you to have to configure them when it's needed.

And, it's not "everything". It's just ONE program that needs to be allowed to go online, which controls activation for all our products so, it will be enough you correctly configure your firewall/antivirus ONCE, and then "everything" will not be blocked anymore. 

That's the advantage of having a single program that handle activation for a whole lot of products (all FSDT products, all Flightbeam products, the QW757, etc.). It could have been worse. Like any single product using a different software module, so each one would have to be independently configured...

Anyway, big pain in the *** when you first start P3D V3 after the update installation.

I can't see how correctly configuring your firewall/antivirus ONCE, after you reinstall Windows (how many times you reinstall Windows ? ) could be considered so difficult.

Unless you are referring to the act of TYPING your Serial Numbers. Something you don't have to do, if you use the .REG files that were created in your C:\Users\YOURNAME folder when you originally activated the products, which are made for the precise reason you will not have to manually type the Serial Numbers when you need them, which is valid BOTH when reactivating due to a Windows install, but also when moving to a new PC.

[Ankh]

The boring thing here is that the Threshold Update from Windows 10 released those days and distributed to the W10 users is actually not classified as an "update" but as an "upgrade", even though M$ does not officially say so. If you read in forums those days, you realize that the fact that Threshold is an upgrade leads to such things like the problem with re-activation. Furthermore, there are users reporting that all data collection settings are restored to default, that those standard apps you removed are all back again and even worse, sometimes this Threshold upgrade seems to even de-install software where W10 considers it to be incompatible with Threshold, notably without asking the user.

So, no, this isse Jonwait reports has NOTHING to do with a NEW Windows 10 installation, that's the problem here. It is the upgrade Threshold that comes in a update-like way on your machines...

[virtuali]

So, no, this isse Jonwait reports has NOTHING to do with a NEW Windows 10 installation, that's the problem here. It is the upgrade Threshold that comes in a update-like way on your machines...

That's exactly my point. We always said a reactivation is needed with a new Windows installation.

If the latest large Windows 10 update BEHAVES like a NEW Windows installation, it's just normal the software would seen it as such, without us having any control over it.

The activation is nothing we handle in our code: it's done by Esellerateengine.dll, so every product out there (even not flightsim related) would behave in the same way. We don't have any control of *what* specific system changes are considered hardware updates, and we don't even know exactly what is being checked by Esellerate.  It's a black box for us, our software just get an notification that "something" has changed, and an activation confirmation is required.

Note that, not ALL request for reactivation will really "consume" an activation. The system is able to recognize an "updated" system from a "new" system, which explains why, although we give 6 activations by default, many users got many more without having to contact us: it was all these "updates" that weren't counted against the limit so, it might be a minor annoyance, but it doesn't really affect the ability to use the product.

[Ankh]

Yes, I understand your point and that's why I was not saying anything critical about the FSDT side of the story. The problem here is, how this so-called Windows 10 update behaves and the criticism is against Microsoft. For me, it is just a plain affront that this Windows 10 "update" decides on its own which software needs re-installation, which software is de-installed and which settings are resetted. IF it would be a full upgrade basically similar to a brand new installation, then I would understand it. This is now excactly the way, Microsoft was advertising how future updates of Windows 10 WILL NOT BE LIKE. They were advertising Windows 10 as being the final version only receiving updates and no need to install a new Windows, yet they already fail with the first big update in the history of Windows 10 by letting the updateprocess end like you install a brand new operating system on your computer. Ridiculous.