System Restore Stopped Working

Topic

New Reply

[daddybear]

Good Morning All

Yesterday my System Restore stopped working with the error message 0x81000203 and box as shown in the attached screenshots.  The Properties box is also greyed out and existing System Restore points have been removed.

The only changes I made after a successful Restore point set-up were an Aomei update from v. 6.2.0 to 6.3.0 and also a zip file containing updated software for my Philips monitor called Smart Control.  I have now deleted/uninstalled both these items with no improvement to System Restore .

I have tried a few things suggested on the internet eg. enabling Volume Shadow Copy and Microsoft Software Shadow Copy Provider / disabling Security software / full anti-malware scans but with no effect on the System Restore fault.

Are there any other recommended actions to correct this problem ?

My OS is Wndows 10 Home 1909 running on a desktop PC.

Regards,

Roy.

• This topic was modified 4 years, 4 months ago by daddybear.
• This topic was modified 4 years, 4 months ago by daddybear.
• This topic was modified 4 years, 4 months ago by daddybear.

Reply | Quote

Replies

[RetiredGeek]

Hmm.0x81000203
Is the Volume shadow copy service running, if not start it and set to automatic.
Have you ever used Kaspersky Removal Tool?
If so, this seems to remove a registry key pertaining to system restore (Volume shadow copy service) on W10
A post by Will Watts has a solution

Windows - commercial by definition and now function...

• This reply was modified 4 years, 4 months ago by RetiredGeek. Reason: Spelling

2 users thanked author for this post.

b, daddybear

Reply | Quote

Microfix – Thank you for the reply.

Yes, Volume Shadow Copy is enabled and running on Automatic – as is also Microsoft Software Shadow Copy Provider.

No, I have never used  Kaspersky Removal Tool.

Regards,

Roy.

Reply | Quote

[b]

AVG TuneUp utility program is another potential culprit:

Windows 10: System restore fails with error 0x81000203

• This reply was modified 4 years, 4 months ago by b.

1 user thanked author for this post.

daddybear

Reply | Quote

Thanks to all for replies.

Have now fixed this by reconfiguring Upper Filter values in relevant registry key.

Still have no idea why it went wrong in the first place.

Regards,

Roy.

Reply | Quote