Cannot create a system restore point and getting error code: 0x81000202.

Anonymous

Original Title: cannot create a system restore point

I have Windows 7 Home premium.

I am unable to create a System Restore point.

I go to Control Panel>System & Security>System>System protection

and get the following error message:

There was an unexpected error in the property page.

The volume shadow copy service used by system restore is not working.

For more information view the event log. (0x81000202).

I have also run a sysscan but all is well.

How can I create a system restore point?

Many thanks

David

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

Answer accepted by question author

Anonymous

Using Win7, 64bit. Problem solved, solution, fixed !!

Since I found a solution, I thought I would do a good thing a post it here. Hopefully it will save someone else a bunch of grief. I don't know how universal my case is.

My system is somewhat unique - the original was modified by changing out the C drive for a SSD, which is much smaller than most drives today (120 GB) I put only Windows on that drive, and as much as possible everything else other places.

This means that there isn't a lot of extra room on the C drive for restore point storage.

Creating a restore point would hang with the message that it couldn't get Volume Shadow Service to work After trying everything I could think of and find to try (which took quite a while) I noticed the following:

The current usage for restore points on the C drive was 12.24GB, the maximum (at 10%) was 11.17. Problem, no?

So.. I cut the max to 5%. Windows told me that it would delete old recovery points - which it did. I then raised the limit back to 10% - now there is available space.

Restore point creation worked fine.

Windows should handle this much better. But Windows should handle lots of things better. In any case my problem is solved - I hope this help you out.

In the past, I deleted all restore points to fix the problem, which I didn't want to do this time. But that would have a similar effect of freeing up space. In the future I will be more careful and monitor this occasionally and manually do the same thing - reduce the available space, lose some older restore points, and then reset.

0 comments

Answer accepted by question author

Anonymous

If you have any backup software like totalrecovery pro 9 or norton ghost they will prevent you from creating a manual restore point. I have total recovery pro 9 and all I do is disable the recovery manager when I want to create a manual restore point. There is no problem with system created restore points they work fine it is the manual ones that are the problem.

Frank

0 comments

Answer accepted by question author

Anonymous

David

What other entries are logged on or shortly before or shortly after that entry i.e. within a minute within a minute either way?

What is interesting is that if the service stopped then it must started which is different to it failed to stop.

Sorry for the delay in answering but I was busy on other things.

Hope this helps, Gerry Cornell

0 comments

63 additional answers

Anonymous

2013-12-15T19:21:38+00:00

The real answer is having the correct settings for the permissions to the windows directory on drive C:\

Allow TrustedInstaller Special <not inherited> This folder and subfolders

Allow SYSTEM Special <not inherited> This folder only

Allow SYSTEM Special <not inherited> Subfolders and files only

Allow Administrators (name\administrators) special <not inherited> This folder only

Allow Administrators (name\administrators) special <not inherited> Subfolders and files only

Allow Users (name\Users) Read and execute <not inherited> This folder, subfolders and files

Allow CREATOR OWNER Special <not inherited> Subfolders and files only

This works. I had the same problem and this is how I fixed it. I have been programming since 1964.
Was this answer helpful?

0 comments No comments
Anonymous

2013-04-20T20:56:58+00:00

Mark

Based on what you say it appears that your system restore is not working correctly. What should happen is that when the system is told to create a restore point it should check available disk space. If there is insufficient disk space then it should remove existing restore points on a FIFO (First In First Out) basis to accommodate the new restore point.

http://www.sevenforums.com/tutorials/335-system-protection-change-disk-space-usage.html

I'm sure it should work this way - in fact I was quite surprised that it didn't. But getting restore points to work correctly isn't something I want to spend a lot of time on. It now works, both for creating and using restore points. So it's good enough for now - there's always a new problem to spend time on.

But thanks for your help. ...

Please note the default setting is that each partition is monitored. This is unnecessary and you should turn off monitoring all partitions except C; that is where your operating system normally resides.

A further complication is that when free disk is reduced to below a specified level, system restore will surrender allocated disk space

http://www.windows7hacker.com/index.php/2012/07/some-facts-about-windows-low-disk-space-warning-balloon/

What can cause confusion is that windows backup uses a different method to determine available disk space, which is unrelated to the amount of free disk space. This commonly causes windows backup to fail. System restore uses free disk space on C to store restore points. Windows backup places backup copies where the user tells the utility to put them.

You can find reports in Event Viewer that can help you find out the nature of the problem.

To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window select Windows Logs and System. You may also need to look at the Application to get a more complete picture.
Was this answer helpful?

0 comments No comments