How to Create a System Restore Point in Windows

Why restore points matter on a developer laptop

A programming laptop accumulates system-level changes quickly: a Docker Desktop install, a WSL kernel update, a Hyper-V feature, a new graphics driver, or a vendor BIOS tool. Most of those changes are safe, but one bad system setting can stop Windows from booting or leave your development environment unstable. A restore point is a snapshot of Windows system files, drivers, and the registry. You can return to that snapshot if a change goes wrong. This is not a substitute for source control or a file backup; it is a safety net for the operating system itself.

Before you enable virtualization for containers and virtual machines, think of the restore point as the quickest way to undo a system change that makes your machine unreliable. The restore point is like an undo button for the operating system. It does not protect your source code, but it makes trying a new kernel or Docker configuration less risky. You can always return to a known-good Windows state instead of spending an afternoon troubleshooting. It works alongside the tools you use every day, including Docker Desktop on Windows and the Visual Studio Code editor you likely run on the same laptop.

Enable System Protection first

System Protection must be turned on before Windows can create restore points. Open the Start menu, type "Create a restore point", and open the matching System Properties result. This dialog is the main control center for System Protection. If you protect only the drive where Windows is installed, that is usually enough, because system files and installed applications live there.

• Select the system drive from the Available Drives list.
• Click Configure.
• Choose Turn on system protection.
• Use the Max Usage slider to decide how much disk space restore points may use.
• Click OK to apply the change.

Create a restore point before a big change

Once System Protection is active, create a named restore point just before the change you are worried about. The process takes a minute and gives you a labeled rollback target. This is especially useful when you are setting up a new development environment or following a guide that asks you to turn on Windows features.

In the System Properties window, on the System Protection tab, click Create. Type a label that records the moment, for example "Before Docker Desktop install" or "Before enabling Hyper-V". Windows will create the point and confirm when it is done. The label is the name you will see later in the list of available restore points. Using a descriptive label is important because Windows does not explain why the point was created.

• In System Properties, System Protection tab, click Create.
• Type a descriptive label for the moment.
• Wait for Windows to finish creating the point.
• Close the dialog when you see the confirmation message.

When to create a restore point

Make a habit of creating a restore point whenever you are about to change a system-level setting. Good moments include installing Docker Desktop on Windows, enabling Hyper-V or Windows Sandbox, updating a laptop BIOS through the vendor tool, installing a driver from a chipset vendor, or applying a Windows feature update.

If you are about to enable virtualization for Docker and VMs, see the guide on enabling virtualization for Docker and VMs for related setup steps, and create a restore point first. The goal is to keep a recent restore point available for the changes you care about. If you install a new tool every week, create a point once a week. If you only touch the system for a major update, create a point immediately before that update.

What a restore point does and does not cover

A restore point records system files, drivers, registry keys, and some application files that Windows understands. It does not roll back documents, code repositories, or other personal data, and it is not a backup strategy. Your source code should live in Git and your working files should be copied with a tool such as File History. If you need a full system image, create a Windows recovery drive and use a full backup instead of relying on restore points.

Because restore points are tied to the system drive, they are a convenient safety net before a Windows update or a driver change. They are not a replacement for storing important project files elsewhere. Think of a restore point as the system-level part of your recovery plan and your repository as the source-code part.

Recover when Windows will not start

If a change breaks boot and you cannot open System Properties, start Windows in the recovery environment. From "Choose an option", select Troubleshoot, then Advanced Options, then System Restore. You may need your BitLocker recovery key if you encrypted the drive. If no restore point exists, you can also try System File Checker or reset the laptop to factory settings as a last resort.

What to pick for your work

Questions

Does a restore point delete my code or personal files?

No. A restore point is a snapshot of system files, drivers, and registry settings. It does not remove documents, code, photos, or other personal files. Still, you should keep code in source control and use File History or another backup for files you cannot recreate.

How often should I create a restore point?

Create one before any system-level change: a driver install, a Windows feature update, an enable of Hyper-V or Windows Sandbox, a BIOS update, or a registry edit. If you make changes often, create a point at the start of each session you want to protect.

Do restore points use disk space?

Yes. Each restore point stores changes to system files and the registry, and the System Protection dialog has a Max Usage slider that limits the combined space. When the limit is reached, Windows removes older restore points to make room for new ones.

Can I create a restore point when Windows will not boot?

You cannot create a new restore point from outside Windows, but you can use an existing one. Boot into the Windows Recovery Environment, choose Troubleshoot, Advanced Options, and System Restore. That is why it is important to create points while the system still works.

What is the difference between a restore point and a recovery drive?

A restore point is a system snapshot stored on your laptop. A recovery drive is a separate USB drive with Windows recovery tools and sometimes a system image. You can use a recovery drive to open Windows Recovery Environment when the system drive is not bootable.