Skip to main content

Fix: To use System Restore, you must specify which Windows Installation to Restore Error

The error ‘To use System Restore, you must specify which Windows Installation to Restore’ is caused due to corrupted system files etc. and pops while trying to run system restore. Sometimes, when you face an error that makes you perform a system restore, your computer might prompt you with this error. Consequently, you aren’t able to perform a system restore which is in some cases essential in fixing an error, hence the error can be a real obstacle.
In some cases, users have reported that their Windows doesn’t boot up while they encounter this issue. Aside from the ordeals, this error can be solved by the solutions provided below quite easily. Therefore, you don’t have to panic and just find your way back through the solutions.

Windows System Restore Error

What causes the ‘To use System Restore, you must specify which Windows Installation to Restore’ Error?

This error can be caused due to one of the following reasons: –
  • Corrupted system files. If any of your prior action has caused your system files corruption, it might be appearing because of that.
  • BCD corruption. BCD is also known as Boot Configuration Data corruption may be the cause of the error as it stores all the boot data.
You can implement the following solutions to try to fix your problem: –

Solution 1: Running CHKDSK

First and foremost, to verify the integrity of the volumes on your hard disk, you’ll have to use a built-in utility called CHKDSK. If you’re unable to boot into Windows, follow the below-mentioned instructions to access command prompt:
  1. If you are unable to boot into Windows, boot up your system and when the Windows logo appears, press F8. This will take you to Recovery Options.
  2. In the Recovery Options, select Troubleshoot.
    Windows Recovery options
  3. There, go to Advanced Options.
  4. Now, select Command Prompt.
  5. Once the command prompt opens, you’ll have to check the integrity of your volumes. Make sure to scan the Primary Partition type volumes as well. Type in the following command (replace C: with your volume alphabets).
    Running chkdsk to verify drives integrity
chkdsk C: /offlinescanandfix
  1. If any errors are found, run the command again until there are no errors.

Solution 2: Using SFC Scan

Like we mentioned earlier, one of the reasons the error might pop-up could be your corrupted system files in which case you’ll have to run System File Checker or SFC. Here’s how to do it:
  1. To know your system drive, type in the following:
Cd /

Dir
  1. If you see ‘Users’ folder in the list, this means it is your system drive, if not change your drive by typing alphabets of your volumes, for example:
F:
  1. After you’ve found your system volume, in the command prompt, type in the following:
    SFC scan to check for corrupt system files
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
  1. Where C: is your system drive.

Solution 3: Using DISM

DISM or Deployment Image Servicing and Management is a tool that can be used to restore the integrity of system files as well as service Windows. You’ll have to use this tool to restore the health of your system meaning to restore the integrity of your system files. Do the following:
  1. In the command prompt, type in the following:
    Using DISM to verify files
DISM /Image:C:\Windows /Cleanup-Image /RestoreHealth /Source:C:\Windows\WinSxS
  1. Here, C: is your system volume.
  2. If it vomits an error, you’ll have to insert a windows bootable USB or DVD and then enter the following:
    DISM fixing files through the new source
DISM /Image:C:\Windows /Cleanup-Image /RestoreHealth /Source:esd:E:\Sources\Install.esd:1 /limitaccess
  1. Where E: is the removable drive meaning USB drive or DVD drive. Replace it if you have to.
  2. In some cases, the install.esd may be install.wim. In such an event, you’ll have to enter the command as follows:
DISM /Image:C:\Windows /Cleanup-Image /RestoreHealth /Source:wim:E:\Sources\Install.wim /limitaccess

Solution 4: Using Bootrec

There’s a built-in command-line tool called Bootrec.exe which can be used to troubleshoot Windows startup/boot up issues. To scan your system for boot up issues, do the following:
  1. In the command prompt, type in the following one-by-one:
    Executing bootrec to fix startup issues
BootRec /Fixmbr

BootRec /FixBoot
Executing bootrec to fix the bootup issues
BootRec /RebuildBCD
  1. Reboot your system.
Make sure a bootable USB or DVD is inserted into your system before running the commands.

Solution 5: Run Windows Repair

Lastly, what you can do to fix this or any other error that you’re facing is to run Windows Repair. For this, you’ll require a Windows bootable USB or DVD. Here’s how:
  1. Insert your bootable USB or DVD.
  2. Boot into the USB or DVD.
  3. There, select ‘Repair your computer’.
    Repairing Windows
Please make sure you follow the solutions in the given sequence.

Comments

Post a Comment

Popular posts from this blog

Fix: The Following Error Occurred Attempting to Join the Domain

Several users are getting the ‘ following error occurred attempting to join the domain ‘ error when trying to connect a computer to a home or work domain. Most of the time, the error is accompanied by an explanation message telling the user that it has exceeded the maximum number of computer accounts. The issue is not restricted to computers that connect to a domain for the first time, as it’s often reported to occur with PCs and laptops previously connected to the same domain. The following error occurred attempting to join the domain. Your computer could not be joined to the domain. What is causing the ‘following error occurred attempting to join the domain’ error? We investigated this particular error by looking at various user reports and the troubleshooting guides that they themselves followed to get the issue resolved. Based on what we were able to gather, there are several different scenarios that might trigger this particular error message: SMB1 support is di...
Post a Comment
Read more

Fix: System Found Unauthorized Changes on the Firmware, Operating System or UEFI Drivers

Several users are struggling with the  System found unauthorized changes on the firmware error  at every startup or when trying to take their computer out of hibernation mode. Most affected users report that the issue started occurring after they installed some pending Windows updates. The issue is mostly encountered on Windows 7. The system found unauthorized changes on the firmware, operating system or UEFI drivers. Press [OK] to run the next boot device, or enter directly to BIOS Setup if there are no other boot devices installed. What is causing the System found unauthorized changes on the firmware error We investigated this particular issue by looking at various user reports. This error will occur whenever your system is checking the firmware one some computer hardware parts as part of a new security feature. To be precise, the error is occurring because not all Windows versions will support this new security feature. As it turns out, there are sev...
Post a Comment
Read more

Fix: There is a system repair pending which requires reboot to complete

A pending system repair is a notification which means that no system level actions can be performed until the system repair in queue is processed. This is usually fixed after a reboot. This error appears on Windows PC after an SFC scan has been launched. SFC stands for System File Checker and it’s a tool used to find and fix errors concerning system file. However, the problem occurs when this error message comes up after you try to run the scan. The system checks for pending system repair files when the SFC is initiated and these files have remained there from previous system repairs. If you have indeed launched a system repair process, restart your computer and check to see if the problem is gone. Otherwise, follow the method below. Solution 1: Delete the Following Files in Command Prompt These files keep track of pending system repair processes running on your computer and the file may have gone corrupt. Deleting will reset the pending processes and the system won’t...
Post a Comment
Read more