Home error codes system restore troubleshooting windows

System Restore Error 0x80071160: Troubleshooting File Extraction Failure

Updated: • 0 • 9 min read

System Restore is a long-standing and vital feature in Windows that allows users to revert their system to a previous working state. This can be incredibly useful for recovering deleted files or undoing system changes that have led to instability. However, System Restore can sometimes fail, presenting errors that prevent users from effectively utilizing this recovery tool. One such error is System restore failed to extract the file, error 0x80071160, often associated with appxstaging. This error typically arises due to permission issues that hinder the extraction of files from the System Restore backup.

In many instances, the problematic file is WdBoot.sys, which is the Microsoft antimalware boot driver and a critical operating system file. When System Restore encounters difficulties extracting this or similar files, it signals a deeper issue that needs to be addressed to ensure the smooth operation of the system recovery process.

Resolving System Restore Error 0x80071160

If you encounter the “System restore failed to extract the file, error 0x80071160” error, it indicates that System Restore has been unsuccessful. To rectify this problem, it is essential to employ an administrator account, as resolving this error often necessitates modifications to file permissions. The following troubleshooting steps can help address this issue and restore the functionality of System Restore.

  1. Disable Antivirus Software
  2. Initiate System Restore from the Advanced Recovery Environment
  3. Rename the WindowsApps Folder
  4. Repair Windows using DISM and SFC Commands

Having a robust backup strategy in conjunction with System Restore is always recommended. In situations where System Restore fails, as indicated by error 0x80071160, a separate backup can serve as a reliable alternative to restore missing files and system configurations.

1] Disable Antivirus Software

System restore failed error

User reports suggest that antivirus software can be a significant contributor to the System Restore error 0x80071160. Antivirus programs, while crucial for system security, can sometimes interfere with system processes, including System Restore. As a preliminary troubleshooting step, temporarily disable your antivirus software, whether it’s Windows Defender or a third-party solution.

If you are using a third-party antivirus program, consult its documentation for instructions on how to temporarily disable it. For Windows Defender, you can typically disable real-time protection through the Windows Security settings. After disabling the antivirus, attempt to run System Restore again to see if the error persists. If System Restore completes successfully, it indicates that the antivirus software was indeed interfering with the process. Remember to re-enable your antivirus software once troubleshooting is complete to maintain system security.

2] System Restore from Advanced Recovery Environment

Since permission issues are often implicated in the System Restore error 0x80071160, utilizing the Advanced Recovery Environment (WinRE) can provide a more conducive environment for System Restore. WinRE operates outside of the standard Windows environment, potentially circumventing permission restrictions that may be causing the error. You can access the Advanced Startup Options either from within Windows or by booting from a Windows 11/10 Bootable USB drive.

Steps to Access System Restore from Advanced Recovery Environment:

  • Accessing Advanced Startup Options from within Windows:

    1. Open Windows Settings by pressing Win + I.
    2. Navigate to Update & Security > Recovery. In Windows 11, the Recovery option is located under Windows Update > Advanced options in Settings.
    3. Under Advanced Startup, click the Restart now button.

  • Navigating to System Restore in WinRE:

    1. After your system restarts in the Advanced Recovery Environment, select Troubleshoot.
    2. Then, choose Advanced options.
    3. From the Advanced options menu, click on System Restore.
    4. Follow the on-screen prompts to choose a restore point and initiate the System Restore process.

If System Restore is successful from the Advanced Recovery Environment, the error was likely due to permission constraints within the regular Windows environment. If the error persists, you can also explore other options within the Recovery Environment, such as Startup Repair, before attempting System Restore again.

3] Rename WindowsApps Folder

Another potential solution involves renaming the WindowsApps folder, which is located in the Program Files directory of your Windows installation drive (typically C:\Program Files). The WindowsApps folder is a hidden system folder that contains applications downloaded from the Microsoft Store. Modifying this folder requires adjusting permissions and may resolve issues related to file extraction during System Restore.

