Automatically Create System Restore Point on Schedule in Windows 10  

Page 8 of 9 FirstFirst ... 6789 LastLast

  1. Posts : 6
    Windows 10 Pro x64
       #70

    My task failed to start (Launch failure):

    Task Scheduler failed to launch action "powershell..exe" in instance "{e0edba53-6910-4a72-8dcd-d6340b26a4e4}" of task "\Create Restore Point on Schedule". Additional Data: Error Value: 2147942402.

    So I opened a Command Prompt as Admin, started powershell and pasted in the command and get:

    -ExecutionPolicy : The term '-ExecutionPolicy' is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
    again.
    At line:1 char:1
    + -ExecutionPolicy Bypass -Command "Checkpoint-Computer -Description " ...
    + ~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (-ExecutionPolicy:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Automatically Create System Restore Point on Schedule in Windows 10-untitled.jpg
      My Computer


  2. Posts : 68,543
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #71

    Hello @JoseIbarra,

    Something may be wrong with how the command was entered for the task.

    Normally, the command would be this below to run:

    powershell -ExecutionPolicy Bypass -Command "Checkpoint-Computer -Description \"Automatic Restore Point\" -RestorePointType \"MODIFY_SETTINGS\""

    I can't be certain, but it looks like there may be an extra space in front of the command where it's C:\WINDOWS\system32> -ExecutionPolicy instead of the correct C:\WINDOWS\system32>-ExecutionPolicy without the extra space.

    If not, then please go ahead and post screenshots showing what you have set at step 8 to see if anything may stand out.
      My Computers


  3. Posts : 6
    Windows 10 Pro x64
       #72

    Cockpit Error.

    The reason the Task would not run is because in Actions, Program/script I had:

    powershell..exe (too many dots)

    Now it works

    I still don't know why (when I was tring to figure it out) if I open a Command Prompt, then start PowerShell and paste in just the arguments it complains about -ExecutionPolicy but I guess I'm not too worried about that.

    Does that work for anyone?

    If I paste into Command Prompt window the entire string like this:

    powershell -ExecutionPolicy Bypass -Command "Checkpoint-Computer -Description "Automatic Restore Point" -RestorePointType "MODIFY_SETTINGS""

    That works too.

    Oh well...


      My Computer


  4. Posts : 68,543
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #73

    JoseIbarra said:
    Cockpit Error.

    The reason the Task would not run is because in Actions, Program/script I had:

    powershell..exe (too many dots)

    Now it works

    I still don't know why (when I was tring to figure it out) if I open a Command Prompt, then start PowerShell and paste in just the arguments it complains about -ExecutionPolicy but I guess I'm not too worried about that.

    Does that work for anyone?

    If I paste into Command Prompt window the entire string like this:

    powershell -ExecutionPolicy Bypass -Command "Checkpoint-Computer -Description "Automatic Restore Point" -RestorePointType "MODIFY_SETTINGS""

    That works too.

    Oh well...
    Great news.

    Correct. That's how the command is being used for the task.
      My Computers


  5. Posts : 93
    Windows 10 pro 64 Bit Version 21H1 (OS Build 19043.844)
       #74

    restore failure


    JoseIbarra said:
    My task failed to start (Launch failure):

    Task Scheduler failed to launch action "powershell..exe" in instance "{e0edba53-6910-4a72-8dcd-d6340b26a4e4}" of task "\Create Restore Point on Schedule". Additional Data: Error Value: 2147942402.

    So I opened a Command Prompt as Admin, started powershell and pasted in the command and get:

    -ExecutionPolicy : The term '-ExecutionPolicy' is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
    again.
    At line:1 char:1
    + -ExecutionPolicy Bypass -Command "Checkpoint-Computer -Description " ...
    + ~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (-ExecutionPolicy:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

    Automatically Create System Restore Point on Schedule in Windows 10-untitled.jpg
    I cannot get my restore point schedule to work i get this same thing.. Additional Data: Error Value: 2147942402
    But now Im confused seeing Im reading various commands to enter into the ADD ARGUMENTS section..some sites are also saying this command means you need to enter in the Absolute path as in C://... So can someone help me to enter in the proper info or setup to get this to work.. I was on windows build 2004 and had this set up and it worked fine, but i recently clean installed the latest build 21H1. I have been trying many sites setups to get this to work again cause I forgot what sites info worked for me but these commands here arent working for me..
    Edit: I just tried this setup here and again failure..heres what the error shows..

    "Task Scheduler failed to launch action "wmic.exe" in instance "{e109e852-1268-4510-9e73-bd0334936d83}" of task "\Daily Restore Point". Additional Data: Error Value: 2147942402."

    This is like the 10th different setup I have tried and every one ends in failure with this code..??? Im at a loss..
    Creating a restore point Manually works just fine.

    Anyone? Does this NOT work in Build 21H1 anymore?
    Last edited by imanalien; 28 Feb 2021 at 22:59. Reason: forgot info
      My Computer


  6. Posts : 210
    Windows 10 Pro
       #75

    Thanks Shawn, yet another useful tutorial. Like phrab case, I upgraded in-place to Windows 21H1 and was burning some neurons because the task wasn't working, and then I re-read the tutorial and realised I had to create the regkey again, all is good now.
      My Computer


  7. Posts : 68,543
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #76

    ksio89 said:
    Thanks Shawn, yet another useful tutorial. Like phrab case, I upgraded in-place to Windows 21H1 and was burning some neurons because the task wasn't working, and then I re-read the tutorial and realised I had to create the regkey again, all is good now.
      My Computers


  8. Posts : 281
    Win 10 21H2 LTSC
       #77

    Brink I recently discovered you can make new volume shadow copy just for specific drives, this gets round the problem that if C: runs out of VSS space it will delete all old restore points on other drives as well.

    The command is an example for the D drive 'wmic shadowcopy call create Volume=D:\'

    Not sure if thats worthy of a new tutorial but I hope this is useful to people.

    The downside of this method as I think its more of a debug command than a supported feature is that I expect any vsc created this way will not be auto deleted, so probably requires manual management. But also an upside if you dont like these been auto deleted.

    Another warning, you cannot delete these shadow copies created this way in the system restore gui, unless you delete all at once in one go. Going to the gui for the drive will show a warning that there is addition system vsc on the drive which might affect space allocated for system restore points.

    To delete the volume shadow copy I made this way I ran 'wmic shadowcopy delete' which then asks one by one for each shadowcopy if you want to delete it, to get the ID I first ran 'vssadmin list shadows /for=D:' but they do appear to be listed in creation date order so would be the last one if its the most recent created.

    Finally when listing shadowcopies with vss admin.

    Ones created as system restore points have the following attributes.
    'Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered'
    The one created with wmic command had the following attributes.
    'Attributes: Persistent, Client-accessible, No auto release, No writers, Differential'

    Interesting.
      My Computer


  9. Posts : 4,269
    Windows 11 Pro 22H3
       #78

    Thank you Shawn, as always works as expected!
      My Computers


  10. Posts : 68,543
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       #79

    Hemimax said:
    Thank you Shawn, as always works as expected!
      My Computers


 

Tutorial Categories

Automatically Create System Restore Point on Schedule in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:22.
Find Us




Windows 10 Forums