Old floppy disks and documents are digitally transformed into secure files on a modern laptop.
Digging through a shoebox of 3.5-inch floppy disks, an old Iomega Zip drive, or a decades-old backup directory has a way of turning a casual weekend cleanup into an unexpected digital archaeology expedition. You spot a presentation or report from 1996, double-click it on a modern Windows PC running Microsoft 365, and wait for the nostalgia to hit. Instead, you are greeted by an unceremonious error dialog or a locked-down security banner. While Microsoft has spent years tightening or retiring compatibility with some of its earliest binary document formats, the free and open-source LibreOffice suite has quietly positioned itself as a remarkably capable digital Rosetta Stone for files created in the 1990s.

Recent testing and reporting by XDA Developers writer Ty Sherback highlighted just how stark this divide has become when dealing with vintage Microsoft Office files. Yet behind the frustration of an unreadable .ppt or restricted .doc file lies a fascinating collision between digital preservation and modern enterprise cybersecurity. Why does Microsoft Office struggle with or restrict its own heritage formats, how does LibreOffice manage to open them effortlessly, and what security risks do you actually take on when cracking open thirty-year-old binary files?

Old floppy disks and documents are digitally transformed into secure files on a modern laptop. The PowerPoint 95 Wall and Microsoft's Legacy Restrictions​

If you want to see a hard cutoff in backward compatibility, look no further than legacy presentations. According to Microsoft Support documentation, PowerPoint 2007 and all subsequent versions of the software are completely unable to open presentations saved in the PowerPoint 95 format. There is no hidden compatibility toggle in the ribbon and no prompt allowing you to force the file open.

Microsoft’s official support guidance for recovering a PowerPoint 95 presentation is a masterclass in catch-22 troubleshooting: the company advises users to open the file in PowerPoint 97, 2000, 2002, or 2003, choose File > Save As, re-save the deck in the newer Presentation (*.ppt) format, and then bring that converted file into PowerPoint 2007 or later. For the vast majority of Windows users and IT departments who do not keep a twenty-year-old copy of Office 2003 running in a virtual machine, that advice is essentially a dead end.

How Word, Excel, and Trust Center File Block Fit In​

With older word processing documents and spreadsheets, the situation is slightly more nuanced. In his testing for XDA Developers, Sherback noted that legacy formats such as Word 6.0 and Word 95 fall under Microsoft Office’s Trust Center File Block rules, opening by default in Protected View with editing disabled unless a user adjusts their Trust Center settings—and that system administrators in enterprise or school environments can configure policies to refuse those files outright.

Microsoft’s official documentation on Protected View confirms the broader mechanics of this defense layer across Word, Excel, and PowerPoint for Microsoft 365, as well as Office 2016 through Office 2024. When a file is restricted by File Block, fails file validation, or originates from an untrusted location, Office opens it in a read-only Protected View mode where most editing functions are disabled. Microsoft also specifically notes that binary Word 97–2003 (.doc, .dot), Excel 97–2003 (.xls, .xla, .xlt, .xlm, .xlb), and PowerPoint 97–2003 (.ppt, .pot, .pps, .ppa) files are among the formats subject to file-validation scans that check for structural tampering or corruption. If a system administrator has enforced group policies or Microsoft 365 cloud policies preventing users from exiting Protected View, the "Enable Editing" or "Edit Anyway" options are locked out entirely.

Section Summary:

  • PowerPoint 95 Cutoff: PowerPoint 2007 and newer cannot open PowerPoint 95 presentations at all, with Microsoft recommending an intermediate conversion using PowerPoint 97–2003.
  • Protected View and File Block: Modern Microsoft Office uses File Block and file validation to isolate older binary files in read-only Protected View, which IT administrators can lock down via policy.

Why LibreOffice Still Reads the 1990s Playbook​

While Microsoft moved toward stricter defaults and retired its oldest presentation parsers, The Document Foundation’s LibreOffice suite maintained and expanded its legacy import filters. Rather than stripping out support for early 1990s binary structures, LibreOffice keeps dedicated conversion filters wired directly into Writer, Calc, Impress, and Draw.

A look at the official LibreOffice 26.8 file conversion filter tables reveals just how deep this backward compatibility runs across the suite:

LibreOffice ModuleDisplayed Legacy Filter NameInternal API Filter NameSupported Extensions
ImpressMicrosoft PowerPoint 1-4 and 95'sPowerPoint 3.ppt, .pot
ImpressPowerPoint 97–2003MS PowerPoint 97.ppt, .dps
WriterMicrosoft WinWord 1/2/5MS WinWord 5.doc
WriterMicrosoft Word 6.0MS WinWord 6.0.doc
WriterMicrosoft Word 95MS Word 95.doc
WriterMicrosoft Word for DOSDosWord.doc
WriterMicrosoft WriteMS_Write.wri
CalcMicrosoft Excel 4.0MS Excel 4.0.xls, .xlw, .xlc, .xlm
CalcMicrosoft Excel 5.0MS Excel 5.0/95.xls, .xlc, .xlm, .xlw
CalcMicrosoft Excel 95MS Excel 95.xls, .xlc, .xlm, .xlw
CalcMicrosoft MultiplanMicrosoft Multiplan.mp

