Document Recovery ( AutoRecover ) is not working for Excel 2016. System: Windows 8.1 64 bit Microsoft Excel 2016 MSO (16.0.8528.2126) 64 bit No fix even after a full Online repair of Office 2016 and, of course, all possible Office Updates. After working for hours on several Excel documents (which had previously been saved with a file name etc.), the power went out in our building. When the power was restored and Excel reopened, I was presented with the expected list of Recovered Documents on the left side. HOWEVER, every single one of these were simply "the Original version" or "the version last saved by user" (something like that). Meaning they did not contain ANY new data that had been entered since the last time I had saved them/reopened them despite the AutoRecover being set to 1 minute. NOTES : Document Recovery seems to be working for Word and PP. The settings in Options>Save are all the same for all Office products: currently set to AutoRecover every 1 minute. The ...AppData>Roaming>Microsoft>Excel folder contains no backup file/folder for new or reopened Excel Documents. Thank goodness, the AutoRecover does seem to be updating the equivalent folder for Word ("AutoRecovery save of DocumentX.asd" files get updated) and PowerPoint (the "pptXXX.tmp" file also updated). Edit: This is obviously some MSOffice Bug. Of the multiple 'test' spreadsheets I've been playing around with to study this, exactly 1 of them seems to actually back up. But absolutely no other ones and none of my previously created sheets ever backup to AutoRecover.

I have just lost 2 days work as well because I was given recommendations by the program that autosave has superseded "save as". When I reopened a recent file I only had my last manually saved version. C:\Users\fsmsf\AppData\Roaming\Microsoft\Excel\ only contains files with extensions I cannot open with Excel Frustrated doesn't begin to sum up how I feel! Win 10 office365

This is a terrible reply to the question. I think, given that the OP is familiar with where to find autosaved files, that they know how the AutoRecover feature works. I am having the same issue and hope that there are some more useful responses out there.

Just a suggestion, watch your Macros. I asked our IT Department before deleting the App folder suggested and he made the good suggestion of making a backup first of it. Glad he did because I went to use some Macros today and the file had been in that folder. He recovered it for me and I'm good to go. Haven't had the system crash so not sure if the "fix" will work for me but sure willing to try it.

This has definitely worked! I crashed yesterday and it recovered fine :) thanks again Andrew!

Excel 2016 AutoRecover not working - NO files being saved to the AutoRecover File location

Anonymous

Document Recovery (AutoRecover) is not working for Excel 2016.

System:

Windows 8.1 64 bit

Microsoft Excel 2016 MSO (16.0.8528.2126) 64 bit

No fix even after a full Online repair of Office 2016 and, of course, all possible Office Updates.

After working for hours on several Excel documents (which had previously been saved with a file name etc.), the power went out in our building. When the power was restored and Excel reopened, I was presented with the expected list of Recovered Documents on the left side. HOWEVER, every single one of these were simply "the Original version" or "the version last saved by user" (something like that).

Meaning they did not contain ANY new data that had been entered since the last time I had saved them/reopened them despite the AutoRecover being set to 1 minute.

NOTES:

Document Recovery seems to be working for Word and PP.
The settings in Options>Save are all the same for all Office products: currently set to AutoRecover every 1 minute.
The ...AppData>Roaming>Microsoft>Excel folder contains no backup file/folder for new or reopened Excel Documents. Thank goodness, the AutoRecover does seem to be updating the equivalent folder for Word ("AutoRecovery save of DocumentX.asd" files get updated) and PowerPoint (the "pptXXX.tmp" file also updated).

Edit: This is obviously some MSOffice Bug. Of the multiple 'test' spreadsheets I've been playing around with to study this, exactly 1 of them seems to actually back up. But absolutely no other ones and none of my previously created sheets ever backup to AutoRecover.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

I finally found the right location of the autorecovery files for Mac users of Excel!

See: this post on this forum

0 comments

94 additional answers

Anonymous

2018-03-29T15:46:32+00:00

I have just lost 2 days work as well because I was given recommendations by the program that autosave has superseded "save as". When I reopened a recent file I only had my last manually saved version.

C:\Users\fsmsf\AppData\Roaming\Microsoft\Excel\ only contains files with extensions I cannot open with Excel

Frustrated doesn't begin to sum up how I feel!

Win 10 office365
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-29T08:40:26+00:00

This is a terrible reply to the question. I think, given that the OP is familiar with where to find autosaved files, that they know how the AutoRecover feature works.

I am having the same issue and hope that there are some more useful responses out there.
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-28T20:57:20+00:00

Just a suggestion, watch your Macros. I asked our IT Department before deleting the App folder suggested and he made the good suggestion of making a backup first of it. Glad he did because I went to use some Macros today and the file had been in that folder. He recovered it for me and I'm good to go. Haven't had the system crash so not sure if the "fix" will work for me but sure willing to try it.
Was this answer helpful?

0 comments No comments
Anonymous

2018-03-27T16:57:46+00:00

This has definitely worked! I crashed yesterday and it recovered fine :)

thanks again Andrew!
Was this answer helpful?

0 comments No comments