Word 2007 crashing on Windows 7 or won’t open documents

For the last few days my Word 2007 installation on my Windows 7 box has been playing up.

In particular it will not let me use the mouse to edit documents, as in clicking within the Word application does nothing.

If I open a document through Windows explorer or any means other than from the open dialog within the program they will not open.

And when I close Word is crashes and restarts.

The good news is out of frustration this morning I found the solution to the problem.

And it is all the fault of Microsoft and Automatic Updates.

This Microsoft KB article will explain how to fix the problem.

This is the outline of the problem as given by Microsoft

You install an automatic update for Microsoft Office Word 2007 on a Windows Vista-based computer and then restart the computer. If Word 2007 was running when the computer was restarted, you experience one or more of the following symptoms:

  • The mouse does not work when you use Word.
  • You cannot open a Word document from the Search window in Windows Vista.
  • You cannot open a Word document from Windows Desktop Search.
  • Word crashes when you try to start or exit Word.
  • Word crashes when you open the Open dialog box.
  • Word crashes when you save a document.
  • Word crashes when you close a document.

The first thing to note is that this problem applies to Windows 7 now as well as Vista. However, the automatic fix it script that you can download to fix the problem will not work on Windows 7 so you have to fix the problem manually (I will get to this soon).

The second thing to note is that the problem was caused by restarting Windows to install updates while Word was still running. There are only two ways this could happen. a) you didn’t close all the programs running on the system before you restarted. or b) Windows Update automatically restarted the system while these applications were running. What happened to me is b) and that is what really annoys me. Sure you can disable automatic installation of Windows Update files. However, I have the feature turned on for the sake of simplicity. If there are critical updates I want them installed. What I do not apprieciate is Windows corrupting itself in the process of installing updates. Furthermore I do not expect a problem with an Automatic Update to still be a problem more than two years after the problem was discovered (this blog on this exact problem is posted September 2007: http://www.edbott.com/weblog/?p=1771)

The fix is simple, but it does involve editing the registery. Something that you are never advised to do unless you have a serious problem with your computer. Hence my anger at Microsoft for stuffing up their own program through an update.

To resolve this problem, delete the HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Data registry subkey. To do this, follow these steps:

  1. Exit all Office programs.
  2. Click Start type regedit in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.
  3. Locate and then click the following registry subkey:
    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Data
  4. On the Edit menu, click Delete, and then click Yes.
  5. Exit Registry Editor.
  6. Restart Word.

Sorting out Adobe CS4 License Key Issues

Okay this is one of those blog posts that tell you something they really should have included in the instruction manual.

When you install Adobe CS4 Web Standard Academic Edition make sure you enter the license key during install.

If you do not do this make sure you switch the language from US English to International otherwise when you try to insert the license key after installation the program will not accept it and the only remedy is to uninstall and reinstall.

Adobe Install Fail.

First Day of Internship

Okay today was interesting.

I am very tired and now thinking about how much of a challenge I have for me over the next seven weeks on a project that looked so simple from the outset.

I was meant to start work at 8.30am this morning and I had no idea how hard it would be to get carparking and stuff like that. In the end I arrived at 8.10am before anyone else. Doh! Anyway my manager arrived at around 8.20am and we got stuck in pretty quickly.

First things first involved setting up a computer for me. About 10 minutes later I had a computer and desk and 22in moniter to work from and a network login. And by 8.50am I had my first hello world program compiled.

Initially I turned down using visual studio in favour of remaining with gcc. However I quickly discovered that I needed it for some project files and got it installed. (this then came back to bite me as I spent half the afternoon waiting for service pack one to install).

I am also trying to get used to using a huge moniter but not having dual screens. I think I prefer my home set up with 2 19in screens.

My morning consisted of a lot of googling and reading to determine if I could use some LGPL code in a closed source application. In the end we determined that if the LGPL code that was used remained LGPL and open then we could.

My afternoon consisted of trying to get my head around some C code written 20 or so years ago.

This isn’t easy. All the variables are just two letters and there are very few comments in the code. I think it will take me the rest of the week to fully understand how the code works. From then I will need to start working on updating it and making the project.

Dreamweaving in Vista

Two months ago I got a new computer running Windows Vista Home Premium.

Despite all the warnings about old programs not running, I had no issues with any application, except Macromedia Dreamweaver MX 2004 which would just crash on loading.

When I first got the system I spent around half a day trying to work out how to get it work. But I was unsuccessful.

Yesterday I was loaned a copy of Dreamweaver 8 to use until I went back to full time study next year and get CS3. However Dreamweaver 8 had exactly the same loading issue as 2004.

Now I know that MX 2004 is not supported or expected to run in Vista but 8 is meant to.

So out comes the google searches. I eventually narrowed the problem. Software conflict.

Yep, all of you out there using an Acer Computer will probably have a program installed called eData Security. It will run by default at start up. I never use the program (it is designed for file encryption).

To get Dreamweaver to run just uninstall eData Security and voila Dreamweaver MX 2004 and 8 will run.