New
#1
ChkDsk damages file system on SSDs
-
-
New #2
Homer,
Thanks for posting this additional link. This is also reported in gHacks and discussed in
Windows Update KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685 - TenForums
Denis
-
New #3
If there is smoke, there should be fire somewhere.
Running ChkDsk on Windows 10 20H2 may damage the file system and cause Blue Screens - gHacks Tech News
-
New #4
An interesting bug, but to be fair, /f should be used only when needed, not at random. I use just "chkdsk /scan" for the maintenance. F parameter can take several hours on HDD, it is obviously not healthy for SSD.
-
New #5
Armed with a Macrium Reflect image in case of the worst, I tested this on one of my SSD machines. Nothing bad happened....
KB4592438 CU Windows 10 v2004 build 19041.685 and v20H2 19042.685 - post #347
-
New #6
Running chkdsk switches on a SSD appear to be controversial:
CHKDSK on SSD Drives? What's the Deal With Wear and Tear?
-
New #7
Is it possible the issue applies only to GPT/UEFI disks, not MBR? I only have 2 SSDs on Win10 Notebooks, both as MBR, and 1 on a Linux Mint install.
-
-
-
New #9
It is very strange that a particular Win 10 ver with a particular patch can affect a old task as chkdsk c: /f, specially because the task runs under WinRE after boot, but.... as it's Win 10 I can expect anything.
-
Quote
Related Discussions
