New
#140
Basically, you need to fix or avoid the four bugs that I cited previously. Any solution will require tracking what happens after the asynchronous call to SRSetRestorePoint returns. In my case I handled it by injecting a passive API hook to watch for the internal CreateThread call so that I could scarf the thread handle and do a WaitForMultipleObjects on it to know when the thread finishes.
After the async op completes I check with VSS to see if the snapshot was actually created or not. This is because third-party VSS Writers can veto a snapshot for any number of reasons so you need to check the writer responses in order to retrieve the error message to explain the reason for the failure.
SRSetRestorePoint will sometimes lie and claim the restore point was actually created when it in fact decided to skip the whole deal, which can happen if you try to create more than one Restore Point within 24 hours. To work around this you need to fiddle with SystemRestorePointCreationFrequency (documented) and SystemRestorePointCreationFrequencyWU (not documented).
Finally, SRSetRestorePoint uses DCOM so you need to do all the usual gymnastics for getting CoInitializeSecurity to allow interprocess RPC calls between security boundaries. In particular you need to construct the proper DACL with the proper access rights. See https://msdn.microsoft.com/en-us/lib.../aa378987.aspx
Thanks for your advice Gideon, however it is too technical for me.
Perhaps Microsoft will one day provide a Task Scheduler that actually works.
Shawn,
Thank you for all the work you are putting into this. A few days ago I was gifted by Microsoft with Windows 10 v 1607, and all my VBS scrips for creating restore points broke. I visited here, and finally stumbled onto the tutorial you mention above, which uses the command line incantation starting with WMIC. It works with the task scheduler, which was my most important concern.
I changed the user from myself to SYSTEM, because I thought it was cleaner and was more portable. Do you see any problems with that? (It works fine both ways.)
I also set the trigger to "on a schedule" and "daily" since I rarely log off or restart.
I flat out gave up trying to jigger it to accept a customized comment for spontaneous restore point, and chose instead to use your shortcut to the System Protection Panel. It's just one more click, and I been creating enough trouble for myself lately.
--
Jim
Hello Jim, :)
That should work for you as well.
https://www.tenforums.com/tutorials/6...dows-10-a.html
Yeah, it would be nice if the create restore point with custom description options would work properly for everyone again. The odd thing is that they still work fine on my system with build 14955, but not for most.
I downloaded the first option, i.e., create a link but not messages or sucess popups. However, I'm finding the .lnk file opens the Documents folder and "Instant_Restore_Point_message.vbs" is bringing up a success pop up. What am I missing? Thanks,
Hello @highstream, :)
The .lnk file is to open the .vbs file, but the .vbs file must be copied in the location in step 9 for the .lnk to work. Otherwise, you could use just the .vbs file instead.
Hi Brink,
Several days ago both vbscripts that prompt for a description stopped creating restore points.
Both scripts "run", to the extent that the message prompt appears, and in the case of the script that is supposed to give a confirmation, it does that, but the restore points themselves are not created.
The other 2 scripts that don't prompt for a description work fine.
Hello kitpzyxmsir,
Unfortunately, the shortcuts that allow you to enter a description currently do not work for some in Windows 10.
Since they work for me, I haven't been able to find a cause for this yet.