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

111–120 of 159 posts

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

#111

Post by atesti »

gmueckl wrote: post #70
dx87 wrote: post #55

Earlier quoted context omitted.

I know it was an error on my part, but I lost an updated password database file because of unexpected behavior with the Windows file explorer. I had mainly been working out of a single folder, so I didn't realize the next time that I opened the file explorer that it was showing me "quick access" since the file list was populated with the contents of the one folder I was using. I dragged the updated database file to t…

This shows what a steamimg pile of incoherent features and behaviours the Windows Explorer has been gradually turned into since Windows 7. It is quite hard for average users to coax that tool into showing an actually honest content of some directory on the hard drive. There are so many abstractions, redirections, alternative view and on the fly translations (only obvious with languages other than English) in there th…

Try using Total Commander (http://ghisler.com ), it shows you the drive as it really is!

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

#112

Post by gpvos »

xpaulbettsx wrote: post #46

This article is super deceptive, these two bugs are completely unrelated, and the one still standing is pretty obscure: 1. You're extracting a Zip file and intend to overwrite your own data 2. The data isn't overwritten, but it doesn't tell you about it 3. You delete the Zip file, thinking that it's extracted. I'm not discounting that this is a Bug, but I can't think of a time I would've ever lost data because of thi…

Not obscure at all; this is daily practice.

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

#113

Post by mcsofake »

AnIdiotOnTheNet wrote: post #60
Pneumaticat wrote: post #29

Sounds like Linux-class bugs (e.g. KDE copy/paste not working correctly sometimes[0]). I guess Windows has lost its advantage of perceived quality. [0]: https://www.reddit.com/r/linux/comments/9a7k2i/psa_on_kde_ne...

Yeah, it's getting really bad. It seems like now that MS is embracing open source and Linux, they are also embracing some of their worst practices. Treating users like children, not listening to users, rolling releases without regard to stability or consistency, adding features nobody asked for instead of fixing bugs, inconsistent UIs...

> Treating users like children, not listening to users, rolling releases without regard to stability or consistency, adding features nobody asked for instead of fixing bugs, inconsistent UIs...

None of these are unique to open source. IMHO, commercial software tends to be equally bad, if not worse.

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

#114

Post by beagle3 »

pjmlp wrote: post #98
beagle3 wrote: post #87

Earlier quoted context omitted.

MacOS works very well. And if you don’t like Apple hardware, so do many Linux distributions (Ubuntu is very popular and easy to get support for), and even FreeBSD and OpenBSD if you are willing to put in more time. Most people are better served by NOT windows. Using Win10 without a specific program that isn’t available for macOS/Linux is bordering on masochism.

> Using Win10 without a specific program that isn’t available for macOS/Linux is bordering on masochism. Some of us like 100% laptop support without speeding weekends tweaking them instead of being at the park with friends and family. Even buying from Linux friendly hardware stores isn't always a success, as proven by my own Asus netbook.

I have the opposite experience with Win support - my parents replaced their aging windows laptop with a new win10 one, and I had to spend the weekend trying to get their old printer and scanner working again, whereas it still works out of the box with the latest Ubuntu.

The main difference these days, once you got past the setup, is that as a non LTSB/LTSC user, Microsoft keeps inflicting damage onto you (e.g. in the form of reappearing Candy Crush) with no way for you to stop it without continuously actively fighting.

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

#115

Post by kurtisc »

yjftsjthsd-h wrote: post #80
Pneumaticat wrote: post #29

Sounds like Linux-class bugs (e.g. KDE copy/paste not working correctly sometimes[0]). I guess Windows has lost its advantage of perceived quality. [0]: https://www.reddit.com/r/linux/comments/9a7k2i/psa_on_kde_ne...

:D As a Linux-lover, Windows 10 has been an absolute gold mine. I get to roll out all the old lines... "I need a system that just works", "I can't afford to waste time fixing it after every update", "it's just a toy OS"[1], etc. [1] Go on, tell me why Candy Crush is installed by default in the Enterprise edition...

I like seeing how removing the latest unwanted feature requires 'just' a few settings changes. Poetic.

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

#117

Post by xaduha »

kurtisc wrote: post #116
xaduha wrote: post #23

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

From your friendly neighborhood enterprise B2B volume sales team? Or from an illegally shared copy of questionable integrity?

> questionable integrity?

What's what integrity checks are for.

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

#118

Post by kurtisc »

xaduha wrote: post #117
kurtisc wrote: post #116

Earlier quoted context omitted.

From your friendly neighborhood enterprise B2B volume sales team? Or from an illegally shared copy of questionable integrity?

> questionable integrity? What's what integrity checks are for.

Microsoft aren't the ones supplying the tools to fake a licence, though.

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

#119

Post by Angostura »

zitterbewegung wrote: post #38
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 .

Or using Windows 7 because staff can actually use the UI.

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

#120

Post by einr »

gmueckl wrote: post #70
dx87 wrote: post #55

Earlier quoted context omitted.

I know it was an error on my part, but I lost an updated password database file because of unexpected behavior with the Windows file explorer. I had mainly been working out of a single folder, so I didn't realize the next time that I opened the file explorer that it was showing me "quick access" since the file list was populated with the contents of the one folder I was using. I dragged the updated database file to t…

This shows what a steamimg pile of incoherent features and behaviours the Windows Explorer has been gradually turned into since Windows 7. It is quite hard for average users to coax that tool into showing an actually honest content of some directory on the hard drive. There are so many abstractions, redirections, alternative view and on the fly translations (only obvious with languages other than English) in there th…

since Windows 7.

I agree with your main point, but putting the cutoff at Windows 7 is extremely generous. Already by then it was doing absolutely insane things like hiding the actual name of the "Program files" folder and instead showing the localized name.

Let me explain: in Swedish Windows, for instance, "C:\Program Files" was traditionally called "C:\Program" since Windows 95. (Here is where the ACTUAL mistake was made that has turned into technical debt ever since -- why in the name of hell would you LOCALIZE the FILENAME of a SYSTEM FOLDER?)

Anyway, lots of installers aren't locale aware and assume "Program Files" so it used to be that most Swedish users had some software installed in "C:\Program" and some in "C:\Program Files" and it was a total mess. Microsoft "solved" this by having Explorer show "C:\Program" but under the hood it is actually "C:\Program Files". The mind boggles, truly.

Then there's the whole "Libraries" vs "Folders" fiasco, don't get me started...

For me, it's been straight downhill since Windows 98 started hiding the contents of system folders by default.

Luckily, we have 64-bit WINFILE.EXE: https://github.com/Microsoft/winfile :)

Post reply on HN