sodcalculator

10 Tech How-To

How to Automatically Create System Restore Points in Windows 10

Guide 10-57414 · Updated · Step by step

System Restore points let you roll back Windows to an earlier state if a driver update, registry change, or software install causes problems. By default, Windows 10 only creates restore points automatically before major updates, which may not be often enough. This guide shows you how to make Windows create a restore point on a schedule—daily, weekly, or at every startup—so you always have a recent recovery point to fall back on.

What You’ll Need

  • Windows 10 with System Protection enabled (we’ll cover how to check this).
  • Administrator account access—you’ll need to approve UAC prompts.
  • Task Scheduler (built into Windows) and either Notepad or PowerShell.
  • About 15 minutes of time.

Step-by-Step

Step 1: Enable System Protection

  1. Press Win + R, type sysdm.cpl, and press Enter.
  2. In the System Properties window, go to the System Protection tab.
  3. Select your system drive (usually C:) and click Configure.
  4. Choose Turn on system protection.
  5. Set a reasonable max usage (5–10% of the drive is typical). Click OK.
  6. Click Create to make a manual restore point now—this gives you a baseline to test later.

Step 2: Create a Scheduled Task Using Task Scheduler

  1. Open Task Scheduler by pressing Win + S, typing Task Scheduler, and selecting it.
  2. In the right-hand Actions pane, click Create Basic Task.
  3. Name it System Restore Point (or similar) and click Next.
  4. Choose a trigger. For a daily restore point, select Daily and set a time (e.g., 2:00 AM). Click Next.
  5. For the action, select Start a program and click Next.
  6. In the Program/script field, paste the following (this uses PowerShell to create the restore point):
    powershell.exe -ExecutionPolicy Bypass -Command "Checkpoint-Computer -Description 'Scheduled Restore Point' -RestorePointType 'MODIFY_SETTINGS'"

    Leave the Arguments field empty (the command is already included).

  7. Click Next, review the summary, and click Finish.

Step 3: Configure the Task to Run with Highest Privileges

  1. In Task Scheduler, locate your new task in the Active Tasks list.
  2. Right-click it and select Properties.
  3. Go to the General tab.
  4. Check Run with highest privileges. This is essential—without it, the task will fail silently.
  5. Under Security options, choose Run whether user is logged on or not (this requires you to enter your password).
  6. Click OK.

Step 4: Test the Task

  1. Right-click the task and choose Run.
  2. Wait a minute or two, then check if a restore point was created:
  3. Open System Properties (Win + R, type sysdm.cpl), go to System Protection, and click System Restore.
  4. Click Next—you should see a restore point with the description you set.

Step 5: (Optional) Create a Restore Point at Every Startup

  1. Instead of a daily trigger, you can trigger the task at logon.
  2. In Task Scheduler, create a new basic task, but when choosing the trigger, select When I log on.
  3. Use the same PowerShell command as above.
  4. Set it to run with highest privileges as described in Step 3.

Common Mistakes

  • Forgetting to run with highest privileges—the task will appear to run but won’t actually create a restore point.
  • Using the wrong command syntax—extra spaces or missing quotes can cause PowerShell to fail. Copy the exact command from Step 2.
  • Not enabling System Protection—even with the task, no restore points will be created if protection is off.
  • Setting the max usage too low—if the disk space limit is tiny, older restore points get deleted quickly to make room.
  • Creating the task without a password—if you choose “Run whether user is logged on or not” and don’t set a password, the task may not run.

Tips

  • Set the schedule to a time when your PC is on but idle, like early morning, to avoid interrupting your work.
  • Use a descriptive name in the -Description field, like “Weekly Restore Point”, so you can easily identify it in the list.
  • If you have multiple drives with System Protection enabled, the command creates restore points for all of them at once.
  • You can combine this with a manual restore point before major changes, but the scheduled one covers you automatically.
  • Keep at least 5% of your drive for System Protection to ensure multiple restore points can exist.

Troubleshooting

Task runs but no restore point appears

  • Check that the task is set to Run with highest privileges—this is the #1 cause.
  • Verify System Protection is enabled for the drive (Step 1).
  • Open Task Scheduler, right-click the task, and select Run. Then check the Last Run Result column. A result like 0x0 means success; a non-zero code indicates an error.
  • If you see 0x1, the command may have failed. Try running the PowerShell command manually (as admin) to see the error.

PowerShell command fails

  • Make sure you’re using the exact command with proper quoting. In Task Scheduler, the Program/script should be powershell.exe and the Arguments field should contain the -ExecutionPolicy Bypass -Command "..." part. Alternatively, you can put the whole thing in the Program/script field as shown in Step 2—both work.
  • If you get an error about execution policy, the -ExecutionPolicy Bypass flag should handle it. If not, run PowerShell as admin and execute Set-ExecutionPolicy RemoteSigned.

Restore points are being deleted too quickly

  • Increase the max usage in System Protection settings. If you have a large drive, 10% or more is fine.
  • Windows also deletes older restore points when the disk runs low. Ensure you have free space on the system drive.

Task doesn’t run at all

  • Check the task’s Triggers—make sure the start time is correct and that the task is enabled.
  • If you chose “Run whether user is logged on or not”, confirm the password is correct. If you don’t want to enter a password, choose “Run only when user is logged on”—but then the task won’t run if you’re not logged in.
  • In Task Scheduler, look at the History tab for the task to see any errors.

Frequently Asked Questions

How often should I create restore points?

Daily is a good balance for most users. If you make frequent system changes, you might prefer weekly or at every startup. Just remember that each restore point uses disk space.

Does creating restore points slow down my PC?

No, the process runs in the background and takes only a few seconds. It uses a small amount of CPU and disk I/O, but it’s negligible on modern hardware.

Can I create restore points on multiple drives?

Yes, if you enable System Protection on other drives, the scheduled task will create restore points for all of them simultaneously.

Will this work on Windows 11?

Yes, the same steps work on Windows 11, since Task Scheduler and System Protection are essentially the same.

What’s the difference between a restore point and a backup?

A restore point only contains system files, settings, and registry—it doesn’t back up your personal files. For file backups, use File History or a full backup solution.

Can I manually create a restore point anytime?

Yes, just open System Properties → System Protection → Create. The scheduled task automates this, but you can always do it manually before risky changes.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →