Menu
homePhoto and video

Windows system file checker. Checking the integrity of Windows system files. Restoring System Component Store: DISM

Hello friends! This article is a logical continuation of the recently launched epic about the fight against. And now the author will share with you one more effective method eliminate such troubles.

Therefore, the topic of the story will sound like this: the SFC scannow command in Windows 7 and 10. We will also consider the question of why sometimes it cannot restore system files. That is, simply put, it refuses to work.

So, what kind of command is this and what is it for? So, SFC scannow is system utility, which serves for automatic check and recovery important files operating system.

It is quite easy to use, but sometimes various nuances may arise. So let's get down to business to understand everything. All further actions will be shown on Windows example 10, although in Win 7 everything is done almost the same way.

Then enter the command itself:

The system scan process will begin, which may take quite some time. long time. So now all we can do is wait and hope that this team can fix everything.

After finishing the work, a report will appear, which will tell you about real situation business You will also have the opportunity to familiarize yourself with the log file and understand in detail the important details:

But as you can see in the screenshot above, in our case everything did not go very smoothly. Damaged files were detected, but Windows 10 was unable to restore them.

This happens because the SFC scannow parameter is unable to restore those system files that are currently being used by the operating system itself. In general, a real paradox emerges.

But nevertheless, there is a way out of this situation. You need to try the above steps in the Windows Recovery Environment. How to enter it on the tenth version of the system is described in great detail in

Well, on the seven you will have to use a pre-prepared boot disk and set it as priority on the computer. Alas, there is no other way.

Well, we continue the process of treatment and file recovery using Win 10 as an example. And now you will need to enter a small series of commands. The first one will be like this:

With the next function we will print common list installed on your computer hard drives. Each of them has already been assigned personal number, which we will need in the next step:

Now select the disk number zero discovered above, since it is the only one in the system:

At this stage, all that remains is to sort out the hard drive in order to understand which one is the system one, that is, with Windows installed:

After necessary information received, you can, so to speak, and move on from here. To do this, enter the following command:

And now, finally, the hour of truth has come. Now we will check the system files again and, in case of problems, try to restore them. So, let's start the process:

In this expression, the letter "C" indicates logical hard section disk on which the operating system is installed. Also, when entering, it is very important to ensure that the input is correct, in particular, to put problems where necessary.

Now we can only hope that after the scanning process is completed, the message “Windows Resource Protection has not detected any integrity violations” will be displayed.

What else can you tell about the SFC scannow command? For example, this parameter will be able to display a log with the results of work on the desktop in the recovery environment:

And the following method will allow you to check and restore a specific file. For example, in work Windows given the parameter will look like this:

Where "kernel32.dll" represents the name the desired file. And the entire expression is the path to the directory where it is located. The exact same command in the Windows 7 and 10 recovery environment will be slightly different:

Well, friends, now you know why sometimes the SFC scannow command in Windows 7 and 10 cannot restore system files. But in conclusion, it’s worth saying that there is another similar utility, which we also .

If you suddenly have any questions, feel free to ask them in the comments to the article. Now you can relax a little and watch a very interesting video. Guys, you definitely need to watch this.

Just like hardware, software also deteriorates because it is subjected to significant loads from the user. Therefore, checking the integrity of system files in Windows 10 should be performed periodically, and, if necessary, damaged areas should be repaired.

Examination

The OS has a built-in utility that identifies damaged files and replaces them with working versions.

Good to know! The original OS files are stored on the system disk in the folder Windows\WinSxS.

Possible problems

Restoring the OS using sfc /scannow will fail if the source storage itself has been damaged. In this case, you must first restore the original image using the utility Deployment Image & Servicing Management (DSIM). It is designed to work with Windows images.


Good to know! When restoring storage DISM utility Update Center is used.

Recovery

After running the utility DISM and restore the sources, run the command again on the command line sfc /scannow. This will happen full recovery integrity of the system. For further work restart your computer. If for some reason the correction failed and you use radical method reinstalling the OS, read how to create a bootable USB flash drive in the article “Creating a Windows 10 installation flash drive in various ways.”

Conclusion

Integrity Windows files 10 is broken after incorrect handling of them, frequent reinstallation programs or overwriting information. To restore, use the built-in utility sfc /scannow, which will do everything automatically using the original file storage. If the original image is damaged, restore it using Deployment Image & Servicing Management.

The operating system includes a large number of system files ensuring its normal operation. 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 WinSxS folder. If they differ or the file is missing, it is replaced with the original one from the repository.

To use System File Checker you need command line launched 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.

Not always required full scan With automatic correction, so there are a few more 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, a message will notify that the protection windows resources did not detect 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 found damaged files and their successful replacement with the 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 work sfc utilities will be impossible. To solve the problem, you can try automatic recovery 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 key combination Ctrl+F 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 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 0.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\a29d89c 6d17ed2019a3d0000f415f015. $$_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 similar version Windows operating system and save it to some folder on your machine or to a USB flash drive.

