Windows 10 October 2018 Update rollout now paused

Geneo said:

I ran into this strange issue the other day - I extract from com0presed files a lot. I was copying over some files from a zip for a program update and it took me a bit to figure it out - it silently failed. I ended up deleting the originals. before copying.

This release is a bit of a muck-up, isn't it?

It is still doing it in the latest CU 17763.104 but it works correctly in the latest fast ring release.

LEOPEVA64 said:

There are so few people that use Windows Explorer to extract compressed files that maybe that's why this bug went unnoticed:

The Windows 10 October 2018 Update has another strange file management issue which could lead to data loss

I already confirmed that the bug exists but I also confirmed that this bug is not present in the Fast ring and Skip Ahead builds, so Microsoft may already know about this bug and they are going to back ported the fix to O18U with a CU as they have done several times in the past and as they did recently with the fix of the bugs of the task manager.

Bree said:

I can confirm that it exists in both the x86 and x64 version of 1809, 17763.55.



I use it all the time, but the bug only hits when you extract a file to somewhere where a file of the same name already exists. Not something I generally do, so I hadn't spotted this one

kado897 said:

I found that bug some time ago. This is the hub entry. https://aka.ms/AA2raiv

I haven't been using File Explorer in a very long time, because I think it's full of bugs and I get a lot of unexpected behavior. One thing is for sure, it is very slow. CMD has been my goto place for a few years if I handle files.

lolcocks said:

When are these updates going to resume?

I am guessing Microsoft will be releasing another ISO?

Gooooooooooooood question! In just 12 days it's November. Or by that time they'll call it the NOVEMBER-update.......

Geneo said:

yeah, i am on 104. good to hear it is fixed. thanks.

Problem is we don't know that it was ever a problem on the 19H1 builds so it may not have been fixed as such.

What I fail to understand is HOW updates break pre-existing behaviour.

New coders attack old code with bright idea; either there's no regression testing schedule, or it's been revised or rewritten. MS lost swathes of testers passing that back into the development team. Terrible idea.

MS's test requirements for Windows could be massive given the range of compatibility issues, devices, drivers, programs; without a cast iron spec to work to, rigidly adhered to by all, you'd be sunk.

I suspect that unless MS revises its development process significantly we'll see much more of the same.