This issue happens because you have a non-ASCII character in your username. Historically, the way to get around this has been to just create a new user profile on your machine without ASCII characters. However, we are about to release LBT 1.5 in the next few days, which we’re happy to say is the first release to have full support for non-ASCII characters. So you could use the old workaround or just wait a few days until we officially release LBT 1.5.