I had the same problem, also on v 1803. So as a test I created another restore point, but this time I first went to onedrive, settings, account and "unlinked this pc", ie., logged out from Microsoft. I then did a restore and it worked just fine. My reasoning was that if I unlinked my onedrive folder, that folder would then be nothing special, just another folder on the computer. Seems to have worked.
"System Restore failed to extract the file (...\OneDrive) from the restore point."
Since updating to Windows 1803, system protection does not work. Restore will not restore from the restore point created during the update. Nor will it restore from any new restore point I create. I get the message:
System Restore did not complete successfully. Your computer's system files and settings were not changed.
Details:
System Restore failed to extract the file (<the path on my system>\OneDrive) from the restore point. An unspecified error occurred during the System Resotre. (0x8007018b)"
This is the same result if I attempt to restore to the point that the Windows 1803 upgrade occurred. And if I attempt to restore to a point I created immediately after the upgrade. And if I attempt to restore to a point created immediately before I attempt to restore to it. In other words. It is not possible for me to create a restore point and restore to it.
On the rare occasions when I attempted a restore in the past, it worked okay.
I tried this on another machine also recently updated to Windows 1803. The restore point creation then restoration worked correctly. The only obvious difference between the two is that the machine on which the restore worked had only a C:\ drive. The machine on which the restore fails uses a restore point that covers two drives and the OneDrive file that cannot be recovered is on the non-C: drive.
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
68 answers
Sort by: Most helpful
-
Anonymous
2018-11-13T07:48:06+00:00 -
Anonymous
2018-08-14T18:03:38+00:00 I am having the exact same problem. I need to go back to my 1709 version as the 1803 version does not work due to a graphics card problem.
Microsoft updated the machine to 1803 this afternoon, now I try to do a restore previous version and does not work.
Then tried to do a system restore and get the stupid that it could not restore due to a file on OneDrive.
Booted in to safe mode and did a full HDD check, then opened a command line and remove all my OneDrive files/folders to make sure that are no clashes.
Tried System Restore again with the same error.
System Restore should only touch OS/System files and not my files on OneDrive. I think we have a serious bug in 1803.
Raoul
-
Anonymous
2020-04-22T13:26:24+00:00 Hi guys,
I had the same error, I followed Apolari advice, i.e. run the restore in safe mode without network, and it worked, here what I specifically did:
1- Open Settings ->Update & Security -> Recovery -> Advanced Startup -> Click Restart ->
2- Choose Troubleshot -> Startup Settings
3- Choose option number 4, Safe Mode
4- Run CMD as admin and write the following command "rstrui.exe" and click enter. Your system restore window should start.
5- Chose your restore point and wait until restart.
I have Windows 10 Version 1909 (Build 18363. 720)
I hoped it works for you.
Thank you Apolari
-
Anonymous
2018-07-12T17:13:35+00:00 Thanks, Pedro. That's a good suggestion. I may wait to do a new in-place install in hopes a less drastic suggestion comes to this thread.
-
Anonymous
2018-10-31T19:52:20+00:00 Same problem.
Tried all disk scans from here (https://troubleshooter.xyz/wiki/fix-restore-point-not-working-in-windows-10/#Method\_5\_Perform\_a\_Clean\_Boot) - there were no issues with restore points, disk, system etc.
Tried different restore points. None can recover.
In "regular" mode system restore always shows an error with Sharepoint or OneDrive files.
In "safe mode" shows error in some system files on C drive.
I see 30 people have the same question and no one from MSFT replied since July?