When a user or client reports a corrupt file, the most reliable approach is a fixed triage order: stop further writes to the file, make a working copy, look for a clean version in backups or version history, try the application's own repair, and only then use repair software on the copy. If the file was deleted or lives on a failing drive, recover it first and repair second. Keeping the original untouched, documenting what you did, and setting realistic expectations about partial repairs will save you time and awkward conversations.
This guide is for in-house IT staff, managed service providers and small business owners who end up being "the computer person". It covers a repeatable workflow, how to handle bulk damage after a drive failure, and how to talk to users about results.
A triage workflow for corrupt files
- Stop the damage spreading. Ask the user not to keep opening, saving or re-syncing the file. Repeated save attempts and sync loops can overwrite a good version with a bad one.
- Make a working copy. Copy the damaged file to your own working folder and do all further work on that copy. If the copy fails or is very slow, suspect the storage and switch to the data recovery path below.
- Check for a clean version. In order: OneDrive or SharePoint Version history, Properties > Previous Versions (File History, restore points or server shadow copies), your backup system, and the original source if the file was emailed or downloaded. A clean earlier version beats any repair.
- Try the application's own repair. Word and Excel both offer File > Open, then the arrow next to Open and Open and Repair. For video, check whether VLC plays it. For ZIPs from the web, re-download.
- Repair the copy. Use repair software on the working copy and preview the result before handing it back.
- Return, record and prevent. Give the user the repaired copy, note what was and was not recovered on the ticket, and fix the cause so it does not happen again.
Repair and data recovery are different jobs. If the file was deleted, the drive is not detected, or Windows cannot copy the file at all, use data recovery tools or a recovery service first. Repair the files you get back afterwards.
Common scenarios and what to try first
| Scenario | Likely cause | First move |
|---|---|---|
| Shared Excel workbook "file format or extension is not valid" | Interrupted save, sync conflict, or a renamed file | Version history on the share or OneDrive, then Open and Repair |
| Word "found unreadable content" | Damaged document structure | Let Word try its recovery, then repair a copy if text or formatting is lost |
| Scanned PDFs open blank or with errors | Incomplete transfer from scanner or email | Re-scan or re-send if possible; otherwise repair the PDF |
| Site photos or videos from a phone or dashcam won't open | Battery died or card filled during recording | Sample-file video repair with a working clip from the same device |
| Hundreds of files won't open after a drive failure | Fragmented or partly overwritten files from recovery | Batch check, then batch repair the damaged ones |
| Client archive with CRC errors | Incomplete upload or download | Ask for a fresh copy; repair if it is the only one |
For the Office errors in particular, see our guides to Excel's "file format or extension is not valid" and Word found unreadable content, which you can also send to users who want to understand what happened.
Handling bulk damage after a drive failure
The hardest jobs are not single files but whole folders. After a failed laptop drive, a corrupted USB disk or a recovery from a formatted NAS volume, you may have thousands of files where some open and some do not, with no easy way to tell which.
A sensible order of work:
- Recover everything you can from the failing drive to a healthy one, then stop using the failing drive.
- Run a damage check across the recovered folders so you know the scale of the problem and can report it.
- Prioritize with the user. Current client files and financial records usually matter more than a decade-old photo archive.
- Batch repair the damaged files and review anything marked as partial.
- For documents that cannot be rebuilt, extract the text and data so the user can at least recreate them.
The guide to recovered files that won't open explains why recovered files are so often damaged and what to expect.
Using File Repairer in a support workflow
File Repairer is a Windows tool that fits steps 5 and 6 of the triage workflow. It runs on 64-bit Windows 10 (version 1809 or later) and Windows 11, and covers Word, Excel and PowerPoint (including legacy .doc, .xls and .ppt), PDF, JPEG, PNG, HEIC, camera RAW, MP4, MOV, AVI, MKV, ZIP and RAR. See the supported file types table. Features that matter for support work:
- Client data stays local. Repairs run on the PC where it is installed and files are never uploaded; only the license check and update check go online. That makes it easier to stay within data protection commitments to clients.
- Non-destructive by design. Originals are never changed. Repaired copies get " (repaired)" in their names and go to a folder you choose or a "Repaired" folder next to each original.
- Triage at scale. Drag in whole folders. Tools > Check Files for Damage marks files Damaged or No damage found without changing anything, and Repair All handles the batch.
- Clear outcomes. Each file ends up as Repaired, Partly repaired, No damage found, Needs a sample file, Text extracted or Failed. An optional repair report gives you something to attach to the ticket.
- Preview before you hand back. Check documents, sheets, slides, PDF pages, photos, video frames and archive contents, with a "what was recovered" panel.
- Fallback for the worst cases. Tools > Extract Text & Data pulls every readable piece of text and data out of a document too damaged to rebuild.
Checking, repairing and previewing are free, so you can assess a job before committing. Saving repaired copies needs an Installation Key, and each license covers one PC, so a common setup is to install it on a dedicated technician workstation and bring files to it. It does not recover deleted files, read failing drives, remove passwords or break encryption.
Setting expectations with users
Users tend to assume a file is either fixed or lost. Reality is often in between, and how you explain that matters.
- Explain partial results plainly. If part of a file was overwritten or never saved, nothing can recreate it. Show the user what came back rather than describing it.
- Ask them to check the content. The user knows whether a spreadsheet is missing last week's figures. Get them to confirm before you close the ticket.
- Hand back copies, not replacements. Keep the original damaged file until the user is satisfied, in case another approach is needed.
- Be careful with locked files. A password-protected file that "won't open" may not be damaged at all. That is a separate conversation about who holds the password.
Reducing future tickets
Most corrupt-file tickets trace back to a handful of causes: no version history, unsafe removal of USB drives, sync conflicts, dying drives and power loss. Turning on OneDrive or SharePoint version history, setting up File History or server-side backups, monitoring drive health and fitting a UPS to key machines removes most of them. Our guide to preventing file corruption is written for end users and works well as a handout.
Frequently asked questions
Should I repair the user's original file?
No. Always work on a copy and keep the original untouched until the user confirms the result, in case another approach is needed.
Can File Repairer be used on client files without uploading them?
Yes. All checking and repair happens on the PC where it is installed; only the license and update checks go online.
How many computers does one license cover?
One PC per license. Many technicians install it on a single workstation and bring damaged files to it.
