Run system file check 7. Restore damaged Windows system files using the SFC and DISM commands. Restoring the integrity of Windows files

Windows? Checking the integrity of Windows 10/8/7/XP is needed if you suspect that some of the system partitions have changed or become defective due to the influence of malware.

There are several tools available to check integrity Windows files 10. The most common is SFC.exe, DISM.exe is often used. You can also use the Repair-WindowsImage function in PowerShell. We recommend using several methods, but one at a time. This is necessary because each of the options will check the integrity different files. If you need to perform such a procedure, but do not know how to check the integrity of Windows 10 system files correctly in order to correct them and resume work, carefully read the recommendations below, follow the sequential steps, then you will be able to check and restore the integrity of Windows 10 system files and others versions.

Check the status of system files using Windows tools

Scanning with SCF

Many users use the sfc /scannow command to scan the operating system before restoring lost or damaged files in order to ensure their correct functioning, restore smooth operation, and troubleshoot problems by restoring damaged components. It examines and corrects system partitions of the Windows 10 OS offline.

To activate this command, first open CMD, start with administrator rights. You can activate the utility using the mouse by clicking right click on the main Start menu, then selecting “Command Prompt” from the list. In the dialog box, type sfc /scannow and press Enter.
A check will begin, defects will be identified, and then they will begin to correct without your intervention, assistance automatically, by the system itself. If no errors are found, you will be informed that no problems were detected by OS resource protection.

If you decide to check one specific system file, then command line specify scf /scanfile=”path to file”.
It should be noted that SCF is not able to correct errors in those partitions that are running at the time of scanning, so it is best to use SFC exclusively when running “Windows 10 Environment Recovery”.

Running SFC using the recovery environment

To properly activate SCF, follow the steps below in sequence.

After completing the steps described above, a list of volumes will appear; you need to remember or write down those letters that correspond to the system partition and the “System Reserved” disk.

sfc / /scannow /offbootdir=bootloader partition letter:\ /offwindir=E:\Windows (or your path to the Windows 10 directory).

As a result, a scan should run that checks the integrity of system files, and recovery will be available for all of them. Please note that the check will take quite a significant amount of time; you do not need to turn off or restart your computer during the entire procedure. Last action will only need to be executed when the scan is complete and you close the Command Prompt.

Scanning with DISM.exe

This utility is used to mount images, makes it possible to identify and correct problems that arise with OS partitions as a result of their damage, and perform recovery. It's great for sections that SFC couldn't handle. It can also be used if SFC was unable to detect any problems during scanning. Therefore, do not limit yourself to just one type of scanning and treatment of damaged areas; be sure to carry out this operation when working with system components.

The command line is also used to launch DISM.exe. Activate it as an administrator and then follow the steps:

dism /Online /Cleanup-Image /CheckHealth - this function provides information about defects and damage to various components of Windows 10. A deep scan, however, is not performed; only previously found data is used.
dism /Online /Cleanup-Image /ScanHealth - scan for possible damage component repositories. This check often requires quite a lot of time, periodically freezing during the implementation process (usually by 20%).
dism /Online /Cleanup-Image /RestoreHealth - a thorough inspection and reconstruction of system files in offline mode, restoration, which also takes a long time.

All logs of actions when executing the above commands are written to the path Windows\Logs\CBS\CBS.log, Windows\Logs\DISM\dism.log

Similar to the previous utility, DISM is also launched through Windows 10 recovery mode.

Checking the integrity of system files in Windows 7/8 is identical to the same operation in 10. This is done in the same way - via the command line via SFC and the corresponding command. All actions are performed in the same sequence as described earlier. A similar algorithm is used to check the integrity of system files in Windows XP. The command line interpreter starts like this:

go to the Start menu;
click on the “Run” option;
In the dialog box, type the command “cmd”, then Enter on the keyboard.

As a result, a regular command line will open and you can perform all the steps to check OS files for defects.

All of these operations will help restore corrupted, damaged sections of any Windows-class operating system, which will solve the problems of malware interfering with the computer, restore its performance, and allow you to avoid extreme measures, such as a full system restore in case of operational problems. You do not need to reinstall the entire OS; it is enough to restore damaged components. Identify them using special teams and utilities, and your computer will continue to work.

). In this case, some begin to worry and look for all sorts of reasons and ways to eliminate freezes.
I will not repeat myself and write why this happens, because... The article is not about this and I have already given a link to solving problems above.
I’d rather show you one interesting way that will help you check your system for errors.

