In this article, we will be trying to resolve an error that some users are facing when doing a system restore to an earlier date. The issue doesn’t allow the user to restore from the restore point created. It says “System Restore did not complete successfully” with the following Details:
Causes:
Let’s look at the possible solutions now.
Method 1: System Restore From Safe Mode
Before trying any fix you could first try disabling your antivirus completely and then do a restore. Similarly, also try disabling Windows Firewall and try to do a restore. If these did not help then let’s try doing a system restore from Safe Mode. Follow the instructions below:
Method 2: Run Check Disk (chkdsk)
If System Restore is not working then there is a possibility that there is some issue with your hard drive. Check Disk or ‘chkdsk’ is a command-line tool that helps to analyze and fix file system and hard drive errors. Follow the steps below to scan your hard drive for bad sectors:
Method 3: Run the System File Checker (SFC) Tool
System File Checker or SFC is a tool to check and fix corrupt system files. It scans Windows and restores the files which are not functioning correctly. To run this tool follow the instructions below: For more information about SFC, click this link. Method 4: Unlink One Drive If you want to create a new restore point and are experiencing an issue creating one then this method will also be helpful to you. Follow the instructions below:
Unlinking One Drive
Creating A New Restore Point
Now, if you want to create a new Restore point without any issues follow steps below:
Method 5: Reinstall Windows 10
Reinstalling Windows should be your last resort. In case none of the above solutions works then you can try doing a fresh install of Windows. It is a lengthy process and there are a number of ways to do it like using a USB or through the ISO file. Follow this link to correctly reinstall Windows 10 in your computer. If you specifically want to go back to a previous restore point and none of the above solutions has worked then, it’s probably better to wait for Microsoft to officially resolve this issue.
