How to Back Up Your PC Before Factory Resetting or Reinstalling Windows 11

Resetting or reinstalling Windows 11 is easy. Rebuilding the PC you had before the reset is the hard part.

A clean Windows desktop can hide a surprisingly long list of things you still need: files outside Documents, cloud placeholders that were never stored locally, Outlook archives, browser data, application settings, license information, BitLocker keys, game saves, virtual machines, custom fonts, SSH keys, VPN profiles and small databases buried inside AppData.

If you are about to factory reset or reinstall Windows 11, treat the job as a recovery project, not a housekeeping task. Your goal is not merely to copy “important documents.” It is to make sure the new Windows installation can be turned back into a working computer without depending on the old installation after it has been erased.

The short answer

Before resetting or reinstalling Windows 11, copy your personal data to an external drive, NAS or another independent backup destination. Do not rely only on Reset this PC > Keep my files. That option is designed to preserve personal files, but it removes installed apps and resets settings, and a clean installation can remove everything on the Windows drive.

Then verify your cloud data, export or record application-specific data, confirm your Windows activation status, save your BitLocker recovery key somewhere you can access from another device, and make a list of apps you will need to reinstall. For important or heavily customized PCs, create a system image as an additional fallback.

Microsoft's Windows Backup app can help with selected folders, settings, credentials and an app list when you use a personal Microsoft account, but its folder backup relies on OneDrive. It is useful for migration convenience; it is not a substitute for an independent pre-reset copy of everything that matters.

1. Know which Windows recovery option you are actually using

“Reinstall Windows” can mean several different things in Windows 11, and they do not have the same data-loss risk. Before deciding what to back up, identify which path you intend to use.

Microsoft's current recovery guidance makes the distinction explicit. Fix problems using Windows Update reinstalls the current Windows version while preserving apps, documents and settings. Reset this PC gives you a choice to keep personal files or remove everything, while a clean installation from media is the more destructive route.

The important point is not that one option is safe and another is dangerous. Any recovery operation can go wrong because of a failed drive, wrong partition selection, power loss, user error or a problem that was already damaging the filesystem. A backup should exist before you test how well “Keep my files” keeps your files.

Cloud download does not mean cloud backup

When Reset this PC offers Cloud download or Local reinstall, that choice describes where Windows gets its installation files. It does not mean Microsoft is making a cloud copy of your personal data before the reset. Your backup plan is separate.

Factory reset can mean an OEM-specific recovery process

PC vendors sometimes use “factory reset” to describe a manufacturer recovery environment that restores the machine to an original or near-original state. The exact behavior can differ from Microsoft's Reset this PC. If the vendor recovery tool warns that the drive will be erased, believe the warning and treat the process as destructive even if the marketing language sounds friendly.

2. Make a real file backup before touching Reset

Start with the data you would care about if the PC's internal drive became unreadable five minutes from now. Put that data somewhere the reset cannot touch: an external hard drive, a NAS, another computer, or a separate backup repository.

A simple pre-reset file set usually includes:

• Desktop, Documents, Pictures, Videos and Music;
• Downloads if it contains installers, invoices, exported archives or other files you actually need;
• work and project folders stored outside the standard profile;
• data on secondary internal drives if the reinstall procedure might repartition or format them;
• local archives such as ZIP, 7z, PST, database or virtual-machine files;
• scans, photos and media that exist nowhere else.

If you already have scheduled backups, do not assume yesterday's job captured everything you added for the reset. Run a fresh backup and check its completion time. Pre-reset is one of the rare moments when a manual “Run now” is worth doing even if your normal schedule is healthy.

“Keep my files” is a recovery feature, not your backup

Reset this PC with Keep my files is useful because it reduces the amount of data you must restore. But it is still operating on the same machine and usually the same internal drive that contains your only live copy. It cannot protect you from selecting the wrong option, a failing SSD, partition mistakes, or files that were not where Windows expected personal data to be.

The independent backup is what turns a reset from a gamble into a maintenance task.

Use a versioned backup if you are already troubleshooting corruption

If the reason for reinstalling Windows is strange crashes, ransomware, filesystem errors or application corruption, a simple mirror of today's state may copy the problem. A versioned Full/Incremental or Full/Differential backup gives you a better chance of reaching back to a known-good copy after the new installation is running.

