24 years ago my company moved from mac to windows (granted macs would crash every 20 minutes). At the time we were given a windows laptop to try for a bit, with the rollout a month or so later. When I went to shut it down I asked how to... 'press start', I was told. I thought 'nope, they still don't get it... pressing start to stop... send it back to them and tell them to try again and harder'. Its still true.
That old joke ... But i have a solution for you: You could use that fancy thing called a "power button" - no joke, it will actually help you in turing of the computer - or do you want to only start it with this button?
Jokes aside: cmon, its not a big deal to open the windows menu to power of the machine. The Word "Start" is now missing since Windows Vista which released 2007 - nearly 15 Years ago!
More in reply to the comments than the original article....
In my experience no developer ever actually imagines that their code could possibly have bugs. Yes yes, they will say that of course all software has bugs, but deep down they know that that doesn't mean their code, just other's code. Turn all that code into products and that means when something goes wrong it isn't the product's fault. Therefore it must be the user's fault.
Error messages can't possibly explain the problem, because the product can't know what the dumb user did. So don't bother really trying.
This from the perspective of someone doing customer support.
