Guides

Back up important files before malware removal

Plan a Windows file backup before cleanup or reinstallation, protect existing copies, separate suspect files, and verify what you can actually restore.

Before cleanup that may delete files, remove applications, or reinstall Windows, establish how you will preserve the personal data you need. A useful backup plan names the files, destination, date, and recovery method. The presence of a drive called “Backup” does not establish that the latest documents are there or that the copy is safe to restore.

This guide covers Windows personal-file preservation before a planned cleanup or recovery step. If files are actively being encrypted or someone has unauthorized remote control, do not connect your ordinary backup drive. Start with incident diagnosis and qualified help. On a work or school device, let the responsible administrator choose the preservation process.

Protect the copies you already have

First inventory existing backups without exposing them to the suspect computer. Note where they are stored, when they were made, and whether they predate the incident. An older intact copy may be more valuable than overwriting it with the current state.

The CISA and partner ransomware guide recommends offline backups and testing their availability and integrity. Its organizational guidance illustrates the underlying problem: backups accessible from an affected system can also be damaged. Keeping a separate copy disconnected reduces that exposure; it does not certify every file in the copy as benign.

Current situationPreservation decisionWhat to avoid
A usable pre-incident backup existsRetain it unchanged while assessing newer filesReplacing the only earlier copy
Only current files are availablePlan a separate, dated preservation copyCalling that copy a known-clean backup
Active encryption or remote control continuesGet incident help before attaching storageExposing a normal backup drive
A cloud folder shows sync errorsCheck availability from a trusted deviceAssuming a visible filename is a retained copy
An administrator manages the computerFollow the organization’s processMoving business data to personal storage

Do not resume a scheduled backup merely to see whether it works on an actively compromised computer. If an incident investigator needs records, avoid cleanup that destroys them until the preservation plan is clear.

Decide what you need to keep

Make a short inventory of irreplaceable data: documents, photos, ongoing projects, local email archives, and application data that is not already recoverable elsewhere. Check custom save locations as well as familiar folders. A project stored on another drive will not be preserved just because Documents was copied.

Record legitimate software names and the official route for reinstalling them. Keep necessary license and recovery information private. Prefer obtaining applications again from their publishers rather than carrying an unknown collection of installers into a rebuilt system.

Separate ordinary personal data from suspicious downloads, scripts, executables, archives, and whole browser profiles. Documents themselves can contain active content, so file type alone is not a safety verdict. Do not open a questionable attachment to decide whether it deserves a backup. Mark uncertain material clearly for later review, and do not restore quarantined items to make them easier to copy.

If important data is already encrypted, keep the originals and the relevant incident details for qualified recovery advice. Renaming files, deleting encrypted copies, or trying unrelated repair utilities can change the material you may later need.

Understand the backup method’s actual scope

Microsoft’s backup and recovery overview distinguishes personal-file backups from Windows recovery tools. A recovery drive does not include personal files. A System Restore point is also not a substitute for a document backup.

For a computer judged suitable for normal backup operation, choose the method you can verify:

  1. An existing file-backup arrangement: inspect its latest successful run and included locations. Preserve earlier versions rather than silently replacing them.
  2. File History: Microsoft documents copies of files in libraries to an external drive or network destination. Check whether custom locations are included and whether the required versions exist.
  3. Windows Backup and OneDrive: understand which folders actually synchronize and whether their contents have reached the account.
  4. A separate manual preservation copy: record exactly which folders were copied and any failures. It preserves selected data, rather than a complete Windows installation.

Follow Microsoft’s File History instructions for its current setup and restore controls. The documentation describes library coverage and adding other folders through libraries. Do not assume it includes every drive, installed program, or application database.

The Windows Backup guide describes a consumer Microsoft-account workflow. Selected folders synchronize to OneDrive; app restoration includes pins and routes to reinstall applications. This is different from retaining a full independent disk image. Work or school accounts have different support arrangements.

Verify completion without opening suspect content

Record the selected folders, destination, date, and any copy or backup errors. Compare the intended inventory with what the backup reports and what is actually available. A completed progress bar is not useful if the critical project folder was outside the selected scope.

For known ordinary files, check that representative items can be retrieved through the backup’s documented restore route. Avoid a trial that overwrites the only working copy. File History’s documentation includes restoring to another location, which helps keep the current version available during comparison.

If a file is suspicious or its origin is unclear, verify its preservation through listings and records; do not run it as a test. A saved copy remains untrusted until assessed. Scanning can provide additional evidence later, but a no-detection result alone does not make a suspect archive appropriate to restore.

Keep enough information to access encrypted backups and the computer’s recovery controls. Where BitLocker applies, Microsoft’s recovery-key guidance explains retrieval. Keep the key private and accessible independently of the device being recovered. A key stored only on an inaccessible encrypted drive will not help you unlock that drive.

Keep preservation separate from restoration

For a routine established before an incident, use offline backups to plan disconnected copies and ransomware backup resilience to examine retention, destructive access, and retrieval. Keep those established copies protected while deciding how to preserve current suspect data.

The file restoration guide explains how to choose a dated version and destination after remediation, including File History, Time Machine, and OneDrive limits. Keep the preservation copy separate until you have decided what can be restored.

After the copy finishes, keep preservation storage disconnected when it is not needed. Do not automatically reconnect it to every computer or overwrite earlier versions. Label a copy made during suspected compromise with its date and uncertainty so you can distinguish it from a pre-incident backup.

Continue with the appropriate Windows scan or supported recovery plan. Before restoring data, use recovery after malware to review the destination system and the items being brought back. Restore wanted personal data selectively; reinstall ordinary software from trusted sources.

Backing up protects against some data-loss consequences of cleanup. It does not remove malware, revoke stolen sessions, or replace account recovery. This guide was researched and edited on 6 October 2026. No backup or malware recovery experiment was performed.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy