steven36 Posted October 7, 2019 Share Posted October 7, 2019 Remember the problematic rollout of last year's fall update to Windows 10? Microsoft would just as soon forget it happened, and hopes users do, too. As expected, Microsoft never put Windows 10 1809 on a majority of users' PCs, instead sidestepping the problem-hounded upgrade that was delayed by months earlier this year. According to AdDuplex, a Lithuanian company whose metrics technology is embedded in thousands of Windows Store apps, Windows 10 1809 powered 26% of surveyed Windows 10 systems as of Sept. 25. The decline from August was small, only 3 percentage points, yet it was the largest since the version peaked in May. Windows 10 1809, unlike its predecessors, never powered even a third of all Windows 10 systems: It peaked at 31% in May. That was at odds with its immediate precursor, Windows 10 1803, which hit 90% for a high, and the upgrade before that, version 1709, which pegged 92% before falling. Instead, Microsoft pushed Windows 10 1809 into the background, for all intents skipping past it to instead offer Windows 10 1903 to most users after it was released. That upgrade, also known as "Windows 10 May 2019 Update" (Microsoft abandoned descriptive naming at the end of 2017), got a slow start but by August was on 33% of all Windows 10 machines. A 13-percentage point increase in September pushed that number to 46%, making 1903 the most-installed version of Windows 10. The switcheroo from the usual meant that Microsoft never aggressively delivered Windows 10 1809 to its forerunner, 1803 - last year's spring upgrade - as it should have by former practice. Windows 10 1803 has plunged in its share of all Windows 10 PCs - last month it was on just 24% of the total. But the beneficiary of that decline was not the next in line (1809) but the one after that (1903). Microsoft is responsible for the shunning of 1809; it isn't something that happened organically. Why? Because through 1809's release - originally slated for October 2018 but effectively delayed until early 2019 because of problems, including data loss experienced by customers who upgraded before the company shut off the spigot - Microsoft was the sole determiner of how quickly a feature upgrade was adopted by unmanaged PCs. Because it declined to follow its own up-to-then rules, millions of Windows 10 users were left running 1803 rather than upgraded to 1809. That was a problem because the former was scheduled to fall off the support list on Nov. 12, 2019, at least for Windows 10 Home and Windows 10 Pro users. And if they weren't running 1809 they were soon going to be forced to upgrade to something else. Like 1903. Normally, that wouldn't be a problem: There was plenty of time between May 21 - when 1903 debuted - and Nov. 12 to push that version to everyone, including the people running 1803. (Remember, the six-month interval between those two dates was exactly the same as the usual six-month stretch between feature upgrades.) But Microsoft had monkeyed up the cadence by, in April, suddenly handing to users a considerable amount of control over upgrade timing with the "Download and install now" option in Windows 10 Home (and Windows 10 Pro users who relied on Windows Update). The option let them decide when to download and install a feature upgrade, a responsibility Microsoft had jealously guarded. Ironically, by giving users upgrade oversight, Microsoft threatened to completely upset the release schedule. Could Microsoft assume that users would upgrade in time so that they stayed in support? No. Why not? Because users had never voluntarily migrated from one version of Windows to another version in such a short amount of time. Instead, they took years to affect a voluntary change. (Don't believe it? Just look at the time it's taken to reduce Windows 7 from its 2015 peak of 61%.) Faced with the choice between a) giving Windows 10 users, all of them, including Home and Pro, freedom to choose their upgrade moment and b) total chaos, with huge portions of Windows 10's consumer base unsupported, unprotected and under attack from hackers, Microsoft did the right thing and picked the former. But it needed a mechanism to keep the chaos at bay. That's why the company reserved for itself an exception to "Download and install now." It would intervene and initiate an auto-install when the version on the machine neared end of support. Microsoft announced the start of 1803-to-1903 forced upgrades on July 16 or four months before 1803's slated retirement. The AdDuplex data reflected that, with 1903 climbing 5 points in July (while 1803 declined just over 4 points) but exploding with gains in August (up almost 22 points, as 1803 fell by almost 21 percentage points). Notice the nearly tit-for-tat gain/loss when comparing Windows 10 1903 and 1803, another sign of Microsoft's "interference" in the upgrade of the former. With less than two months before Windows 10 1803 leaves support, Microsoft still has work to do, although that work looks manageable. Undoubtedly, there will be some running 1803 after the support deadline, including PCs that cannot be upgraded because of unresolvable issues or those Microsoft doesn't address in time. (Check here for the most-current list of blocking problems.) Interestingly, the biggest takeaways from the entire skip-1809-and-go-directly-to-1903 muddle was Microsoft showing customers that it is possible to blow by one of the every-six-months feature upgrades. And that the idea that every feature upgrade needed to be accepted and installed to serve the Windows-as-a-Service (WaaS) model was on a shaky foundation. And that customers would first tolerate, then embrace, the rapid release tempo. And finally, it showed that Microsoft can be a master in making lemonade from lemons, or at least convincing customers that what they had in hand was lemonade. Data from analytics vendor AdDuplex shows that Microsoft's forced upgrades from Windows 10 1803 to 1903 has been successful so far and that skipping the intervening 1809 worked. (Data: AdDuplex.) Source Link to comment Share on other sites More sharing options...
steven36 Posted October 7, 2019 Author Share Posted October 7, 2019 I told everyone this a few months ago that Microsoft was ignoring this version , While it was riddled with bugs the whole time most people except for update seekers were never on it. Seems after 4 years people would have learned not to seek upgrades. Link to comment Share on other sites More sharing options...
zigzag Posted October 7, 2019 Share Posted October 7, 2019 MS force upgraded me from Windows 10 build 1809 to Linux. This was successful. Now i am free of MS upgrades. Link to comment Share on other sites More sharing options...
steven36 Posted October 7, 2019 Author Share Posted October 7, 2019 2 hours ago, zigzag said: MS force upgraded me from Windows 10 build 1809 to Linux. This was successful. Now i am free of MS upgrades. Did you go cold turkey from windows to Linux ? That not very long to be using Linux but we all started on some date , i started out migrating to Linux soon after the 1st release of Windows 10 TH1 in 2015 dual booting , every release i used it less and less so when Redstone 4 came out i wiped Redstone 3 off my computer and installed Windows 8.1 back that came with my computer and put Ubuntu on it . I can count the times i booted into windows on one hand in the last year and some change . 525 days today i been Windows 10 free . Edit:I was hoping Windows 10 was going to be problem free OS like Windows 7 and 8.1 and was excited about it and was going to buy it but after i seen how much trouble it was because it was free it was hard to customize to my liking programs to fix it and things break with new versions and cost money because the cracks were never updated plus upgrades are very time consuming . I rather use my OS than talk about it so started using OSes that don't need fixed so often . Some people pirate LTSB so they dont have to , but for me i done it the legal way. Link to comment Share on other sites More sharing options...
zigzag Posted October 8, 2019 Share Posted October 8, 2019 I think i started using Linux more frequently with Windows XP in dual boot. Eventually i used windows less with every boot. Later i get rid of Windows when Windows 10 take too much effort to fix. The LTSB not so good when you need Windows Store apps for Microsoft Exclusive titles. I choose Win10 Enterprise or Win10 Education version over any LTSB version. Link to comment Share on other sites More sharing options...
zanderthunder Posted October 8, 2019 Share Posted October 8, 2019 For Surface Book 2 owners, they have to remain on v1809 update because dGPU driver bug that prevents them to upgrade to v1903. And sadly, no news yet on the bug tho. That means, they can't yet fully ignore 1809 yet. Link to comment Share on other sites More sharing options...
zigzag Posted October 8, 2019 Share Posted October 8, 2019 I read that Surface products cannot be repaired easily. Better if people not buy products that planned so fixated. Link to comment Share on other sites More sharing options...
steven36 Posted October 8, 2019 Author Share Posted October 8, 2019 29 minutes ago, Edward Raja said: For Surface Book 2 owners, they have to remain on v1809 update because dGPU driver bug that prevents them to upgrade to v1903. And sadly, no news yet on the bug tho. That means, they can't yet fully ignore 1809 yet. Surface Linux: Penguins like nice things too. - Reddit yes you can you just put Linux on it and use it instead. Link to comment Share on other sites More sharing options...
zanderthunder Posted October 8, 2019 Share Posted October 8, 2019 1 hour ago, steven36 said: Surface Linux: Penguins like nice things too. - Reddit yes you can you just put Linux on it and use it instead. Not without some caveats tho. Also not recommended for noobs. https://www.reddit.com/r/SurfaceLinux/comments/6eau79/current_state_of_surfaces/ (This guide not fully updated yet with latest informations for newer-generation Surface devices and newer Linux versions.) Easy to say, hard to execute. Link to comment Share on other sites More sharing options...
steven36 Posted October 8, 2019 Author Share Posted October 8, 2019 1 hour ago, Edward Raja said: Not without some caveats tho. Also not recommended for noobs. https://www.reddit.com/r/SurfaceLinux/comments/6eau79/current_state_of_surfaces/ Easy to say, hard to execute. Not really that hard for a experienced Linux User .A noob wouldnt even be able to maintain Windows 10 with all the bugs let alone Linux on a Surface . Just sell your Surface to a noob and buy you a Dell with Linux or install Linux on it and call it a day . I wouldnt buy no hardware made by no big tech company to begin with but some use Linux on all of them .Google is even making it more easy to install Linux on older Chrome Books. Quote Linus Torvalds uses the Dell XPS 13 for development. My daily diver is also a Dell also I have a Gateway AMD Box with Linux . Intel and AMD has built in open source drivers in the Linux kernel . Ubuntu the latest releases have built in closed source nvidia drivers and its backported to the driver install manger in 18.04 LTS. I had my share of caveats with my Gateway AMD Box with Linux-in the past when AMD was making the transition from closed to open source drivers in Linux like i could not boot in Ubuntu 16.04 it was not nothing i could not overcome I just installed Manjaro witch was still patching the closed driver and i know a lot more about Linux now than i did then stuff like that just helped me to learn and now AMD fixed it in 16.0.4.3 so its all years ago in the past . When i 1st started using Linux i use to tripe boot Windows 10 , Linux Mint 17.3 and Manjaro on my AMD PC All i did back then in my spare time was study how to fix software i had 3 OSes i had to set up and overcome any bugs,. Then I stop distro hoping and started using just Ubuntu Linux so ive not reformatted in over a year , one day i will test some new stuff if i ever get time. Before that i posted and tested software in Windows for years so it was easy for me to catch on to Linux. I had to swallow my pride and become a noob again as in Linux after years of learning about Windows was all. After Microsoft put there head in the cloud and started putting mobile apps on PC i lost interest in that scene , Link to comment Share on other sites More sharing options...
zanderthunder Posted October 8, 2019 Share Posted October 8, 2019 Nonetheless, it's a free will to choose. I rest my case here. Link to comment Share on other sites More sharing options...
steven36 Posted October 8, 2019 Author Share Posted October 8, 2019 4 hours ago, Edward Raja said: Nonetheless, it's a free will to choose. I rest my case here. I bet you when they bought it they had no idea that Microsoft was going to block them from installing a new version of Windows 10 because of NVIDIA BTW there is a Fix in insiders now that fixes the problem were you can now upgrade your version of Windows 10 info posted here OCT 7 2019 yesterday https://answers.microsoft.com/en-us/surface/forum/all/surface-book-2-gpu-driver-disappears-randomly/57233544-e262-45bb-a6a6-0d04197b7498?page=36 Quote This fix will be generally available through Windows Update as soon as it completes our quality testing. Microsoft Surface Laptop 2 gets bad reviews in 2019 for the price they want its not worth it. https://www.digitaltrends.com/laptop-reviews/microsoft-surface-laptop-2-review/ NIVDA drivers has been problematic off and on Windows 10 since day 1 so its not just a problem on Linux. Good to see there moving away from them https://community.amd.com/community/amd-business/blog/2019/10/02/microsoft-takes-pole-position-in-laptops-based-on-amd-technology Link to comment Share on other sites More sharing options...
zanderthunder Posted October 11, 2019 Share Posted October 11, 2019 On 10/8/2019 at 5:33 PM, steven36 said: BTW there is a Fix in insiders now that fixes the problem were you can now upgrade your version of Windows 10 info posted here OCT 7 2019 yesterday https://answers.microsoft.com/en-us/surface/forum/all/surface-book-2-gpu-driver-disappears-randomly/57233544-e262-45bb-a6a6-0d04197b7498?page=36 Well, I guess the issue is solved, for now. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.