Thank you for reporting this @djc5166. Looking at the logs, this is most likely caused by a session name generation. This is based on your Windows username, and looking at the code, I'm guessing that ...