However, the operating system will not allow you to simply replace files; you will first have to obtain the appropriate permission. This can be done in graphical interface, which 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, find out the desired label disk can be done 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 we move on to 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 have reviewed various ways Restoring damaged system files in Windows in automatic and manual modes, including using the Windows Recovery Environment. 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 Windows 10/8/7/XP OS is needed if you suspect that part of 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 smooth operation, and troubleshoot problems by restoring damaged components. offline mode examines and corrects system partitions of Windows 10 OS.


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 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 be started, defects will be identified, then they will begin to be corrected 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 above steps, 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 what defects and damage are present different components windows 10. 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.

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 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 teams 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 for analysis file integrity systems. Also, files are often damaged due to improper shutdown of the PC and power surges. Therefore, every user of the "Seven" must be able to produce self-check and resuscitation of system files in 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 commands to perform the scan “sfc /scannow” 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.

  1. Restart your computer;
  2. 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 working Windows 7, or from an external installation media with the 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 following applications:

  1. Remote Procedure Call Locator;
  2. Remote call procedures;
  3. 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 “Windows Module Installer” service is activated manual type start the recovery service.

Additional analysis methods via "SFC"

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

  1. 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”.
  2. If necessary, you can only resuscitate specific file, typing in the console: “sfc /scanfile=Location”.
  3. 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 of this useful utility, like sfc. As part of Windows, it allows you to check system files for discrepancies with the original version, which is very useful when source files systems were replaced by a crooked installer, an evil virus or a careless user. Undoubtedly, Windows Vista and windows 7 have brought system security and the protection of their files to 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 installation windows disk 7 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 one from the list windows instance 7 which is corrupted 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

When the sfc command is launched in Windows 7, the scan results are written to LOG file to this file: C:\WINDOWS\LOGS\CBS\CBS.LOGWe are only interested in the lines in this file labeled . To filter not required lines you need to open a command line as an administrator, and insert the following command into it: findstr /c:"" %windir%\Logs\CBS\CBS.log >

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 it 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 verification is complete, 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 commands will appear on your desktop text file with the name sfcdetails.txt, 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 Microsoft program 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 its use from Office applications, then 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 inscriptions 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.

). 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 occur 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 the initial parameters to default.
/ENABLE – Enable normal operation 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.

Unstable problem Windows operation 7 is often associated with corruption or deletion of system files, for example, after reinstalling or installing an infected program. This is not the most complex problem- there are many ways to recover data standard means OS or manually. The simplest and effective options Let's look at it further.

Rollback to last stable state

By default, in all Windows, protection is active for system partitions. It is responsible for creating special checkpoints containing configuration information and system files of the environment before modifying it - installing applications, drivers and updates. Moreover, recovery points are created without such a reason by the system with at certain intervals or by the user himself.

If problems began to appear relatively recently, and you remember the approximate date of their appearance, then the best solution is to roll back the OS to the moment when no failures were observed during the operation of the OS.

In a production environment this is very easy to do:

All that remains is to reboot, after which the damaged system files will be replaced with previous working versions.

If Windows won't boot

Even if the damage to system data is so serious that the OS cannot boot on its own, you can use restore points:


The corresponding selection utility will launch control point, which needs to be worked with in the manner described earlier.

If pressing F8 does not open the boot options window, you will only be able to get into the recovery environment if you use the boot/ installation disk.

Using the standard SFC utility

This application checks and repairs basic OS system files. It can also be run on the command line with boot disk, from the window for selecting boot options after pressing F8 and from a running system. The last option is the simplest:


Once the operation is complete, SFC will notify you of the results - the corrupted data should be detected and corrected.

Recovering data manually

Sometimes the methods described above cannot fix the problem. For example, when DirectX update from distributions supplied with various applications, often get lost DLLs. Therefore, always try to update DirectX from the office. Microsoft website, and if trouble has already happened, then if there is new version all DLLs will be updated automatically after installing a fresh component package from the website http://www.microsoft.com/ru-ru/download/confirmation.aspx?id=35.

If the new version is on specified page no, then any DLL from another source can be transferred to your system yourself. Libraries are stored in the following directories:

  • for Windows 7×32 - in the folder C:\Windows\System32;
  • for Windows 7x64 - in the C:\Windows\SysWOW64 directory.

If, when you launch an application, a window appears informing you that a DLL is missing, and the installer from the Microsoft website reports its presence on your system latest version libraries and does not update components, you can simply use search engine. Find DLLs on the Internet and move them to the specified folders.

Not only DLLs, but also any damaged system files can be extracted from the installation Windows distribution 7. To do this, you just need to know which files are damaged. Often the OS itself informs the user about the absence of a DLL or about an application error, for example, Explorer.exe. You can get the information yourself.

Let's find out what system information is faulty

To do this, you will again need the command line; we have already described how to open it. Write the following command here:

indstr /N:"" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt", where N is the drive letter.

Press Enter, after which sfcdetails.txt will be created on the desktop, which you need to open and carefully review. Its content will be similar to the image below.

Here we see that the Accessibility.dll library is damaged. It is this that you will need to find on the Internet or extract it yourself from the existing Windows 7 distribution to carry out the recovery.

Extracting OS components from the distribution

In addition to the installation disk, you will need a small free application 7-zip. With its help, we will work with the install.wim image located in the sources directory. The order is as follows:


All that remains is to copy them to the desired folder or to a flash drive. You can replace damaged data with them using installation/bootable media or LiveCD.