@peter_vw Your error looks similar to the one I experienced. It turned out I wasn’t using the latest patch version of Python. I was stil on 3.10.8, while 3.10.11 was the latest 3.10 version.
Despite what @kvangiessen proposed in that topic, we later encountered exactly the same issue on a colleagues computer. That was also fix by upgrading 3.10.8 to 3.10.11.
But come to think of it: Maybe the viktor-cli install be both executed after installing the new Python patch version was the actual fix 