Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Even After Fix, Windows 10 Update Is Botching File Operations

gizmodo.com.au

Post reply on HN
Print view View original

31–40 of 159 posts

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#31

Post by Fellshard »

doodliego wrote: post #27

An OS used by billions of people including government agencies, hospitals, and nonprofits is not some videogame that needs new content. It's mission critical software, and these utter delinquents are treating it like a Steam early release. If MS won't get its act together, they should be regulated, broken up, or have their OS seized by eminent domain for the public good.

First half, yes.

Second half, no. That's pretty disturbing territory being leapt into, and sets a very bad precedent.

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#32

Post by gruez »

xaduha wrote: post #23

If you're really tired of this shit, then get LTSB.

I'm not sure how LTSB could have prevented this at all. Ironically, 1809 was a LTSB release, so if you were upgrading from 1607 LTSB (to get WSL working, for example), you would also be exposed to this bug.

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#33

Post by jessedhillon »

vlunkr wrote: post #24
majewsky wrote: post #13

Earlier quoted context omitted.

So WSL is just "an excuse to insert telemetry and ads"? That's a very original POV.

You’re really putting words in their mouth. WSL is not a core part of windows that has been rewritten.

WSL is one of the features which has seen major improvement from the updates in the past 12 months.

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#35

Post by gpm »

doodliego wrote: post #27

An OS used by billions of people including government agencies, hospitals, and nonprofits is not some videogame that needs new content. It's mission critical software, and these utter delinquents are treating it like a Steam early release. If MS won't get its act together, they should be regulated, broken up, or have their OS seized by eminent domain for the public good.

Seized, absolutely not. Of course since the government already has the source there is nothing that needs to be seized. The government can just declare the temporary monopoly that they granted on copying it to be over (to be clear, this would take an act of congress...).

I'd almost be sympathetic to them doing that - but I also think the outcome would be absolutely terrible. Necessary maintenance (fixing security bugs, updating to new hardware, etc) takes a lot of work and I'm not clear that anyone else would step up to do a good job of it. See how the various android OEMs act...

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#36

Post by starky »

ux-app wrote: post #7

This is ridiculous, but to save yourself, run backups. I've been doing a full system disk backup every 24 hours for the past 2 years. So far it has saved my bacon once. Fwiw, i use Acronis for bups. The restore process for a 128gb ssd took about 10mins.

I started using Acronis to backup everything I don't want to lose about a year ago. A couple months ago, one of my hard drives failed (which I've never had happen before). Instead of trying to limp my files from the half-working hard drive, I just restored to the new disks and remapped the hard drive to the old letter, took maybe an hour and it was like nothing had happened.

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#37

Post by ygjb »

Teckla wrote: post #8
thrower123 wrote: post #2

Yikes. This sounds, however, like a completely different bug, if it is only triggered by unzipping archives. I'm sure that the situation is more complicated than it looks - because it looks like there is just a shocking lack of QA testing being done, if basic edge cases like this are resulting in undefined behavior.

I'm astonished Microsoft doesn't have automated tests for something as mundane as testing their built-in zip archive extraction functionality.

I expect there are automated tests, but it's been my experience that automated tests are usually not very deeply implemented. They often test the expected code paths, and new code, with new tests that fail to review the existing tests can often result in regressions that are not caught.

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#38

Post by zitterbewegung »

doodliego wrote: post #27

An OS used by billions of people including government agencies, hospitals, and nonprofits is not some videogame that needs new content. It's mission critical software, and these utter delinquents are treating it like a Steam early release. If MS won't get its act together, they should be regulated, broken up, or have their OS seized by eminent domain for the public good.

I bet a lot of enterprises are still using Windows 7 or older because they are mission critical systems for the reasons you state above . (Also because they have to validate all their software to the new operating system .

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#39

Post by DaiPlusPlus »

Fellshard wrote: post #31
doodliego wrote: post #27

An OS used by billions of people including government agencies, hospitals, and nonprofits is not some videogame that needs new content. It's mission critical software, and these utter delinquents are treating it like a Steam early release. If MS won't get its act together, they should be regulated, broken up, or have their OS seized by eminent domain for the public good.

First half, yes. Second half, no. That's pretty disturbing territory being leapt into, and sets a very bad precedent.

Isn't there already precedent for the state to step-in to ensure the continued survival of privately-owned and operated corporations and infrastructure that society has taken a strong dependency on? ("too big to fail", etc)

Re: Even After Fix, Windows 10 Update Is Botching File Operations

#40

Post by asdfasgasdgasdg »

doodliego wrote: post #27

An OS used by billions of people including government agencies, hospitals, and nonprofits is not some videogame that needs new content. It's mission critical software, and these utter delinquents are treating it like a Steam early release. If MS won't get its act together, they should be regulated, broken up, or have their OS seized by eminent domain for the public good.

> or have their OS seized by eminent domain

If there's one thing the government is known for, it's writing bug-free, efficient software.

Also, for real, this bug is not that bad. It's obviously a bug you'd rather not have. But no user data is lost. It just fails to surface an overwrite dialogue, and assumes the result is no.

Post reply on HN