Important Note: Before renaming the WindowsApps folder, it is strongly recommended to create a system restore point. This precaution ensures that you can revert your system to its current state if any unforeseen issues arise from renaming the folder.

You can rename the WindowsApps folder using either Safe Mode or the Advanced Recovery Environment.

Safe Mode Method

Safe Mode Command Prompt

  1. Boot into Safe Mode: Restart your computer and boot into Safe Mode with Command Prompt. The process for entering Safe Mode can vary depending on your Windows version. Typically, pressing F8 or Shift + F8 during startup may provide access to the boot menu, where you can select Safe Mode. Alternatively, you can use the msconfig utility to configure your system to boot into Safe Mode.
  2. Log in with an Administrator Account: Once in Safe Mode, log in using an administrator account.
  3. Open Command Prompt: Search for “Command Prompt” in the Start Menu, right-click on it, and select “Run as administrator”.
  4. Execute Commands: In the elevated Command Prompt, type the following commands one by one, pressing Enter after each command. These commands assume that your Windows installation is on the C: drive. Adjust the drive letter if your Windows is installed on a different drive.
cd C:\Program Files
takeown /f WindowsApps /r /d Y
icacls WindowsApps /grant "%USERDOMAIN%\%USERNAME%":(F) /t
attrib WindowsApps -h
rename WindowsApps WindowsApps.old

*   `cd C:\Program Files`: Changes the current directory to the Program Files folder.
*   `takeown /f WindowsApps /r /d Y`: Takes ownership of the WindowsApps folder and all its subfolders and files, recursively. The `/d Y` option answers "Yes" to all prompts.
*   `icacls WindowsApps /grant "%USERDOMAIN%\%USERNAME%":(F) /t`: Grants full control permissions to the current user for the WindowsApps folder and all its subfolders and files, recursively.
*   `attrib WindowsApps -h`: Removes the hidden attribute from the WindowsApps folder, making it visible in File Explorer.
*   `rename WindowsApps WindowsApps.old`: Renames the WindowsApps folder to WindowsApps.old.
  1. Reboot Windows: After executing the commands, reboot your computer normally.
  2. Try System Restore Again: Once Windows has restarted, attempt to run System Restore again and check if the error 0x80071160 is resolved.

Advanced Recovery Method

Advanced Recovery Command Prompt

  1. Boot into Advanced Recovery Mode: Boot your computer into the Advanced Recovery Environment as described in section 2.
  2. Navigate to Command Prompt: In the Advanced Recovery Environment, go to Troubleshoot > Advanced options > Command Prompt.
  3. Execute Commands: In the Command Prompt, type the following commands, pressing Enter after each one. Again, these commands assume Windows is installed on the C: drive.
cd C:\Program Files
attrib WindowsApps -h
rename WindowsApps WindowsAppsOld

*   `cd C:\Program Files`: Changes the directory to Program Files.
*   `attrib WindowsApps -h`: Removes the hidden attribute from the WindowsApps folder.
*   `rename WindowsApps WindowsAppsOld`: Renames the WindowsApps folder to WindowsAppsOld.
  1. Reboot Windows: Type exit to close the Command Prompt and then click Continue to reboot Windows normally.
  2. Try System Restore Again: After restarting, attempt to perform System Restore and see if the error is gone.

4] Repair Windows System Image using DISM

If the previous steps do not resolve the System Restore error 0x80071160, the issue might stem from corruption within the Windows system image. The Deployment Image Servicing and Management (DISM) tool is a powerful command-line utility that can be used to scan for and repair corruption in the Windows system image. Running DISM commands can help restore the integrity of system files and potentially resolve issues that are hindering System Restore.

Steps to Repair Windows System Image using DISM:

Related: loading
  1. Open Command Prompt or PowerShell as Administrator: Search for “Command Prompt” or “PowerShell” in the Start Menu, right-click on it, and select “Run as administrator”.
  2. Execute DISM Commands: In the elevated Command Prompt or PowerShell window, type the following DISM commands one by one, pressing Enter after each command.
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
DISM.exe /online /cleanup-image /startcomponentcleanup

