Windows 10: sfc /scannow taking forever...

@zbook

Thanks for reminding me of the log.
I'm aware of it and will have a close look at it.
Thanks again.*Smile

 

I just did a clean install of the latest Windows updated version of 1803 (OS Build 17134.1) and the sfc /scannow command is taking forever to complete.
It's been on 8% for over an hour now and still running.

What gives?

:)

 

auto update fails

I've already tried that, I have since done a system file check with the "admin command prompt" sfc/ scannow. and trying to download again. Fingers crossed but its taking forever !!

 

sfc /scannow

This did not work .. My laptop won't even boot to windows

 

Could be any number of things I suppose. Have you tried exiting and restarting it? I have had it "get stuck" before and that usually solved it.

 

I clicked on the maximize icon,
of the CMD dialog.
Then clicked on the minimize icon and the sfc /scannow process shot well over 30% and seems to be running quite well now.

It finally completed the scan,
without any integrity violations.

Very odd behavior...

 

Have you got memory integrity enabled in the core isolation setting in Windows Security Centre(formerly Windows Defender)? This gives me similar issues with SFC.

 

I'm afraid that wasn't the case.
I have it turned off.
As can be seen in my screenshot below.



By all accounts,
things seem to be running nicely.

 

Perform the following steps and report the results into the thread.

Open administrative command prompt and type or copy and paste:
1) dism /online /cleanup-image /scanhealth
2) dism /online /cleanup-image /restorehealth
3) chkdsk /scan
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

 

@zbook

I understand that you're trying to help.
However,
everything is running fine and very quickly.

With scf scans working correctly with no integrity violations.



The chkdsk /scan shows nothing wrong.



Why should I run the dism commands?

 

The dism commands above can be run as needed.
If sfc /scannow is ok then you are set.

If the time is the issue you can open the log and see what it did from start to finish.
cbs.log

 

@zbook

Okay thanks! *Thumbs