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

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted. Very often the fix is to run SCANPST.EXE on the offending PST/OST file. However, every time I go to do this I forget where the two executable files are. Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

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

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition. However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition. This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell: reagentc /disable If you get the error message "REAGENTC.EXE: Operati...

Artifact Weblog

Search This Blog