Page 1 of 1

xyPlorer crash @ "new tab" and settingd

Posted: 17 Feb 2022 23:30
by memyselfandi
Hello "user forum" ;-)
and hello xyplorer developers?

Let's get it straight from the start:
I have a paid version of xyplorer (Pro, Lifetime licence).

I have to turn here with a problem that xyplorer has been giving me for quite some time.

The problem is a reproducible crash of xyplorer when generating a new TAB. Furthermore xyplorer crashes when you call the configuration (F9 or Icon).

In the status bar a text appears in red and English; something like "There is a problem with your licence-key".
There is also the behaviour that after a longer period of inactivity (meaning xyplorer was not used for a longer period of time) some "new TAB" are possible at first. Then, without any noticeable "influence", a crash occurs with the next "new TAB".

I have not found a solution to the problem either here in the forum or elsewhere on the WWW.

In the forum (here) I come across statements that the crashs at "new TAB" is an indication of a cracked version. Possibly because of the message in the status bar?

Well, as I said, I have a paid Pro, Lifetime!
Was - to ward off crackers (key generators) - something changed in the licence check that is now no longer "tolerant for legal licences", i.e. provokes these crashes?
The question is that the crashing is only noticeable with the 20s versions!

I have already tried "/fresh".
Here, too, the crash occurs reproducibly with "new Tab" and "calling up the settings"! The only exception is that the crash does not happen immediately, but after a certain time (the settings have to be restored; click-by-click). However, as soon as the 1st crash has occurred, it behaves as with my "first" installation. So crash "immediately" with "new TAB".

Even uninstalling and reinstalling xyplorer does nothing (licence data input; correct spelling; case-sensitive observed). Same behaviour as with "/fresh".
(I don't know if something is "stored" in the registry regarding the licence and I'm not looking for it).
It is also irrelevant whether the *.ini is saved in the installation folder or in the user path (User; %Appdata% [Roaming] ).


All very annoying and frustrating!!!

Is the problem known with 'legal licenses' (paid version)?
Who can help?
What can solve the problem?


Greetings


Windows 10 Home
Version 21H2
Operating system build 19044.1469
Windows Feature Experience Pack 120.2212.3920.0

Acer Aspire VN7-793G
NVIDIA GeForce GTX 1060
Intel(R) Graphics 630

Re: xyPlorer crash @ "new tab" and settingd

Posted: 17 Feb 2022 23:42
by highend
Menu - Go - Go to Application Data Folder

Make a backup of your XYplorer.ini, delete the original file.

Menu - File - Exit without Saving

Restart XYplorer, enter your license details.

If it still does crash, send your license details to support@xyplorer.com

Re: xyPlorer crash @ "new tab" and settingd

Posted: 18 Feb 2022 00:01
by memyselfandi
Hi highend.
Thanks for the answer.
It doesn't work what I expected, since it's practically the same as a new installation (or similar to /fresh).

I will then have to use the email address?!
But not today.
Fr = workday...

Re: xyPlorer crash @ "new tab" and settingd

Posted: 18 Feb 2022 13:34
by admin
The reproducible crashes you describe are typical for cracked license keys. Please contact me by email and put your license data in the top of the mail. Thanks.

Re: xyPlorer crash @ "new tab" and settingd

Posted: 21 Feb 2022 16:37
by memyselfandi
machine translated text

Hi.
The problem (the topic) can be closed [for the time being].

I updated to ver.20.90 and in this context recognized that the license code that I used when troubleshooting - my electronic "Vault" was incomplete (digits were missing).
I was able to use my "hard copy" (printout of the license code) at the weekend.
With this "infinitely many" new TABs are now possible again!

Why or however, this caused the crashes beforehand and I then entered the (incomplete) license code again (notification: "There is a problem with your license code")???
In any case, the "spiral" started with the "corrupt" code.
No matter. For today.

Will now restore my lost configurations (settings) and turn back here if problems arise again (apparently there is a certain latency with incorrect code?!?).

In this sense.