SFC /scannow problem Still with 29704.1000

Shaun Montgomery 50 Reputation points
2026-10-24T17:04:19.6866667+00:00

Windows Insider Experimental Build 29695.1001

Running dism..scanhealth and restorehealth completes without any errors reported.

sfc /scannow reports corrupted files that were repaired successfully.

However, subsequent runs of sfc after a restart keep on returning the same message.

Here is a screenshot of repairs seen.

User's image

Windows Insider program | Windows Insider preview | Performance and maintenance

3 answers

Sort by: Newest
Most helpful Newest Oldest
  1. CrazyKats 20,295 Reputation points Volunteer Moderator
    2026-10-25T23:56:20.4233333+00:00

    Hi Shaun,

    Even if you copied and shared the

    Feedback link we can't open it if

    you didn't choose what is shown in

    Johnny's image.

    User's image

    If you didn't check this box it's private.

    Was this answer helpful?

  2. Johnny55 5,240 Reputation points Volunteer Moderator
    2026-10-25T21:04:48.69+00:00

    Hello Shaun,

    I confirm your findings that sfc is not fully repairing files on every restart. My FBH link:

    https://aka.ms/AA13yn6i

    Your FBH link is not working. Did you forget to Share Feedback Publicly at bottom of FBH post as shown in screenshot. I cannot upvote.

    Share

    Regards,

    Johnny

    Was this answer helpful?

  3. AI answer

    2026-10-24T17:04:37.0366667+00:00

    This pattern usually means the underlying Windows image or component store still needs repair, even if DISM /ScanHealth and DISM /RestoreHealth completed without reporting an error.

    Use this sequence from an elevated Command Prompt:

    1. Run: 
         DISM.exe /Online /Cleanup-Image /RestoreHealth
    2. After it completes, run: 
         sfc /scannow
    3. Restart Windows.
    4. Run sfc /scannow again and check whether it still reports the same files.

    If SFC continues to report corruption after restart, use a repair source instead of Windows Update:

    DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:C:\RepairSource\Windows /LimitAccess
sfc /scannow

    Replace C:\RepairSource\Windows with the actual repair source location.

    If the repair source is a WIM file, this form can be used:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:c:\install.wim:1 /LimitAccess
sfc /scannow

    Important: sfc /scannow must be allowed to reach 100% completion, and the Command Prompt window should not be closed before that.

    Expected results:

    • DISM should report that the restore operation completed successfully.
    • A healthy result from SFC is: Windows Resource Protection did not find any integrity violations.
    • If SFC still says it repaired files on every run, the image source used for repair is likely not matching the installed build correctly.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.