System Restore works sporadically

I'm running 20H2.

I've long had a scheduled task that is intended to create a restore point every so often. I noticed a few days ago that it was only creating a occasional restore points, and most weren't created when they should be.

The task uses the wmic.exe method:

Code:

WMIC.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint "Restore Point Name", 100, 1

I see the same behavior manually as I get with the task: Usually, no restore point is created.

When I try using wmic.exe to create a restore point, the Application log always reports the following, even when no restore point is created:

Code:

Successfully created restore point (Process = C:\WINDOWS\system32\wbem\wmiprvse.exe; Description = Manual Restore Point).

A few seconds later, though, this entry appears:

Code:

Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW.  hr = 0x8007001f, A device attached to the system is not functioning.. Operation:   Executing Asynchronous OperationContext:   Current State: DoSnapshotSet

Sometimes, I can get System Restore to work properly for awhile if I totally disable it for my Windows volume, and then re-enable it. But sometimes, even that doesn't work.

I've run chkdsk (no problems found) and sfc /scannow (no problems found).

Ideas?

STRESSED said:

I do image, but they serve different purposes, and restoring from an image is a time-consuming hassle.

Agreed, backing up and restoring is a hassle. System Restore Points, when they are working, is an easy way to recover minor hiccups. Although I most do routine backups because I've had to restore from major hiccups, I see the value in SRPs as long as they will restore when needed.

Hello @STRESSED,

To see the list of System Restore Points that you have available, this Tutorial may help . . .

> How to See List of All Available System Restore Points in Windows

System Restore Points are a bit hit and miss though!

I hope this helps.

Thanks. I was aware of how to check for available restore points, but they really were not being created, even after having been reported as being successfully created.

I've changed the scheduled task to use PowerShell (rather than wmic.exe) and I'm going to use System Protection (i.e. SystemPropertiesProtection.exe) to manually create restore points from now on.

So far, so good. The restore points created using both of these methods have so far appeared correctly in rstrui.exe.

Edit: It has been nearly 2 weeks since I made the changes above, and I haven't had the problem since. I don't understand why wmic.exe stopped working, but I actually prefer using PowerShell and SystemPropertiesProtection.exe anyway.

Edit 2: I think the deprecation of WMIC may be why I experienced this issue. Or maybe not. If it was being deprecated, it seems it would simply stop working, rather than work sporadically.

STRESSED said:

I've changed the scheduled task to use PowerShell (rather than wmic.exe) and I'm going to use System Protection (i.e. SystemPropertiesProtection.exe) to manually create restore points from now on.

So far, so good. The restore points created using both of these methods have so far appeared correctly in rstrui.exe.