<rant>
Then stop shoving a banner at us telling us to upgrade. Until you know the product is actually fully functional and 99% stable, don't put it front and center as if we 'have' to update.
This is almost identical to what Sonos did:
- Push an update as if 'required'
- Act as if it's the best thing since sliced bread and how it's a completely new and better system
- Don't properly even QA it for assurance that upgrades will even work
- Don't offer feature parity with the system it's replacing
- Gaslight users as if their usage of plugins and using it to manage their systems is their fault for it not working / covering it up as 'known issues'
I'd be less annoyed if it were not for the fact the last major upgrade I did with WAC over two months after it went GA had very similar issues, stopping it from even properly upgrading. That should be a fundamental requirement for it to go GA is ensuring you've covered the majority of use cases - and as mine is NOT that custom in any way shape or form, I know that two failures in as many main upgrades is indicative of shoddy QA and program oversight.
More: This is Microsoft's replacement for MMC applications on prem - invest into it properly. Don't act as if it's 'free' - we pay Microsoft a SH!T ton of Money per year for our on-prem systems and get less and less actual development every cycle. Azure isn't included in what we pay for SA, and our SA benefits are worth less every release cycle. We're not seeing major improvements on most of the core Windows Server functionality, instead 90% of the R&D is tied directly into shoving us into Azure services or tying us into Azure/Cloud hybridization - which isn't included in our SA/OnPrem costs anyways!
</rant>