Why am I not surprised at all? Heard that M$ has completely removed the testing team by adapting to DevOPs, which makes end users in production environment the white mouse.
Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
11–20 of 306 posts
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#12I feel like Windows Update didn't used to be such a shitshow. Was I just not paying close enough attention a decade ago?
I had auto-CHKDSK-on-restart trash an NTFS drive circa early noughties, FWIW. Never stored anything valuable on NTFS after that.
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#13Not delaying updates is like opting in to be a beta tester. I don’t want to sound smug, that was just a word of warning. It’s just a switch to flip and it will save you from many headaches.
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#14This 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 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
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#15This 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…
[deleted]
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#16Has Microsoft acknowledged the problem yet? It's still not listed as a known issue on the update page: https://support.microsoft.com/en-us/help/4592438/windows-10-...
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#17This 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…
Enterprise version (LTSC) hasn't had a feature update since November of 2018. Only security updates.
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#18This 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…
>Oh well, I guess I will be using Macbooks for the rest of my life
https://www.macrumors.com/2020/11/15/macos-big-sur-update-br...
Dropping quality is happening everywhere.
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#19This 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 restart loop that can only be fixed with a hard reset. I also had to give up my Mac Thunderbolt setup because I've been fighting the same Thunderbolt crash that many people have been complaining about since Catalina was released in 2019 ( https://rachelbythebay.com/w/2020/10/16/gameover/ ).
Meanwhile, my Windows machine just keeps chugging along, drama free. All of my hardware and peripherals work just fine with it, but I often have to play the plug-unplug game with audio peripherals until video playback works on my Mac.
Five years ago I never would have guessed I'd be writing an HN comment praising my Windows machine and lamenting all of the issues with my Mac, but here we are. It's downright depressing to think of all the time I've lost in the past year waiting for my MacBook to reboot or replugging USB cables until everything works after I wake it from sleep.
Re: Windows 10 20H2: ChkDsk damages filesystem on SSDs with KB4592438 installed
#20I 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 two of them fail initial windows updates. Out of the box. How do you even do that?