XYplorer Beta Club

Hi Don,
i get the feeling that XY is going through a many bugs phase currently, triggered by the glow-up thingy.
That said, i generally like the glow-up development. But it seems to have thrown XY into beta.

Here are a few:
Version: XY 28.40.0203
scaling 100 % and 125 %
win 11
(Most bugs already exist since a few versions.)

1) A Run-time error '91' appears reliably after a (re-)start of XY and then after the FIRST calling of ::#711; (check for updates) and closing the pop-up dialog.
2) BTW that pop-up dialog sometimes looks normal sized and sometimes is extremely looooooong (wide) while keeping the normal height.
3) Also, the tool bar menu looks too camped together. When I go into settings and change the spacing in styles forth and then back to my initial spacing, it looks again normal, as I would expect. Sometimes that bug does not happen. (Maybe solved itself all of a sudden? Glad, I made that shot before it solved itself temporarily.)
4) But now I cannot even open the settings because F9 acts as if the dialog opened invisibly. XY freezes, only after I press Escape, it becomes reactive again.
(That bug is in fact new to me with this newest version.)

5) Also, the Cancel button in the customize toolbar dialog seems ... awkwardly placed.

Hi auotocart

Since you're a regular poster here, wouldn't it be time for you to read the red bit at the top of this page and do one of the strongly recommended things there?

Interesting, but unfortunately I cannot repro any of this. Is there anything usual about your system (3rd party skins, themes...)?

3rd party skins, themes... Not aware of any.

Maybe I have unusual style settings in XY, like overall spacing and line spacing set to the absolute minimum, I think it's -9 and -4? In list view I use details with thumbnails by default, file icons are hidden, font size can change from time to time but it's usually a bit bigger (15 or more).

Do you get the same issues with a fresh instance?

I was able to reproduce the following 2 bugs in a fresh 64 bit 28.40.0203 version:

1) Run-time error '91'. Same as above. What I should also note is that when closing the update-dialog, it kind of flickers in a very strange way with white rectangles appearing shortly. Then it completely disappears and the run time error dialog pops.

I also now noticed that the whole head line is missing:
fresh 64 bit: vs. 32 bit:
2) Displaced Cancel button to a degree
fresh 64 bit:
The other 3 errors I could momentarily NOT reproduce in the fresh 64 instance.

That said the cramped tool bar menu and the looong update dialog bugs come and go in my regular 64 instance, so the same might be true to the fresh 64 instance.

The settings dialog not appearing and instead freezing XY until I press Escape, is also NOT present in the fresh 64 instance -> that is ok there. Currently it is a permanent bug in my regular 64 instance. It also just happened in the latest version or my regular 64 instance (according to my observations).

Weird. Something wrong with your system fonts? "Segoe UI Semibold" works? Try to select it in the 32-bit version.

Seems to work fine in the 32 bit version.
(In the 64 I can currently not test it because I can't access the settings dialog.)

autocart wrote: ↑03 Oct 2026 14:04 (In the 64 I can currently not test it because I can't access the settings dialog.)

That might be fixed in the latest beta:

ok, thank you, at least the settings dialog in 64 bit XY pops up again.

setting the font to Segoe UI semibold seems to make no difference in 64 bit XY either.

but when I open the apply to ... dialog in the font settings and then close it, I again get that same Run-time error '91' again, this time so bad that it crashes XY completely.

With the update-dialog, it at least does not crash XY and the error only appears the first time that I check for updates.


Let me test it on my office laptop in the next days. I think the bugs are not as visible or not present at all there.
Here, on my personal laptop, were the bugs, as it seems, are more present, I have an external GPU, btw. That setting is not very common. Maybe it has something to do with that?

external GPU should not be a problem unless it is a problem

admin wrote: ↑03 Oct 2026 15:49 external GPU should not be a problem unless it is a problem

Wow, I just thought I test it out, restart my laptop with the eGPU disconnected. Bugs gone.
It is the eGPU after all. Fuck.

Or it has to do with the 2nd monitor that is connected to the eGPU and has a different scaling factor than the laptop monitor. BTW, it really is an old flat screen TV, not a dedicated PC monitor.

Ok, final conclusion:
It IS/WAS the 2nd monitor (old flat screen TV) that I had set to be the primary monitor (when connected). Now I returned to the laptop monitor to be the primary monitor again and the bugs are all gone even when the eGPU and the TV are connected.

Funny, though: The 32 bit version did not seem to be bothered by the TV being primary.