New
#100
I'm glad it's working for you with "7" using the original script in the tutorial and new test command, but it should also work with "0" as well to have the specified "Instant Restore Point" description used in System Protection.
Now I just have to figure out why 7 and not 0 for you.
Are you joined to a domain?
Not just me but I bet others...some listed in this thread.......others not knowing that their RPs are not being created. After all, how many people check since 8/30 MS updates ?
Dumb question...I know you need to figure out "why" but isn't just putting "7" in there a universal fix ?
When you put "7" in the code and run on your W10 does it give you custom name or default ?
I ran the above two codes back-back........here is CP & CCleaner pics of successes.........no VSS errors.
CCleaner is using the specified "Instant Restore Point" description from the script.
System Protection isn't since the script had "7" instead of "0".
I can use "7" for the instant shortcut, but I can't for the others that allow you to enter your own description since "7" wouldn't use it.
I have run sfc /scannow several times.
UAC is OFF
I see "Thekochs" is having the same issue with his Surface Pro 4.
Running the vbs from the desktop is the same: runs/completes/no results/vss error event: "Unexpected error calling routine QueryFullProcessImageNameW. hr = 0x8007001f, A device attached to the system is not functioning"
I have no *.bak SID's
I Do Not have system protection turned on for other drives than just the Windows C: drive.
I tried "test_w10_createrp-success_message.vbs" with the same results
I tried your two scripts: "test instant restore point.vbs" and "instant restore point.vbs". Like "thekochs" neither created a rp.
************
Skipping ahead: Your newest steps 2 & 3 downloads work for me too!
Great news guys. I'm glad they're working for you now. Thank you for taking the time to troubleshoot with me. :)
How could CCleaner know what was in your vbs unless it read what the vbs input box/vbs created for the rp? Isn't CCleaner reading directly from something from within Win 10?
Are you still going to try to figure out what is going on with scripts 4 & 5 for us? I know it's only 2 users reporting but I wonder how many are assuming it works when it doesn't, or just giving up.
The specified description from the script is there, but for whatever reason, Windows doesn't use it when "7" is used. CCleaner still references the specified description.
I'll still be working on trying to find a way for Windows to use the specified description when "7" is used, or possibly find another method that may work better for steps 4 and 5.