3 ms·

Except it's not changing how software behaves. In both cases, clicking the Red X dismisses the notification. That's it. Nothing more. That's the UI convention

Except it's not changing how software behaves. In both cases, clicking the Red X dismisses the notification. That's it. Nothing more. That's the UI convention as it always has been. As for users not reading, that may well be the case - it doesn't mean it's not their fault. If you wanted to take aim at a screwy dialog, I'd go for the original [A]bort [R]etry or [C]ancel... This 'change' (that isn't) is nothing compared to around 75% of UIs today. Sure, lots of people are upset because something didn't do what they expected. Yup, the engineers sorting this out maybe aren't the greatest UI/UX people. To state that MS are trying to 'trick' people is the disingenuous line though. Anyway, I really can't be bothered to discuss it anymore, as (a) I read dialogs, (b) I have machines that aren't auto upgrading because I followed the methods to stop the prompts a while back, and (c) xkcd tells me it's time to stop.

exodust 10y ago
Regardless of people not reading dialog boxes, a major update of Windows can take a long time and be very disruptive. When it's done, things may look and feel unfamiliar and applications may not work. Such a significant change should not come about automatically by way of simply closing a dialog box. There should at least be one final dialog box requiring confirmation: "go ahead with Windows 10 update now? Yes/No" and if that dialog box has an X close button, it should be wired up to "no". If user clicks "yes", it would be polite to double check with "this update could take awhile, are you sure?" and supply links to a checklist of things people might want to know ahead of updating. This is undoubtedly a deceptive and aggressive UI pattern by Microsoft for their own product agenda, and the bad press is deserved.