Feb 04 2022 11:02 AM - edited Feb 04 2022 01:03 PM
Hello! Hoping to get some advise on the correct solution and maybe this can help someone else as I spent a bunch of time troubleshooting on my own and working with my IT folks, which was useless. I have Excel (Microsoft® Excel® for Microsoft 365 MSO (Version 2111 Build 16.0.14701.20278) 64-bit; this may be outdated slightly but my company manages the updates) setup to open to a blank workbook (under Options -> Start up options, unselected "Show the Start screen when this application starts"), this results in Excel opening Book1; this is my preference. Since the last update from Microsoft (maybe unrelated, but who knows), after the specified time for AutoRecover, a popup warning appears and states "An unexpected error has occurred. AutoRecover has been disabled for this session of Excel." The error is definitely tied to this Book1 upon first opening Excel and happens every time I reopen Excel. I change the AutoRecover time, the error pops up shortly after that time (changed from 10 minutes to 2 minutes and the error shows up after 2 minutes now instead of 10 minutes).
My initial troubleshooting to identify the issue:
Advanced troubleshooting I've already done:
Solution (workaround):
This solution did not resolved the issue of Book1 staying open after I open the file I actually want to be working in, so this is a workaround that I can live with for now, but would love any advise on how to get it working correctly. Thank you in advance!
Jan 30 2024 06:38 AM
I'm running into the same issue, curious if you ever found a permanent solution or even just what's causing it? Thank you in advance! @Heather9000
Feb 12 2024 08:07 AM
For the last last several weeks I've been experiencing the same problem. I can provide a couple of clues. The problem only affects one particular workbook. I was able to resolve it for 2 weeks by restoring a copy of the offending workbook from a December backup. This suggests the problem is in the workbook itself.
The message repeats periodically. I'm not sure what the interval is, but it is not long (minutes vs hours). I suspect it is tied to the autoRecover feature.
Roy
Feb 13 2024 05:25 PM