General Category > General Discussion

eSellerate error - 25007 machine mismatch

<< < (2/2)

virtuali:

--- Quote from: devgrp on August 04, 2015, 10:59:16 am ---So you are basically telling me that when I install a scenery and put in my serial number its not activated right ?
--- End quote ---

Never said that. When you insert a Serial Number, it IS reactivated right away.

It's when you change hardware or reinstall windows that a new reactivation might be triggered, and THIS might not happen immediately.

As I've said, "you" might have not changed hardware, but Windows itself might have downloaded some updates in the background that triggered a reactivation.


--- Quote ---All these problems started when I install the beta. And for the record its wasnt just GSX asking for reactivation, it was all my FB and fsdt sceneries.
--- End quote ---

Again, this doesn't have anything to do with the Beta. The activation message comes from the Addon Manager, which is (bit-by-bit) identical to the regular version, and the actual hardware check is made by the Esellerate library, which hasn't changed in years.


--- Quote ---I just dont believe that installing gsx and all the sceneries since the 7/29 and now 8/3 thats when they decided to be activated, when the activation window popped up and ask me if I want the scenery to be activated and told me that the serials were back up.
--- End quote ---

It happened, whether you believe it or not. And it can happen. And it HAS happened to other users, long before we made the Beta. If you checked the forum  for the 25007 error, you would see could always happened, even if the user was sure he didn't changed anything, and it's usually due to changes in Windows drivers that for some reasons are reported as hardware changes to Esellerate. Our software doesn't even try to understand how the hardware detection works, it simply gets a notification from the Esellerate .DLL that a reactivation check is needed, so it simply complies with it.


--- Quote ---You just seem to think your "beta" program doesnt have bugs.
--- End quote ---

It doesn't have bugs that we can reproduce, and we fixed all the bugs that has been reported so far that we COULD reproduce, WHICH IS WHY, I asked you to help us finding the "inoperative menus" bug you reported in another thread.

It doesn't have ANY "bugs" or changes in the hardware change detection process, which is totally unchanged from the old version, it was never under our control, not before, not now in the Beta.


--- Quote ---Instead you blame AV software from MS who has tons of programmers working for them
--- End quote ---

YOU blamed the antivirus, because you said it all worked after disabling the antivirus. I trust your report, but I don't have any problems with the MS Defender, and this is what I always used, and it never flagged any of our products as threats.

When I explained the Taggant system, you only report was generically "I turned off the antivirus", so I couldn't possibly know which one you used, but I tell you that Windows Defender is fine, and doesn't mistakenly detect any of our software as threats, it never did before, and it doesn't to that now with the Beta.


--- Quote ---Its safe to say that since I'm not the only one have this problem, its your program thats the problem which you need to fix
--- End quote ---

If you are referring to the 25007 error, it's NOT our program that has this "problem". As I've said, several times, the hardware detection is done by Esellerate, and we don't have the slightest idea how they do that. You said yourself that it always worked for years, so you KNOW it works.

But it can happen, and it happened to other (few) users in the years, and this was long before the beta, so the issue doesn't have anything to do with it.

When this happens, it's must be due to some changes happening in Windows, usually triggered by driver updates, that looks like the hardware has changed. But again, we are not entirely sure what's causing it, because our software doesn't even TRY to deal with your hardware.

1) Windows reports an hardware change (because of a driver update) to the Esellerate dll

2) The Esellerate dll decides this is an updated hardware, and reports to our software about the 25007 error

3) The Addon Manager displays the message, prompting to reactivate.

It's a BLACK BOX for us but, as you said yourself, it usually WORKS FOR YEARS.

And besides, could you please contact me in private indicating all your Order Numbers ? Because, I tried searching for your past orders to see your activation history, using both the email you used to register on the forum and your name, but the only orders I was able to find were your GSX order and an order for KIAH so, I wonder if you ordered under different names, because you said "all my FSDT sceneries".

And, if you still have the OTHER problem you reported in the other thread, which is the inoperative menus, we really need to setup a Teamviewer connection to check this.

devgrp:
I didnt blame the AV. I said I did as you suggested when I install your sceneries. You are the one that said to disable AV and have the AV exclude certain files before we start installing. Its clear if we have to do that, then coualt is doing something to make all AV think its a virus. I've never had to do that with any other scenery and I have plenty.

And how is installing some updates able to trigger a reactivation from your sceneries and not others. Maybe you need to work on that part of the program because installing a few updates in the background shouldnt trigger a reactivation. You're basically saying that everytime windows installs updates the reactivation script will be triggered which is unacceptable. And I've posted a video showing the unresponsive menus that I and others are having. It seems like you cant reproduce none of the problems that people report. Maybe because you are working in a controlled environment