3. Find the data Windows does not put in obvious folders

The largest pre-reset mistakes are rarely the obvious folders. Most people remember Documents and Pictures. They forget the small, specialized data that makes a PC feel like their PC.

Audit every local drive and every unusual root folder

Open File Explorer and look at the top level of each internal drive. Folders such as D:\Projects, C:\Work, D:\VMs or a vendor-specific data directory will not magically move into Documents because you are resetting Windows.

If you develop software, edit video, run virtual machines or use technical applications, look for repositories, source trees, render caches that matter, VM disk images, local package repositories and configuration exports. Some of these can be recreated; others cannot.

AppData deserves inspection, not blind copying

%APPDATA% and %LOCALAPPDATA% contain application settings, caches, databases and user profiles. Copying the entire folders and dumping them back onto a clean Windows installation is usually a bad restore strategy because stale settings and version-specific data can reintroduce problems.

Instead, identify applications whose local data is valuable. Examples include:

• password-manager vaults that are genuinely local rather than cloud-synced;
• email client profiles and local archives;
• FTP/SFTP site lists and saved sessions;
• IDE or editor settings that are not synced;
• custom templates, presets, actions and dictionaries;
• game saves stored locally;
• small accounting, catalog or media-library databases;
• SSH keys, certificates and scripts in custom user folders.

Use each application's export or backup function when it has one. A clean export is usually safer and more portable than copying an opaque program-data directory.

Do not forget the “boring” personal files

People routinely miss fonts, custom Office templates, scanner profiles, printer presets, locally stored address books, saved macros, e-book libraries and configuration files for utilities they set up years ago. These items are often tiny, which makes them easy to protect once you remember they exist.

4. Verify OneDrive and other cloud files before the reset

Cloud sync is helpful during a reinstall, but it creates one dangerous illusion: a file can appear in File Explorer even when the PC does not hold the file's full contents.

With OneDrive Files On-Demand, cloud-only files can be represented by placeholders. If you make an offline backup by copying the OneDrive folder without first making the required files local, you can end up protecting placeholders rather than independent file contents.

For important OneDrive data, use one of these approaches before the reset:

1. Confirm OneDrive reports Up to date and check the important files through the OneDrive website.
2. If you want an independent external-drive copy, mark the required folders Always keep on this device, wait for them to download fully, then back them up.
3. Alternatively, export/download important cloud data directly through the service's web interface.

Our OneDrive-to-external-drive guide covers this in more detail, including why sync and independent backup solve different recovery problems.

Windows Backup is useful, but know what it is doing

The Windows Backup app can remember settings, credentials and an app list, and it can protect selected user folders through OneDrive for consumer Microsoft accounts. That can make the post-reset setup much smoother.

But the folder portion is still OneDrive synchronization. It does not capture every arbitrary local folder, every desktop application's data, a complete registry state or a bootable image of the old Windows installation. Use it as one layer, not as the only pre-reset safety net.

Check other sync services from the web

Do the same sanity check for Dropbox, Google Drive, iCloud Drive or other sync tools. Sign in through a browser and make sure recently edited files have actually reached the service. A green sync icon is useful; an independent confirmation from another device or the provider's website is stronger.

5. Save application data, email and browser information

A Windows reinstall removes friction from the operating system by removing a lot of application state. That is good when the old state is part of the problem, but you should deliberately preserve the parts you still need.

Email: know whether the mailbox is server-based or local

Microsoft 365, Outlook.com, Exchange and IMAP accounts usually keep the authoritative mailbox on the server. After reinstalling Outlook and signing in, much of the mailbox can resynchronize.

Local PST archives are different. If years of old mail live in a PST that is not stored on the mail server, back up that PST explicitly. Also consider signatures, templates and any other local Outlook items that matter to your workflow. Our Outlook email backup guide explains the distinction between server mail and local Outlook data.

Browser sync is convenient, but export critical bookmarks if they matter

Signing into Edge, Chrome or Firefox can restore bookmarks, passwords, extensions and settings depending on what sync options you enabled. Before erasing Windows, open the browser's sync page and make sure the expected categories are enabled and current.