Notice how LibreOffice Impress explicitly separates PowerPoint 3 ("Microsoft PowerPoint 1-4 and 95's") from MS PowerPoint 97 ("PowerPoint 97–2003") and modern Impress Office Open XML (.pptx) files. Because that dedicated early parser remains in the codebase, LibreOffice doesn't choke when handed a pre-97 slide deck.

In his firsthand testing on Linux for XDA Developers, Sherback threw a variety of vintage files at LibreOffice: Word 6.0 and Word 95 documents, old IRS workbooks saved in Excel 5 and Excel 95, an even older Excel 4 worksheet, and a 42-slide PowerPoint 95 university lecture deck ironically titled "XML, HTML and All That". According to his report, LibreOffice opened all of them on the first try without extra configuration, preserving text, data, and slide rendering.

Beyond Word, Excel, and PowerPoint​

The rescue mission doesn't stop with core Office apps. LibreOffice’s filter architecture—bolstered by the Document Liberation Project—also covers an impressive museum of orphaned desktop formats. According to LibreOffice’s filter documentation and community blogs, the suite includes import filters for:

  • WordPerfect Documents (.wpd) and WordPerfect Graphics (.wpg)
  • ClarisWorks / AppleWorks text documents, spreadsheets, presentations, and drawings (.cwk)
  • Lotus 1-2-3 (.wk1, .wks, .123), Quattro Pro 6.0 (.wb2), and Lotus WordPro (.lwp)
  • Microsoft Works documents and spreadsheets (.wps, .wb1, .wb2, .wq1, .wq2)
  • Microsoft Visio 2000–2013 (.vdx, .vsd, .vsdm, .vsdx, .vstx)
  • Microsoft Publisher 98–2010 (.pub), supported via the reverse-engineered libmspub library in LibreOffice Draw—a feature The Document Foundation recently spotlighted as a lifeline for users after Microsoft ended Publisher support in Microsoft 365.

That said, veteran IT admins know better than to expect pixel-perfect miracles on every thirty-year-old file. As Sherback also acknowledged, import fidelity on complex legacy documents is not guaranteed: missing vintage fonts, intricate page layouts, or old OLE embedded objects can shift during import. Still, recovering 98% of a document’s text and structure beats staring at a "cannot open this file" error box every day of the week.

Section Summary:

  • Dedicated Legacy Filters: LibreOffice maintains explicit import filters for Word 1/2/5/6.0/95, Excel 4.0/5.0/95, and PowerPoint 1–4 and 95 alongside modern XML formats.
  • Orphaned Format Support: Through libraries like libmspub and others, LibreOffice also opens retired formats including Microsoft Publisher (.pub), WordPerfect, Lotus 1-2-3, and ClarisWorks.

The Security Trade-Off: Why Legacy Parsers Are Dangerous​

It is tempting to chalk up Microsoft’s handling of legacy formats to planned obsolescence or corporate nudge tactics, a sentiment that frequently surfaces in community discussions. However, look at the problem through the lens of a security architect, and the picture changes dramatically.

Before Microsoft introduced the ZIP-compressed, XML-based Office Open XML formats (.docx, .xlsx, .pptx) with Office 2007, Office documents relied on complex binary structures. Parsing those binary records requires intricate pointer arithmetic, fixed- and variable-length table allocations, and nested stream readers—much of it originally designed in an era before modern memory-safety hardening, fuzzing, and strict bounds checking existed. Every legacy binary parser left enabled by default on hundreds of millions of Windows PCs represents dormant attack surface waiting for a crafted file to exploit it.

Case in Point: LibreOffice CVE-2026-8356​

If anyone doubts that 1990s file parsers carry real security risks in 2026, LibreOffice’s own security logs provide the proof. On June 15, 2026, The Document Foundation published a security advisory for CVE-2026-8356, a vulnerability discovered in LibreOffice’s import filter for legacy binary PowerPoint files.

According to The Document Foundation’s official advisory for CVE-2026-8356:

  • The Flaw: A stack buffer overflow existed when importing a colour-replacement record from a binary presentation file.
  • The Mechanism: Two fixed-size colour tables were populated from the file during import, but the parser failed to reset the write position between two passes over the record. If a crafted file contained combined colour counts exceeding the table capacity, the parser wrote past the end of the fixed tables directly onto the stack.
  • The Fix: Discovered via automated analysis with Anthropic’s Claude, validated by Arthur Chan of Ada Logics, and patched by Collabora Productivity developer Caolán McNamara, the vulnerability was fixed in LibreOffice 26.2.4 by eliminating the unused second pass into those tables.

