The loop looks like this: you open the deck, PowerPoint says it found a problem and offers to repair, the repair “succeeds”, you save, and the next open asks again.

Nothing is being repaired, because PowerPoint is fixing the symptom each time and writing the same broken part back into the file.

Why the loop happens

A .pptx is a ZIP of XML plus embedded media. PowerPoint’s repair pass rewrites the parts it can parse and drops the rest. If the actual cause is one of the following, the cause survives the repair and the deck breaks again immediately.

1. A media file is corrupt or in a format PowerPoint cannot index. An MP4 with an unusual codec, a WAV ripped from a phone, an image whose header is damaged. The slide looks fine in the editor and breaks on the next open. This is the most common cause by a wide margin.

2. Fonts referenced but not installed. Less common, but it produces the same dialog. Decks built on a colleague’s machine with licensed fonts will repair-loop on yours.

3. The deck was saved to a synced folder mid-write. OneDrive or Dropbox picked up the file while PowerPoint was still writing. The result is a structurally valid ZIP with a mismatched manifest.

4. The file is over the practical size ceiling. Decks above roughly 300 MB, usually stuffed with uncompressed video, hit limits in PowerPoint’s parser before they hit disk limits.

Locating the broken part

This takes five minutes and tells you exactly what to fix:

  1. Copy the file, rename the copy to .zip.
  2. Extract it.
  3. Look in ppt/media/. Sort by size, then check the biggest files first.
  4. Open the suspicious ones directly — a photo that will not preview, or a video that will not play in VLC, is your culprit.
  5. Also check that [Content_Types].xml exists and that ppt/presentation.xml ends cleanly rather than mid-tag.

If a media file is the problem, delete it from the extracted folder, re-zip everything (starting with [Content_Types].xml), rename back to .pptx, and open. The deck loads; you lose one video, not the presentation.

Fixes worth trying, in order

Compress the media. In PowerPoint: File → Info → Compress Media → Standard. This re-encodes video and images into formats PowerPoint handles natively. It is the single most effective fix for repair loops, and it usually shrinks a 200 MB deck to under 40 MB.

Save as a fresh file. File → Save As → .pptx with a new name. This rebuilds the package from PowerPoint’s internal model rather than copying the old container. If the loop was a structural mismatch, this ends it.

Round-trip through Google Slides. Upload, open, then download as .pptx. Google’s importer is lenient and its exporter writes a clean package. Expect to lose some transitions and any SmartArt.

Move it off the synced folder first. Copy to a local path, repair there, then put the fixed copy back. Repairing inside a OneDrive folder is how you get a second, different corruption on top of the first.

When it is not worth fixing

If the deck contains hundreds of carefully built slides, animations and embedded charts, the round-trip fixes will technically work and visibly damage the design. At that point the right move is a structural repair: isolate the broken parts, replace only those, and leave everything else byte-identical.

That is also the case where re-saving repeatedly does the most damage — each save flattens a little more of the original structure.

FAQ

Will Compress Media damage the video quality?

It re-encodes, so yes, slightly — and it drops unusual codecs entirely. For a repair that is the right trade: a deck that opens everywhere at 720p beats a deck that opens nowhere. Keep the original file, and if the presentation is client-facing, replace the compressed video afterwards with a version you control.

The deck opens fine on my laptop but repair-loops on the meeting room PC.

That is almost always fonts — the same mechanism behind most “file is corrupt” reports in Word. The deck references a font that only exists on your machine, and the second computer substitutes it in a way that breaks the theme’s relationships. Embed the fonts (File → Options → Save → Embed fonts in the file) or switch to a font both machines have.

Can a repair loop be caused by the file name or location?

Yes, occasionally. A path over about 250 characters, a folder on a network share that drops the connection mid-read, or a name containing characters the sync client rewrites. Copy the file to C:\deck.pptx and open it there — if the loop stops, the file was never the problem.

If the deck is large and every round-trip fix costs you layout fidelity, the manual repair route keeps the slides intact instead of flattening them.

Big deck, no clean backup? Send the original to help@easyofficefix.com with a note on which slides matter most. Assessment and flat price first, and the original layout is preserved wherever it can be.