Currently use AutoIT and InnoSetup for installation wrappers those that don't have installers with silent support or have the ability to automate the settings. This is where BSD and Linux shine compared to Windows! Scripting and automation is built-in with the ladders and greatly lacking in the former.
The opposite happens in CMD on Windows, at least in the past.
Applications that wrote a lot to the logscreen were slowed down by it. While writing to stdout is buffered, it seems that the rendering itself runs in the same thread as the application.
Making a selection freezes the terminal and this stops the rendering, allowing the application to run much faster.
Removing the selection (by pressing escape) rerendered the window (and the buffer), and it went back to its original slowness.
To this day I still attempt never to click inside a running cmd / powershell console. Too many times script execution has been halted by this. It is probably something that has been fixed long time ago but I am still a bit paranoid about it.
It isn't a bug, you could actually toggle this behavior. Don't know how the option was called and cannot find it in Windows 11. But it certainly was still there in the latest Win10 build.
I think it was called something like quick edit or similar.
There is even an option to change the behavior so that the window doesn't freeze if you select anything. Batches freeze completely when you clicked anywhere and I found out the hard way.
Probably some feature that John requested because he couldn't read some output quickly enough. I don't understand how this can be the default behavior.
Still happens for Disk Cleanup, in a way. It can get stuck at parts, and it might finish but the window doesn't go away until you hover the mouse above it.
Observed the same, it's very annoying. I start a script to image the VM (which among others does disk cleanup before finally handing over to sysprep)... and sometimes I find the unattended VM hours later still waiting for me to move the mouse over the window.
I had an issue like this once installing windows 2000. If you didn’t move the mouse during the installation, it would hang and fail. Finally got it to install by sitting there moving the mouse.