If bookmarks are business-critical, export an HTML copy as well. That small file is cheap insurance against discovering after the reset that you were signed into a different browser profile or sync was disabled months ago.

Export data from applications that have a formal export function

Password managers, accounting packages, photo catalog tools, note applications and specialist utilities may have their own backup/export workflows. Use them. An application-created archive usually contains a cleaner and more documented representation of the data than copying random files from Program Files.

If an application uses cloud storage, verify it independently just as you did with OneDrive. “It signs in” and “all of my data is on the server” are not the same statement.

6. Record apps, activation, licenses and recovery keys

Data backup answers “where are my files?” The next layer answers “how do I get this computer working again?”

Make an app inventory before the reset

Take screenshots of Settings > Apps > Installed apps, or write down the software you actually use. You do not need to reinstall every utility accumulated over five years. The list is there so you do not forget something important two weeks later.

For a more technical inventory, Windows Package Manager can export apps it can match to configured sources:

winget export -o apps.json

The resulting JSON is useful as a reference and can help with batch reinstalling supported packages later. It is not a perfect image of every installed program: WinGet warns when it cannot match an installed application to a package source, so keep your human checklist too.

Confirm Windows activation and edition

Open Settings > System > Activation and record whether Windows is activated and which edition you are running—Home or Pro, for example.

Microsoft says a PC with a digital license can reinstall the same edition of Windows 11 without entering a product key, and it normally activates online afterward. Linking the digital license to your Microsoft account gives you another recovery path, especially if activation troubleshooting is needed later.

Do not assume that rule applies to every paid application on the PC. For third-party software, record the account, serial number or deactivation procedure according to the vendor's licensing model.

Save the BitLocker recovery key outside the PC

This is one of the most important pre-reset checks. If Device Encryption or BitLocker is enabled, confirm that you can retrieve the 48-digit recovery key from another device. Microsoft notes that the key may be stored in your Microsoft account, a work/school account, a printout or a USB file depending on how encryption was enabled.

Do not save the only copy of the recovery key inside the encrypted Windows drive you are about to erase. Recovery tools can ask for it after firmware, boot or storage changes, and Microsoft Support cannot recreate a lost key for you.

Capture the few hardware details that are hard to remember

Windows Update usually handles common drivers after reinstall, but specialized systems deserve a small hardware note. Record the PC model, motherboard/network adapter if custom-built, GPU model, printer/scanner model and any vendor utilities you depend on. For unusual storage, audio, RAID or network hardware, download critical drivers before the reset if losing network access would make recovery awkward.

7. Decide whether you also need a system image

A file backup helps you rebuild. A system image gives you a chance to go back.

If the PC is heavily customized, used for paid work, or contains software that will be difficult to reinstall, making a full system image before resetting Windows can be worthwhile. The image preserves the old Windows installation, applications and system state as a separate recovery layer.

This is especially valuable when you are resetting because of a vague performance or stability problem rather than confirmed malware. If the clean install creates a new problem—missing specialist software, an incompatible driver, a forgotten configuration—you still have a path back to the old disk state.

For the imaging options and recovery workflow, see our Windows 11 system image guide.

Recovery media is not a system image

A Windows installation USB, recovery drive or vendor recovery partition can help boot or reinstall the operating system. It does not automatically contain your current documents, installed desktop applications and customized working environment. Keep the concepts separate: recovery media starts recovery; backup data supplies what you need to recover.

8. Build a two-copy pre-reset backup with Perfect Backup

If you already use Perfect Backup, the pre-reset job is a good time to simplify rather than create a complicated new scheme. The goal is to make one fresh, verifiable set that is physically or logically outside the Windows disk being reset.

A practical workflow is:

1. Create or review a Files and Folders Backup job.
2. Select the personal and project folders identified during your audit, including custom paths outside the standard Windows profile.
3. Choose an external disk, NAS or other destination that the Windows reset will not erase.
4. Use a versioned method such as Full, Incremental or Differential when you want older states available.
5. Run the job manually before beginning the reset, even if it also has a schedule.
6. Review the completion log and restore several test files to a temporary location.

For a one-time pre-reset checkpoint, a fresh Full backup is attractive because it is easy to reason about: everything selected for that run belongs to one complete restore point. If you already have a healthy Full + Incremental or Full + Differential chain, you do not have to throw it away; just confirm the chain is current and restorable.

