Not all items in folder are listed

[parent55]

In the target folder, Windows explorer lists 25 items (all children folders)
In the target folder, XYxplorer lists only 2 of the items (all children folders) and one is an out of date spelling (yes, I did a refresh)
I am running a fully updated Windows 10 Pro and fully updated XYplorer

[highend]

And you have no ghost, global or normal visual filter active?

Show the status bar, look if there is a blue bulb icon show which lists e.g. 2 items of 25...

[parent55]

No filters active

Btw, When I try to use "help > contents and index" XYplorer crashes

[parent55]

My Mistake, I was looking at correct folder but on two different drives. The second drive has only two folders. My apologies.

However invoking "Help > Contents and index" does crash XYplorer

[highend]

Make a screenshot of Windows Explorer showing that folder and the same for XY.
Show them both

Is the XYplorer.chm file unblocked?

[parent55]

My Mistake, I was looking at correct folder but on two different drives. The second drive has only two folders. My apologies.

However invoking "Help > Contents and index" does crash XYplorer

[admin]

However invoking "Help > Contents and index" does crash XYplorer

Run this through the address bar, what is returned?

Code: Select all

echo get("help");

[parent55]

Dialog box displays:

C:\Program Files (x86)\XYplorer\XYplorer.chm

Then I again tried Menu Help > Contents and Index
and again XYplorer crashed

Then I tried "F1" and did get the help window

Then I tried again tried Menu Help > Contents and Index
and It Worked !! ??

I closed XYplorer and started it again and tried Menu Help > Contents and Index
and It Worked !! ??

As a new XYplorer user the only way since installing that I had tried to used help was Menu Help > Contents and Index
and it crashed every time.
But now that I used F1 and succeeded to get the Help window, it works now every time regardless of how I invoke it.
Strange first timer behavior if you start with the Menu Help > Contents and Index

I guess there must be some variable or flag or path that gets set when it works the first time that persists thereafter.

[admin]

Thanks for the info! I will try to fix it in the next beta.