Someone had a problem with installation, which is obviously kind of important. To replicate I deleted the whole directory and re-installed -- and it just worked. Can't reproduce the problem.
So I read through the install process with the error in mind. It can't find pyfiglet which is jumbo weird. I am using some trixy business to make the venv work regardless of the directory it is installed into. Generally speaking you can't pick up a venv and plop it down somewhere else; you create a new one and install whatever is needed inside it.
The trixy stuff starts in win_install.ps1, a powershell script run by the installer to do the python module installations. I think this is where the problem is. It used system python (py on windows) to make a "path.json" file that includes the absolute path of the installation directory. If system python does not exist it probably just fail and keeps trucking.
Longwinded, but I have reason to believe this version with the minor change of using the python inside the venv to create path.json has a chance of resolving the problem. The alternative is to virtualbox a clean windows and try the installation there. PITA. I hope this works.