Paul,

I just went through the same last week. I spend about three weeks figuring out why my application would crash under Windows 10 at clients but did not in our lab.
Finally I got a crash report pointing to a DLL in the temp folders which when I opened turned out to be from the ARG command bars.

I had to re-purchase the library again (as my subscription expired). We did not have a chance yet to confirm whether it resolves the issue at the client though.
Thanks for noting that the theme is the cause. It at least is something I can forward to clients.

Walter,




>We've been running the ARG command bars control for quite a few years and it's always worked well. Unfortunately we've just run into an issue with one of our customers where this control is randmly crashing the application (VFP 9 SP2) with a C5.
>
>We are running an older version of Command Bars. They recently reported that it was crashing pretty regularly throughout the day. We eliminated as many variables as we could with no luck. Ultimately they realized (from the various Windows logs) it was happening every time the domain sync'd policies - they could reproduce the crash by forcing it via gpupdate /force.
>
>Interestingly, this app is working just fine on other Windows 10 machines. The difference was the machines it worked on had a different theme (not the default Windows theme). They also ran across this fix in Command Bars posted on the website:
>
>[-] Library crashes with "unhandled exception in KernelBase.dll" on Windows 10 (build 10586 or higher) when user changes system theme, colors and so on.
>
>So we decided to download a demo copy of this version and have them try it to see if it resolved the issue (we figured if it worked we'd just buy the upgrade). Now the app crashes immediately - basically as soon as we launch the ARG menu it crashes (not a VFP crash). I tested this on a local Win 10 machine and it worked just fine - it prompted that you had to run as Admin the first time, then displayed the ARG copyright as expected since this is the demo.
>
>We see this in the log:
>
>Faulting application name: Test.exe
>Faulting modudule name: unknow, version 0.0.0.0 Exception code: 0x4000001f Fault offset: 0x05db3351 (there are a few other fields, but they are empty or just contain the GUID reporting ID, or "unknown")
>
>It's not very useful. We've verified this happens immediately as the menu runs by adding a Y/N messagebox around the menu. If the menu is run - it crashes. If it isn't run, it doesn't crash.
>
>So we're kind of stuck. If we use the current version, it crashes when the GP is updated on some machines if they've got the default theme. If we try the updated version, it crashes immediately.
>
>ARG support has been MIA on this, so I was hoping maybe someone else has run into this and has a better fix than "change the theme"