F5F Stay Refreshed Hardware Desktop Trapped in automatic chkdsk for eight hours—can I power off?

Trapped in automatic chkdsk for eight hours—can I power off?

Trapped in automatic chkdsk for eight hours—can I power off?

B
Bluemail888
Junior Member
7
11-22-2021, 07:29 AM
#1
Hello there! The issue is that my computer has been unresponsive for over eight hours while scanning and repairing the drive labeled "C:". No progress was visible, and the spinning disk continues. Despite the chkdsk utility launching automatically by Windows, nothing changed during this period. I recently updated to Windows 11 version 22H2, installed new drivers via Armourycrate, and added Blender 3.4 and FL Studio 21 on the same day. The Samsung Magician tool was functioning well before this incident. My system is a self-built machine about seven months old. There hasn’t been any percentage displayed, possibly because the SSD appears healthy to Windows but still needs verification. I’m wondering if forcing a shutdown via the power button could help without risking data loss while chkdsk runs.
B
Bluemail888
11-22-2021, 07:29 AM #1

Hello there! The issue is that my computer has been unresponsive for over eight hours while scanning and repairing the drive labeled "C:". No progress was visible, and the spinning disk continues. Despite the chkdsk utility launching automatically by Windows, nothing changed during this period. I recently updated to Windows 11 version 22H2, installed new drivers via Armourycrate, and added Blender 3.4 and FL Studio 21 on the same day. The Samsung Magician tool was functioning well before this incident. My system is a self-built machine about seven months old. There hasn’t been any percentage displayed, possibly because the SSD appears healthy to Windows but still needs verification. I’m wondering if forcing a shutdown via the power button could help without risking data loss while chkdsk runs.

L
louracame
Junior Member
40
11-22-2021, 08:35 AM
#2
You can stop the PC by pressing the power button repeatedly until it turns off. If that doesn’t help, unplug the power cord and then plug it back in. This usually resolves the issue as I’ve done many times before. For your next question, please explain more.
L
louracame
11-22-2021, 08:35 AM #2

You can stop the PC by pressing the power button repeatedly until it turns off. If that doesn’t help, unplug the power cord and then plug it back in. This usually resolves the issue as I’ve done many times before. For your next question, please explain more.

F
Fullalexis10
Member
167
11-30-2021, 07:42 PM
#3
Short update, everything is back under control. For future reference: I initiated a forced shutdown, the computer started normally but ignored the scan. It went through all diagnostics in Samsung Magician, no issues found in LBAs or SMART checks. However, Over-Provisioning was marked as corrupted and required a chkdsk run. I executed it via admin command prompt, typed "sfc /scannow" and waited 30 seconds instead of the usual 8 hours. Windows displayed disk errors, so I ran "chkdsk /scan". It finished scanning only after 30 seconds, then froze briefly before restarting. After restart, it worked without a scan, went to Magician again, and Over-Provisioning resumed. My take is that the late W11 22H2 update likely affected the SSD partitioning somewhat.
F
Fullalexis10
11-30-2021, 07:42 PM #3

Short update, everything is back under control. For future reference: I initiated a forced shutdown, the computer started normally but ignored the scan. It went through all diagnostics in Samsung Magician, no issues found in LBAs or SMART checks. However, Over-Provisioning was marked as corrupted and required a chkdsk run. I executed it via admin command prompt, typed "sfc /scannow" and waited 30 seconds instead of the usual 8 hours. Windows displayed disk errors, so I ran "chkdsk /scan". It finished scanning only after 30 seconds, then froze briefly before restarting. After restart, it worked without a scan, went to Magician again, and Over-Provisioning resumed. My take is that the late W11 22H2 update likely affected the SSD partitioning somewhat.