Troubleshoot Microsoft Excel XLSB Save and Corruption Errors
Question details
Troubleshoot a Microsoft Excel XLSB workbook that reports corruption or cannot be saved after a recent Microsoft 365 update.

- Product
- Microsoft Excel for Microsoft 365
- Device & OS
- not provided
- Scenario
- The user needs to identify whether Excel add-ins, the Office installation, or a recent update is causing XLSB save or corruption errors.
- Observed behavior
- Excel reports that an XLSB workbook is corrupted or displays an error while opening or saving the file after an update.
Record the exact Excel error message and your Microsoft 365 version and build number from File > Account > About Excel. Work on a copied XLSB file while testing so you can preserve the original workbook for recovery or support analysis.
Disable Excel and COM add-ins to isolate the XLSB error
Use this first when the issue began after an update or occurs only when Excel starts normally.
Add-ins can interfere with workbook opening, calculation, and saving. Testing Excel without them helps determine whether an add-in is causing the XLSB corruption message.
Close Excel, press Windows+R, type excel /safe, and select OK. Try opening and saving a copy of the XLSB workbook.
In Excel, select File > Options > Add-ins. At the bottom, choose Excel Add-ins in the Manage list, select Go, clear all selected add-ins, and select OK.
Return to File > Options > Add-ins. Choose COM Add-ins in the Manage list, select Go, clear all selected COM add-ins, and select OK.
Restart Excel normally and test the workbook. Re-enable one add-in at a time through File > Options > Add-ins > Manage > Go until the error returns.

Repair the Microsoft 365 Office installation
Use Online Repair if disabling add-ins does not stop XLSB corruption or save errors.
Update Excel and save a temporary XLSX copy
Use this when the issue is linked to a recent build and you need a workable copy while investigating the XLSB problem.
Use WPS Office for everyday Excel-compatible spreadsheet work
If Microsoft Excel update-related errors interrupt your work, WPS Office provides a free, lightweight spreadsheet alternative with a familiar interface and seamless migration for common Excel files. You can continue reviewing and editing compatible spreadsheets while you investigate the Microsoft 365 XLSB issue.
- 1. Install WPS Office: Download and install WPS Office, then open WPS Spreadsheet from the WPS Office home screen.
- 2. Open a compatible workbook copy: Select Open and choose an XLS or XLSX copy of the affected workbook rather than replacing the original XLSB file.
- 3. Review worksheet content: Check formulas, tables, and formatting in WPS Spreadsheet, and confirm that the information you need is available.
- 4. Save in an Excel-compatible format: Select Menu > Save As and choose Excel Workbook (*.xlsx) when you need to share the workbook with Microsoft Excel users.

Frequently Asked Questions
Why does Excel say my XLSB workbook is corrupted after a Microsoft 365 update?
A recent Excel build, an incompatible Excel or COM add-in, or damaged Office components can trigger the message. Start Excel with excel /safe, disable add-ins through File > Options > Add-ins, and test a copy of the workbook.
How do I repair Microsoft Excel without uninstalling Office?
On Windows, go to Settings > Apps > Installed apps, find Microsoft 365 or Microsoft Office, select More options > Modify, and choose Online Repair. Restart the computer after the repair completes.
Can I convert an XLSB workbook to XLSX as a workaround?
Yes, if Excel can open the workbook. Select File > Save As > Browse, choose Excel Workbook (*.xlsx), and save under a new name. Check macros, data models, connections, and other advanced features afterward because they may not transfer fully.
What information should I include when reporting an XLSB issue to Microsoft?
Include the Excel version and build from File > Account > About Excel, the complete error message, workbook size and characteristics, installed add-ins, whether Safe Mode changes the result, and reproducible opening or saving steps.
Should I overwrite the original XLSB file while troubleshooting?
No. Keep the original XLSB unchanged and perform tests on a separately named copy. This preserves the source file if you need to attempt recovery or send it to support.




