M
mschmieg
Over the last several months, all three of my computers have failed to properly complete a chkdsk c: /f command on the reboot. The process is to open command prompt as an administrator, type chkdsk c: /f and then y for it to run the next time the computer is booted. After a reboot, the computer runs chkdsk on the c: drive and reports that scanning and repairing is 100% complete and then stops. The little circle rotates, but it never restarts as it previously did. They have been allowed to run for hours without any action. The only way to complete the process is to turn off the power and turn it back on at which point it says again that scanning and repairing is 100% complete and it then goes into Windows.
All three systems are running Windows 10 Pro, 20h2, and all three are using an SSD as the boot drive. Two of them are running UEFI drives and one is running a SATA SSD. This all started with the September Cumulative Update and all three machines started it at the same time, though the machines are all different. The machines are a Dell XPS 8930 with a Samsung 760 EVO Plus set to ACHI, a Dell 5482 with a Crucial P1 set to ACHI, and a Dell Studio 1737 antique with a Samsung 860 set to ACHI.
This is not a critical problem, but it is a bit irritating now and then.
Continue reading...
All three systems are running Windows 10 Pro, 20h2, and all three are using an SSD as the boot drive. Two of them are running UEFI drives and one is running a SATA SSD. This all started with the September Cumulative Update and all three machines started it at the same time, though the machines are all different. The machines are a Dell XPS 8930 with a Samsung 760 EVO Plus set to ACHI, a Dell 5482 with a Crucial P1 set to ACHI, and a Dell Studio 1737 antique with a Samsung 860 set to ACHI.
This is not a critical problem, but it is a bit irritating now and then.
Continue reading...