"System Restore failed to extract the file (...\OneDrive) from the restore point."

Anonymous
2018-07-12T16:47:23+00:00

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.

0 comments No comments

68 answers

Sort by: Oldest
  1. Anonymous
    2020-02-08T21:19:49+00:00

    Even if there is not a fix, the create-a-restore-point applet should provide a cautionary warning.  It's one thing for the restore points not to work.  It's another for them to provide a false sense of security.  I wonder how many people mistakenly believe they have protected themselves by making a restore point that has no hope of every being restored to.

    On this point, we are in complete agreement. We can only guess at how many others have similarly been fooled and lost critical data.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-02-12T08:06:22+00:00

    Hi,

    should be so easy for Microsoft to solve it by allowing to set ExcludeFiles and/or ExcludeDiretcories.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-02-25T11:54:37+00:00

    Amazing that this issue still exists. My second rodeo with this problem. Last time I was upgraded from 7 Pro and could not undo a mistake. So I clean install 10 Pro. That was not exactly pretty either and thinking I might have preferred the 7-10 Pro mash up. 

    But here I am again knowing I have major issue and desperately need to roll back as far as I can to see if the problem goes away.

    And 10 did not have driver for over 2TB partition. Had I known I would not have attempted to convert to GPT with software purchase. About 700GB data may be gone.

    Is there a way to have system restore ignore the offending file and then just resync OneDrive?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-02-25T13:47:48+00:00

    The inability to restore is still a mystery, but resyncing a local OneDrive copy or partial copy is easy.  Right-click the cloud in the systray, choose more, then go to the account tab and unlink the OneDrive.  I don't think you have to restart, but I would just to be safe.  Then open OneDrive and go through the linking sequence.  I think you will lose the setting for files that you want kept locally.  So you might want to make a note of which ones they are before you unlink.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-04-20T06:48:54+00:00

    I can't believe that we're still sitting with the same problem with no fix from Microsoft.

    Was this answer helpful?

    0 comments No comments