Search Products

Stay Connected:
The cart is empty.
Cart contains {{shoppingcart.totalQuantity}} Item(s) Total: {{shoppingcart.subtotal}} {{}}

Browse by Category

Useful Links

How to Repair Corrupted Windows System Files and dealing with the BSOD

How to Repair Corrupted Windows System Files with the SFC and DISM Commands


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.

If the SFC command doesn’t work, you can use the 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.

When You Should Run These Commands

Run this command when troubleshooting a buggy Windows system. If Windows is blue-screening, applications are crashing, or some Windows features just aren’t working properly, the SFC command may be able to fix this. Even if the SFC command doesn’t repair any files, running it will confirm that no system files are corrupted and you can continue to troubleshoot your system with other methods.

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 can fix the underlying Windows system and make SFC run correctly.

Run the SFC Command to Repair System Files

You’ll need to do this from and Administrator Command Prompt window. To open one on Windows 10 or 8.1, right-click the Start button and select "Command Prompt (Admin)”. On all versions of Windows, you can also search the Start menu for Command Prompt, right-click it, and select Run as Administrator.


Type the following command into the Command Prompt window and press Enter to run a full system scan:

sfc /scannow

Leave the Command Prompt window open until the command completes — this may take some time. If everything is fine, you’ll see the message "Windows Resource Protection did not find any integrity violations.”

If you see a "Windows Resource Protection found corrupt files but was unable to fix some of them” message, try rebooting into Safe Mode first. On Windows 10, 8.1, or 8, hold the Shift key while clicking the Restart option to access the advanced boot options menu. On Windows 7 or earlier, reboot your computer, and then press and hold the F8 key while it’s booting up. Run the sfc /scannow command from within Safe Mode.

Run the DISM Command to Fix SFC Problems

On Windows 10, 8.1, and 8, the Deployment Image & Servicing Management tool can fix component store corruption that prevents the SFC command from working properly.

To run this command, open a Command Prompt as administrator. Type the following command and press Enter. DISM will check your Windows component store for corruption and automatically fix any problems it finds.

DISM /Online /Cleanup-Image /RestoreHealth

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 DISM command changed anything, restart your computer afterwards. You can now run the SFC command again and it would be able to replace any corrupted files with the correct ones.


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 System Restore or a System Reset

If you’re still experiencing system problems and these tools can’t help, you can try more drastic actions. Running the System Restore tool will restore your Windows operating system files to an earlier state, and this may fix system corruption problems if the operating system wasn’t damaged at that earlier point.

There’s always just performing a system reset or reinstalling Windows, too. On Windows 10, 8.1, and 8, you can perform a "Reset this PC” operation to reset Windows to its default state. You’ll have to reinstall your programs after, but you won’t lose any personal files. 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 the above commands, try searching the web for the errors you encounter. The commands will often point you to log files with more information if they fail, too — check the log files 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.

The above commands also have other options, too. For example, you can have the SFC command check only a single Windows file for corruption and repair it. You can have the DISM command perform a quick check for system corruption without repairing it, or provide a WIM or ESD file containing Windows operating system files.

Useful Tips for Dealing With BSODs (blue screen of death)

BSODs have a variety of root causes, but these tips will help you deal with many blue screens:

  • Use System Restore: If your system recently started blue-screening, use System Restore to roll its system software back to a previous state. If this works, you’ll know that it’s likely a software problem.

  • Scan for Malware: Malware that digs deep into Windows and gets its hooks into the Windows kernel at a low level can cause system instability. Scan your computer for malwareto ensure buggy malicious software isn’t causing it to crash.

  • Install Updated Drivers: An incorrectly installed or buggy driver can lead to crashes. Download the latest drivers for your computer’s hardware from your computermanufacturer’s website and install them — this may fix BSODs caused by driver problems.

  • Boot Into Safe Mode: If your computer is blue-screening every time you turn it on,try booting into safe mode. In safe mode, Windows loads only the essential drivers. If a driver you’ve installed is causing Windows to blue screen, it shouldn’t do so in safe mode. You can work on fixing the problem from safe mode.

  • Check for Hardware Problems: Blue screens can be caused by faulty hardware in your computer. Try testing your computer’s memory for errors and checking its temperature to ensure that it isn’t overheating.

  • Reinstall Windows: Reinstalling Windows is the nuclear option. It will blow away your existing system software, replacing it with a fresh Windows system. If you followed M-Tech Laptops standard recommendation to create a system image once your computer is setup, you can avoid the time and hassle of reinstalling Windows. If your computer continues to blue screen after this, you likely have a hardware problem. Contact technical support at 626-243-3284 and have your serial number handy.(begins with PS2)