Few people know, but in Windows OS there is one useful “little thing” that can search And correct errors in the system itself. Moreover, it will not touch third-party programs, but will only check its system files. This is useful and interesting because many do not think that the reason may be hidden in the system itself, but feverishly begin, and so on. All in all . Yes, it is useful and can lead to good result, but with all these actions it is good to remember something else that I will write about below.

I already wrote a little about this function in the article, which can also arise due to a failure in system files, which are often forgotten. But still, within the framework of this article, I will repeat...

So, let's run:

and enter it into sfc /scannow:

The system check will begin:

All you have to do is wait.

For those interested, here is a description of the command and keys.

sfc
Where:
/scannow – immediately scans all protected system files.
/scanonce – scans all protected system files once at the next system boot.
/scanboot – scans all protected system files at every boot
/REVERT – Sets initial parameters default.
/ENABLE – Enable normal operation of Windows file protection
/PURGECACHE – Clear file cache and check files immediately
/CACHESIZE=x – Sets the file cache size

In the command line (Start -> Run -> cmd) we write the command sfc / and the desired key.

After the check is completed, the system will report the results and ask you to reboot.

That's all I have. Thank you all for your attention.

The operating system contains a large number of system files that provide it normal work. If one or more files are damaged, the OS will not be able to fully function. This can be expressed as errors and failures during operation, for example, Explorer crashing or problems managing Windows components, or the inability of the computer to boot.

There can be many reasons why system files are damaged in the Windows operating system. This could be viruses, tweakers, deliberate modification of files by the user, damage to hard drive and so on. Microsoft developers foresaw the possibility of such an event, so they created a system for checking the integrity of Windows system files (System File Checker tool). It allows you not only to identify changes, but also to return everything to its original state. automatic mode, if possible.

The point of the work is to compare system files located in windows folders with reference samples that are stored in a special storage windows components located in the WinSxS folder. If they differ or the file is missing, it is replaced with the original one from the repository.

To use the System File Checker, you need a command prompt running with computer administrator rights. To check, use the sfc command, which has several keys. To start checking the integrity of all protected files and automatically correcting changed or missing ones, enter the sfc /scannow command and wait for the file verification process to complete. It may take a long time, so be patient. A summary message will be shown at the end.

A full scan with automatic fixing isn't always necessary, so there are a few other keys that might come in handy.

/verifyonly - only checks all system files without attempting to automatically restore them
/scanfile - scans and restores a specific file, requires specifying the full path to the file
/verifyfile - checking a specific file without automatic correction

If everything is in order in the system, the message will notify that Windows resource protection has not detected any integrity violations. Otherwise, the message will differ depending on the situation. If windows can't execute this command, then do the same in safe mode.

If damaged files are detected and successfully replaced with correct versions, Windows will notify you of this with a corresponding message. At this point, we can consider the operation to check and restore the integrity of the Windows system files to be successfully completed.

Restoring the Component Store

However, it is possible that the storage itself will be damaged or missing. This is especially important for those who like to install custom OS builds instead of original images. In this case, the sfc utility will not work. To solve the problem, you can try to automatically restore the Windows component store using the command available starting from Windows 8:

Dism /Online /Cleanup-Image /RestoreHealth

Owners 7 having installed update KB2966583 can only check the storage with the command:

DISM /Online /Cleanup-Image /ScanHealth

The execution results can be found by looking at the log at C:\windows\Logs\CBS\Checksur.log

Manual recovery of damaged files

However, there may be a situation where the scan shows errors, but Windows Resource Protection will not be able to automatically correct them. Information about them will be contained in the CBS log file located at C:\windows\Logs\CBS\CBS.log which can be opened by any text editor.

Only for this it must be launched with computer administrator rights. The file stores a lot technical information, but we are interested in the lines containing . You can find them using the search built into the editor by pressing the Ctrl+F key combination or go the other way and run the following command in the command line running as administrator.

Findstr /c:"" c:\windows\logs\CBS\CBS.log >c:\sfcresult.txt

Thus, we tell Windows that it needs to find all the lines containing in the CBS.log file and save the result to drive C in the file sfcresult.txt. Thus, the file will contain filtered information related to the operation of the sfc command. All that remains is to study it carefully, not forgetting to pay attention to the date and time indicated in the line with the time of the scan, so as not to study old results. In this case, the system successfully restored the autoplay.dll file using the reference file from the storage in the WinSxS folder, about which there is a corresponding entry in the log.

2017-02-04 13:30:58, Info CSI 0000032f Repairing 1 components 2017-02-04 13:30:58, Info CSI 00000330 Beginning Verify and Repair transaction 2017-02-04 13:30:59, Info CSI 00000331 Repairing corrupted file "\??\C:\windows\System32"\"autoplay.dll" from store 2017-02-04 13:30:59, Info CSI 00000332 Repair results created: POQ 140 starts: 0: Move File: Source = "\SystemRoot\WinSxS\Temp\PendingRenames\e0b17dc6d17ed201983d0000f415f015._0000000000000000.cdf-ms", Destination = "\SystemRoot\WinSxS\FileMaps\_00000000000000 00.cdf-ms" 1: Move File: Source = "\SystemRoot\WinSxS\ Temp\PendingRenames\3a1480c6d17ed201993d0000f415f015.$$.cdf-ms", Destination = "\SystemRoot\WinSxS\FileMaps\$$.cdf-ms" 2: Move File: Source = "\SystemRoot\WinSxS\Temp\PendingRenames\a29d89 c6d17ed2019a3d0000f415f015. $$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = "\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms" 3: Hard Link File: Source = "\SystemRoot\WinSxS\amd64_microsoft-windows-autoplay _31bf3856ad364e35_6.1.7601.17514_none_04c88123045c625c \autoplay.dll", Destination = "\??\C:\windows\System32\autoplay.dll" POQ 140 ends. 2017-02-04 13:30:59, Info CSI 00000333 Repair complete

If it is impossible to fix the damaged system file automatically, we will have to fix it ourselves. The whole point of the operation comes down to replacing files existing on the computer with known good copies. They can be copied from another computer with a similar version of the Windows operating system and saved to some folder on your machine or to a flash drive.

However, just replace the files operating system will not allow you, you will first have to obtain the appropriate clearance. This can be done in the graphical interface, as we have already written about. Here we will look at how this can be done using the command line. First we need to take ownership of the damaged file, let's run the following command.

Takeown /f full_path_to_the_file, for example takeown /f C:\windows\system32\autoplay.dll

A useful technique that simplifies this operation. Now let's give the administrators group full access to the problematic file. Let's use the icacls command. In windows on English language you need to replace “ADMINISTRATORS” with “ADMINISTRATORS”.

Icacls full_path_to_file /GRANT ADMINISTRATORS:F, for example icacls C:\windows\system32\autoplay.dll /GRANT ADMINISTRATORS:F

Now we can replace old file to a new original one. This can be done either by using Windows Explorer or by continuing to work in the command line.

Copy full_path_to_the_new_file full_path_to_the_replaced_file copy D:\new\autoplay.dll C:\windows\system32\autoplay.dll

As a result of all the manipulations, we replaced the damaged system file manually. There's just one final touch left to secure yourself against possible problems in the future, we need to restore the previous owner of the object in the person of TrustedInstaller and regain our previous rights. Again this can be done using Windows Explorer or using the following commands:

Icacls C:\windows\system32\autoplay.dll /setowner "NT Service\TrustedInstaller" icacls C:\windows\system32\autoplay.dll /GRANT:r ADMINISTRATORS:RX

Where else can you get original system files?

Copying files from another computer is a fairly convenient and simple method, but you don’t always have another computer with a similar operating system at hand. In this case, you can use a windows distribution disk or a system recovery disk, if you made one.

The difficulty is that the information on them is stored in packed form in a file with the .wim extension and therefore you will have to work a little. In order not to mess around with the command line, let's use free archiver 7-zip. If you don’t have it on your computer, you can download it here; you’ll probably find it useful for working with archives.

The system files we are interested in are located in an image file named install.wim in the sources folder, and the image can contain several different versions operating system in the appropriate folders, be careful. On the recovery disk, the file is named boot.wim.

If your computer won't boot

All of the above referred to the case when the computer could boot and we had the opportunity to perform the check directly in Windows. However, the damage to system files may be so severe that it will not be able to boot. In this case, you can check the Windows system files in the WinRE (Windows Recovery Environment) recovery environment. To do this, boot into the recovery environment, as described here, and launch the command line.

Sfc /scannow /OFFBOOTDIR=X:\ /OFFWINDIR=X:\windows

Here X needs to be replaced with the drive letter on which the OS we want to check is located. The difficulty is that the drive letters in Windows RE may not match the partition letters in Windows itself. To find them out, run the following commands sequentially.

Diskpart List disk Sel disk 0 Detail disk Exit

As a result, we get a list of volumes on the system disk and their corresponding labels. We will substitute the required label instead of X in the command to start scanning system files. However, you can find out the desired disk label in another way, by brute force.

Cd /d C: dir /b

Here we first went to drive C, and then displayed a list of files in this section, by which we can understand which drive it actually is. If you didn’t guess, then move on to the next letter and look at the list again.

Cd /d D: dir /b

Sooner or later it will be found by “scientific poking” system disk. Suppose in the recovery environment the drive with windows has the letter G and we want to check the originality and, if necessary, automatically correct the file “C:\windows\System32\msconfig.exe”, then the command will take the following form:

Sfc /scanfile=G:\windows\System32\msconfig.exe /offbootdir=G:\ /offwindir=G:\windows

We looked at various ways to restore damaged system files in Windows in automatic and manual modes, including using the environment windows recovery. With its help, you can troubleshoot computer problems caused by damaged operating system components.

beginpc.ru

Checking Windows system files for integrity

Why do you need to restore the integrity of Windows system files? Checking the integrity of the Windows 10/8/7/XP OS is needed if you suspect that some of the system partitions have changed or become defective due to the influence of malware.

There are several tools to check the integrity of Windows 10 files. The most common is SFC.exe, DISM.exe is often used. You can also use the Repair-windowsImage function in PowerShell. We recommend using several methods, but one at a time. This is necessary because each option will check the integrity of different files. If you need to perform such a procedure, but do not know how to check the integrity of Windows 10 system files correctly in order to correct them and resume work, carefully read the recommendations below, follow the sequential steps, then you will be able to check and restore the integrity of Windows 10 system files and others versions.

Check the status of system files using windows tools

Scanning with SCF

Many users use the sfc /scannow command to scan the operating system before restoring lost or damaged files in order to ensure their correct functioning, restore uninterrupted operation, and troubleshoot problems by restoring damaged components. It examines and corrects system partitions of the Windows 10 OS offline.

Check using the command line

To activate this command, first open CMD and start with administrator rights. You can activate the utility using the mouse by right-clicking on the main “Start” menu, then selecting “Command Prompt” from the list. In the dialog box, type sfc /scannow and press Enter.
A check will begin, defects will be identified, and then they will begin to correct without your intervention, assistance automatically, by the system itself. If no errors are found, you will be informed that no problems were detected by OS resource protection.

If you decide to check one specific system file, then specify scf /scanfile=”path to file” on the command line.
It should be noted that SCF is not able to correct errors in those partitions that are running at the time of scanning, so it is best to use SFC exclusively when running “Recovery” windows environment 10".

Running SFC using the recovery environment

To properly activate SCF, follow the steps below in sequence.

After completing the steps described above, a list of volumes will appear; you need to remember or write down those letters that correspond to the system partition and the “System Reserved” disk.

sfc / /scannow /offbootdir=bootloader partition letter:\ /offwindir=E:\windows (or your path to the windows 10 directory).

As a result, a scan should run that checks the integrity of system files, and recovery will be available for all of them. Please note that the check will take quite a significant amount of time; you do not need to turn off or restart your computer during the entire procedure. The last step will need to be performed only when the scan is completed and you close the Command Prompt.

Scanning with DISM.exe

The command line is also used to launch DISM.exe. Activate it as an administrator and then follow the steps:

dism /Online /Cleanup-Image /CheckHealth - this function provides information about what defects and damage to various components of Windows 10 are present. A deep check, however, is not performed; only previously found data is used.
dism /Online /Cleanup-Image /ScanHealth - scans for possible damage to the component storage. This check often requires quite a lot of time, periodically freezing during the implementation process (usually by 20%).
dism /Online /Cleanup-Image /RestoreHealth - a thorough inspection and reconstruction of system files in offline mode, restoration, which also takes a long time.

