Are you a Windows 1 in 10 (1809)? Or a mighty 80 percenter (1803)? With the next release of Windows 10 edging closer, users continue to steer clear of Microsoft's October 2018 update. Figures published by ad slinger AdDuplex show that the Update of the Damned, aka the Windows 10 October 2018 Update, has dribbled its way onto 12.4 per cent of Windows 10 PCs sold. It's a far cry from the near …
Yep, it's empty, I must be on Windows 10 1809.
(Note too, if your Downloads folder has files still, you obviously haven't yet cleaned up the previous 1803 version of Windows, by running the Disk Cleanup Tool and selecting every option)
(There's no warning on the subtle change to the Disk Cleanup tool in 1809, Microsoft just thought they'd helpfully add YOUR Downloads folder to the list of locations).
Microsoft interns have obviously taken over the asylum.
The only positive, is you can now lock down Windows 10 privacy/permissions, so Microsoft (or Apps) can't go anywhere near your stuff, and FFS, they sell it as though they are giving you something. I suppose we'll have to wait and see if those privacy permissions survive the feature upgrade process with Windows 10 19H1.
Yes of course it'll use my ISP connection, but will only allow internet through the VPN connection, if switched to the standard Ethernet connection (in Windows) it'll tell me no internet connectivity on that connection (despite the VPN obviously using that for its traffic)
They are configured the same on my Son's new PC that ended up with being updated by mistake, but do not work. Whereas the Mac that I set-up with bootcamp and is still running 1803 is working perfectly - screen-time, permissions, activity reporting. New PC on 1809 - useless. no restrictions, notification 24hrs late every time.
1809 is noticeably slower on startup than 1803, even with an SSD, but we've still talking seconds here, but you can see the difference (had two identical laptops to compare this). A lot of bloatware features that I've justed turned off, that will be dropped in 2-3 versions no doubt due to lack of use.
This post has been deleted by its author
That's the official name. Just as the 1809 update was called the October 2018 update even when it was delayed until November. I don't know who is setting the numbers or the names, nor do I know what the H is doing in that number now, but that's Microsoft's decision.
"while it would be nice to pretend that 1809 never happened, the Update of Damned has been slapped with the Long Term Servicing Branch (LTSB) moniker meaning it will hang around for another 10 years"
What does this mean? Sounds like you're saying 1809 will be supported until 2028, but I see no indication of that on the link provided:
https://support.microsoft.com/en-gb/help/13853/windows-lifecycle-fact-sheet
It says the end of service for Home & Pro is 2020, and for Enterprise & Education is 2021. What are you referring to?
Sorry for them? Why? It's not like the world hasn't been watching Redmond go steadily downhill for the two decades since the release of Win2K. Anybody in WinSupport these days should have known exactly what they were getting into. So why be sorry for them? Perhaps mildly irritated at them for continuing to contribute to the enabling of MS's bad coding practices, though.
Started testing it once Trend Micro updated their WFBS to support it (i.e. late December) and it's worked fine for me - no deleted files, no dropped internet connections, no nuffin. In line with the stats in the article, about 10% of the company fleet of computers are now running it.
I prevented the auto upgrade to 1803 by setting my connection to metered* after hearing various horror stories. 1709 retains support until April so that deadline will eventually force my hand.
Have all the programmers at Microsoft retired/died/quit?
* - https://www.pcworld.com/article/2953132/windows/set-windows-10s-wi-fi-connections-as-metered-to-download-forced-updates-at-your-own-pace.html
I have a device that - despite my best efforts - is still stuck on 1511. It's only a testbed/play device so I don't particularly care, but it amuses me that it repeatedly tries to update to 1803 and then the oh-so-informative "Something went wrong. Retry?" loop.
And trust me, using 1511 compared to 1803 is rather like using Windows 8 compared to 8.1 - both are execrable nightmares of "F*** you, users" but at least the latter is pretending to go in the right direction.
I'm mainly running W7 x64 but I do have a laptop running 8.1 which is fine, and recently inherited an all-in-one running W10 which seems to be happy just doing stuff.
I suspect that 99% of end users have no issues and it is only the deeply (anally?) techie types who care.
My main concern recently is the broken W7 update thst screws network sharing.
At some point I'm going to have to upgrade, although I'm tempted to move W7 to W8.1 if that is still an available option. A long time since i did the clean installs on the low cost upgrades from Vista.
"My main concern recently is the broken W7 update thst screws network sharing."
That really annoyed me too! It has now been fixed. See the post here: https://answers.microsoft.com/en-us/windows/forum/all/kb4480970-no-networking-invalid-handle-error/00d87fe8-876a-45d9-beb9-2c2fd9fff0aa
Here's a perfect example of why Microsoft's 6 month upgrade cycle is madness:
I just checked the Gigabyte website and notice that new motherboard drivers for Windows 10 version 1809 have just been released for my motherboard (which is only 18 months old).
So, 1809 was supposed to be released in September 2018, actually got released in October, pulled and re-released in November and new motherboard drivers are finally available at the beginning of February 2019.
And, another "new" version of Windows 10 is just around the corner - March or April from what I hear. I'll probably see another new set of motherboard drivers around about July or August. Just before the next new release.
Total insanity.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
