>>We no longer support windows XP
We are not using Window XP as our build environment, but some of our customers are still using Windows XP. That is the reason we can't upgrade to the latest enveloping tool.
>> It is a recommendation from our side to use the latest tools for the users.
>> Hence, we hope the concern is sorted as of now.
But why is one out of 15 developers keys suddenly shown as a masterkey, while all others show the CRCGK vendor id. Is the dongle almost dead? Is there a battery inside or flashmemory inside, which got corrupt.
We cant depend on the developer keys, when suddenly these dongles can start new behavior.
So is there a way to get my developer key, to behave as it has done before?