virtuali:

--- Quote from: devgrp on August 04, 2015, 05:05:16 pm ---I didnt blame the AV. I said I did as you suggested when I install your sceneries.
--- End quote ---

But YOU said it worked ONLY after you did that. Never happened to me with the MS Windows Defender, but what reasons do I have not to believe your report ? If disabling the antivirus fixed your issue, what is the problem, exactly ?


--- Quote ---You are the one that said to disable AV and have the AV exclude certain files before we start installing.
--- End quote ---

That's what you have to do if the antivirus is the source of the problem. What do you think the exclusions are there for ? Because antivirus vendors KNOW they can catch false positives.


--- Quote ---Its clear if we have to do that, then coualt is doing something to make all AV think its a virus. I've never had to do that with any other scenery and I have plenty.
--- End quote ---

Couatl is not a scenery, so it's wrong to compare it with a scenery, it's a support program used by GSX and sceneries too, and it should be compared to something like the Flight1 module, with the difference that while the Flight1 wrapper module does ONLY anti-piracy protection, while 99% of Couatl does is totally unrelated to anti-piracy: it's a Python interpreter to allow scripting to allow any kind of interaction with objects ( GSX is written 100% in Python ), which saves a lot of valuable memory, by running externally from FSX, and it might resemble some an utility module like FSUIPC.

Guess what, if you Google for "antivirus" and "Flight1 wrapper", you'll see PLENTY of similar issues with antivirus products. ANY FSX module that has any reasons to use cryptography (would you trust a module that handles your personal details when ordering products if IT DIDN'T ? ), will be red-flagged by antivirus.

And the reason is very simple: when a module is encrypted against any tampering, the antivirus CANNOT "peek" inside it, to check if it's REALLY dangerous, because that's the whole point of being encrypted against any tampering. So, to err on the safe side, the very fact of being encrypted against any tampering is considered enough proof to report a virus, because the antivirus CANNOT tell the difference, since it cannot look inside the executable.

WHICH IS WHY, the Taggant system has been proposed, to allow legit authors to digitally sign their executables to be recognized as safe and still being able to use encryption against tampering, which is becoming mandatory for any executable that has to deal in *some* way with users private data.

WHICH IS WHY, we immediately adopted the Taggant system, but we cannot be sure how fast all antivirus will recognize it, because the first commercial working implementations of it has been released quite recently.


--- Quote ---And how is installing some updates able to trigger a reactivation from your sceneries and not others.
--- End quote ---

Because our sceneries ( and FB ) use Esellerate, and not others. Besides, you still haven't replied to my request (in private) to send me a list of all your past orders, so I could check your activations and when/how they happened. As I've said, I couldn't find any other orders for FSDT sceneries other than KIAH so, I wonder if with "all my FSDT sceneries" you meant JUST KIAH, or you have other orders, maybe made under a different name or email.

And no, I'm not asking this to question your report, but ONLY to see when those reactivations happened, and eventually add new ones. I ALREADY did that for GSX and KIAH (the only order I could find), so you have several spare activations left so, if you have other sceneries, it's in your best interest to say which ones, and their order numbers, so all their activations could be verified and added if you need new ones.


--- Quote ---Maybe you need to work on that part of the program because installing a few updates in the background shouldnt trigger a reactivation.
--- End quote ---

We don't have to work on anything, because we don't have any control of how what Windows drivers say to Esellerate, which is doing all the hardware detection. It anyone had to work on this, it should be Esellerate, but since their .DLL is used by hundreds of products, even unrelated to flightsim or games, if this was really a common issue, they would have fixed it long ago.


--- Quote ---You're basically saying that everytime windows installs updates the reactivation script will be triggered which is unacceptable.
--- End quote ---

YOU said "it worked for years". Are you saying you never, ever, installed any Windows updates before ? Surely that's not the case, so you already have proof that, normally, installing updates will not cause any problems.

But apparently, SOME of the updates that has been published these days, caused this problem, on YOUR system. Perhaps it was simply the timing of the installation of the updates, otherwise it would have happened to everybody.


--- Quote ---And I've posted a video showing the unresponsive menus that I and others are having. It seems like you cant reproduce none of the problems that people report. Maybe because you are working in a controlled environment
--- End quote ---

And I've I ASKED you to be able to check your system directly with Teamviewer, so I can run some test on YOUR system. To this request, you still haven't replied.

This clearly demonstrates that, when a real problem is found, we are trying everything to fix it, but since we cannot reproduce it, we NEED your help. But this is a real problem, the activation issue you had, IT'S NOT.

Navigation

[0] Message Index

[*] Previous page