New
#50
Ron,
You might run a "SFC /SCANNOW" command to see if there may be an issue with system files causing this.
https://www.tenforums.com/tutorials/2...dows-10-a.html
The scripts no longer work since W10 8/30 security updates..........now get VSS error.
Doing manually thru W10 CP works fine and so do this command.....
cmd.exe /k "wmic.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint "My Shortcut Restore Point", 100, 7"
.....from this site.
** REMOVED**
Someone who wrote these scripts needs to check/test.
Last edited by Brink; 05 Sep 2016 at 21:48. Reason: Removed link
Hello,
I have tested the shortcuts here on several systems and VM's using the latest 14915 build as posted here, and it still works just fine for me if all the steps are followed exactly.
Please double check to make sure all steps were done.
Does running the unblocked .vbs file directly from your desktop work for you?
When you run the .vbs file or shortcut, are you prompted by UAC to elevate?
They ALL run and complete but no Restore Point listed and Event Viewer shows VSS Error.
"Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW. hr = 0x80070006, The handle is invalid."
The manual creation thru Control Panel>System works fine and so does the command string I listed above.
I am running 14393.105 ...this is what was released to me for my Surface Pro 4 on 8/30/16
I have Windows Defender, MBAM, MBAE & CryptoPrevent installed....but other than definition files nothing has changed here for these....I could see them blocking the "script" but clearly that is not happening. Your scripts worked fine for a long time but just checked them last night and saw they stopped right after the Microsoft 8/20/16 security updates. Have not opened your scripts but something changed within MS and VSS that no longer likes your script command/string/etc. Also, note I ran SFC and no integrity violations found.
Last edited by thekochs; 06 Sep 2016 at 08:25.
I'll have to do some more testing to see why they are not working for you when they are for me and just about everyone else.
There's gotta be some difference on your system, but just not sure what yet.
There is couple posters on this thread that never got it to work....read back.
Also, be careful when you say that it "works" for all.....the script runs fine.....just no RP created.
You can easily see this in Tools of CCLeaner or going into Control Panel > System.
Users may not know it is not working unless they go into CP and then actually bring up Restore and check for listings.
They would not also know they they are getting VSS errors (which is the problem itself) unless they go into Event Viewer and most users would not do that and only the techy folks would know what they are seeing and correlate to this script running.
This also has only happened since the 14393.105 updates of 8/30/16......this is clearly in my list when they stopped logging/creating.
Anyway, I'm convinced it is not the system (meaning O/S) because I can create manually thru CP or via this command line string.
cmd.exe /k "wmic.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint "My Shortcut Restore Point", 100, 7"
Not sure what within your script you are calling to "VSS" but something broke with 14393.105
Hope that helps you chase it down.
The thing is that the scripts do still work on all my systems and VM's using build 14915, and do actually create restore points as shown at the post below.
https://www.tenforums.com/tutorials/4...tml#post797261
I've also had some of the other mods test on their systems, and they report the same.
I just need to find out why it's not working for some of you.
You mention 14915....I am on W10 Pro Version 1607 14393.105 ....which for me is latest for Surface Pro 4
This is what came out for me on 8/30/16.........
Microsoft Surface Pro 4 update history | Surface firmware updates
https://support.microsoft.com/en-us/help/12387/windows-10-update-history
Your script worked prior which was for me Version 1607 Build 14393.82
Let me know what you find.....right now I'm using the CMD string that works instead of your script for daily Task Scheduler RP creation.