VLK Office update on retail Win XP ?

[schaefferhund]

Hello,

Question: Is there any reason why a (legal) VLK MS Office cannot be Windows
Updated if installed on a system which runs on a (genuine) Win XP Pro retail?

I have 2 computers.
The Company HP laptop that I also take home, and a Dell PC at home.

Company HP laptop:
- Microsoft Windows XP Professional with its VLK, Volume Licensing Key (
PID: nnnnn-640-nnnnnnn-nnnnn )
- Microsoft Office Professional Edition 2003 with its VLK, Volume Licensing
Key ( PID: nnnnn-640-nnnnnnn-nnnnn )

Dell PC: Dual booting XP Pro and Vista Ultimate (both are my own retail,
individual licenses)
- Microsoft Windows XP Professional (retail), with its Individual Licensing
Key ( PID: nnnnn-016-nnnnnnn-nnnnn )
- Microsoft Windows Vista Ultimate (retail), with its Individual Licensing
Key ( PID: nnnnn-448-nnnnnnn-nnnnn )

My home Dell PC runs Sun’s OpenOffice. But, to do some office work on my
home PC (and synchronise later with the company’s laptop), I have installed
the (VLK) Microsoft Office Professional Edition 2003

Validation is successful for all OS and Office versions on both computers
(http://www.microsoft.com/genuine/)

Now this is what happens:

Windows Update has no problem under Vista. But, under XP, I get this error
msg:

The following updates were not installed:
Update for Microsoft Office 2003 (KB949074)
Security Update for Microsoft Office 2003 (KB951535)
Update for Microsoft Office Outlook 2003 Junk Email Filter (KB962870)

Do I need to discard my retail Win XP Pro and install the company’s VLK?
(i.e., perform a repair, in-place upgrade) Do I have other choices?

Why is it OK under Vista and not under XP?

Thank you, regards,
JL

 

[Peter Foldes]

Do I need to discard my retail Win XP Pro and install the company’s VLK?

schaefferhund

For all this that you described in your post it would be best and proper to get in
contact with your Company's IT person before proceeding with anything concerning all
the VL installs that you would like to do.
The IT person is the one capable to answer your concerns when it comes to the
Company's VLK software

 

[schaefferhund]

Thanks, Peter, but I our IT person is just as puzzled as me by this
behaviour...
Rgds,
JL

 

[Peter Foldes]

schaefferhund

Not much of an IT person you have. You might want to do the following for those
updates to install


1st Rename Office subkeys

Note: Removing the following registry keys may reset customized user
settings for your Microsoft Office programs.

1. Close all the applications.
2. Click on Start->Run, type in REGEDIT and click on OK.
3. Locate and select the following registry subkeys:

HKEY_CURRENT_USER\Software\Microsoft\Office\11.0
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0

4. Right click on 11.0 and rename them to Old11.
5. Close the Registry Editor.

2nd. Detect and Repair Office 2003


1. On the Windows taskbar, click Start, point to and click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Change/Remove Programs on the left pane.
4. Highlight Microsoft Office Professional Edition 2003 on the right pane
and click Change.
5. Insert the correct version of CD when it requires.
6. Select “Reinstall and Repair†and click Next.
7. Select “Detect and Repair errors in my Office installationâ€.
8. Click Install and wait the process to end.

3rd. Install the Updates

 

[schaefferhund]

Happy Easter, Peter,

Changing (deleting) the TWO registry subkeys you indicated did the job.
Note: before posting, I had previously tried kb895456, but this KB only asks
you to tweak with this ONE key:
HKEY_LOCAL_MACHINE \Software\Microsoft\Office\11.0\Registration

Result: "MS Office 2003 has been repaired successfully" w/o needing to
5.Insert the CD...

And, this time, these 2 updates were listed and installed:
Update for Microsoft Office Outlook 2003 Junk Email Filter (KB962870)
Security Update for Microsoft Office 2003 (KB951535)

Having even performed a complete removal and re-install of Office 2003, we
(our IT person and I) had suspected that the problem could be related to some
possible intricacies of the MS licensing policy (rather than to installation
errors or file corruption).

Thanks for your help.
Regards,
JL

 

[Peter Foldes]

Thanks for posting back and letting us know. Good Luck