Microsoft reckons the accursed Windows 10 October 2018 Update is finally fit for business Microsoft has confirmed that Windows 10 1809, aka the Update of the Damned, is now ready for "broad deployment." The announcement – which comes mere weeks before the next version of Windows 10, 19H1, is expected to put in an appearance – means that the Operating System update is ready to be unleashed on businesses. Handy, …
Anyone running WSUS/SCCM managed machines who just auto-approves every single update and pushes it straight out to production deserve everything they get.
If you don't have a "Testing" group with a handful of imaged-up PC's on it within your WSUS, and "Approve" to them first, you really have nobody else to blame when things go wrong. We already *know* that Microsoft won't take the blame, or act in a timely manner, as shown here.
At least you have the option to revoke approval for the dodginess, though. Home users are stuffed.
they did yes, but that was for those who probably started 1809 before it was yanked. However this release effecting says feature update is CBB ready. My WSUS lists it as "1809 2019-03B" as opposed to the 1809 in nov. The 2019-03B supersedes the latter but doesn't seem to be a different size.
The update has been more a problem to get installed rather than in-code bugs. I have updated 5 Win10 systems to 1809 and installation failed multiple times on 3 of them; it took most of an afternoon on each to get 1809 to finally "stick". On one unit in order to get the 1809 update I had to do a full download of the upgrade and implement a full off-line install, on the other I was *this close* to doing the same but the *third* installation attempt was finally successful (and the installation attempts each take quite a while).
So Microsoft needs to figure out rollout issues, for judging from my experience it is the most difficult part of the 1809 equation.
We rolled 1809-2019-03B to a room of 30 machines on Friday via WSUS without issue, this was a far cry from the November update which barfed on the same 30 machines (before rolling back automatically). We also rolled out 15 machine via PDQ and the 1809 ENT ISO (VL) running the /auto update switch, all these worked also. The plan is to roll 1809 to a further 500 machines next week - im happy to use WSUS for this.
And they wonder why people want control of when and how to deploy updates on their machines.
I wonder how much businesses have lost (real hard currency affecting their bottom line) with all the forced updates that break things ?
Not every company has a full time IT person, but the impact is the same, they are not home users, but are treated as so by the MS "big corporate" and "everyone else" views..
How much is it costing the companies
Not enough. Or rather, the bill hasn't lighted on the right desk (read: C suite) and the "constant IT problems" are being "fixed" with a constant parade of replacement personell or contractors for now.
When the bill does reach the right level, goodbye Microsoft...they seem to be betting they can manage damage at that level but eventually even they will have to answer to the board in larger corps (as in, pay up or get replaced)
It costs us no more that it used to. We initially installed 1511, then WSUS'd to 1709 a couple of years later, now we are going to 1809 a couple of years later. A 2 year OS update is no more than we did with XP->W7 then W7 SP1, then 8.1 now 10. I suppose that if you keep to the 6 month update and have to fix the bugs then I feel sorry for you.
The REALLY frightening thing is that there is apparently a server channel that runs the same 6 month updates. Jesus, I feel for those people who effectively do an inplace update on their server every 6 months!
Deactivate developer mode, that did it for me ;-)
In any case, read the update logs to figure out what is failing for you, that is what I did ... I think I used:
https://docs.microsoft.com/en-us/windows/deployment/update/windows-update-logs
Then google for the "too many to mention" errors I got ...
The VM that runs a certain crappy, soon to be replaced with free software, Windows-only software package was locked to an older (barely working) W10 build a long time ago, then firewalled into oblivion. There it will stay, unloved, unactivated, and unupdated until it can finally be purged at some point.
How far Microsoft has fallen!
Is their any evidence Microsoft has rehired more QA staff, or are they just locking the remaining 5 in the office over the weekend?
Certainly looking at the facepalm inducing but otherwise increasingly irrelevant electron rewrite of Skype, the answer is no.
Curious what evidence exists to suggest Microsoft quality hasn't dropped back to 2000's vintage. Rather like Apple. Anyone got a Linux dvd I can borrow?
“We will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary to.”
Until that and all the spyware and adverts are permanently removed
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
