Many users recently complained about various issues involving the way Windows Server 2016 interacts with certain apps and platforms.
The reported problems include even things as common the Start button not working, which forces users to implement powershell coding and scripting to overcome the issue.
Is it me or does the start button in Win2016 only work 60% of the time? Noticed this on both my vSphere VMs and AWS instances.
Another user quickly confirmed he is having the same problem:
yes! this! i thought we’d fucked something at work as we have some servers where the start button randomly doesn’t work and you have to powershell whatever it is you are trying to do but it’s happening here too.
One program in particular is having problems. Azure cloud services have not been behaving accordingly, especially on Microsoft Server 2016.
Is it Azure, or is it Microsoft Server 2016?
Microsoft Azure is the software giant’s attempt at offering cloud services to help organizations with their business endeavors.
The purpose of this service is to offer users the chance to build, manage and deploy programs on a global network using whatever tools and frameworks they may have at hand.
Given that the service itself is there to offer users a means of developing their apps and getting a certain degree of exposure, having to uses lines of code on a program that’s supposed to ease the coding process seems counter-productive.
However, users compared how well Azure behaved on both Microsoft Server 2016 and 2019 and eventually concluded that the cloud service is not to blame, but rather the OS.
The update button is often unresponsive
This recent issue brought to the surface some other problems users are facing, and that would be the long waiting times when trying to perform Server 2016 updates.
Here’s how one user describes the problem:
Required updates need to be installed. Clicks button. Literally nothing happens
More so, the last time Server 2016 issues were addressed was in April 2018 along with the Windows Server, version 1803.
Because this was also the last final version to be branched off the Server 2016 codebase, it would seem that Microsoft has probably migrated its attention to the much newer Server 2019.
Another element that supports this theory is that Server 2019 has been reported to be much better optimized for the latest hardware.
Thus, the only real reason why anyone would still be using Microsoft Server 2016 is because they lack the hardware that could run 2019 properly.