CHKDSK keeps restarting on Stage 4. Can anyone help?

Hi, first thing to do is to ... check your disk.. but with a 3rd party program.

You can try chkdsk X: /scan - which scans only, report right there on the GUI, FWIW, where X is the drive letter in question.

As your laptop is unbootable, you have 2 primary options.
a. Create a live boot disk (Google, e.g. Hiren's, Bob Omb's) using another PC, then boot your lapop from that live boot disk. You should find a program such as Crystal Diskinfo on the live boto disk, or use its portable version.

b. Remove the disk from your laptop, put it in a USB caddy and so test it using another PC.

c. Not the best: boot your PC from a win 10 install disk to a command prompt then run a SMART assessment (tutorial available).

Being stuck on a Windows update could possibly have resulted from a failing disk, I suppose; more often it really is a matter of patience assuming your O/S and disk were intact.

How could you recover?
a. many tenforums members endlessly recommend the routine use of 3rd party disk imaging. If you have such an image or your Windows partitions, you can restore that, even if you need to replace the internal disk. I'm guessing you don't.

b. Most likely you will be faced with a clean install- in whch case I recommend using a new disk in your laptop, removing the existing one and keeping it aside so you can extract whatever you may not have backed up.

Hello @mdb1983,

Welcome to TenForums.

If you are eventually able to Boot.

I do NOT know if this will help. Even though it failed to complete, there is quite possibly a log file, or part of a log file available.

The two commands below will check for the chkdsk log. They are set to only produce that LAST log run for each.

Depending on what parameters you used, ID:26212 is a scan run on the LIVE OS - NO RESTART NEEDED, and ID:1001 is a scan run during BOOTUP - RESTART NEEDED.

You may have better success in just running chkdsk in information mode using chkdsk %SystemDrive% and then re-running the ID:26212 command below.

Copy & Paste the following commands into a CMD Prompt and press Enter.

Code:

Get-WinEvent -FilterHashTable @{LogName='Application'; Id='26212'} -ErrorAction 'SilentlyContinue' | Where-Object {$_.ProviderName -Match 'chkdsk'} | Select-Object -First 1 | Sort-Object -Property {$_.ProviderName, $_.TimeCreated} -Descending | Select-Object -ExpandProperty Message

Code:

Get-WinEvent -FilterHashTable @{LogName='Application'; Id='1001'} -ErrorAction 'SilentlyContinue' | Where-Object {$_.ProviderName -Match 'wininit'} | Select-Object -First 1 -ErrorAction 'SilentlyContinue' | Sort-Object -Property {$_.ProviderName, $_.TimeCreated} -Descending | Select-Object -ExpandProperty Message

I hope this helps.

Please edit your profile with ALL your hardware specs. It will help us to help you
System Specs - Fill in at Ten Forums

Sad to say but it seems that your drive (HDD or SSD?) has failed.
As Dalchina suggested, with a WinPE tools drive, like Bob Omb's you can diagnose the drive

CHKDSK should not be used on an SSD

ken1943 said:

CHKDSK should not be used on an SSD

Where did you read such a fake information?
CHKDSK checks the logical structure of a NTFS or Fat32 drive and should be run always on a problematic drive.

Just read up, after years, that chkdsk does not harm an ssd.
Thanks for your reply to make me check.

ken1943 said:

Been reading that about SSDs since they came out. Same reason a defrag program should not be used.

For defrag it's correct. For chkdsk is fake.

Your reply made me check and found out chkdsk does not harm an ssd

Thanks at 80 yrs old still learning !!