Windows 10: Create System Restore Point shortcut in Windows 10

Yup, some folks work and some don't....you can read back through the thread that some never got to work and never posted again. I have solution with the CMD line so my posting is to help try to debug what is going wrong. Clearly there is something within the script specific to a W10 internal change that now causes issue. The VSS works fine for my Macrium Image to USB HDD images, and also doing the CP SP creation and the CMD line I got from this thread.

https://www.tenforums.com/tutorials/4...tml#post802065

My suggestion is for Shawn to cut down his VBS to the very basic RP creation command for W10 and let me put in a BAT file and let me try. We can see if "that" command itself has an issue or if OK something above it......basically a hard coded command.

BTW, did you the "test" script above ?

 

Can confirm the cut down script above created a restore point entry and reported success.

Mine is '10 Pro x64- is yours Home?

A while back you mentioned "now get VSS error."
Does the event log tell you anything helpful?

 

Pro

 

A while back you mentioned "now get VSS error."
Does the event log tell you anything helpful?
What was the error msg - have you researched it?

 

Look at post #61....it says handler issue.
System Restore Point shortcut - Create in Windows 10 - Page 7 - Windows 10 Forums

I am not a VSS guy nor do I understand the script so my fishing/googling for answers is not going to produce anything.
I have a solution that works........the CMD line.........
cmd.exe /k "wmic.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint "My Shortcut Restore Point", 100, 7"
....which also uses VSS, no errors, and provides a RP created.

I'm willing to help debug/test any changes to the script but I can't provide any knowledgable insights on why.
My suggestion is to boil down what the script is trying to run/launch for the RP command into a hard coded one or two line example I can put in a BAT file and see if works. It appears from reading the script that the coder is creating a shell app.......if so, something within that code is no longer valid to VSS under some new condition for some W10 configs within .105. I'm willing to test a hard coded (simplified...even more than the "test" one) version but past that I don't know how to proceed.

 

I am having this exact same issue. The script no longer works. I can manually create a system restore point, but the script now gives me VSS errors, even if I manually run the script. It creates an 8193 error that says either:

Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW. hr = 0x80070006, The handle is invalid..

Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

or

Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW. hr = 0x8007001f, A device attached to the system is not functioning.
.

Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet


This error only started after the Anniversary Update.

 

I mean this in the most light hearted way....YEAH !!!!
Thought I was going crazy and the experts here I think were wondering if it is a "poster system one-off issue". *Wink
Anyway, welcome aboard !!!! ....I'm sure these guys will figure it out.....smart cookies.

In mean time you can use this command...
cmd.exe /k "wmic.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint "My Shortcut Restore Point", 100, 7"
as a stop gap until the script is fixed.....not as elegant but works.

Note, under CMD the /k means to keep command prompt open, /c means to close.
I use the /c version under my task scheduler so it runs daily and the window pops up for 30 seconds or so then closes.
I use the /k version on my Desktop as shortcut.

Again, do not like it as much as this script.....not as clean, but will work in mean time.

 

You could try Tweaking.com's free cautious repair tool - select only the Repair VS Copy Service repair.

And you could think about trying this:
VSS error 8193

Ok, different specific error, but same kind of general error.
Nothing ventured.. nothing gained. You could at least look at that reg. key.

 

Sorry, but the problem is not with our PCs (O/S).....it is with the script.
I ran SFC and no integrity issues.
Also, the VSS works fine with both the manual CP > System & also CMD line creation.
VSS also works fine with my Macrium Image of my HDD daily to USB HDD.
I'm not going to experiment on my PC...clearly not a "PC" issue.
You also have poster that it fails on with multiple HDDs enabled.
Check out the crazy video on post #66: System Restore Point shortcut - Create in Windows 10 - Page 7 - Windows 10 Forums

I'm willing to test out more cut down VBS to get to root cause....my recommendation is to provide a hard coded string that I can put in BAT file to see if works.....my efforts here are to help with something that clearly has a coding issue. I have a solution with the CMD string that works fine.....I'm but not going to jeoporadize my PC in any way by running other utils, etc.

IMHO there are many folks having this problem but since the script "completes" they really have no idea if the RP was truly created unless they go check, nor do they know there was associated VSS issue for reason of failure.
It would take more than the average user to note/check these things.....AND nothing to alarm them things are wrong.

 

Yes, things ventured can really F-Up things. *Sick

And YES, if you read in prior parts of thread there is no .BAK in registry for User Profile.
Look at my post #63: System Restore Point shortcut - Create in Windows 10 - Page 7 - Windows 10 Forums
The VSS works....just not within this script.

 

@thekochs,

I don't like how crude the command currently runs, and would like to use it but with the same way the scripts in the tutorial run for better usage.

I'm going to work on completely rewriting the scripts today to use the newer command, then post back with it for you to test if you like. *Smile

 

Agreed.........CMD is brute force but works in mean time.

Happy to try what you come up with.
My suggestion is you will create a script with a lot of IF/THEN to ID things.
If you want to send me a line or two that is the RAW RP creation that we can put in simple BAT file (eliminates VBS issue) then I can try.
If that works then you can build the nice script around it.

 

Ok @thekochs,

Here are two scripts to test. If it works for you, then I'll use it with a version that you can enter your own restore point description like step 4 and 5.

The first one below, is a basic one just to test the W10 command. You'll just need to run the .vbs, and click on Yes in the UAC prompt to allow.

Test_Instant_Restore_Point.vbs

The second one below, is to test the same W10 command above, but also using get OS from the original script for compatibility with previous Windows. This is to test to make sure none of the get OS is working with W10 command for you as well.

Instant_Restore_Point.vbs

 

OK...tried the first one but go no UAC prompt.......did not create RP & VSS error.
Oddly here is window is generated which looked like the window from CMD line.




This was at header of above when "running"




I then ran the CMD line one I have and it DID create RP & no VSS issue......here is pic of that window.



This was header of the above CMD when "running"




So, other than the name in quotes "*****" the difference is 100, 7 vs 100, 0 ?

UPDATE
I changed your VBS code from 0 to 7...and it worked !!!!!
WScript.CreateObject ("WScript.Shell").run "cmd /k ""wmic.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint ""Instant Restore Point"", 100, 7"""
What is that parameter ?

 

@thekochs,

Did you unblock the .vbs file before running?

Unblock File in Windows 10 - Windows 10 Forums

You should have gotten a UAC prompt? Did you disable UAC?

Be sure to give it about 5 seconds after running to check to see if a restore point has been created. It can sometimes take that long before it shows up in System Protection.

Are you joined to a domain?

0 = Allows a custom restore point description, and has "Type" as "Install"

7 = Uses "Automatic Restore Point" description, and has "Type" as "System"