Member Avatar for Techno22

Unable to run this programme.
I am unable to run as admin when I click command prompt.
A message comes back saying: sfc is not recognised as an
internal or external command, operable programme, or batch file.
I ran disc check on start up but did not receive any report, although
it did run.

  • 2 Contributors
  • 2 Replies
  • 335 Views
  • 14 Hours Discussion Span
  • Latest Post Latest Post by Techno22

Dani AI

Generated

Nice catch by — that solved it for . For anyone else who sees "'sfc' is not recognized..." even when you try elevated access, the message means the command processor cannot find the sfc executable (SFC must be run with Administrator rights and uses the Windows component store). See Microsoft’s sfc reference for syntax and offline options. (Microsoft: sfc command). (learn.microsoft.com)

Quick diagnosis and safe fixes (do these before copying files from other machines):

  • Confirm sfc.exe actually exists and try the full path:

    dir %windir%\System32\sfc.exe
C:\Windows\System32\sfc.exe /scannow

    If the file exists but the shell still reports "not recognized", check whether your PATH includes the system folder or temporarily change into System32 to run it; missing or broken PATH entries are a common cause. (If you need to add %SystemRoot%\system32 to PATH, do so via System Properties → Environment Variables.) (makeuseof.com)

  • You mentioned CHKDSK ran on startup but showed no on-screen report — boot-time CHKDSK writes details into the Event Viewer (Application log), typically under source "Wininit" with Event ID 1001. Open Event Viewer -> Windows Logs -> Application and look for Wininit/1001 to copy the CHKDSK result. (winhelponline.com)

When SFC reports problems but cannot fix some files, extract the SFC entries from the CBS log for inspection:

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log > %userprofile%\desktop\sfcdetails.txt

That produces a readable sfcdetails.txt you can review. If SFC still can’t repair, run DISM (Windows 8/10/11) or the System Update Readiness tool on older Windows to repair the component store before re-running SFC; Microsoft documents the DISM /RestoreHealth workflow. (learn.microsoft.com)

Summary checklist: confirm sfc.exe exists, try full-path run, verify PATH, pull CHKDSK and SFC logs, then repair the component store (DISM/CheckSUR) if needed.

Recommended Answers

All 2 Replies

Member Avatar for rch1231

Hello,

When you go to start the command prompt right click on CMD.EXE and select Run As Administrator. You should then have thr correct permissions and path to run sfc

Member Avatar for Techno22

Many thanks.
Worked perfectly.
No integrity violations.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.