Live data from Hacker News

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

borncity.com

161–170 of 306 posts

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

#161

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…

AFAIU Windows updates roll out to regular users first, and to corporate customers much later (perhaps depending on how the admin configures it). In a way, regular users are test monkeys. But this makes it less likely to brick corporations. (Of course this can still happen to due unique corp settings).

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

#163
post #65

Looking beyond the obvious problem here, just curious why the admin ran chkdsk /f for no reason, then did it on 6 more systems after observing it caused ntfs failure.

https://m.xkcd.com/242/ maybe. One hopes the reporter had backups (or was testing on disposable systems) before trying to reproduce a data-loss condition.

I'd say admin has had issues with users hard resetting the PC's and corrupting data, albeit slowly, and so runs chkdsk before it gets real bad.

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

#164
post #122

Earlier quoted context omitted.

Seems Apple managed to eliminate a major source of defects by removing the DIMM connectors from the MacBooks.

Or they couldn't figure out a way to make the slots more reliable (or thinner, I guess), and as a bonus locked in higher memory upgrade prices.

It also reduces the amount of space taken up by the connectors and such, and have a better testing suite without manual assembly, that can give false positives.

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

#165
post #160

Overwhelming desire to run this wusa /uninstall /KB:4592438 should I?

No need. This is just as overblown a reaction. First of all there's no reason to ever run chkdsk/f in the first place if there are no problems with your SSD. Secondly, just never use chkdsk /f - chkdsk /scan is faster, requires no restart and no further action is needed if no problems were found. Problems can be fixed using chkdsk /spotfix otherwise, which doesn't cause any problems.

You wonder why this is not the default behaviour and/or what /f should do.

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

#166
post #128

It's sad to say but I've had more hassle with Windows 10 than any previous (NT based anyway) release. 2000, XP, Vista, and 7 all served me well. 10 has done everything from deleted my files (thanks, October 2018 Update) to DESTROYING my Linux boot loader that was placed on a separate hard drive.. it has no business touching that! I always looked at Linux as not being worth the hassle.. now it's not worth the hassle t…

I've had pretty much the same experience as you. Honestly, linux runs faster uses less resources and is infinitely customizable. If anyone's work allows them to make the switch (eg. No hard dependencies on windows) then consider doing it, it is absolutely worth it.

Particularly with the online versions of Microsoft Office which, while not feature rich, work decently enough to act in lieu of the windows versions.

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

#167
post #160

Earlier quoted context omitted.

No need. This is just as overblown a reaction. First of all there's no reason to ever run chkdsk/f in the first place if there are no problems with your SSD. Secondly, just never use chkdsk /f - chkdsk /scan is faster, requires no restart and no further action is needed if no problems were found. Problems can be fixed using chkdsk /spotfix otherwise, which doesn't cause any problems.

You wonder why this is not the default behaviour and/or what /f should do.

Yeah - IMO MS should've deprecated the /f-option years ago and emulate it like that.

But that's what you get from disbanding most of your QA-team I guess...

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

#168

Earlier quoted context omitted.

My favourite Windows bug is the Start Menu search function. Install Windows Server 2016 or 2019 in any manner you choose: Blank VM with ISO image, new Azure VM from Microsoft template, whatever . Try using the Start Menu. Nothing will work. The search upon typing will not show all items. If you click on a search result, it won't launch. Type "SQL" to try and match "Microsoft SQL Server Management Studio" and be shock…

I suspect that search indexing is slow and you weren't patient enough. Leave that machine a week and everything will be indexed...

No, Windows regularly changes the index order and "learns" what you commonly type and what you click for which phrase.

This leads to absurd situations where the index show different programs for each letter.

For example on my machine:

Up > Windows Update first

Upd > Lenovo System Update first

Upda > Windows Update first

Update > Lenovo System Update is the only result

When I search for Visual Studio, only a few programs are found. I made a shortcut for the Visual Studio Command prompt because Windows search regularly threw it out of the results. One day it's there, the next it's gone. Horrible UX.

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

#169
post #46

Earlier quoted context omitted.

On work, I never had so much trouble, like with my HP ZBook and Win10. It had already once a complete reset, but still, I have a lot of trouble. Special since the new BIOS update about a month ago, it crashes once or twice a day again. In theorie Win10 looks nice. I tryed to upgrade one of my notebooks at home from Win7 to Win10. Privacy is one thing, but CandyCrush and things like that, was a totaly show stopper for…

HP's drivers are the worst I came across. We got HP Elitebook notebooks at work a few years ago and replaced them with Lenovo and Dell because the HPs kept crashing and slowing down over time. Their "utility" software like HP Sure Click slowed the whole system down and turned into nagware. There were at least 3 HP programs hogging the tray area and made discovery of my actually wanted tray icons hard. On top of that…

Secret to a (semi)happy life with HP - Identify the hardware and install drivers directly from the manufacturer (or any other company, like Lenovo heh) and do not install any HP software, ever.

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

#170
post #46

Earlier quoted context omitted.

HP's drivers are the worst I came across. We got HP Elitebook notebooks at work a few years ago and replaced them with Lenovo and Dell because the HPs kept crashing and slowing down over time. Their "utility" software like HP Sure Click slowed the whole system down and turned into nagware. There were at least 3 HP programs hogging the tray area and made discovery of my actually wanted tray icons hard. On top of that…

Yes, HP seems really like worse machines. I just set the max. CPU to 80% because of the costant fan noise. He is quiet now but also slower (of course). Also just the sound driver is around 500MB in RAM, serious? Lucky me I have 32GB. Since I work in a large company, I have nothing to say about the computer brand. At home I'm a happy Fujitsu user since many years.

Notebookfancontrol works with HP ZBooks G1-G2 (same controller as the Elitebook 8760w), you can use that. But it won't fix their terrible cooling system.
Post reply on HN