As soon as I launch it from the tools menu WealthLab crashes.

So you've just installed v2017.06, right? I think some file may be corrupt so let's try the following:

1. Close WLP
2. Enable hidden file visibility in Windows
3. Navigate to: c:\Users\username\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Data\NeuroLab
4. Backup everything, then delete the files (should be 4 txt/xml documents by default)
5. Restart WLP

Does that help? If so, please zip and attach those files. If there are no files also let us know. Thanks.

First off there are only 3 files there:
Broad Markets.xml
Patterns.xml
RSI Periods.xml

After backing up and deleting I get the same result.
The UI looks like it shows up, the cursor stops spinning, and everything looks like it's ready to go, then a moment later Wealth Lab crashes leaving a [ Debug ] [ Close Program ] dialog up.

But the files did not restore themselves.

I then tried uninstalling and reinstalling (manually downloading and installing 2017.06) the add-in and running it all in admin mode. But same result and same files are present.

And BTW when I check for updates in Wealth Lab it says I have the current version.

I'd be happy to keep trying or debug in VS.

Thanks for the report.

QUOTE:
First off there are only 3 files there:

So no NeuroLabConfig.txt there. Makes sense. NL crashes before it's able to save the config file. We'll try to investigate.

QUOTE:
I'd be happy to keep trying or debug in VS.

If you could get us a stack trace that would be appreciated.

This is all I could get because the debugger wouldn't attach:



Not sure what I need to do to get more info.

1. Please do not use external image hosters. Always attach images straight to your forum post using "Add Attachment(s)". I've converted your raw http links into images.

2. If I were in your position I'd give this suggestion a try:

Current debbuger framework configuration

P.S. Does your "c:\Program Files\Fidelity Investments\Wealth-Lab Pro 6\WealthLabPro.config" file contain this string?

CODE:
Please log in to see this code.

Sorry about the external images. I couldn't see how to add attachments.

This is what I have at the end:

CODE:
Please log in to see this code.

And I have the latest VS Studio 2017.

Thanks but have you had a chance to try my suggestion #2?

Sorry, I'm reading that stack overflow, and I can't infer what you want me to do. ???

When attaching debugger to WealthLabPro.exe process I wanted to know whether it's possible to click "Select" and choose appropriate option. For me it correctly defaults to "Automatic: Managed (v4.5, v4.0) code" so no need in extra steps. What's your experience?

Mine says: "Automatic: Managed (v4.6, v4.5, v4.0) code"

This is as far as I could go. Attaching the debugger didn't seem to help and I had to click 'Debug' and keep pushing through until VS2017 showed me this.

CODE:
Please log in to see this code.

I'm on Windows 10. Intel 6700k. AMD Fury X. 64GB 3200 RAM

Thank you, looks helpful and makes sense. This is a low-level error (exception in a DirectX DLL), most likely your graphic driver issue. This is not a Neuro-Lab bug as it does not work with graphics directly. That's why it hasn't been reported so far by others.

Wild guess: issue may be rooted in ZedGraph (a legacy .NET 2.0 DLL which powers NL). To prove it, please install these extensions:

Particle Swarm Optimizer (PSO)
Genetic Optimizer (GA)
Extra Performance Visualizers

They all share one common trait: powered by ZedGraph. If they aren't already installed, after restarting WLP please either run a PSO or GA optimization, or enable Monte Carlo Lab visualizer, reopen a strategy window, and execute backtest. Let me know how it goes. tia.

K. Well I've been using PSO for a couple weeks without any issues. :/
Lemme check these others out.

Yeah I ran a PSO. Then switched to the Fitness Graph and no errors. :(
I'll be installing WL on another computer in the next week so I can get back to you if it works on that computer which has a different GPU.

There's a chance that it's some property like antialiasing or smoothing in NL's ZedGraph control that upsets your graphics driver. I don't recall whether it's enabled in Monte Carlo Lab or Analysis Series so you might want to give these visualizers a final try. Since it looks unlikely that they have antialiasing/smoothing, I wouldn't expect them to crash. Thanks.

On second thought, it's hardly a ZedGraph issue. NL makes even greater use of WPF controls rather than ZedGraph. I suspect a conflict between NL's WPF controls and your video driver, resulting in startup crash.

Please give a final try to MLC and Analysis Series before discarding that version in post #16. If output is charted correctly you might want to create a support ticket and we'll work it out there privately.