ScanPST speaks in short, alarming sentences. Translated, each one tells you exactly what is broken and whether a retry, a conversion, or an extraction tool is the right answer.
Most people read a ScanPST error as one word: failed. In reality the tool produces a handful of distinct messages, and they are not interchangeable. One means something interfered with the scan. One means the file's header is destroyed. One is not really about corruption at all - it is about a file format from another era hitting its size wall. Matching the message to the cause is the difference between a ten-minute fix and a weekend of blind retries. Here is the decode, message by message. Every repair mentioned starts from a copy of the file, with Outlook fully closed.
What it means: the scanner hit damage it could not walk past - or something disturbed it mid-scan. The reassuring half of the message is true: nothing was written, so the file is exactly as it was.
Companion wording: The file is not a personal folders file. This is the heaviest message of the set.
.pst, did a backup program rename or compress itThis code has a famously specific meaning: the PST is in the old ANSI format (Outlook 2002 and earlier, and some ancient archives) and it has reached, or is close to, that format's hard 2 GB limit. Corruption in ANSI files typically begins as the size approaches roughly 1.8 GB.
No repair pass can fix a format limit - the file is not just damaged, it is full in a way its own format cannot grow past. The honest route is conversion: bring the mail into a modern Unicode PST (by importing in batches into a new data file where Outlook can still open it), and retire the ANSI file. The oversized-PST page in this series covers both size walls in full.
80040900 points at severe structural corruption or header damage a step below "not recognized" - the tool can start, but the damage is deep. Expect partial recovery at best from this tool; extraction or backup is usually the real answer.
The related symptom is the freeze: the scan stalls in a later phase, or Windows reports the Inbox Repair Tool has stopped working. Before calling it dead, check whether it is actually working - a many-gigabyte file on a mechanical disk can legitimately take an hour or more. Watch disk activity in Task Manager and whether the .log file beside the PST is still growing. A growing log means patience; a frozen log with zero disk activity for a long stretch means the pass has truly died.
Not every report is a failure. When ScanPST finds only minor inconsistencies and says repairing them is optional, it means the structure is fundamentally sound. Many such files open and work perfectly.
.log file sits beside your PST with the scan's own record - which phase it reached, what it found, what it changed. When a message is not covered here, that log plus the phase number is the evidence any technician (or forum answer) will ask you for first.Find your error in the video walkthrough and watch the fix applied to a real file.
Watch Full VideoThe tool does not recognize the file. It means ScanPST cannot even read the file's structure, so no pass will help. Scan stopped files sometimes yield to a clean retry on a local copy; header-dead files go straight to extraction tools or a backup.
Open the .log file created beside your PST - it records the phase where the scan stopped and the errors it met. The phase localizes the damage: early phases are about the file's headers and folder structure, later phases about the items inside.
Not by itself - corruption has many causes. But if PST files keep corrupting on the same PC, check the drive's health with its SMART status. Repeated file corruption is a classic early symptom of a failing disk.