Prevent PST Corruption Size Discipline Clean Shutdowns and Simple Habits
Every page in this series is emergency medicine. This one is the vaccination - the handful of habits that decide whether you ever need the others.
By Technical AnshuOutlook 2010 to Microsoft 3658 minute read
Watch the video for the repair - then adopt the habits that make it the last repair you run
PST corruption feels random, but its causes are a short, boring list: a file grown too large, Outlook killed mid-write by a power cut or a forced shutdown, the file stored somewhere it should never live, and a disk quietly failing underneath it. None of these are exotic, and all of them are habits rather than fate. This page is the prevention checklist - the cheapest repair is the one that never happens.
The healthy mailbox checklist
Archive last year into its own PST - live file stays lean
Compact Now run after every big clean-up
Outlook fully closed before shutdown or power off
PST stored on a local disk - never a network share or synced folder
A backup copy exists from this week, Outlook closed when it was taken
Five habits. Together they remove the overwhelming majority of PST corruption before it starts.
1
Keep the File Modest
Size is the master variable: big files corrupt more often, scan slower, and lose more when they do. The discipline that works:
Archive by year into separate PST files - the live file holds current work, closed years sit in their own files you can open when needed
Delete in bulk regularly and empty Deleted Items and Junk as routine, not as annual events
After any big deletion, run Compact Now from the data file's settings - deletion alone leaves the space reserved inside the file; compacting is what actually shrinks it
There is no official magic number, but experienced technicians keep the live file well below the ceiling - think in the 10 to 20 GB range rather than flirting with 50.
2
Close Outlook Before the Power Goes
The classic corruption story is a write interrupted: a power cut, a forced shutdown, a laptop battery dying while Outlook was mid-sync. A PST is being written constantly while Outlook runs, and cutting power mid-write is asking the file's tables to disagree with each other.
Close Outlook and let it exit fully before shutting down - on a busy mailbox the process can linger after the window closes
Avoid force-killing Outlook in Task Manager except when it is genuinely hung
On desktops in areas with unreliable power, a small UPS is cheap insurance - it exists to buy clean shutdowns, and this is exactly the purchase it justifies
3
Store the PST Where It Belongs
A PST belongs on a local disk. Two popular arrangements are corruption recipes:
Network shares - Microsoft does not support live PSTs on network drives; the file's constant small writes over a network connection invite exactly the inconsistencies ScanPST later finds
Synced cloud folders - keeping the live PST inside a OneDrive, Dropbox, or Drive-synced folder means two programs fighting to own a file that changes every second; sync your backups, never the live file
Failing or removable drives - a live mailbox does not belong on a suspect disk or a USB stick; archives can visit, the working file should not live there
4
Mind the Disk Underneath
A PST is often the largest, most-written file on a PC, which makes it the first casualty of a drive going bad - and the first messenger. If corruption recurs on the same machine, check the drive's SMART health before blaming Outlook again. Keep sensible free space on the drive as well: a disk at 99 percent full gives every large write a chance to fail halfway. Treat a second corruption on one machine as a hardware investigation, not a software ritual.
5
Back Up Like You Mean It
Every page in this series exists because someone, somewhere, had no backup. A backup changes corruption from surgery to errand:
Copy the PST on a schedule with Outlook closed - a copy of an open, writing file can be as corrupt as the original
Keep the copies on a different drive than the original, with at least one older generation retained
For Microsoft 365 and Exchange accounts, remember the server already holds the mailbox - know which of your files are containers and which are caches, and spend backup effort on the containers
Do this, and the worst PST day of your year becomes: restore last week's copy, lose nothing important, carry on.
The honest ending: prevention is unglamorous and it does not trend - nobody makes a video titled "nothing went wrong this year". But the entire repair industry for this file format feeds on skipped habits. Size discipline, clean shutdowns, local storage, and one real backup: that is the whole secret.
Watch the Complete Process in the Video
Learn the repair in the video while you are calm - then set up the habits so you rarely need it.
How big should I let one PST get before splitting it?
Well below the ceiling - many technicians split by year and keep the live file under roughly 10 to 20 GB. There is no official magic number; smaller files scan faster, repair faster, and lose less when something does go wrong.
Is Compact Now safe to run regularly?
Yes, on a healthy file - it reclaims the space left behind by deleted items. Run it after large clean-ups, with Outlook otherwise idle. Compacting a corrupt file is not a repair, though; fix corruption first and compact later.
My PST sits in a synced OneDrive folder. Is that really a problem?
Yes. Sync tools and Outlook both try to own the file while it is open and changing, and that tug of war is a documented path to corruption. Keep the live PST on a local, non-synced path and sync your backup copies instead.
This guide is based on the Technical Anshu video above - if a step gets stuck, ask in the video comments and you will get an answer there.