*   `DISM.exe /Online /Cleanup-image /Scanhealth`: This command scans the component store for corruption and records any corruption detected in the CBS log file.
*   `DISM.exe /Online /Cleanup-image /Restorehealth`: This command repairs the component store corruption automatically. DISM will use Windows Update to provide the files required to fix corruptions.
*   `DISM.exe /online /cleanup-image /startcomponentcleanup`: This command performs a component store cleanup operation to reduce the size of the component store.
  1. Wait for the Commands to Complete: The DISM commands may take some time to complete, especially the /Restorehealth command, as it may need to download repair files from Windows Update. Do not interrupt the process.
  2. Restart Your Computer: Once all DISM commands have finished executing, restart your computer.
  3. Try System Restore Again: After the restart, attempt to run System Restore again and check if the error 0x80071160 has been resolved.

System Restore, while generally reliable, can be susceptible to corruption and permission-related issues, like many other Windows features. Ideally, it should function seamlessly, but the complexities of the Windows operating system can sometimes lead to such errors. This underscores the importance of maintaining multiple backup solutions. Having at least two backup methods in place ensures redundancy, so if one method, like System Restore, fails, you have a secondary option to rely on for system recovery.

Hopefully, these troubleshooting steps will assist you in resolving the System Restore Error 0x80071160 and restore your system’s ability to create and utilize restore points effectively.

Frequently Asked Questions: Error 0x80071160

How do I fix error 0x80071160?

The error code 0x80071160 can manifest in different contexts within Windows. While this article primarily focuses on its occurrence with System Restore, it is also associated with Windows Update. When encountered as a Windows Update error 0x80071160, it typically prevents your computer from installing updates.

To address the Windows Update error 0x80071160, begin by running the Windows Update Troubleshooter. This built-in automated tool in Windows 11/10 is designed to diagnose and resolve common Windows Update issues.

Steps to Run Windows Update Troubleshooter:

  1. Open Windows Settings (Win + I).
  2. Navigate to Update & Security > Troubleshoot > Additional troubleshooters.
  3. Select Windows Update and click Run the troubleshooter.
  4. Follow the on-screen instructions and allow the troubleshooter to complete.

If the troubleshooter does not resolve the error, other potential fixes for Windows Update error 0x80071160 include:

  • Clearing the Software Distribution Folder: This folder stores temporary files for Windows Updates. Deleting its contents can sometimes resolve update issues.
  • Resetting Windows Update Components: This involves resetting various Windows Update services and components to their default configurations.
  • Performing a Clean Boot: Starting Windows in a clean boot state can help identify if third-party software is interfering with Windows Update. Try installing Windows Updates after performing a clean boot.

How do I fix a failed System Restore?

System Restore failures can arise from various factors. Common causes include corrupted system image files or bad sectors on the hard disk. However, other underlying issues can also contribute to System Restore malfunctions.

To address a failed System Restore, consider the following approaches:

  • Repair System Image Files with SFC and DISM: As discussed in step 4 of the troubleshooting guide above, use the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools to scan for and repair corrupted system files. SFC (sfc /scannow) scans for and repairs corrupted system files, while DISM (DISM.exe /Online /Cleanup-image /Restorehealth) repairs the Windows system image.
  • Run CHKDSK to Repair Bad Sectors: Bad sectors on your hard disk can also interfere with System Restore. Run the Check Disk (CHKDSK) utility to scan for and attempt to repair bad sectors. Open Command Prompt as administrator and type chkdsk /f /r C: (replace C: with your system drive letter if necessary) and press Enter. You may be prompted to schedule the disk check for the next system restart.

By employing these troubleshooting steps, you can effectively address the System Restore Error 0x80071160 and other System Restore failures, ensuring the reliability of your system recovery options.

Do you have any other tips or experiences resolving System Restore errors? Share them in the comments below!

Post a Comment