3 ms·

And if you are not present at the screen, it ass-u-mes "where do you want to go today? Wait, that's not up to you: Windows X it is!" Very useful when employees

And if you are not present at the screen, it ass-u-mes "where do you want to go today? Wait, that's not up to you: Windows X it is!" Very useful when employees turn up for morning shift to find a Brand New Os. Which doesn't play well with hardware (because the HW vendor is still working on a WinX driver). Which was the reason the upgrade from Win7 had not been greenlighted yet. But hey presto, all great and good; never mind that a company can't do its business; that's not a problem for MS, here's your bunch of broken boxes, and that's your problem now. We got what we wanted, screw everything else: https://lh3.googleusercontent.com/-hkAhasCtTg8/Tny1nldYIFI/AAAAAAAAAGc/KcSFrDNv2xs/w506-h419/computer%252Cdesign%252Cimages%252Cphilosophy%252Ccomputers%252Ccartoon-c020938493360a30c06cc73132112e7d_h%255B1%255D.jpg https://lh3.googleusercontent.com/-hkAhasCtTg8/Tny1nldYIFI/A... And yes, this is exactly what "spent trust" is: orders came from On High to take off, nuke the site from orbit, repave with Win7 images, and never ever let Windows Update touch the boxes again (!): MS is now, by executive fiat, considered rogue ("we literally cannot afford another Windows X infection, WU is now an attack vector"). Everybody loses (except for that guy at MS whose bonus hinges on number of finished WinX installs; btw if he's reading this: you are, personally, a reason why we can't have nice things): security is undermined by no more patches, man-months are wasted on getting stuff to work again, there's plenty of MS-directed anger, customers are angry at company, not to mention we won't get WinX anytime soon, if at all. Whether anyone is willing to convince the mgmt that they've overreacted over MS's overeager installer is left as an exercise to the reader. (The "close-as-yes" is also not "an issue", it is not mere "bad UI" - that is black-hat UX (and oh, very much against MS's own UX guidelines, hello hypocrisy!); deception, plain and simple.) ((The mix of app styles is but a minor quirk; and for really oooold apps, there's Virtual PC anyway.))

WorldMaker 10y ago
«The "close-as-yes" is also not "an issue", it is not mere "bad UI" - that is black-hat UX (and oh, very much against MS's own UX guidelines, hello hypocrisy!); deception, plain and simple.» I don't attribute that to malice but an honest mistake. I think there was a combination of engineering pride involved ("Why wouldn't people want to upgrade as soon as they could?") and engineering obstinacy ("We don't want another XP!"), perhaps even more than that marketing metric everyone thinks they were focused on. As for the anecdote of the business outage. My condolences. It sounds like the HW vendor should have done a better job at messaging to Microsoft that their existing hardware driver was not testing compatible with Windows 10 (and maybe a better job at their driver in general). Also, companies had the options to use System Center and Group Policy to drive GWX away, and admittedly that's not an easy admin task, but generally something companies should do for mission critical PCs anyway. (Not to mention that GWX is/was different on Enterprise SKUs and possibly a sign your anecdotal company was using not properly licensed Home or Pro SKUs on mission critical machines.)
- Piskvorrr 10y ago
  See? "Blah blah blah not MS problem (plus a poorly veiled accusation of piracy, to add insult to injury)" Anyway, doesn't matter now if the GWX fiasco was malicious or not. Damage is done.
  - WorldMaker 10y ago
    Sorry, was not accusing of piracy, only possible ignorance. I've worked with companies that didn't know the difference between Home and Pro and Enterprise SKUs and I don't think everyone realizes how many small and medium sized business run on Windows Home editions. Windows is a huge ecosystem and there is a lot of blame to pass around in every direction. I admitted that it was an MS problem, but I was also trying to point out that it was an ecosystem problem too. (There hasn't been a major driver architecture change between Vista and 10 and it blows my mind how many drivers needed new releases every Windows version between Vista and 10 and weren't just magically compatible.) Apologies if that point did not come across well.
    - Piskvorrr 10y ago
      Thank you for the clarification; my apologies for venting at you as if you were MS. There were ways that the organization should have blocked the upgrade better; and I agree that the need for new drivers where old ones ought to be fine is definitely not MS's fault.

WorldMaker 10y ago

«The "close-as-yes" is also not "an issue", it is not mere "bad UI" - that is black-hat UX (and oh, very much against MS's own UX guidelines, hello hypocrisy!); deception, plain and simple.» I don't attribute that to malice but an honest mistake. I think there was a combination of engineering pride involved ("Why wouldn't people want to upgrade as soon as they could?") and engineering obstinacy ("We don't want another XP!"), perhaps even more than that marketing metric everyone thinks they were focused on. As for the anecdote of the business outage. My condolences. It sounds like the HW vendor should have done a better job at messaging to Microsoft that their existing hardware driver was not testing compatible with Windows 10 (and maybe a better job at their driver in general). Also, companies had the options to use System Center and Group Policy to drive GWX away, and admittedly that's not an easy admin task, but generally something companies should do for mission critical PCs anyway. (Not to mention that GWX is/was different on Enterprise SKUs and possibly a sign your anecdotal company was using not properly licensed Home or Pro SKUs on mission critical machines.)

Piskvorrr 10y ago
See? "Blah blah blah not MS problem (plus a poorly veiled accusation of piracy, to add insult to injury)" Anyway, doesn't matter now if the GWX fiasco was malicious or not. Damage is done.
- WorldMaker 10y ago
  Sorry, was not accusing of piracy, only possible ignorance. I've worked with companies that didn't know the difference between Home and Pro and Enterprise SKUs and I don't think everyone realizes how many small and medium sized business run on Windows Home editions. Windows is a huge ecosystem and there is a lot of blame to pass around in every direction. I admitted that it was an MS problem, but I was also trying to point out that it was an ecosystem problem too. (There hasn't been a major driver architecture change between Vista and 10 and it blows my mind how many drivers needed new releases every Windows version between Vista and 10 and weren't just magically compatible.) Apologies if that point did not come across well.
  - Piskvorrr 10y ago
    Thank you for the clarification; my apologies for venting at you as if you were MS. There were ways that the organization should have blocked the upgrade better; and I agree that the need for new drivers where old ones ought to be fine is definitely not MS's fault.