System File Checker: Difference between revisions

Revision as of 18:18, 10 May 2016

Revision as of 18:23, 10 May 2016

Line 58:

In Windows NT-based operating systems, System File Checker can be invoked via [[Windows Command Prompt]], with the following command:

<source lang="dos">

sfc /scannow (to repair problems)

</source>

or

<source lang="dos">

sfc /verifyonly (no repair)

sfc /scannow

</source>

Line 66 ⟶ 70:

In Windows Vista and onwards, files are protected using [[Access control list]]s (ACLs), however the above command has not changed.

System File Checker in Windows Vista and later Windows operating systems can scan specific individualspecified files. Also, scans can be performed against an offline Windows installation folder to replace corrupt files, in case the Windows installation is not bootable. For performing offline scans, System File Checker must be run from another working installation of Windows Vista or a later operating system or from the Windows setup DVD which gives access to the [[Windows Recovery Environment]].

In cases where the component store is corrupted, a tool called CheckSUR can be installed on Windows Vista and 7, which checks the store against its own payload and repairs the corruptions that it detects. Windows 8 and later integrate the functionality of CheckSUR into [[Deployment Image Service and Management Tool|DISM]].