This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
Hi, Dr. Jonas Moses. I initiated this thread and should have updated it. Some time ago, the problem disappeared from my machines. This happened after a number of updates to Windows and OneDrive. So an update may have corrected the problem. Of course I cannot be sure. I checked just now to make sure my system could create a restore point and restore from it. It can. So please post whether you are using the most current versions of Windows 10 and OneDrive.
I haven't been monitoring this topic for a while so sorry if this suggestion has already been discounted, but I do wonder if you have tried simply turning off one drive before doing the restore?
Yes, several times. I am the kind of engineer who even asks "uhh...did you remember to plug in your device?"
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
I haven't been monitoring this topic for a while so sorry if this suggestion has already been discounted, but I do wonder if you have tried simply turning off one drive before doing the restore?
MattgyverLee, how about a solution that doesn't include observations such as, "this is great for future restore points..." We are not here seeking solutions for future restore points, we want to know what to do about past restore points...as in: what do I do to stop my System Restore from failing because of OneDrive, right now? I have a fail in Powerpoint, which only just has occured - it keeps crashing every time I try to open a file (an image, for example) to add to a slide. This is new, and I have been using Powerpoint, daily, on my machine, for three years, since purchase. I am convinced that a recent MS 10 update, or one of my other software packages (i.e. during the past day or two), has somehow corrupted my system, and the only clean and simple (supposed to be) operation is a system restore.
Doesn't anyone have a clue, which does not include the stupid notion that, "for the future, try this...?" We are here to resolve an issue for the now. Not for the next time!
