My primary ZTW.HST file has become corrupted, not sure if the cause was me or ZTree, so leave me to investigate that part.
Possibly the corruption was caused when I was doing lots of resize by frame testing, I first saw at start-up warnings about unrecognized entries from then.
Now I know what to look for I might be able to find the cause of the corruption.
What is the path length limit of pn= entries? From what I acan guess the corrupted were ~62 long.

There are a number of broken pn= entries, the "?" are random Unicode characters.
pn=D:\xxxxxxxx\xx?????
pn=D:\xxxxxxxxxxx?????
pn=D:\xxxxxxxx\xx?????
pn=D:\xxxxxxxxxxx?????
pn=D:\xxxxxxxxxxx?????
pn=D:\xxxxxxxx\xx?????
pn=D:\xxxxxxxxxxx?????
pn=D:\xxxxxxxx\xx?????
pn=D:\xxxxxxxx\xx?????
pn=D:\_
pn=D:\xxxxxxxx\xxxxxxx



[Bug]
with the corrupted ZTW.HST, ZTree not installed under "C:\Program Files" and starting ZTree like this
pushd %APPDATA%\ZTreeWin
c:\...\ZTW64.EXE /M /MAX:-2:-1 /TZ /TV /Y /ZM (some directories)

* to log a branch
[B]ranch
crash

If I use notepad to remove the corrupted ZTW.HST entries and rerun ZTree then no crash.


Thanks
Ben