The utility will help detect and restore damaged files

All logs of actions when executing the above commands are written to the path windows\Logs\CBS\CBS.log, windows\Logs\DISM\dism.log

Similar to the previous utility, DISM is also launched through Windows 10 recovery mode.

go to the Start menu;
click on the “Run” option;
In the dialog box, type the command “cmd”, then Enter on the keyboard.

As a result, a regular command line will open and you can perform all the steps to check OS files for defects.

All of these operations will help restore corrupted, damaged sections of any Windows-class operating system, which will solve the problem of malware interfering with the computer, restore its performance, and avoid extreme measures, such as a full system restore in case of operational problems. You do not need to reinstall the entire OS; it is enough to restore damaged components. Identify them using special commands and utilities, and your computer will continue to function.

NastroyVse.ru

How to perform a system file check in the Windows 7 operating system

As a result of some Windows 7 malfunctions and infections malware there is a need to analyze the file integrity of the system. Also, files are often damaged due to improper shutdown of the PC and power surges. Therefore, every “Seven” user should be able to independently check and resuscitate system files on a computer with Windows 7.

File analysis method

The main tool for checking and analyzing their integrity in “Seven” is the “SFC.exe” application built into the OS, which can also restore defective files. Regular use of the command to perform the “sfc /scannow” scan will ensure the smooth operation of Windows 7. It is recommended to use it at least once every six months.

Analysis procedure

The built-in Windows 7 scan tool is launched as follows:

Note: Do not close the console until the procedure is complete. Upon completion, the results of the completed program will appear.

Restart your computer;
Ready. The system integrity check has been completed and the corrupted files have been fixed.

Sometimes it happens that an application cannot cope with fixing damaged files on its own. In such cases, it is recommended to perform analysis in safe mode, but even if this does not resolve the problem, you need to run: “findstr /c:” “%windir%\Logs\CBS\CBS.log >”%userprofile%\Desktop\sfc .txt".

After this, a “txt” file will appear on the Windows 7 desktop with a list of all files that the program is not able to resuscitate itself. The user needs to copy these files to himself from another computer, but with a working Windows 7, or from an external installation media with a distribution kit of the “Seven” modification that runs on the user’s PC.

Algorithm for restoring a damaged file manually

Now, knowing the exact name and location of the problematic file that the application could not fix automatically, you need to replace it. To this end, it is necessary to take the following sequential steps:

What if the SFC.exe application does not work at all?

It happens that the utility cannot even start. In such a situation, you should analyze the performance of the following applications:

Remote Procedure Call Locator;
Remote call procedures;
Starting DCOM server processes.

If these programs are functioning normally, "SFC.exe" will start.

Also, the utility will not cope with its functions when the manual startup type of the recovery service is activated in the “Windows Module Installer” service.

Additional analysis methods via SFC

If you need, for example, to analyze the integrity of files on a remote OS or solve various other problems, then there are several of the following effective techniques:

It is possible to carry out the check without the subsequent recovery process. To do this, using the algorithm of the instructions given above, you need to use the command “sfc /verifyonly”.
If necessary, you can resuscitate only a specific file by typing in the console: “sfc /scanfile=Location”.
In a situation where you need to analyze Windows installed on another logical partition of the hard drive, the command: “sfc /scannow /offwindir=Windows directory location” will help.

Conclusion

Some users, at their own discretion, modify files, change icons in Explorer, and the like. After the application works to analyze and correct the integrity of the OS, all adjustments made will be canceled and will again take the default form. Therefore, such computer owners will need to perform all their system modification operations again after the utility has completed its work.

windowsTune.ru

Checking Windows 7 system files from the WinRE recovery environment

You've probably heard about such a useful utility as sfc. Being part of Windows, it allows you to check system files for discrepancies with the original version, which is very useful when the original system files have been replaced by a crooked installer, an evil virus, or a careless user. Undoubtedly, Windows Vista and Windows 7 have taken system security and the protection of your files to a new level and reduced the likelihood of system files being replaced. Reduced, but not eliminated, and it’s very difficult to protect yourself from the inquisitive mind and curiosity of the user.

Therefore, if, as a result of certain actions, your system refuses to boot, and you suspect (or even firmly believe) that the matter is that an important system file has been replaced by a damaged copy, you can check the integrity of system files using WinRE (windows Recovery Environment) , directly on the “fallen” system.

Running the sfc.exe utility from the Windows 7 recovery environment

1. Insert the Windows 7 installation disc into the DVD drive and boot from the DVD. Wait for this window to appear: Set the keyboard layout to "US" and click "Next".

2. In the next window, click "System Restore".

3. Now select the instance of Windows 7 that is damaged from the list and click “Next”. I have one.

4. Launch Command Prompt

To scan and repair one specific file, type sfc /scanfile=X:\windows\explorer.exe /offbootdir=X:\ /offwindir=X:\windows

Replace X: with the letter of the partition where your system is located.

To scan all operating system files completely, run the command sfc /scannow /offbootdir=X:\ /offwindir=X:\windows

You are not being deceived, the verification can really take some time, in my case it lasted about 7 minutes. Upon completion, the utility will display the path to the log of its work and tell you what it did with system files.

Winreview.ru can be found on Vkontakte, Facebook and Twitter. Join us!

winreview.ru

command SFC /SCANNOW - Checking system files in windows 7 - How to do this in windows 7?

1.png 47.21K 81 downloads

2.png 44.34K 51 downloads

3.png 200.96K 54 downloads

It is useful to view the logs and if you see in the scan results that the SFC command was unable to replace some system files, then you can try to do it manually.

Thank you, I completely forgot about this command, that it exists in Windows 7. I used it before, as soon as I installed the system, but then it completely slipped my mind. Now I ran the check, but thank God all the system files are in place. Now I’ll bookmark this topic so I don’t forget.

Very interesting and necessary information, I started checking now, thank you for this topic on the forum about Windows 7.

How to restore system files in Windows 7

The sfc /scannow (System File Check) command scans all Windows 7 system files and, if it finds changed, damaged or missing files, replaces them with correct versions if possible.

How to run sfc /scannow command in Windows 7?

1) Launch the command line as administrator.

2)In the command line, enter the command sfc /scannow (see screenshot)

1.png 47.21K 81 downloads

3)When the check is completed, I hope that everything will be fine with your Windows 7 system files, just like mine in the screenshot I posted below:

2.png 44.34K 51 downloads

If you know that you have damaged system files, but sfc /scannow did not give any results, then try to restore to a time when you have intact system files. You may have to go through several restore points before you find the point where there were undamaged Windows 7.4 system files) Checking system files takes time (15-30 minutes). After the check is completed, close the command prompt.

When the sfc command is launched in Windows 7, the scan results are written to a LOG file in this file: C:\WINDOWS\LOGS\CBS\CBS.LOGWe are only interested in the lines in this file labeled . To filter out unnecessary lines, you need to open the command line as an administrator, and insert the following command into it: findstr /c:"" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txtAfter running this command, a text file named sfcdetails.txt will appear on your desktop, which will contain the results of scanning Windows 7 system files.

3.png 200.96K 54 downloads

It is useful to view the logs and if you see in the scan results that the SFC command was unable to replace some system files, then you can try to do it manually. Tell me how to replace system files manually

Installed Office Tab Enterprise 8.0 on the program Microsoft Office 2010 v14.0.4763. During the installation process and after installation and activation, it displays (when starting the program itself and any Office application) error 1907: The font cannot be registered. Checking and fixing system files did not help, what should I do? If in this program you uncheck the boxes for using it with Office applications, the applications launch without problems. With uv. Victor.

Hello! The sfc / scannow command does not start for me. In the start menu, enter "cmd" in the search bar. I run the search result as an administrator and see, as in the first screen, as in the second screen, it doesn’t work. If I enter “sfc / scannow” and run the search result as an administrator, nothing appears. Just for a hundredth of a second, a window pops up and instantly disappears. Tell me the solution. Thank you!

Attached files

Tell me, what if I have a third party HDD, where I need to check the integrity of the system, how can I do this? By the way, on the laptop to which this disk belonged, the system does not boot at all, as if it were not there, although yesterday everything was fine, the laptop’s battery just ran out and it turned off.

