Skip to main content

Recovering Unsaved Documents in Microsoft Office

I got a set of worried messages from a customer of mine recently who had fired up Microsoft Word and proceeded to create a document without saving it.  After spending hours on it they then shut down their PC and accidentally clicked on the option to to not save the document.  Was there a way to get it back?

After a little bit of digging I found the answer.  There are two ways to resolve this:

1. Quicker, slightly more techie method:

-  Open a Windows Explorer window and browse to the following location:

-  c:\users\<USERNAME>\AppData\Local\Microsoft\Office\UnsavedFiles

-  There should be a file or files with the ASD extension.  One of these will hopefully be the file you are missing.

-  Double-click to check and see - the files should open up with Word.


2. Slower but less techie method:

-  Open up Microsoft Word and just click on a Blank Document template to get started.
-  Click on the File menu and then click Info
-  Click on Manage Document
-  Click Recover Unsaved Documents
-  This will bring up an Open window at the location listed in Option 1
-  Choose the most likely file in the list and click Open
-  Once you've found the file you were looking for make sure to save it





Comments

Popular posts from this blog

Evolution MK-249C MIDI Keyboard Mac OS X Problem

Mac OS X generally seems capable of dealing with just about anything you can throw at it. However upon connecting my trusty Evolution MK-249C MIDI keyboard up to my 2nd generation MacBook it steadfastly refused to play ball. This keyboard has always been instantly recognised by Windows XP and so it was surprising to encounter this. The M-Audio website (M-Audio took over Evolution it appears) offered no real assistance. There was no driver available for Mac OS X 10.4.9 as the keyboard is supposed to be "Class Compliant" which apparently means it doesn't need one... strange. Eventually after consulting some forums I found the fix. The problem seems to be related to Mac OS on the Intel MacBooks. There is a patch on the M-Audio site but only for MacOS 10.1.5. This must be downloaded and installed. Here is the link: http://www.m-audio.com/index.php?do=support.drivers&f=596 Upon restarting the OS the keyboard was recognised by Mac OS and GarageBand had no trouble tal...

XP Startup Issues - The Recovery Console

The Windows Recovery Console is a fantastically useful tool if you find yourself with a PC that will not boot Windows. There are many useful Windows startup tools such as Last Known Good Configuration and the many different flavours of Safe Mode but all of these rely on a bootable Windows system. System Restore is completely useless in this scenario since it relies on one being in Windows to use it. The kinds of things that could couse an unbootable Windows system could be: Corrupted boot files - e.g. NTLDR, NTDETECT.COM Corrputed Windows system files - NTOSKRNL.EXE, HAL.DLL The Recovery Console allows you to boot into an environment "underneath" that of your Windows installation (by using the Windows CD or by choosing it at boot time if you pre-installed it) and so you can perform major low level repairs to your Windows installation. Follow the link below to find out how to use the Recovery Console: http://support.microsoft.com/kb/314058/

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS