Guides

Restore personal files after malware cleanup

Choose file versions and destinations after cleanup, compare File History, Time Machine and OneDrive recovery, and verify data without overwriting originals.

Restoring personal files means choosing a recoverable version and placing it on a suitable device. It does not establish that the device has been cleaned, undo account theft, or prove that every copied item is benign. Decide what is missing or damaged before selecting a restore method; a whole-account rollback is a much broader action than retrieving one document.

Use this guide after addressing the immediate incident through recovery verification. Do not attach your ordinary backup disk to a device that is still encrypting files or under unauthorized control. On a work or school device, let IT choose the recovery destination and handle business data. If you have not preserved the available copies, begin with backup preparation.

Establish what you are trying to recover

For suspected ransomware, start with containment and recovery planning. A file restoration procedure cannot by itself establish whether further damage, unauthorized access or a disclosure remains unresolved.

Write down the wanted folder, approximate last good date, backup location, and acceptable destination. Distinguish deletion, overwriting, encryption, and a file that merely appears missing from the current view. Check that you are looking in the correct account and folder before making a recovery change.

SituationUseful recovery routeImportant limit
One file was overwrittenAn earlier retained versionYou need a version from before the unwanted change
A backed-up folder was deletedFile-backup restore or the provider’s recycle binAn unavailable or expired copy cannot be assumed recoverable
Many cloud files changedReview account-wide rollback optionsA rollback also affects legitimate later work
A manual copy exists on a separate driveCopy selected data into a recovery folderIts date and contents still need checking
Files are encrypted and no good backup is knownPreserve originals and seek qualified incident helpA normal file restore is not a universal decryptor

An extension added to a filename does not reveal the complete damage. Do not rename or overwrite encrypted originals in the hope that another program will open them. Keep uncertain material separate while the recovery route is assessed.

Prepare the destination and preserve the source

Use a destination whose remediation, updates, and protection have been reviewed. Reinstall needed applications from independently reached official sources. Restoring an old installer collection or complete browser profile can introduce software and settings you did not intend to recover.

Microsoft’s OneDrive ransomware workflow specifically puts remediation of connected devices before cloud restoration. Otherwise restored files may be encrypted again. A clean destination alone is insufficient if another affected device can still write to the same account.

Keep the backup source unchanged where your recovery method allows it. Prefer a new, clearly named folder for selected recovered files until you have compared them with current data. Do not use the only backup disk as a temporary working drive or silently replace the newest wanted document with an older one.

Decide how sensitive data will be handled. A personal device or consumer cloud account may be inappropriate for work records. File names, password exports, mail archives, and recovery credentials can all need restricted access even when they contain no malicious code.

Recover selected files with Windows File History

Microsoft documents restoration through the original file or folder location. In File Explorer, open the relevant folder’s properties through Restore previous versions, select the wanted version, and inspect it using Open in File History. Use Restore to… when you want a separate destination rather than overwriting the current data.

For deleted content, select the parent folder that used to contain it. Check the selected date before confirming. Microsoft warns that an in-place replacement cannot be undone. An empty version list means you need to investigate backup coverage or choose another source; turning on File History now cannot create missing historical copies.

Restore a small selection first and check its contents. A File History recovery retrieves backed-up data, not all installed applications or proof of a trustworthy Windows installation. Windows recovery tools serve different purposes: System Restore and recovery media do not substitute for a retained personal-file version.

Recover individual items with Time Machine on Mac

Apple’s item-restoration guide starts from the Finder window for the location containing the wanted item. Open Time Machine, browse the available backup dates, select the item, and choose Restore. This documented workflow returns items to their original location, so plan for any existing current data before confirming.

Use the version selector in Apple’s guide for your macOS release. Do not assume the backup contains a file simply because that file is visible in a cloud folder today. Establish which dated backup actually has the wanted contents.

This is selective data restoration. Migrating an entire account, restoring applications, or rebuilding the operating system are broader workflows. After a security incident, choose each deliberately rather than treating the existence of a Time Machine disk as a reason to reintroduce everything.

Choose the smallest appropriate OneDrive recovery

For an overwritten file, OneDrive’s version-history instructions let you select the item on the website and inspect available versions. A work or school administrator may have disabled versioning. Check the account, timestamp, and actual contents. Use the provider’s current controls instead of trusting an unsolicited recovery email.

For deletion, Microsoft documents recycle-bin limits: personal accounts normally retain deleted items for 30 days; work or school accounts normally use 93 days unless the administrator changes the setting. Permanently deleted items cannot be recovered through that bin, and this route does not give you ownership of someone else’s shared files. Check the actual account and administrator policy.

Whole-OneDrive restoration is a separate Microsoft 365 subscriber feature for undoing eligible activity within the last 30 days. Review the activity and selected point carefully. Files created after that point move to the recycle bin, so a broad rollback can disturb wanted newer work. Recovery availability and a paid subscription are not guarantees of a usable pre-incident version.

Verify the recovered data before ordinary use

After recovery, establish an offline backup routine and review ransomware resilience so future restoration has retained versions and independent access. Keep the incident preservation copy separate from the new routine until its status is understood.

Compare the expected folder structure, file count, sizes, dates, and a representative set of wanted contents. A successful copy message establishes transfer, not completeness. Note failures, unavailable cloud contents, and files that still do not open in the intended updated application.

Use the active security product’s supported scanning process where appropriate, without uploading private data to a public reputation service. A scan with no detections is limited evidence. Do not enable macros, run embedded programs, or bypass a warning merely because a file came from a backup. Suspicious attachments and scripts need their own assessment.

Keep the current and restored copies until you have resolved differences. Reconnect ordinary synchronization only when connected devices and account access have been addressed. For browser information, follow selective browser restoration; for exposed credentials, follow account recovery.

Record what was recovered, from which dated source, to which destination, and what remains unavailable. That record helps the next recovery decision and avoids treating an incomplete attempt as a complete result. This guide is researched documentation guidance; no site-run file-recovery experiment or human technical sign-off is claimed.

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