You create a restore point in Windows 11 through the Start menu search for "Create a restore point," which opens the System Protection tab of System Properties, where you select your system drive and click Create. The catch is that System Protection is often off by default on a fresh install, especially on machines where the drive arrived formatted with a single partition. Until you turn it on for that specific drive, the Create button sits greyed out and nothing happens no matter how many times you click it.
That greyed-out button is the single most common reason people give up on this feature, so this walkthrough starts there rather than pretending the path is always smooth.
Why the Create Button Is Greyed Out and the Exact Fix
System Protection runs per drive, and Windows 11 ships with it disabled on many prebuilt machines because manufacturers reclaim the disk space. Open the Start menu, type "Create a restore point," and press Enter. The System Properties window opens on the System Protection tab. Look at the Protection Settings list: every drive shows "Off" or "On" in the Protection column. If C: says Off, select it and click Configure.
In the Configure window you get three radio buttons β Disable system protection, Turn on system protection, and (on some builds) an option to restore default settings. Choose Turn on system protection. The slider underneath, labeled "Max Usage," sets how much disk space the feature may consume, expressed as a percentage of the drive. Microsoft's documented default is 1% of the drive, and on a 1 TB drive that is roughly 10 GB before Windows trims older points. Click Apply, then OK.
Return to the System Protection tab and the Create button is now live for C:. If it still isn't, check that you're not on a drive formatted as exFAT or FAT32 β System Protection uses the Volume Shadow Copy Service and requires NTFS. External USB drives formatted NTFS can be protected too, but Windows won't let you create a point on removable media in every edition, so verify before relying on one.
Microsoft's own support documentation confirms that restore points are created automatically before significant system events β driver installations, Windows Updates, and app installs that use the installer API β but only when protection is already on. An off drive gets no automatic points either, which is the quieter half of the problem.
Step-by-Step: Creating the Point in Under 30 Seconds
Here's the sequence in the order you actually perform it. The whole operation takes about 20 to 40 seconds on a modern SSD, most of it waiting for the progress bar.
1: Press the Windows key, type Create a restore point, and hit Enter. The System Properties dialog opens directly to the System Protection tab. 2: Under Protection Settings, confirm C: (System) shows On. If not, follow the Configure fix above first. 3: Click the Create button at the bottom right of the tab β it sits beside Configure and System Restore. 4: In the small dialog labeled "Create a restore point," type a description. Use a format you'll recognize months later, such as "Before GPU driver 566.xx" or "Clean install + Office, 12 Nov." 5: Click Create and wait. A progress bar runs; a "The restore point was created successfully" message confirms completion. Click Close.
The description field caps at 255 characters, though anything past about 60 gets truncated in the restore list. Name the change, not the date β Windows stamps the date itself.
If the progress bar fails partway with error 0x8004231F, that's the Volume Shadow Copy Service reporting insufficient shadow storage. Raise Max Usage in Configure by a few percentage points and retry. Error 0x80042306 means another backup or imaging tool holds a VSS lock; close Macrium Reflect, Acronis, or any open backup job and try again. Neither error indicates a broken system β both are space or contention issues.
Manual Points vs. Automatic Points: When Each One Fires
The comparison matters because most people assume Windows is already protecting them. It usually isn't until you switch it on.
| Trigger | Who initiates | Runs when protection is Off? | Typical description shown |
|---|---|---|---|
| Driver or update install | Windows (via VSS) | No | "Automatic Restore Point" |
| App install using the installer API | Windows | No | "Automatic Restore Point" |
| Scheduled task (if enabled) | Windows Task Scheduler | No | Depends on task config |
| Your manual Create click | You | No | Your typed text |
| Restore-point purge at max usage | Windows | n/a | Oldest points deleted first |
The scheduled-task row deserves a note. Windows ships a task called "SR" under Task Scheduler Library > Microsoft > Windows > SystemRestore, disabled by default. Enabling it lets you run a daily point without touching the dialog β useful on machines you experiment on. The task still requires protection to be On for the target drive.
Automatic points are created before Windows Update installs, but Microsoft changed behavior in recent builds: feature updates (the twice-yearly larger releases) now often roll back through the uninstall mechanism rather than a restore point, so don't count on a point existing for a major version jump. Check the System Protection tab after a big update and you'll frequently find no new entry.
For anyone who tinkers β registry edits, driver swaps, beta software β manual points before each change beat automatic ones because you control the description and the timing. For everyone else, turning protection on and letting Windows handle it is enough.
How Much Disk Space Restore Points Actually Eat
Microsoft's documented default cap is 1% of the protected drive's capacity, adjustable up to 100% via the Max Usage slider. On a 512 GB SSD that ceiling is about 5 GB; on a 2 TB drive, about 20 GB. Old points are deleted first when the cap is reached, so the feature never silently fills your disk.
Real consumption per point is small. A restore point stores registry hives, driver files, and changed system files through shadow copies β not a full disk image. On a typical Windows 11 install, a single point runs a few hundred megabytes to roughly 2 GB depending on how much changed since the last one. Ten points on a 1 TB drive sit comfortably inside the 10 GB default.
The tradeoff is visible if you're tight on space. On a 128 GB laptop SSD with 8 GB free, even a 1.28 GB cap competes with the page file and update staging. Raise Max Usage only if you have headroom; otherwise leave it at 1% and accept that you'll keep maybe four or five points. The System Protection tab shows "Current Usage" next to the slider in the Configure dialog, so you can watch it grow.
If you want more history without more disk, image the machine with a third-party tool instead β restore points are for rolling back system state, not for recovering personal files. They never touch your Documents, Pictures, or Desktop contents, which is the next point and the most misunderstood one.
What a Restore Point Does Not Back Up
A restore point captures registry, system files, drivers, and installed program binaries β not your data. Documents, photos, email in local folders, browser profiles, and anything under your user directory stay untouched by both the snapshot and the restore. If you delete a file and then restore to a point from yesterday, the file stays deleted.
It also doesn't cover programs cleanly in every case. Apps installed after the restore point disappear from the Start menu and registry, but leftover folders and some license activations can survive, leaving a half-installed state. Adobe and some game launchers are known for this; expect to reinstall or re-activate.
Drive letters other than the protected one aren't covered either. If you moved your Steam library to D: and only C: is protected, a restore won't fix a broken game install on D:. Protect each NTFS drive you care about, individually, through the same System Protection list.
Third-party backup is the right tool for files. File History (still present in Windows 11 though deprecated in favor of OneDrive) or a proper image backup handles data; restore points handle the operating system's configuration. Treat them as two layers, not substitutes. That distinction alone prevents the worst outcome β restoring the system to fix a problem and finding your work files unchanged but your app settings scrambled.
Restoring From a Point: The 15-Minute Rollback and Its Undo
To roll back, reopen System Properties > System Protection and click System Restore. The wizard lists available points with date, time, description, and type (Manual, Automatic, Install). Select one, click Next, confirm, and click Finish. Windows warns that the restore can't be interrupted, signs you out, runs the process, and reboots. On an SSD the whole cycle typically finishes in 10 to 20 minutes; on a spinning drive, plan on 30 or more.
The restore itself is reversible. Before applying changes, System Restore creates a restore point of the current state and labels it "System Restore" in the list, so you can undo a rollback that made things worse. This is the strongest argument for the feature: it's a two-way door, unlike a clean install.
Programs installed after the chosen point are removed from the registry and Start menu, and drivers revert. Files created after the point persist. If the rollback fails with "System Restore did not complete successfully," the common causes are antivirus interference (temporarily disable real-time scanning) and a corrupted shadow copy (run vssadmin list shadows in an elevated Command Prompt to inspect).
You can also run System Restore from Windows Recovery Environment if the desktop won't boot: hold Shift while clicking Restart, choose Troubleshoot > Advanced options > System Restore, and pick a point. This path works when the OS is too broken to reach the dialog β the scenario the feature was arguably built for.
Cautions: Ransomware, Domain Machines, and Encryption
Restore points are not ransomware protection. Modern ransomware deletes shadow copies first, and System Restore points live in the same shadow storage. A point created last week will be gone after an encryption event because the malware wipes the volume's shadow copies before encrypting. Offline or offsite backups remain the only real defense.
On domain-joined machines, Group Policy can disable System Protection entirely, and the Create button will be greyed out with no Configure option. Check with your IT department before assuming the feature is broken; the policy is usually "DisableConfig" and "DisableSR" under Computer Configuration > Administrative Templates > System > System Restore.
BitLocker interacts with restore points in a way worth knowing: rolling back to a point created before a BitLocker configuration change (enabling, changing PIN, or turning off) can leave the machine prompting for a recovery key on next boot. Have your recovery key saved to your Microsoft account or printed before restoring on an encrypted machine.
Restore points also don't survive a Windows feature update cleanly in every case; some points from the previous build are purged with a notification stating so in the System Protection list. If you're about to install a major update, make your own point and note the description.
Checking, Cleaning Up, and Scripting the Task
The System Protection tab's System Restore button opens the picker, which doubles as your inventory β every available point with its type. To purge everything and start fresh, open Configure and click Delete, then confirm. That removes all points for that drive but leaves protection on. Don't confuse it with Disable, which stops future points.
For a scheduled daily point without the GUI, create a task in Task Scheduler that runs powershell.exe with the argument -Command "Checkpoint-Computer -Description 'Scheduled daily' -RestorePointType MODIFY_SETTINGS". The Checkpoint-Computer cmdlet is built into Windows and respects the same 1% cap. Note that Windows limits automatic checkpoint frequency to one per 24 hours by default unless you change the registry value SystemRestorePointCreationFrequency under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore β setting it to 0 removes the throttle.
Verify points exist by opening an elevated Command Prompt and typing vssadmin list shadows. You'll see shadow copy sets with creation timestamps β the ground truth behind the GUI list. If the list is empty while System Protection shows On, shadow storage may have been cleared by a cleanup tool; recreate a point manually.
Keep the habit small: before any driver update, registry hack, or new software install, spend the 30 seconds. The feature costs you nothing but a little disk and pays back the first time a change goes sideways.
FAQ
Does creating a restore point slow down my PC?
No measurable slowdown in normal use; a point is a snapshot of system files taken at that moment, not a background process. The only cost is disk space inside the Max Usage cap you set β 1% of the drive by default, per Microsoft's documentation. If you notice the machine feeling sluggish right after clicking Create, it's the shadow copy write finishing, typically under a minute.
Can I create a restore point if my C: drive is nearly full?
Usually not, because the shadow storage can't grow past the free space available, and the operation fails with error 0x8004231F. Free up at least 2 GB more than the current Max Usage setting before retrying. If the drive is under 10 GB free, disable and re-enable protection after cleanup so the slider recalculates against the new capacity.
Do restore points protect my personal files and photos?
No. Restore points cover registry, system files, and drivers only. Your Documents, Pictures, Desktop, and Downloads folders are outside the snapshot and remain exactly as they are after a rollback. For file protection, use File History, OneDrive's version history, or a separate image backup β restore points and file backup solve different problems.
Why did my restore point disappear after a Windows update?
Feature updates and some cumulative updates purge older points and state so in the System Protection list, typically replacing them with an "Automatic Restore Point" for the new build. Rolling back to a point from a previous build is unsupported. Create a fresh point immediately after any major update completes and keep a separate image backup for true version rollback.
How many restore points can I keep at once?
The count is governed by the Max Usage cap, not a fixed number β Windows deletes the oldest point when the cap is hit. At the 1% default, a typical Windows 11 install holds roughly five to ten points. Raising Max Usage to 3-5% on a drive with free space extends history considerably; on a 128 GB SSD that's not advisable.
Is a restore point the same as a backup?
No, and treating them as equivalent is the costliest mistake here. A backup copies your data and can rebuild the machine after a drive failure; a restore point only rewinds system configuration on a working drive. Restore points also die with the drive, while backups live elsewhere. Run both.
Can I create a restore point from the command line or a script?
Yes β PowerShell's Checkpoint-Computer cmdlet does exactly what the Create button does and takes a description and type. Batch it through Task Scheduler for scheduled points. Watch the built-in 24-hour throttle unless you adjust the SystemRestorePointCreationFrequency registry value, which Microsoft documents under System Restore technical reference.
What happens if the restore itself fails partway through?
Windows attempts to roll back the rollback and reboot to the prior state; you usually end up where you started rather than in a worse place. If it fails during boot, run System Restore from the Recovery Environment instead. Antivirus interference and corrupted shadow copies are the two most common causes, both fixable before retrying.
This article is general educational information about Windows system tools, not technical support for a specific machine or guarantee of recovery outcomes. Feature availability varies by Windows edition, build, and organizational policy; check Microsoft's official support documentation for your version, and consult a qualified IT professional before restoring a business or encrypted device.