Virtual environments are really not viable for music production. Latency and other inconsistensies makes it a no-go.

High level Music production requires very low audio and input latency in addition to consistent and 100% accurate sound reproduction.

A virtual environment is a wildcard here that I at least would not bother trying to make work. (Not saying it can’t be done, just saying it would potentially be a big headache and extremely conditioned on spesific hardware, drivers and configuration settings.)

It’s not the guy in the trenchcoat next to you you need to worry about.

It’s the fact that some unknown entity owns/has set up the WiFi.

Anyone working with complex network setup and admin will tell you how much you can abuse owning the network a user is connected to.

The network guys at work never use public WiFi, not hotels or anything. Neither do I, even with my much more limited knowledge of network administration.

Breach of trademark, not copyright, whole different barrel of fish.

The thing is… I think a lot of people don’t know that they have uefi support…

I have had the same windows install and motherboard (AMD is so great with long term socket support) for years, and figuring out how to change my bios and os setting so that I got a propper uefi boot was non-trivial.

Uefi has been a thing for a long time, but it’s not been the default for motherboards afaik. So you have had to go into bios and find the right settings.