New
#100
Typical example of poor MS software engineering
Typical example of poor MS software engineering
Haven't had any of those problems even in the newer update.
Why is that? Isn't up to users to decide what version do they want to use? So they can use the version that does work and does not trip anything out of the blue?
Alas! Do we need this multiple versions?
(I can continue like that for some time, but these questions have been asked an no credible answers were provided...)
For reference: My work Surface Laptop just only got updated to 1809 quite recently - and works absolutely fine, and did so in receding year with 1709 on-board. Seems this approach does work? And I really neither notice nor am aware at all of any of these 'must-have brand new features' added from 1709 onwards to 1909 inclusive...
Well...I've been litterally working on installing and upgrading hundreds of machines, all with different configurations, different brands and from different eras, the last 3 months and they've ALL worked perfectly with latest updates. Not even one device has had any issues what so ever.
There's some food for though! ;-)