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

Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

borncity.com

Post reply on HN
Print view View original

241–250 of 306 posts

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#241

Post by fortran77 »

PragmaticPulp wrote: post #19
game_the0ry wrote: post #9

This article immediately reminded me of a video I saw a while ago.[1] The long and short - MS basically laid off the staff that tested Windows, and much of it is automated nowadays (I bet the MBA educated executive at MS who was responsible for that got PHAT bonus, at the expense of Windows customers and laid off testing staff, of course). Seems like it happened in 2015, which is why it seems that windows updates hav…

I know we're basically comparing anecdotes, but I've been surprised at how much more I've come to trust my windows workstation than my Mac in the past few years. I can't actually remember the last time my Windows workstation crashed outright (if ever?) but my Mac locks up at least 2-3 times per week. I also have to be extremely careful to avoid high memory pressure under Big Sur now, otherwise Finder spirals into a r…

The person you're responding to has an agenda (perhaps is even a paid astroturfer), and his story is not based in reality. My Windows 10 systems are rock-solid. I switched from all Macs years ago and never looked back.

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#242

Post by fortran77 »

bengalister wrote: post #95
TedShiller wrote: post #61

Earlier quoted context omitted.

For me, OS stability, in decreasing order, has always been: 1. Linux 2. MacOS 10. Windows

Hard to say but for me I would say: 1. Windows 2. MacOS 3. Linux I had more crashes on Linux than any other, all related to the Gpu driver (intel iGpu), and it really depends on the kernel version but newer not necessarily means better. In a VM with i3, it never crashed. But regarding hardware support except for the Gpu, I had better experience with Linux than Windows on the same machine. On Windows my mouse is stutt…

And Linux is the only system I've ever run that had malware show up on it.

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#243

Post by egwor »

spydum wrote: post #202
egwor wrote: post #177

Earlier quoted context omitted.

I have the exact opposite experience. We're running an older version of Office (2016?) at work with Windows 7. Thse are supported by MS via the extended support contracts. It will be upgraded shortly. Basically I get blue screens, rendering issues, slowness, freezing, crashing, random glitches. I regularly lose emails. The changes to Outlook are abysmal too. When a meeting invite I've accepted is amended (e.g. a 'Sta…

Or you know, upgrade to windows 10, since windows 7 has been dead for about a year now.

Yeah, since I don't control what gets run on my desktop there's very little option. The web mail vs of Outlook is even locked out.

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#244

Post by gruez »

donmcronald wrote: post #76
dixie_land wrote: post #14

Earlier quoted context omitted.

I believe Enterprise and LTS editions are on a different cadence. Probably came from the same MBA: let consumers be lab rats to for big enterprise customers

That's exactly what it is and it's becoming more common. Java went that way. Windows went that way. CentOS is going that way. Office 365 is even worse because the low paying users get more frequent updates than high paying users. I know because I tracked down a long file name issue for someone and was shocked they were paying for it and still getting to be a beta tester for the "real" customers (huge businesses).

> Office 365 is even worse because the low paying users get more frequent updates than high paying users.

AFAIK all office subscribers can change their update channel from monthly (default) to SAC (the one that "high paying users" use). The only difference is that the low paying user has to do it via group policy or registry, whereas the high paying users probably have some sort of enterprise admin tool that allows it to be set at the organization level.

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#245

Post by fortran77 »

game_the0ry wrote: post #9

This article immediately reminded me of a video I saw a while ago.[1] The long and short - MS basically laid off the staff that tested Windows, and much of it is automated nowadays (I bet the MBA educated executive at MS who was responsible for that got PHAT bonus, at the expense of Windows customers and laid off testing staff, of course). Seems like it happened in 2015, which is why it seems that windows updates hav…

There’s a chance this bug is caused by a faulty wear-leveling algorithm specific models of SSD. I tried to repro and couldn’t.

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#246

Post by yowlingcat »

eznzt wrote: post #203
2ion wrote: post #199

Earlier quoted context omitted.

Not even to mention the willfully broken font rendering on all peripherals that are not "retina enough" since a few versions ago. Using my work macbook with my trusty 16:10 monitors with 1920x1200 resolution in the home office is a literal eye sore since it's impossible to get a clear font image. The company had to send over a retina-enough screen... The worst font rendering Linux ever had is still better what macOS…

"apple-blessed displays" means "displays that have a pixel density that is appropriate to the year 2020", not necessarily screens that were manufactured by apple

> "displays that have a pixel density that is appropriate to the year 2020"

As opposed to what other year? Color me naive, but I thought it was supposed to be the function rather than the form that we were supposed to make those kinds of comparisons about. What about a low pixel density is /not/ appropriate to the year 2020?

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#247

Post by donmcronald »

fortran77 wrote: post #239
game_the0ry wrote: post #9

This article immediately reminded me of a video I saw a while ago.[1] The long and short - MS basically laid off the staff that tested Windows, and much of it is automated nowadays (I bet the MBA educated executive at MS who was responsible for that got PHAT bonus, at the expense of Windows customers and laid off testing staff, of course). Seems like it happened in 2015, which is why it seems that windows updates hav…

Windows 10 has been the most reliable, productive, stable system for me over the past few years. No doubt they use a lot of automated testing -- how could they not? But today's Windows 10 is -very- reliable.

It's filled with enough annoyances for me to be frustrating at times.

The night light is awful and blasts you with full blue light whenever monitors come out of standby mode and then it'll be "On" but not actually on until you toggle it.

Lately explorer hasn't been refreshing properly, so when I create a new folder I need to right-click, refresh before I see it and can rename it.

Things that auto-install drive me crazy. No, I don't want to "Meet Now".

Every SAC update tries to trick me into enabling OneDrive "backup" (sync is NOT a backup) and I missed it once so all my stuff got uploaded to OneDrive.

BitLocker with a PIN and Windows Update don't seem to know each other exist. Updates auto-restart the computer and then it sits at the BitLocker screen or, in my case, reboots continuously every few minutes spinning the fans up to max on every reboot.

I'm sure there's more, but those are the ones that annoy me daily.

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#248

Post by tyingq »

kabdib wrote: post #20
causality0 wrote: post #4

I feel like Windows Update didn't used to be such a shitshow. Was I just not paying close enough attention a decade ago?

I help run a service that uses hundreds of Windows boxes, and at any one time two or three of them always seem to have a borked windows update state. Recovery is utter fucking voodoo, and it's usually better to flatten a machine than attempt to repair things. A while back I installed a couple racks of shiny, new, absolutely identical servers (except for MAC addresses) with factory-imaged operating systems, and had tw…

"How do you even do that?"

I would guess it's something like non-deterministic order of patch installation. Which seems easy to end up doing even if you think it's deterministic. For example, some patches don't finish install until boot time, so unexpected reboots could bork things. Or things like "can't install this patch while X software is running", etc.

Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed

#249

Post by tck42 »

k_sze wrote: post #25
timvisee wrote: post #10

So, this only occurs when manually invoking ChkDsk with repair, or when Windows decides to do so on bad shutdown? I don't understand how such core things break in Windows.

I suppose it's because they now "test" using virtualized hardware. So even if chkdsk runs during their tests, it's running on a virtualized disk, not a real SSD. Honestly, I'd pay money so they bring back the testing team and not use all of us non-enterprise users as beta users.

Hah - you DO pay money, if you're using Windows. That's the problem.
Post reply on HN