Right now, no, I can’t just confirm that because I need to give a new version of the affected server to my own users and that can only happen if they are willing to participate.
Also, I don’t think I can use .1628 directly because of what I reported here: EROBaseAsyncSocketError: Response already sent - #7 by EvgenyK
Anyway, I’ll contact my users and see what comes up with that, but in the end, I’m convinced that there is more to that situation than just the changes to cbCleanup that were introduced with .1628