'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix PowerPoint for Mac Freezes When Opening AutoRecovery File
Question details
PowerPoint for Mac application freezes and becomes unresponsive when attempting to open an AutoRecovery presentation file.
- Product
- Microsoft PowerPoint for Mac
- Device & OS
- macOS
- Scenario
- The user launches PowerPoint and attempts to recover or automatically open a previously unsaved presentation.
- Observed behavior
- PowerPoint freezes entirely during startup or while loading the file because the AutoRecovery presentation is corrupted or incomplete.
Ensure that PowerPoint is completely closed. If the application is frozen, click the Apple menu and select 'Force Quit' to terminate PowerPoint before proceeding.
Remove the Corrupted AutoRecovery File from the Library
Locate and remove the specific AutoRecovery file causing the freeze to restore normal PowerPoint startup.
PowerPoint for Mac automatically attempts to open recovered files on startup. If an AutoRecovery file was incompletely saved or corrupted, it will cause the application to freeze in an infinite loading state. Removing this specific file from the hidden Library folder breaks the cycle and allows the app to launch normally.
Open Finder, click 'Go' in the top Apple menu bar, hold down the 'Option' (Alt) key on your keyboard, and click on 'Library' when it appears in the dropdown menu.
Follow this specific path: Containers > Microsoft PowerPoint > Data > Library > Preferences > AutoRecovery.
Locate the suspicious presentation file inside the AutoRecovery folder. Drag and drop it to a backup location like your Desktop, or move it to the Trash if you no longer need it.
Reopen Microsoft PowerPoint. The application should now start smoothly without freezing since the problematic file is no longer being triggered.
Try WPS Office for Stable and Smooth Presentations on Mac
If PowerPoint for Mac continues to freeze or crash, consider switching to WPS Office. It provides a lightweight, highly stable presentation tool that is fully compatible with Microsoft PowerPoint formats, ensuring you can edit and present without interruptions.
- 1. Download WPS Office: Visit the official WPS Office website and download the free macOS installation package.
- 2. Install and Launch: Run the installer and follow the on-screen instructions, then open WPS Presentation.
- 3. Open Your Presentations: Simply drag and drop your existing .pptx files into the application to continue editing seamlessly.
Frequently Asked Questions
Where are AutoRecovery files stored on Mac?
AutoRecovery files for PowerPoint on Mac are stored in a hidden Library directory. The exact path is usually Users > [your name] > Library > Containers > Microsoft PowerPoint > Data > Library > Preferences > AutoRecovery.
Will deleting the AutoRecovery file delete my original presentation?
No, deleting or moving the AutoRecovery file only removes the temporary backup that PowerPoint created automatically. Your original manually saved file will remain completely intact in its original folder.
Why does PowerPoint for Mac freeze specifically on startup?
PowerPoint often freezes on startup if it is attempting to automatically load a corrupted AutoRecovery file, restoring a previous session that crashed, or loading an incompatible third-party add-in.
