Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed • Hacker News Board

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

#231

Post by leetcrew » Sun, Dec 20, 2020, 2:54 PM UTC

nolok wrote: post #212

eznzt wrote: post #203

Earlier quoted context omitted.

"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

That's beside the point. There are a lot of non high dpi devices out there. The majority of screens are. Whether it's your personal one (and you can't or don't want to change it) or a professional one (and your company may not want or be able to justify changing dozens of screens), you need to use them. It's possible to display properly and cleanly on them, everyone else does it. It's not as great as on a high dpi ob…

I'm pretty sure it's deliberate. not as in intentionally punishing users, but intentionally not bothering to test their stuff with any third party equipment (excluding the blessed belkin maybe). if I had to distill the apple brand into a single phrase, it would be "my way or the highway". their way might be pretty good if you buy all the way in, but if not, you can go fuck yourself.

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

#232

Post by NullPrefix » Sun, Dec 20, 2020, 2:56 PM UTC

refracture wrote: post #83

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…

>Windows 10 [...] DESTROYING my Linux boot loader that was placed on a separate hard drive.

Would it be fair to say that Windows extinguished your Linux install? :D

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

#233

Post by bserge » Sun, Dec 20, 2020, 2:59 PM UTC

_trampeltier wrote: post #220

bserge wrote: post #169

Earlier quoted context omitted.

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 .

On work I have no rights to do that. There are hundrets of ZBooks in the company and every one has different troubles with it. Is it to much to ask it has just to run troublefree. We all just wanna use it. It just has to work, like a car or whatever. computers are just tools to make our life more easy. I'm to old to spend more time with my computer on work just for fun. My time on work cost money.

Oof, yeah, without a proper configuration, they can be a pain in the ass. Out of the box, brand new, they overheat already. HP software is absolute trash.

I literally use drivers from Lenovo because the ones HP provides are like 5 years old and they don't plan on updating them.

Updating the BIOS is like playing Russian roulette, they seem to introduce more bugs than they fix.

But the hardware itself is nice, I've been using HP workstations for more than a decade. Quality has gone down somewhat (less metal, more plastic, less durable compared to early Elitebooks imo), but they're still nice machines.

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

#234

Post by tzs » Sun, Dec 20, 2020, 3:01 PM UTC

magoon wrote: 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.

He didn’t. It’s a very slow command. He started it in parallel on several.

He only found that there was a problem when the ones started earlier finished and rebooted.

By then it was too late for 7 machines but he was able to stop it on the rest.

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

#235

Post by FeepingCreature » Sun, Dec 20, 2020, 3:08 PM UTC

SomeoneFromCA wrote: post #136

Zardoz84 wrote: post #126

Earlier quoted context omitted.

I never had crashes of Linux on the last 5 years, except 2 or 3 because I was using all the whole RAM and the system freezed. However, I had blue screens with Windows 10 on the same hardware, plus that Windows 10 it's nearly useless on a magnetic HDD.

Linux (and possibly BSDs, did not test) has broken OOM killer, which works the right way only if your swap is disabled. To prevent these situations from happening you need to install EarlyOOM.

Or an M.2 SSD. I can go deep into swap and only notice a slight chugging.

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

#236

Post by kepler471 » Sun, Dec 20, 2020, 3:10 PM UTC

jiggawatts wrote: post #113

kabdib wrote: post #20

Earlier quoted context omitted.

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…

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…

For me, for the rare time I need Edge, typing 'edge' will not show me the Edge browser. It offers an internet search for that word, however if i stop at just 'edg' it will correctly suggest the Edge browser.

There are many similar examples with this same pattern.

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

#237

Post by game_the0ry » Sun, Dec 20, 2020, 3:32 PM UTC

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.

Depends on the company for upgrading, not the employee. All the financial institutions in America are still running windows 7 mostly bc the managers and execs fear switching over, so they would rather run the whole corporation on an essentially unsupported and obsolete closed source operating system than upgrade and figure out a nominally different ui than they are used to.

Inertia is a powerful force in the IT departments of Corp America.

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

#238

Post by DanBC » Sun, Dec 20, 2020, 3:35 PM UTC

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?

It was reasonably common advice, (around 2000-2004) in the MS Small Business Server groups to tell people to wait for a few days before installing updates, to see if other people had problems.

(I'd try to find a few posts but Google searches of Usenet newsgroups is suboptimal).

EDIT here's one thread talking about installing some, but not all, patches and updates: https://groups.google.com/g/microsoft.public.backoffice.smal...

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

#239

Post by fortran77 » Sun, Dec 20, 2020, 3:40 PM UTC

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.

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

#240

Post by gruez » Sun, Dec 20, 2020, 3:40 PM UTC

tremon wrote: post #207

apfsx wrote: post #17

Earlier quoted context omitted.

Enterprise version (LTSC) hasn't had a feature update since November of 2018. Only security updates.

LTSC isn't really meant as an enterprise desktop version. It's meant for industrial systems, the ones you don't expect to touch for years because they're controlling some vital factory process. The expected version you'd be running on enterprise desktops is just the regular semi-annual release, delayed by a few months so the SMB sector can test the major bugs for you.

>LTSC isn't really meant as an enterprise desktop version. It's meant for industrial systems, the ones you don't expect to touch for years because they're controlling some vital factory process.

But why? Is it for the bleeding edge features? I looked at the previous feature updates and everything there looks incidental, nothing that would warrant an upgrade.