"Check for Updates" glitch.

[81RED]

Is not working anymore since the last two betas I think:
Help/Check for Updates.
"A newer version bla bla bla...download it now?".
When clicking "YES" an Explorer.exe window opens, showing me the contents of my windows\system32 folder.

Pretty sure that did not use to happen before. 

[Jeremy Collake]

Thanks for reporting that, I will work to see how such a condition could arise.

[boco]

Just wanted to chime in, having the same problem since the last few releases. The latest beta (3.85.2) introduced a change: Now my PL program directory opens. Strangely 3.85.2 also tells me that a newer version, 3.85.2 is available, which is kinda illogical.

Process Lasso Pro, 3.85.2beta licensed, OS Windows Vista SP2.

[Jeremy Collake]

The secondary update notification for the beta is fixed, but I do not know about the other issue yet. I am still looking into it.

[boco]

Could it have something to do with http://www.bitsum.net/forum/index.php?topic=524.0? It started around the same time (3.84.3) for me.

[Jeremy Collake]

No, I don't believe it has to do with that thread. I simply changed the default from TRUE to FALSE for that, as apparently registry cleaners were killing the setting in rare cases, and then the product would check for updates. All it takes is one person to freak out and make an accusation for people to be suspicious. I suppose I should have defaulted the value to FALSE, but I do set it on install, and didn't anticipate registry cleaners deleting it.

I believe it has to do with the URL returned from the update check. If this URL points to the local file system, it would cause that behavior. That's a guess though, I haven't figured out the exact cause yet. I intend to fully investigate today.

[Jeremy Collake]

I determined the cause of the problem was a script modification on the server. It applied to registered users only. I had undid a special hack for my Japanese reseller, and when doing so, inadvertently was returning a NULL download URL for registered users (as I suspected must have happened).

I am testing the fix now.

UPDATE: Fix tested and complete. Issue should be resolved. I apologize to all those affected by this glitch. I am not sure how long it existed for sure, but too long.

[boco]

Now working as intended.

Btw. I'm too dumb to remember my forum password for more than 2 days, lol.