While XDA Developers suggested a crafted .ppt exploiting CVE-2026-8356 could crash the application and potentially execute code as the user, The Document Foundation’s advisory specifically confirms the stack buffer overflow condition and urges all users to upgrade to LibreOffice 26.2.4 or newer. Either way, a stack buffer overflow in a legacy binary filter is the exact class of vulnerability that keeps enterprise CISOs awake at night. Keeping old filters alive is a tremendous service for digital preservation, but it requires continuous auditing and patching.

Section Summary:

  • Binary Attack Surface: Legacy binary formats rely on complex parsing logic that can expose memory-corruption vulnerabilities if left unrestricted.
  • Real-World Vulnerability: CVE-2026-8356 in LibreOffice (patched in version 26.2.4) involved a stack buffer overflow when parsing colour-replacement records in legacy binary PowerPoint files, underscoring why keeping software updated is critical.

Practical Guide: Safely Recovering and Batch-Converting Legacy Files on Windows​

If you are an IT administrator migrating an archival file share or a Windows user rescuing documents from an old hard drive, you don't need to abandon Microsoft 365 to take advantage of LibreOffice’s compatibility filters. You can use an up-to-date installation of LibreOffice on Windows as a dedicated conversion bridge, turning unreadable or File Block-restricted legacy files into clean, modern .docx, .xlsx, .pptx, or OpenDocument (.odt, .ods, .odp) files.

Step 1: Practice Safe Digital Hygiene First​

  1. Update LibreOffice: Ensure you are running LibreOffice 26.2.4 or later (such as the current 26.8 branch) so that known legacy parser bugs like CVE-2026-8356 are patched.
  2. Work on Copies: Never run conversions directly against your only copy of a 1995 archival file. Copy the legacy files into a dedicated staging folder and keep the originals backed up read-only.
  3. Verify the Source: Only open or convert legacy binary files that come from your own archives or known, trusted sources.

Step 2: Single-File Recovery​

For a handful of files—such as an old PowerPoint 95 .ppt presentation that Microsoft PowerPoint refuses to open—simply launch LibreOffice, choose File > Open, and select the file. Once it renders in Impress, Writer, or Calc, choose File > Save As and select either the modern Microsoft 365 XML format (Word 2010–365 Document .docx, Excel 2010–365 Spreadsheet .xlsx, or Office Open XML Presentation .pptx) or an archival ODF format, which open-standards advocates recommend for long-term vendor-independent storage.

Step 3: Command-Line Batch Conversion​

If you have a directory full of legacy files, LibreOffice includes a built-in command-line conversion tool (soffice --convert-to) that processes files without launching the graphical interface.

According to LibreOffice’s official conversion filter documentation, the command syntax is:

soffice --convert-to OutputFileExtension[:OutputFilterName] [--outdir output_dir]SourceFiles

For example, XDA Developers notes that running soffice --headless --convert-to docx *.doc in a terminal converts a folder of .doc files into .docx in one pass, with the same approach applying to pptx and xlsx, while LibreOffice’s official documentation also highlights exporting directly to PDF (soffice --convert-to pdf *.doc) and specifying an output folder with --outdir.

On Windows, if you want to convert a folder of legacy .ppt files into a separate Converted directory without touching your originals, open Command Prompt or PowerShell in the folder containing your staging copies and run:

& "C:\Program Files\LibreOffice\program\soffice.exe" --headless --convert-to pptx --outdir.\Converted *.ppt

(Note: While wildcard batch conversion is a documented capability of the --convert-to flag, behavior across mixed generations of 1990s binary formats can vary depending on file extensions and corruption. Always inspect the converted output files in Microsoft Office or LibreOffice to verify that layouts, tables, formulas, and slide text survived the transition intact.)

Section Summary:

  • Patch Before Opening: Always run LibreOffice 26.2.4 or newer when handling old binary Office files.
  • Preserve Originals: Convert copies into a separate output directory (--outdir) and manually verify formatting and data integrity before relying on the migrated files.

The Verdict: Two Different Philosophies That Actually Complement Each Other​

At the end of the day, Microsoft Office and LibreOffice are solving two very different problems. Microsoft is defending hundreds of millions of corporate and consumer endpoints against weaponized email attachments, which makes locking down 1990s binary files behind Protected View and File Block—or leaving ancient parsers behind—a defensible security posture. LibreOffice, championed by The Document Foundation, treats universal document access and liberation from proprietary lock-in as a core mission, maintaining the filters needed to ensure that thirty-year-old scholarship, financial records, and personal writing don't vanish into a digital dark age.

For Windows power users and system administrators, there is no rule saying you have to pick only one camp. Keeping a patched copy of LibreOffice alongside Microsoft 365 gives you the best of both worlds: hardened day-to-day enterprise productivity when you need it, and a master key for the 1990s time capsule whenever an old floppy disk or backup drive lands on your desk.

 

References

  1. LibreOffice opens files from the '90s that Microsoft Office now refuses to touch XDA 2026-10-17T14:30:20+00:00
  2. File Conversion Filters Tables help.libreoffice.org
  3. CVE-2026-8356 | LibreOffice - Svobodný kancelářský balík - Smysluplný projekt - Skvělí lidé cs.libreoffice.org