How to Export or Back Up the Windows 10 Registry
Back up a Windows 10 registry key or export the registry before making advanced changes, and learn how to restore the saved .reg file.
- Applies to Windows 10
- 4 min read
View article illustration

A registry export can preserve the values in a key before a targeted change. It is not a snapshot of Windows, and importing it does not necessarily remove values created afterward. Decide what you would need to undo before making the change.
Choose the backup that matches the change
| Your goal | Preparation |
|---|---|
| Change one known value | Export its parent key and record the original value name, type and data. |
| Add a new value or key | Record that it did not exist. Importing an older export may leave the new entry in place. |
| Recover from a system-wide or boot problem | Plan system recovery and a separate file backup. A .reg file alone is not a bootable recovery route. |
On a work-managed PC, use the administrator's change process. If you cannot identify the key a proposed fix changes or explain the rollback, stop before editing. A large “backup of everything” does not make an unknown tweak safe.
Back up a registry key
- Open Start, enter
regedit.exe, and approve the prompt if requested. - Locate the precise key you intend to change. Check the full path, including whether it is under
HKEY_CURRENT_USERorHKEY_LOCAL_MACHINE. - Choose File > Export.
- Select Selected branch and check that the displayed path matches your intended key.
- Save with a descriptive name and date in a private backup location.
Confirm that the file exists before editing. To inspect it, open Notepad first and use its Open command with the file-type filter set to All files; double-clicking a .reg file can start an import instead. Check that its bracketed key path is the one you meant to save. Do not post the file publicly: an application's settings can contain personal paths, identifiers or other sensitive data.
What an import actually restored in our check
On 5 October 2026, an automated editorial check used reg.exe export and reg.exe import on a newly created, disposable key under HKCU\Software on Windows 11 build 26300. Two string values were exported. One was then changed, one deleted, and a third added before importing the export.
| Test value | After importing the original export |
|---|---|
ExistingValue, changed from Before to After | Returned to Before. |
DeletedAfterExport, originally RestoreMe | Reappeared with RestoreMe. |
AddedAfterExport, created after the export | Remained present as StillHere. |
The test key and export were removed afterward; no application or Windows configuration keys were changed. This is evidence of the tested command-line merge behavior, not a Windows 10 device test, a Registry Editor UI test, or proof that every protected key can be restored.
The practical consequence: keep a change record as well as the export. If your edit introduced something new, an import alone may not put the key back into its previous state. Undo only the exact new entry documented in your change record; do not delete neighboring values to make a key “look clean”.
Export a wider registry range
Registry Editor also offers a wider export range. That can produce a large file with unrelated settings and is harder to review. It is not a complete system backup, and an export should not be treated as a way to rebuild a PC that will not start. Prefer a narrowly scoped export for a narrowly scoped change, with a separate recovery plan for more consequential work.
Restore a saved registry export
- Confirm that the file belongs to this PC, account and intended key. Close the affected application where appropriate.
- In Registry Editor, choose File > Import, select the saved export and confirm.
- Read the completion or error message. Reopen the target key and compare the relevant value names, types and data with your record.
- Restart the application or Windows only as the affected setting requires, then repeat the original test.
Use only an export you trust and understand. A .reg file is a set of changes to apply, not a harmless document just because it has a backup-like filename.
Documentation review: 5 October 2026. Export/import behavior was checked in the isolated Windows 11 command-line test described above. Windows 10 UI steps are documentation-based; no Windows 10 device or system recovery test was performed.


