The System File Checker tool built into Windows can scan your Windows system files for corruption or any other changes. If a file has been modified, it will automatically replace that file with the correct version. Here’s how to use it.
When You Should Run These Commands
If Windows is experiencing blue-screen or other crashes, applications are failing, or some Windows features just aren’t working properly, there are two system tools that might be able to help.
RELATED:Everything You Need To Know About the Blue Screen of Death
The System File Checker (SFC) tool built into Windows will scan your Windows system files for corruption or any other changes. If a file has been modified, it will automatically replace that file with the correct version. If the SFC command doesn’t work, you can also try the Deployment Image Servicing and Management (DISM) command on Windows 10 or Windows 8 to repair the underlying Windows system image. On Windows 7 and earlier, Microsoft offers a downloadable “System Update Readiness Tool” instead. Let’s take a look at how to use them.
RELATED:How to Scan for (and Fix) Corrupt System Files in Windows
Run the SFC Command to Repair System Files
Run the SFC command when troubleshooting a buggy Windows system. SFC works by scanning for and replacing system files that are corrupt, missing, or changed. Even if the SFC command doesn’t repair any files, running it will at least confirm that no system files are corrupted and then you can continue to troubleshoot your system with other methods. You can use the SFC command as long as the computer itself will start. If Windows will start normally, you can run it from an administrative command prompt. If Windows won’t start normally, you can try starting it in Safe Mode or in the recovery environment by booting from your installation media or recovery disc.
However you get to the Command Prompt—normally, Safe Mode, or recovery environment—you’ll use the command the same way. Just remember that if you start Windows normally, you will need to open the Command Prompt with administrative privileges. To do this, right-click the Start button and select “Command Prompt (Admin)”.
At the Command Prompt, type the following command and press Enter to run a full system scan and have SFC attempt repairs:
Leave the Command Prompt window open until the command completes, which may take some time. If everything is fine, you’ll see the message “Windows Resource Protection did not find any integrity violations.”
RELATED:How to Use Safe Mode to Fix Your Windows PC (and When You Should)
If you see a “Windows Resource Protection found corrupt files but was unable to fix some of them” message, try restarting your PC in Safe Mode and running the command again. And if that fails, you can also try booting with your installation media or recovery disc and trying the command from there.
Run the DISM Command to Fix SFC Problems
You shouldn’t normally have to run the DISM command. However, if the SFC command fails to run properly or can’t replace a corrupted file with the correct one, the DISM command—or System Update Readiness Tool in Windows 7—can sometimes fix the underlying Windows system and make SFC run correctly.
To run the DISM command in Windows 8 and 10, open a Command Prompt with administrative privileges. Type the following command and then press Enter to have DISM check your Windows component store for corruption and automatically fix any problems it finds.
Allow the command to finish running before closing the Command Prompt window. This may take five to ten minutes. It’s normal for the progress bar to stay at 20 percent for a while, so don’t worry about that.
If the results of the DISM command state that anything was changed, restart your PC and you should then be able to run the SFC command successfully.
On Windows 7 and earlier, the DISM command isn’t available. Instead, you can download and run the System Update Readiness Tool from Microsoft and use it to scan your system for problems and attempt to fix them.
Try a System Restore or System Reset Next
If you’re still experiencing system problems and the SFC and DISM commands don’t help, you can try more drastic actions.
Running the System Restore tool will restore your Windows operating system files, settings, and applications to an earlier state. This may fix system corruption problems if the operating system wasn’t also damaged at the earlier point when the restore point was created.
An if all else fails, you could always resort to performing a system reset or reinstalling Windows. On Windows 8 and 10, you can perform a “Reset this PC” operation to reset Windows to its default state. You’ll have the option to keep your personal files in place—though you’ll have to reinstall programs—or to remove everything and do a complete reinstall. Whichever you choose, make sure you’ve backed up your PC first! On Windows 7 and earlier, this will require using your computer’s manufacturer-provided recovery partition or reinstalling Windows from scratch.
If you encounter other errors while running any of the commands we’ve covered, try searching the web for the specific errors you encounter. The commands will often point you to log files with more information if they fail—check the logs for more details about specific problems. Ultimately, it may not be worth troubleshooting serious Windows corruption problems when you can just reset Windows to its default state or reinstall it. That decision will be up to you.
Image Credit: jchapiewsky on Flickr
READ NEXT
If you get the following error: “Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log” when running the sfc /scannow command in Windows 10 then you can try the methods on this page to fix the problem.
But first:
System File Checker
System File Checker is a built-in Windows tool that you can use to scan and repair missing or corrupted system files.
If system files are missing or corrupted, then Windows may not behave as expected and some Windows functions may not work, or Windows may crash.
You can run this tool with the sfc /scannow command in Windows Command Prompt (Admin).
DISM
The Deployment Image Servicing and Management (DISM) tool in Windows 8 and 10, can fix component store corruption that prevents the System File Checker from working correctly.
We will use this tool to fix our System File Checker problem.
The “SFC unable to fix corrupt files” problem
I just reinstalled Windows 10, and after installing all of my software, I scanned Windows with the System File Checker tool.
Windows Resource Protection Sfc
But:
When I ran the sfc /scannow command, I received the following error:
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windirLogsCBSCBS.log. For example C:WindowsLogsCBSCBS.log. Note that logging is currently not supported in offline servicing scenarios.
Fortunately, I found a solution, and on this page, I will share it with you.
And now:
How to Fix “sfc found corrupt files but was unable to fix” in Windows 10Method 1: Windows 10 Safe Mode
The first thing you should try is to (re)boot Windows 10 in “Safe Mode” and then run the sfc /scannow command.
1. Press and hold the [Shift] key on your keyboard.
![]()
2. Click on the start menu button.
3. Click on the power button.
4. Click on Restart.
Note: If the start menu button is not working, then you must open Settings, click on Update & Security, click on Recovery and then click on the Restart now button.
5. Choose Troubleshoot.
6. Choose Advanced options.
7. Choose Startup Settings.
Note: If you don't see Startup Settings, then you will have to click on See more recovery options located at the bottom of the screen.
8. Click on the Restart button.
9. Choose the Enable Safe Mode option (number 4 keyboard key).
10. Log into Windows.
11. Right-click on the start menu button and choose Command Prompt (Admin).
12. Type the following command:
13. Press Enter.
Method 2: DISM
1. Open Windows Command Prompt as administrator.
Three Ways to open Windows Command Prompt as administrator:
2. When the User Account Control (UAC) window appears, you click Yes.
Note: Depending on your settings, you might need to enter your administrator password first and then click Yes.
The Command Prompt window will appear.
3. Type the following command and press Enter:
4. Wait until the command is finished and then you can close the Command Prompt window.
5. Restart your computer.
6. Log into Windows. Dark avenger x apk mod download.
7. Right-click on the start menu button and choose Command Prompt (Admin).
8. Type the following command:
9. Press Enter.
Method 3: DISM and Windows 10 ISO
1. Go to https://www.microsoft.com/en-us/software-download/windows10/.
2. Click on the Download tool now button.
3. Open the media creation tool.
4. Click on the Accept button.
5. Select Create installation media (USB flash drive, DVD, or ISO file) for another PC.
6. Click on Next. Stop skype from opening on startup.
7. Make sure that the correct language, edition, and architecture is selected.
8. Click on Next.
9. Select ISO file.
10. Click on Next.
11. Select a location on your PC where you want to save the Windows.iso file.
Pita bread production line for sale. Automatic pita bread production line is our company's latest development of pita bread processing machinery. This pita bread production line include dough mixing machine, molding machine and pita bread bakery equipment. And it main be used for making Lebanese bread, lavash, etc. The machine is fully automated and easy to operate. These complete pre-owned pita bread production lines are available now from Production Line Equipment. Financing available on all equipment!
12. Click on the Save button.
The media creation tool will now download the Windows 10 iso file.
The download may take a while. The time it takes depends on your Internet connection (speed) and Microsoft's servers.
13. When the download is ready, you will need to unzip (extract) the ISO file with a file archiver program like 7-Zip, WinRar, or WinZip.
14. Open the sources folder of your unzipped (extracted) ISO file.
15. In the sources folder, you will find a install.wim file. Copy this file to your desktop.
![]()
16. Create a new folder on your desktop and name it mount.
17. Open Windows Command Prompt as administrator.
Three Ways to open Windows Command Prompt as administrator:
18. When the User Account Control (UAC) window appears, you click Yes.
Note: Depending on your settings, you might need to enter your administrator password first and then click Yes.
The Command Prompt window will appear.
Note: You must wait until a command is completed before you run the next command.
19. Type the following command and press Enter:
20. Type the following command and press Enter:
21. Type the following command and press Enter:
This may take 5 to 10 minutes, and at 20% it will look like it's stuck (freezes), but that's okay. It's normal. Don't worry. It will work. Just be patient and wait until the command is 100% completed.
22. Type the following command and press Enter:
Note: when you're trying to unmount your wim image and you get an error like 0xc1420127, then try the following command:
Windows Resource Protection Error Sfc …
23. Now it's time to re-run the sfc /scannow command, so type the following command and press Enter:
References:
When you run the System File Checker (Sfc.exe) using the
/scannow parameter to restore missing or corrupt system files, the following error may occur.
Windows Resource Protection could not start the repair service
Additionally, you may experience problems running Windows Installer Setup files and installing fixes from Windows Update.
This happens if the TrustedInstaller (Windows Modules Installer) service is disabled. The TrustedInstaller service has full access to Windows Resource Protection (WRP) files and registry keys, and this services needs to be running in order to restore missing or corrupted WRP resources. The TrustedInstaller service starts on-demand when running the System File Checker.
Use these steps to reset the service startup type of Windows Modules Installer service.
1. Press Winkey + R to launch the Run dialog, type Services.msc, and press ENTER
2. Double-click Windows Modules Installer
3. Set its Startup type to Manual
4. Click OK.
To accomplish the same using command-line, open Command Prompt as administrator. Run the following commands and press ENTER after each line.
Run Sfc Scannow As Administrator
That should fix the problem. Another option would be to run
Sfc /scannow in offline mode (Windows Recovery Environment).
This article was originally written for Windows Vista and 7, but very much applies to Windows 8 and Windows 10 as well.
One small request: If you liked this post, please share this?One 'tiny' share from you would seriously help a lot with the growth of this blog.Some great suggestions:
You'd like to read these articles:About the author
Ramesh Srinivasan founded Winhelponline.com back in 2005. He is passionate about Microsoft technologies and has a vast experience in Windows — delivering support for Microsoft's consumer products. He has been a Microsoft MVP (2003-2012) who contributes to various Windows support forums.
Windows Resource Protection is a feature in Windows Vista that replaces Windows File Protection. It protects registry keys and folders in addition to critical system files. The way it protects resources differs entirely from the method used by Windows File Protection.
Overview[edit]
Windows Resource Protection works by registering for notification of file changes in Winlogon.[disputed] If any changes are detected to a protected system file, the modified file is restored from a cached copy located in a compressed folder at %WinDir%System32dllcache. Windows Resource Protection works by setting discretionary access control lists (DACLs) and access control lists (ACLs) defined for protected resources. Permission for full access to modify WRP-protected resources is restricted to the processes using the Windows Modules Installer service (TrustedInstaller.exe). Administrators no longer have full rights to system files, they have to use the SetupAPI or take ownership of the resource and add the appropriate Access Control Entries (ACEs) to modify or replace it. The 'Trusted Installer' account is used to secure core operating system files and registry keys.
Protected resources[edit]
Windows Resource Protection protects a large number of file types:
WRP also protects several critical folders. A folder containing only WRP-protected files may be locked so that only the trusted installer is able to create files or subfolders in the folder. A folder may be partially locked to enable administrators to create files and subfolders in the folder. Essential registry keys installed by Windows Vista are also protected. If a key is protected by WRP, all its sub-keys and values can be protected. Also, WRP copies only those files that are needed to restart Windows to the cache directory located at %WinDir%WinSxSBackup. Critical files that are not needed to restart Windows are not copied to the cache directory, unlike Windows File Protection which cached the entire set of protected file types in the Dllcache folder. The size of the cache directory and the list of files copied to cache cannot be modified.
Windows Resource Protection applies stricter measures to protect files. As a result, Windows File Protection is not available under Windows Vista. In order to replace any single protected file, Windows File Protection had to be disabled completely; Windows Resource Protection works on a per-item basis by setting ACLs. Therefore, by taking ownership of any single item, that particular item can be replaced, while other items remain protected.
System File Checker is also integrated with WRP. Under Windows Vista, Sfc.exe can be used to check specific folder paths, including the Windows folder and the boot folder.
See also[edit]External links[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Windows_Resource_Protection&oldid=811182917'
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |