Fixed in v.59 
Bug
Confirmed. But I have no idea why the behaviour would be different between (i) starting up in fullscreen and (ii) starting up in borderless and changing to fullscreen later.
It’s possible your computer entered some kind of sleep state while you were away (which would explain the error).
Fixed in v.59 Bug
Acknowledged. Won’t fix.
Noted. You say that setting windowed mode directly works, but not when you try to change to it from within the game? Odd. Perhaps it’s related to the full-screen issue above.
It’s actually oscillating between hitting and missing the barrier (because your spacecraft kicks back when you fire). There was a post a while back about the same issue. Can’t be fixed.
Are you running fullscreen/borderless/windowed? Please try all 3 options and report back if anything helped.
If you place DLLs in the game folder, they will override the system ones (provided they have the same names). This is a general Windows feature, it works for all applications. But you need a DirectX 11.0 replacement (d3d11.dll) – plugging in Vulkan DLLs is definitely not going to work.
Free system memory, GPU type, GPU memory, and desktop resolution.
I haven’t look at them in detail yet, but I see several people running the game on integrated Intel GPUs with 64MB VRAM, so… 
Added to v.59 Idea
That’s actually not possible in the way the groups are implemented. I tried adding a protective bubble. It kinda works (although bubbles sadly don’t block AoE) Idea
Not really sure what the problem is.
Technical simplicity and better user experience. Showing the list (even with a single squadron) also allows you to cancel the operation (there’s no confirmation when you click the button).
Yes.