I have been trying to create a restore point for my computer. The last restore point was made, automatically, over three months ago. This is what I get when I try... " a volume shadow copy service component encountered an unexpected error. check the application event log for more info. (0x80042302)" please try again So I checked the log and went to the online event log help for this. It told me to make my VSS a manual start, so I did. I tried to create a restore point again and got the same message. What am I doing wrong and how do I fix this. I am not on a domaine

Volume Shadow Copy is used by System Restore for the Previous Versions Of Files feature in Windows 7. For purposes of testing, you could try and disable the Volume Shadow Copy service. 1. Click Start and in the Search box type "services.msc". 2. From the Services dialog box, navigate to Volume Shadow Copy and double-click it. 3. From the Volume Shadow Copy Properties dialog box, change the Startup Type to Disabled. 4. Restart your computer and try creating a restore point again. If it succeeds, you won't have any Previous Versions Of Files or the ability to create a backup, but at least you will know if VSS is causing the issue.

Please enter the following command in command prompt. vssadmin list writers > %userprofile%\desktop\writers.txt Then open the file writers.txt on Desktop, check which writer has encountered issues. If it is from a installed program, please let us know the name, also you may try to reinstall theprogram.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks, I did some research and figured it out. Unfortionatly, I don't remember what I did except go in the processes and start several processes and change the settings for them. After doing that several times, because they kept resetting themselves back, I finally said the heck with it and did another windows update. Tada! it was fixed somehow. Thanks for the advice though.