Two destinations are better than one when the reset matters

If the data is irreplaceable, make two independent copies before erasing Windows. For example:

• one versioned backup on an external hard drive;
• one second copy on a NAS, another removable disk or a trusted off-site destination.

This sounds excessive until the one external disk you planned to rely on develops an unreadable sector during restore. A reset is a controlled event—you have the luxury of creating redundancy before you need it.

Disconnect removable backup media before the destructive step

Once the backup is verified, disconnect the external backup drive before booting from Windows installation media or deleting partitions. This removes the possibility of selecting the backup disk by mistake and also keeps the recovery copy isolated while Windows is being rebuilt.

9. Verify the backup before erasing anything

“The backup finished” is not the same as “I can rebuild this PC.” Spend ten minutes proving the recovery path while the old Windows installation still works.

Restore a small sample

Restore at least one document, one photo, one file from a custom project folder and one larger file such as a ZIP or media file to a temporary folder. Open them. The goal is to verify the content, not just the filenames.

Check the newest timestamps

Find something you edited today and make sure today's version exists in the backup. This catches the common situation where a scheduled backup has been failing silently for a week even though older data is present.

Test access from outside the old Windows profile

If the backup is on a NAS, confirm you know the hostname/share and credentials. If it is encrypted, verify the password or key. If the files are in OneDrive, sign in through the web. If the backup uses an application-specific format, make sure you have the installer or know where to obtain the backup software after reinstall.

Keep a tiny recovery note with the backup

A plain text file can save time later. Record:

• Windows 11 edition and activation status;
• backup destination and date;
• BitLocker recovery-key location;
• essential apps to reinstall;
• special data paths such as PST, VM or project folders;
• network/NAS information needed to reach the second copy.

Store that note on the backup destination or print it. Do not leave the only copy on the Windows drive.

10. Restore in the right order after Windows is back

After a clean install, the temptation is to copy everything back immediately. A better order makes troubleshooting much easier.

1. Finish Windows setup and activation. Confirm the correct edition is installed and Windows is activated.
2. Install Windows Update and critical hardware drivers. Get networking, storage, graphics and input devices stable first.
3. Secure the machine. Finish Windows security updates before restoring large amounts of personal data or reconnecting every service.
4. Install essential applications from trusted sources. Start with the tools needed to open or restore your data.
5. Reconnect cloud services deliberately. Confirm the account and sync direction before letting OneDrive or another service process thousands of files.
6. Restore personal data. Bring back Documents, projects, media and application exports to their intended locations.
7. Restore app-specific settings selectively. Do not overwrite a clean profile with the entire old AppData tree unless you know the application supports it.
8. Rebuild backup immediately. Create a new post-reinstall backup once the machine is stable.

That last step matters. Your pre-reset backup is a safety net for the transition. It should not become the only historical copy while you spend the next month rebuilding the computer.

Common mistakes before resetting or reinstalling Windows 11

• Trusting Keep my files as the only copy. It reduces risk; it does not replace an independent backup.
• Copying only Documents and Pictures. Project folders, PST archives, VM disks and application data often live elsewhere.
• Assuming every OneDrive file is stored locally. Files On-Demand can leave cloud-only placeholders on the PC.
• Forgetting BitLocker recovery information. The key should be accessible from another device before recovery starts.
• Backing up installers but not data. Most installers can be downloaded again; your data and custom configuration are the scarce assets.
• Restoring the entire old AppData folder onto a clean install. That can reintroduce stale or corrupted application state.
• Keeping the backup drive connected during partitioning. Disconnect it before destructive setup steps.
• Never testing a restore. A backup you have not opened or restored from is still an assumption.

11. Frequently asked questions

Reset Windows only after you can explain how you will restore it

The best pre-reset checklist is not the longest one. It is the one that answers a simple question: if this PC's current Windows installation disappears right now, what exact steps put my work back?

Make an independent file backup, verify cloud data, save local application information, secure your BitLocker key and license details, and create a system image when the old environment is worth preserving. Then test enough of the backup to remove guesswork.

Once those pieces are in place, a factory reset or clean Windows 11 install becomes what it should be: a controlled rebuild, not an experiment with your data.

← Back to the Learning Center