XYplorer Beta Club

When I tried using [Shift] [F8] to switch the tree listing on and off I got this error:

Error: -2147221008 (0x800401F0)
Desc: Automation error
CoInitialize has not been called.
Dll: 0
Proc: LW@265

Source: XYplorer
XY ver: XYplorer 20.50.0300
OS: Windows 7 Professional (Service Pack 1), 64-bit, Build 7601
Locale: 2057 (en-GB)
ANSI: 1252, ACP: 1252 (ANSI - Latin I)
Font: Segoe UI 10.5, DBCS: No
DPI: 96 (100%), 1280x1024

Date: 2020-01-22 16:54:57

Error: -2147221008 (0x800401F0)
Desc: Automation error
CoInitialize has not been called.
Dll: 0
Proc: LW@265

Source: XYplorer
XY ver: XYplorer 20.50.0300
OS: Windows 7 Professional (Service Pack 1), 64-bit, Build 7601
Locale: 2057 (en-GB)
ANSI: 1252, ACP: 1252 (ANSI - Latin I)
Font: Segoe UI 10.5, DBCS: No
DPI: 96 (100%), 1280x1024

Date: 2020-01-22 16:56:44


Error: -2147221008 (0x800401F0)
Desc: Automation error
CoInitialize has not been called.
Dll: 0
Proc: LW@265

Source: XYplorer
XY ver: XYplorer 20.50.0300
OS: Windows 7 Professional (Service Pack 1), 64-bit, Build 7601
Locale: 2057 (en-GB)
ANSI: 1252, ACP: 1252 (ANSI - Latin I)
Font: Segoe UI 10.5, DBCS: No
DPI: 96 (100%), 1280x1024

Date: 2020-01-22 16:57:12

It happened three times in succession, as above.

Closing XY and restarting it solved the problem, even with exactly the same tabs present and with exactly the same tab current.

I know Win 7 is a few days past end of support now but I doubt if that is the reason.

Can't confirm with 20.60.0400 on Windows 10 1903 x64.

Does upgrading to the latest stable version (20.60.0400 at the moment) helps?

Do you see the same problem with a fresh config?

I have now tried to replicate the same problem with 20.50.0300 and cannot. Many times on the same set of tabs and even the same instance of XY as before.

So would trying a fresh config really prove anything?

Is it the same configuration as before? If yes then it's fixed, if no then it must be some configuration clash.

The configuration is completely unchanged. I just shut XY down, and then started it again. The problem had then gone. And so far so good, it hasn't come back as yet.

Ok, let me know when it comes back (with error message -- I refined the detection grid, next version...).