You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no logging to text file during the Windows Launcher portion of the installer, this can make it hard to debug issues with installer startup.
Specifically for the text-mode/recovery installer, if there is an error while running the launcher (for example, a severe python error or a file missing), the text window will just close immediately, which again makes it hard to debug issues.
The text was updated successfully, but these errors were encountered:
I have partially fixed this issue in 6461a12 - the fallback install launcher previously would just exit once the python script exited. It will now pause on exit so you can at least read the error messages if something went wrong.
Currently there is no logging to text file during the Windows Launcher portion of the installer, this can make it hard to debug issues with installer startup.
Specifically for the text-mode/recovery installer, if there is an error while running the launcher (for example, a severe python error or a file missing), the text window will just close immediately, which again makes it hard to debug issues.
The text was updated successfully, but these errors were encountered: