I had a response back from both Launchbox support and LEDBlinky support.
Launchbox support
LEDBlinky implementation hasn't been touched for about 2 years when a fix was put in to reduce some kind of slowdowns. Nothing has been touched since then, but there's always a possibility that LEDBlinky, or some other program it relies on changed, which could have caused our integration to stop working. We haven't heard of anything like that, and there's enough users that utilize the LEDBlinky integration that if we did break something for everyone, we would have definitely heard it
LEDBlinky support
I wonder if this has something to do with file permissions on the LEDBlinky folder? Maybe somehow the LaunchBox config app is unable to read the files in the \LEDBlinky folder? Or maybe something is going on with your virus protection software? I’m really just guessing here. But regardless, when you configure LaunchBox and select the LEDBlinky executable, absolutely nothing happens on the LEDBlinky side, so whatever the issue is, there’s nothing LEDBlinky is doing to cause that error. I see the response from the LB support guy but it seems like he doesn’t understand that this error is occurring from the LB configuration app, not when running LEDBlinky. Sorry I don’t have an answer. Maybe the LB forum can help?
I was going to drop roll back on a version or two of launchbox but if your getting a similar error then I dont think rolling back will make any difference.
Im going to check LEDBlinky suggestions and then roll back LEDBlinky version to see if that makes a difference. If none of these work then Im stumped.
Just out of interest what version of LEDBlinky are your using?