Fix Windows pre-release bug

[maltfield]

This issue will track the effort to fix the latest pre-release runtime errors in Windows

[maltfield]

Context: I did a lot of work last year to fix the builds on macos, update the dependencies, and let users choose their own fonts (accessibility). We got close to a release candidate, but iirc the latest pre-release (built a little over a year ago at this point) had a runtime bug on Windows.

Let's fix that bug and see if we can then release v0.8

[maltfield]

Well, I did get the error to display briefly (also I noticed that the hamburger menu was missing on the top-left of the app), but when I tried to re-open it after the crash, Windows refused to launch the BusKill app. It said:

Operation did not complete successfully because the file contains a virus or potentially unwanted software.

Likely some bullshit false-positive, unless GitHub really did serve me something malicious..

Windows notifications said Windows Defender found Trojan:Win32/Yomal!rfn

[maltfield]

Apparently this false-positive was also found in vim. Good job Microsoft..

• Windows Defender detects Trojan:Win32/Yomal!rfn in gvim_9.1.1039_x64.exe vim/vim-win32-installer#366

They even had to add to their FAQ that this is so common:

• https://github.com/vim/vim-win32-installer/wiki#the-installer-contains-a-virustrojanermalware-what-should-i-do

I mean, if Microsoft gave me some way to investigate it (like and "advanced" or "more info" button where it told me that some signature X was found in some file Y), then I could take this seriously. But since Microsoft Defender is well-documented to be absolute untrustworthy, non-transparent, and false-positive crap, I'm just going to ignore this.

[maltfield]

The solution to the Windows Defender false-positive is to quickly tap the notification toast popup, then change the radio button on the Windows Defender window from "Quarantine" to "Allow on Device"