What kind of messages does it write when loading? at what stage does it stop? loading windows 7? Regarding the SFC command - no, it cannot check system files on another disk.

operating room Windows system is in many ways similar to a living organism, which means that sometimes even the slightest damage or deletion of one or more of its files can lead to certain problems. Damage may be caused by viruses or malfunctions. software, sudden power outage, errors when editing system libraries, and so on.

As a result, the user may encounter various errors when launching programs or the inability to install them, problems with system settings and even blue screens of death. Therefore, when diagnosing problems, the first step is usually to check the integrity of Windows 7/10 system files. On this moment There are two main methods for checking and restoring system files - using standard utilities SFC And DISM, launched via the command line or PowerShell console.

The second tool is more powerful and is usually used when SFC is unable to cope with the task or its launch fails with an error. There are also those designed for this purpose third party programs, but they mostly duplicate the functionality of SFC and DISM, providing more convenient access to them by using GUI. In critical cases, when neither SFC nor DISM help, restore the system or its individual components using a previously created backup copy.

Using SFC

SFC utility or otherwise System Files Checker present in all Windows versions, since 2000, and is intended to check the status and restore system files. SFC can take multiple arguments, but in this case we are only interested in one. Using it, checking and restoring Windows 7/10 system files is done as follows. Launch a command prompt or PowerShell console as an administrator and run the following command:

sfc /scannow

The verification procedure will take some time. If errors are found upon completion, the utility will offer to restore damaged files while rebooting the computer. If SFC writes that it cannot recover files, make sure that you have EFS and Bitlocker encryption functions disabled, boot into safe mode, and then repeat the scanning procedure.

To provide maximum access to the file system, the procedure for restoring damaged Windows system files can be performed in the boot environment. There are several ways to get into the recovery environment, but we offer the most universal one. Boot your computer with installation disk Windows, and when the installation wizard window appears on the screen, click Shift + F10. Since the drive letters are different in the boot environment, you need to determine the system partition letter. We execute the following commands:

diskpart
list volume

On MBR disks, the system partition will most likely have the letter D, and the “System Reserved” partition will have the letter C. Knowing the letter labels of the volumes, use the exit command to close Diskpart and check:

sfc /scannow /offbootdir=C:/ /offwindir=D:/

Upon completion Windows scan will reboot in normal mode.

DISM utility

How to check the integrity of Windows 7/10 system files if the method described above does not help or various errors are generated when executing commands? In this case, you can try to resort to a more powerful tool - the utility DISM. Launch a command prompt with administrator rights and run the following command:

dism.exe /online /cleanup-image /scanhealth

If the utility reports that the component store needs to be restored, restore it with the following command:

dism.exe /online /cleanup-image /restorehealth

If you receive errors while running commands, try restoring the component store using elevated PowerShell by running the command Repair-WindowsImage -Online -RestoreHealth while your computer is connected to the Internet.

After completing the procedures, you can check sfc /scannow and see if the errors recur. If yes, check whether you have the Windows Module Installer service enabled, and in general, it is advisable to do this in advance.

Recovering damaged files manually

This method is used if it is impossible to restore damaged SFC files, but to use it, in any case, you will need exactly the same operating system installed on another computer or virtual machine or a backup copy. To determine which files need to be restored, run the command at the command line:

findstr /c: "" %windir%/logs/cbs/cbs.log >"D:/sfc.log"

Information about damaged files will be saved to a log file, in our case it is sfc.log to drive D. The contents of the file can be quite large, look for blocks with key phrase“Cannot repair” with the corresponding scan date and time.

The attached screenshot shows that SFC was unable to restore the Asseccbility.dll file. The same log should indicate the path to the unrecoverable file. Copy the original file from another computer and manually replace the damaged one with it. At this stage, you often have to deal with problems, since the file may turn out to be either in use system processes, or the user will not have rights to it.

To obtain rights and replace such files, you can use standard console utilities Takeown with parameter /f And icacls with parameter /grant administrators:f, but there is a simpler and universal method– use any “live disk” with built-in file manager, for example, Dr.Web LiveDisk. If the computer boots, everything is even simpler; just copy the original files to any folder convenient for you on its hard drive.

Edit boot ISO image the same Dr.Web LiveDisk can be found in UltraISO program by creating a folder in it and copying windows files into it.

