No logging during Windows Launcher portion of install / text mode installer window closes immediately on error

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.

Look at the Windows Launcher code in the installer, likely in a Python script or JavaScript module that handles the text-mode/recovery installer. Start by finding where the launcher initializes and where errors are caught. Add file logging to capture startup events and ensure error messages are written before the window closes. Test by simulating a missing file or a Python error to verify logs are created and the window stays open long enough to read the error.

Written by the indexing model from the issue text.