System Restore in Windows 10 Pro not working

lghtanddrk

Commendable
Sep 29, 2016
4
0
1,520
I have a brand new custom built PC with Windows 10 Pro. System Restore no longer works for me.

I receive the following error every time:

  • System Restore did not complete successfully. Your computer's system files and settings were not changed.
    Details:
    System Restore failed to extract the original copy of the directory from the restore point.
    Source: %ProgramFiles%\WindowsApps
    Destination: AppxStaging
    An unspecified error occurred during System Restore (0x8007045b)
    You can try System Restore again and choose a different restore point. If you continue to see this error, you can try an advanced recovery method.
Only once in all my attempts did I ever get a different error code. This occurred during one of my attempts in safe mode. The message was the same but the error code was (0x80070026).

Here's my system summary:

  • OS Name Microsoft Windows 10 Pro
    Version 10.0.14393 Build 14393
    Other OS Description Not Available
    OS Manufacturer Microsoft Corporation
    System Manufacturer ASUS
    System Model All Series
    System Type x64-based PC
    System SKU Unsupported
    Processor Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz, 3201 Mhz, 8 Core(s), 16 Logical Processor(s)
    BIOS Version/Date American Megatrends Inc. 1401, 11/9/2016
    SMBIOS Version 3.0
    BIOS Mode UEFI
    BaseBoard Manufacturer ASUSTeK COMPUTER INC.
    BaseBoard Model Not Available
    BaseBoard Name Base Board
    Platform Role Desktop
    Secure Boot State On
    PCR7 Configuration Binding Not Possible
    Windows Directory C:\WINDOWS
    System Directory C:\WINDOWS\system32
    Boot Device \Device\HarddiskVolume2
    Locale United States
    Hardware Abstraction Layer Version = "10.0.14393.206"
    Time Zone Eastern Standard Time
    Installed Physical Memory (RAM) 64.0 GB
    Total Physical Memory 63.9 GB
    Available Physical Memory 58.7 GB
    Total Virtual Memory 73.4 GB
    Available Virtual Memory 67.6 GB
    Page File Space 9.50 GB
    Page File C:\pagefile.sys
    Hyper-V - VM Monitor Mode Extensions Yes
    Hyper-V - Second Level Address Translation Extensions Yes
    Hyper-V - Virtualization Enabled in Firmware No
    Hyper-V - Data Execution Protection Yes
Here's how I discovered the issue and all the steps I have tried to troubleshoot and resolve the issue:

  • - I launched the Windows Store and noticed that I was not logged in. Every time I clicked the login it did nothing.
    - I researched solutions for this issue online. The first solution was to sign up for the Windows Preview which should force you to have to login again. Clicking on the login for Windows Preview would immediately close out the login screen.
    - The second solution was to launch msconfig, check all non-Microsoft services, disable them and reboot. This fixed this issue.
    - It then occurred to me that I should have taken screenshots of the services that had been disabled, if any. So, I decided that I would do a system restore to check the list of services and then repeat the steps above, if necessary, should I not be able to login to the Windows Store.
    That's when I discovered system restore was not working. I tried restoring several different points and received the same error message (above with code 0x8007045b).
    - Thinking that the system restore was corrupt, I deleted all restore points, disabled system restore and rebooted. After rebooting, I enabled system restore and made a few test restore points (it's set to use 20% of my hard drive which should be more than enough). You can create restore points with no errors.
    - System restore still gave me the same error. I then disabled my Norton 360 and tried again but got the same error. I also disabled the Norton Product Tampering feature. I even went as far as removing Norton completely with Norton's removal tool.
    - I held down shift and restarted to enter safe mode and tried restoring. I got the same error message but with a different code (above with code 0x80070026).
    - I ran chkdsk, scandisk and sfc and none of them found errors.
    - Thinking that maybe there was a virus on the computer or in the master boot record, I ran complete scans with Norton 360, Malware Bytes, Spybot and Super Antispyware, None of them found issues.
    - Finally, I spoke with Microsoft and they told me to use the Microsoft Media Creation Tool to do a reinstall over my existing copy of Windows 10 Pro. I chose the option to keep my files and apps. - After the installation, I noticed that System Restore was suddenly showing that it was disabled. I enabled it again, deleted the previous restore points and created some new test ones. System restore still gives me the exact same error after restarting the computer and does not complete successfully.
I don't want to wipe out my entire computer and reinstall everything. This makes me nervous that I'm using a computer with no protection should something go wrong. I don't want to have to rely on frequent Acronis backups.

Does anyone have any ideas for other things that I can try?

 
Solution
Try an in place upgrade. It wont delete anything but fixes problems. Cant remember but I think you have to turn on system restore after.
I've used it several time to fix different issues.
http://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

I use this ISO. Seems to work better.
https://www.microsoft.com/en-us/software-download/windows10ISO/

May not fix older restore points but might fix the ones from after you do it.
 


I tried that. Microsoft had me use the Media Creation Tool to replace the existing install. I enabled System Restore after the install and I still get the same error message when doing a system restore.

I also saw a response on another discussion board that it could be Norton's Product Tampering feature causing the problem. I just disabled it and tried system restore again but get the same error.
 


I checked it out in my system and had the same issue. System restore would not work.
But it worked when I did it in safe mode.
But you already tried that.
Maybe try safe mode again.
 
Solution