Now let's look at how to restore Windows 7/10 system files using such a disk. After booting from the media, find your folder with files (in Dr.Web LiveDisk the mount point is /cdrom), copy the original files to the clipboard, go to the target directory of the folder win and replace the damaged ones with them.

If the original files are located on Windows disk, look for them in the win location, in the section in which you placed them. This method is convenient because it removes all restrictions file system Windows, allowing you to gain exclusive access to it.

Using Third Party Applications

Development special programs, which would allow you to restore damaged and deleted system files, does not make sense, since all the functionality necessary for this is available in the system itself. However, there are tools that make it easier to access regular means using a convenient graphical interface. This, for example, is Microsoft DaRT – boot disk, which is a set of administration tools that also includes a scan and recovery module for Windows system files. The procedure for such a check is presented in the screenshots below.

To make it more convenient to launch SFC, there are also programs Windows Repair and, only unlike Microsoft DaRT, they start from the working system.

In Windows Repair, to start the check, you need to go to the Pre-Repair Steps section, click on the “Step 4 (Optional)” tab and click the “Check” button.

In Glary Utilities, go to the “Modules” tab, select “Service” in the menu on the left and click “System File Recovery”. In both cases, the standard SFC console utility will be launched.

Other methods

As for the question of how to recover completely deleted system files, everything should be clear. If the disk size allows, regularly create backups system partition, or at least do not disable system protection, so that if something happens, you can roll back to the previous one.

And the last thing I would like to draw your attention to. If you downloaded and installed a custom build, be prepared for the fact that SFC will more than likely find corrupted files in it. The reason is very simple - collectors very often modify their images, replacing, for example, original icons in libraries and so on. Therefore, before restoring original files, think about whether you really need it if there are no problems with the system.

This article shows the steps by which you can recover damaged Windows system files using the SFC utility

If the operating system is unstable and various errors are noticed in its operation, then to troubleshoot problems you can use the SFC command line utility to restore the integrity of damaged system files.

SFC (System File Checker) is a Windows system tool for checking and restoring system integrity, which scans and checks all protected Windows system files for errors and replaces damaged or missing files with a copy of Windows files located in the WinSxS directory.

How to check and repair damaged system files using the SFC utility

To scan and repair damaged system files, run the following command as an administrator:

Depending on the scan results, you will see one of the following messages:

Windows Resource Protection did not detect any integrity violations. This means that no damaged or missing files were found on the system.

Windows Resource Protection cannot perform the requested operation. This message means that an error occurred during scanning. If you encounter this issue, try running the command sfc /scannow

Windows Resource Protection detected corrupted files and successfully repaired them. See CBS.Log WinDir%\Logs\CBS\CBS.log for information. This message appears when the SFC utility was able to correct the problem. You can view detailed information about the files that were recovered in the log file stored in C:\Windows\Logs\CBS\CBS.log

Windows Resource Protection has detected corrupted files, but is unable to repair some of them. See CBS.Log %WinDir%\Logs\CBS\CBS.log for information. In this case, Windows was unable to fix some files. Again, you can see the list of files in the log file stored in C:\Windows\Logs\CBS\CBS.log. In this case, the user will have to manually replace the missing or corrupted files.

You can also check and restore damaged system files using open as administrator.

How to check and repair damaged system files if the system does not boot

If the operating system does not boot, then you can also use the tool to restore the integrity of damaged system files, since the SFC utility supports offline scanning and recovery of damaged system files.

To do this you will need a (disk) with . Boot from the installation media and on the regional settings selection screen, launch the command line by pressing the key combination Shift + F10

Now you need to find out the letter of the partition on which the Windows operating system that needs to be checked is installed. This must be done because the drive partition letters in the boot environment are often different from those used in the running system.

There are several ways to do this, such as diskpart, wmic or the dir command, but we will use another method.

At the command prompt, run the following command:

In the Notepad window that opens, select from its main menu File - Open...

In the Explorer window, you will see the available sections and the letters assigned to them. IN in this example The partition on which the operating system is installed has the letter C. The Explorer and Notepad windows can now be closed.

Knowing the letter of the partition on which the operating system is installed, run the following command at the command line:

sfc /scannow /OFFBOOTDIR=C :\ /OFFWINDIR=C :\Windows