1809 update finally released by Microsoft, along with empty promises of future change

We always knew it would come eventually; the only remaining question was the timing of the thing. Let's start with the details, as reported by ZDNet:

Microsoft has resumed the rollout of Windows 10 version 1809. The re-release of the so-called October 2018 Update comes more than five weeks after the company pulled the original installation files from its download servers and stopped its scheduled delivery through Windows Update just days after its initial debut on Oct. 2.

In a blog post, Microsoft's John Cable, the director of Program Management for Windows Servicing and Delivery, says the data-destroying bug that triggered that unprecedented decision, as well as other quality issues that emerged during the unscheduled hiatus, have been "thoroughly investigated and resolved."

Meanwhile, back in Windows 10

With Windows 10's 1809 update still M.I.A., and having had a very bad month in October, Microsoft were likely hoping to put the worst of their WaaS woes behind them. They've been busy hyping the latest 19H1 update's build and its features, and saying nothing at all about the ill-fated 1809 update, which is looking more and more like it also won't release until the first half of 2019.

But the best-laid plans of mice and men often go awry, and Microsoft's plans for Windows-as-a-Service are increasingly looking like they were poorly laid from the very start, so it should surprise nobody that Windows 10 has another issue. And, wow, is is a doozy, as reported by Gordon Kelly at Forbes:

Spotted by The Register, Microsoft’s activation servers have started accidentally downgrading expensive Windows 10 Pro systems into cheaper Windows 10 Home PCs, then invalidating their licences. Needless to say, that's a nasty financial hit (Home is $119, Pro is $199) and affected users are furious.

[...]

And it’s not just upgraders being affected. Problems with automated Windows 10 Home downgrades are being reported with fresh installs on different Windows Pro versions as well.

“Same issue on Dell computers running Windows 10 Pro 1803 that we just bought. Need to deploy to clients but they won't activate,” explained another user on Reddit.
Microsoft’s response? It’s not great.

On its official Answers page, Microsoft warns there is a “temporary issue” with the company’s activation server but has not disclosed any further details. As for users calling Microsoft’s call centres, the response is to simply wait for a fix.

Cue the expensive class-action lawsuits in 3... 2... 1...

Microsoft's "fixed" 1809 update has another data-deleting bug

Have your facepalm ready, and then read this reporting from Jason Evangelho at Forbes:

Apparently I'm not done beating this dead horse yet. That's because yet another file-deleting bug has surfaced in Microsoft's Windows 10 Build 1809 update. The same update Microsoft pulled from public circulation because it was wiping entire user folders from existence. The new bug centers around Microsoft's Unzip application, and seems to present itself in two distinct forms.

There are entirely too many situations where this could lead to data loss with varying degrees of severity. Here's how one Reddit user describes the issue:

"The issue is that in 1809, overwriting files by extracting from an archive using File Explorer doesn’t result in an overwrite prompt dialogue and also doesn’t replace any files at all; it just fails silently. There are also some reports that it did overwrite items, but did so silently without asking."

Other users are confirming the same issue, and there's currently an entry about it on the Windows 10 FeedbackHub.

Really, what were we expecting?

No word yet on whether Microsoft will actually delay 1809's redeployment over this issue, as they've yet to issue a statement on the subject that I've been able to find. Unlike the previous data-deletion issue, this one can be worked around by simply using 7zip, or some other third-party unzipping application, rather than Windows 10's built in archiving functionality.

Still, there's really no way around it; for an update that's already been pulled due to another (much more serious) user data deletion issue, and which has also been plagued with reports that users are having BSOD issues, it really seems like it's time to simply pull the plug on 1809 entirely. Just admit that it's not ready for release, cancel the fall roll-out, finish fixing the fucking thing, and then re-release it in the Spring. The current 19H1 release can be pushed back to next fall, if necessary, thus benefiting from extra development and testing time -- time that Microsoft clearly needs in order to deliver reliably bug-free products.

Yes, that would mean delaying the much-hyped "feature" that allows users to delete more of Microsoft's own bloatware, but MSFT clearly didn't think that was much of a priority before now, and are only making half-hearted efforts in that direction, anyway (when they start allowing users to remove Edge and Cortana, in addition to Groove Music and Paint 3D, let me know, but until then, I'll continue to say they're not really serious about bloatware). And delaying both 1809 and 19H1 would allow them to make the necessary internal changes to focus their team's attention on the quality and completeness of these releases, something which is sorely lacking now.