Tech World

How Do I Repair Windows 10 with Command Prompt?

Windows 10 was Microsoft’s answer to the not so successful Windows 8 where users actually opted to stick with Windows 7 instead of upgrading to the latest version of Windows. However, this was not the case when Windows 10 was released to the market.

It basically used Windows 7’s framework and improved every bit of it and added a few tweaks to make it even better. With over 50 million installs worldwide, Windows 10 has been warmly welcomed by computer enthusiasts.

However, it is not perfect. Windows 10 also encounters a few errors and bugs once in a while which is normal for operating systems. This is why Microsoft makes it a point to rollout updates at patches to the system to ensure that everything works well on your computer.

Luckily, Windows 10 has a few tools that you can use to perform basic troubleshooting and repair. On this guide, we are going to show you how to repair Windows 10 using the Command Prompt which is a very useful tool to perform different kinds of command to your operating system

Let’s get started.

Method 1: Repair Windows 10 using SFC Scan.

The first tool that we are going to introduce to you is SFC Scan. System File Checker is a built-in tool on Windows that users can use to scan system files on your computer. It automatically repairs corrupted files and replaces missing files on your operating system.

For you to use the System File Checker on Windows, you would need to run it on Command Prompt. You can follow the steps below to guide you through the process.

1. On your computer, press on Windows Key S and search for Command Prompt.

2. Now, click on Run as an Administrator to launch Command Prompt with administrative privileges.

3. After that, type sfc /scannow on Command Prompt and hit Enter.

4. Lastly, after System File checker attempts to repair your system files it will return a message depending on the result of the scan.

Check out the list below for all the possible messages that will appear after running SFC scan.

1. Windows Resource Protection did not find any integrity violations – This kind of message appears when System File Checker did not detect any missing or corrupted files on your operating system.

2. Windows Resource Protection could not perform the requested operation – If this message appears after running SFC scanner, it means that the tool detected a problem during scan and an offline SFC scan is needed.

3. Windows Resource Protection found corrupt files and successfully repaired them – If SFC scanner was successful in repairing missing or corrupted files on Windows, this message will appear.

4. Windows Resource Protection found corrupt files but was unable to fix some of them. – Just like the second message, this will appear if System File Checker was unable to repair corrupted system files on your computer.

Now, try to run sfc /scannow command at least two or three more times to ensure that all corrupted files on your computer was repaired successfully.

However, if SFC Scan was unable to repair corrupted files on your operating system you can try running the tool in offline mode which is discussed in detail below.

Method 2: Run SFC Scanner in Offline Mode.

SFC scanner cannot repair some system files especially if it is being used to run Windows. In this case, it is best that you run SFC scan in offline mode so that all of your system files would be scanned and repaired.

To do this, you can follow the steps below.

1. Press on Windows Key I on your keyboard to open Windows Settings.

2. After that, click on Update & Security.

3. Now, on the side menu click on Recovery and select Restart Now.

4. Wait for Windows 10 to restart, then click on Troubleshoot from the selection menu that will appear.

5. Next, click on Advanced Options and select Command Prompt.

6. To run SFC scan offline, you would need to point the tool exactly where your installation files are located. Type wmic logicaldisk get deviceid, volumename, description and hit Enter.

7. On our case, installation files are located at Drive: C. Now, type the following commands sfc /scannow /offbootdir=C:\ /offwindr=C:\Windows.

8. Lastly, hit Enter and wait for the scan to finish repairing and replacing all your corrupted system files.

Now, reboot your computer normally and observe if you would still encounter problems on Windows 10 after repairing your system files.

On the other hand, here’s another way on how you can repair Windows 10 using the Command Prompt.

Method 3: Use DISM to Repair Windows.

Windows 10 features a command-line utility called Deployment Image Servicing and Management. DISM command is used to prepare and repair Windows images, Windows Setup, and Windows Recovery.

To repair Windows using DISM, check out the steps below.

1. On your computer, click on Windows Key S and search for Command Prompt.

2. Now, click on Run as Administrator to run CMD as an Admin.

3. Lastly, you can select from the commands below on what would you like to use and hit Enter.

DISM /Online /Cleanup-Image /CheckHealth – this will scan Windows for any corruption on its system files.

DISM /Online /Cleanup-Image /ScanHealth – this command checks and repairs any problem with Windows images.

DISM /Online /Cleanup-Image /RestoreHealth /Source: repairSource\install.wim – this runs an advanced scan on your system files and automatically repairs any problem detected.

After running DISM command on your computer, restart it and use it normally to check if any problems on Windows 10 would still occur after repairing your system files.

In summary, Windows 10 has come a long way and with the addition of these simple tools that automatically repairs system files on your computer makes the whole Windows experience a whole lot better.

These tools are available on all Windows 10 versions and all you need to do is to know how to use these tools to your advantage.

  • Love
  • Save
    3 loves 1 save 2 comments
    Add a blog to Bloglovin’
    Enter the full blog address (e.g. https://www.fashionsquad.com)
    We're working on your request. This will take just a minute...