-
Notifications
You must be signed in to change notification settings - Fork 196
[BREAKING] "Invalid option a", due to Win11 Default Terminal Swap #792
Comments
I believe the underlying Windows change is this: Classic Console API vs Virtual Terminal Sequences. There's logic to check the process ID against the "console" that started it that uses calls like GetrConsoleWindow that don't have a virtual terminal equivalent. |
Any word on this? It's a breaking bug for Win11 to those that use Windows terminal. At one point, Win11 prompts if you want to permanently switch, and there's 0 reason not to (to those that do not know about this bug) as it's superior in every way. |
I confirm the issue and strange behaviors at startup on Win11 computers. Didn't know it was linked to Windows Terminal (I have it on default too). I noticed that whichever way I try to start nzbget it will fail on that parcticular computer/setup. Either by opening a .nzb file or by starting nzbget from the start menu or from a shortcut or directly the nzbget.exe file. Note : Starting nzbget with "Run as administrator" seems to bypass these issues and launch correctly. |
Hmm, this should probably get a priority bump:
CC @hugbug |
I've figured out a workaround that allows you to keep the new Terminal as default. Create a shortcut to nzbget.exe and put it anywhere. Right click > Properties, and in "Target" add Then you can put the shortcut in the startup folder (go to 'Run' and type in A note: You might have to first run the program with the old console set as the default so it can get the config set up or something, not sure, I forgot to test. Then after you get it to running you can change the default terminal back to the new one. |
https://devblogs.microsoft.com/commandline/windows-terminal-is-now-the-default-in-windows-11/ |
https://forum.nzbget.net/viewtopic.php?t=3910
Win11 offers to default your terminal to the fancier (and superior) Windows Terminal. This breaks NZBG completely. Easy to repro. See thread above for further details.
The text was updated successfully, but these errors were encountered: