Have you ever closed Word after making a bunch of changes, and then accidently clicked ‘No' when asked if you want to save your changes? Then you suddenly realized what you have done, only to find that there was no way to recover your work? You are not alone. In fact, so many people were in similar situations that we improved Office 2010 so you can get that document back! We call this feature Versions and I would like to spend a little time introducing it to you.
In prior versions of Office we periodically save your document in the background when you are editing a document. We keep this file around so we can use it to recover your work if the application crashes.
For Word, Excel, and PowerPoint, Office 2010 improves on this idea. In the Backstage view we expose the periodic autosaved files from your current editing session and allow you to compare or restore them as the newest document. We purge them when you save and close your editing session.
Additionally, if you close an editing session without saving, we now keep your last autosaved file and let you access it from the Backstage view, under Recent Documents, or from Document Information when you open your document again. So now you can recover that unsaved work with a few simple clicks.
To ensure that we don't clutter your computer with these autosaved files, we only keep these files for 4 days, or until the next time you edit your document.
Now you can enjoy Office 2010 Excel, PowerPoint and Word with the knowledge that the software is working to protect you from losing your work.
I think this will fast become a much-loved feature, particularly in education environments. Am I right in assuming this feature naturally extends to new documents that have never been saved?
Is there any chance that the true Word Versioning feature (dropped in 2007) might be able to be given a new life again....
This is a great feature, because I have done this more times than I care to admit. But, as an IT guy I have to ask... what kind of security block and options do we have to PREVENT or LIMIT this behavior more. I can think of nothing worse than a person typing up a document to later decide it was a really bad idea and scrap it... if that mistake can be so easily recovered, I can see a recipe for disaster brewing.
This is great, but when will we be able to get our hands on it?
Giving users access to the AutoRecovery files is a great enhancement but two things the article might have mentioned (and my apologies if I'm wrong about this...)
One, you have to have selected (under Excel (for example) Options, Save group) (1) Save AutoRecovery Information and (2) Keep the Last Auto Recovered File If I Close without Saving.
Second, if the AutoRecovery time interval is say 10 minutes, you can lose as much as that many minutes of changes.
What if I start a new document, work with it (do not save it), close Word and accidentally click Don't save? can you recover from that? (it may seems to be silly but happened to me.)
amazing help we r proud of OFFICE MICROSOFT
This certainly a major improvment for many users
Please use Task Dialogs instead of the old grey Save confirmation dialog box (message box style). The old message box is suitable for Windows XP, but under Vista and Windows 7, use Task Dialogs.
A reasonable start - although I forsee some security issues here - and a small help.
Of course, after 20+ years (?) of development it would be nice to see something a little more sophisticated. Document versioning under Word 2003 is a pig that deserved to go I'm afraid but surely after all this time, it would be possible to have automated and semi-automated versioning that produces multiple files on demand and is able to compare two versions "diff" style?
Working with large and complex documents day-to-day, especially where people are reviewing them, I have had to write my own replacement save macro that keeps backup copies before saving a new version because I can't trust word (at least up to 2003 commonly in use with my customers) not to eat critical bits of the document (like styles for example) at inopportune moments.
I use a DVC wherever I can but these are designed for coding not for document management and so are not ideal.
What control will administrators have over these settings?
I can see these recovery files being a concern during EDiscovery. If that recovery file exists when a subpoena/litigation hold order comes in, I expect it would be required to be included even though the user did not intend it to exist.
I think I might prefer to set these to destroy at log off/restart or after 24 hours at most.
Thank you for your comments and questions, I will try and respond to some of them:
• You asked if this feature extends to new document.
o In the case of new documents we will keep your last autosave and all those will be accessible from Versions -> Manage Versions -> ‘Recover Unsaved Documents‘.
• Is there any chance that the true Word Versioning feature (dropped in 2007) might be able to be given a new life again?
o This release we are not planning to revive the Word versioning feature that was dropped in Office 2007.
• What kind of security block and options do we have to PREVENT or LIMIT this behavior?
o The user can go into application Options -> Save and disable this
o This can be disabled via Group Policy
• Is this feature on by default and what is the default?
• The default AutoRecover interval is 10 min for Word, Excel and PowerPoint. Thus a file is autosaved every 10 min when actively editing. Thus if you close without saving, you may not recover the changes you made since your last autosave.
• By default we will create an “I closed without saving” version
Program Manager (MSFT)
why is it that the 'save a backup' option is still not turned on my default?
I lost work from an unsaved document in Word 2010 a couple of weeks ago when a dialog popped up because I maanged to hit ctrl-w while typing and and I accidentally clicked no to save - and I had no prompt to autorecover, nothing on the Backstage menu and only a partial 45 minute old autorecovery file that I found by hand. I think this was an interaction with offline files - can you document how you work with offline files from Windows Server fileshares and network drives?
I was just (literally) angered by just this accident. I am now sure to buy office 2010 when it comes out.
Could someone please fix the "tags"? There are only 4 blog posts that are tagged with "Backstage". The second-oldest one is called "Part 3". Why aren't parts 1 and 2 tagged "Backstage"?