Why is validating genuine Microsoft Office software such a pain? RRS feed

  • Question

  • Diagnostic Report (1.9.0019.0):
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    Cached Validation Code: N/A
    Windows Product Key: *****-*****-YRPRK-RPDQ2-9K6XT
    Windows Product Key Hash: DyVbNiyWaituzaZu/+jK8Q/Lq/Q=
    Windows Product ID: 76487-OEM-2211906-00122
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {437D671C-3C83-491D-8271-EF37AD7162F7}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered,
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A
    Version: N/A

    WGA Notifications Data-->
    Cached Result: 0
    File Exists: Yes
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 114 Blocked VLK 2
    Microsoft Office Professional Edition 2003 - 114 Blocked VLK 2
    OGA Version: Registered,
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-230-1

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\IEXPLORE.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{437D671C-3C83-491D-8271-EF37AD7162F7}</UGUID><Version>1.9.0019.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-9K6XT</PKey><PID>76487-OEM-2211906-00122</PID><PIDType>2</PIDType><SID>S-1-5-21-2796713857-3359896355-3042452539</SID><SYSTEM><Manufacturer>Equus Computer Systems</Manufacturer><Model>Nobilis</Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>PRG3110H.86A.0059.2008.1024.1834</Version><SMBIOSVersion major="2" minor="4"/><Date>20081024000000.000000+000</Date><SLPBIOS>Equus Computer Systems,Equus Computer Systems,Equus,Equus</SLPBIOS></BIOS><HWID>217E38F70184E078</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08:00)</TimeZone><iJoin>1</iJoin><SBID><stat>2</stat><msppid></msppid><name>Equus Computer Systems</name><model>Nobilis</model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version=""/><File Name="WgaLogon.dll" Version=""/><File Name="OGAAddin.dll" Version=""/></GANotification></MachineData><Software><Office><Result>114</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>114</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>59D1605114E3500</Val><Hash>vfZmaSmFPIYrLWTcZSZErUQg+Fo=</Hash><Pid>73931-640-0000106-57185</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="11" Result="114"/><App Id="16" Version="11" Result="114"/><App Id="18" Version="11" Result="114"/><App Id="19" Version="11" Result="114"/><App Id="1A" Version="11" Result="114"/><App Id="1B" Version="11" Result="114"/><App Id="44" Version="11" Result="114"/></Applications></Office></Software></GenuineResults> 

    Licensing Data-->

    Windows Activation Technologies-->

    HWID Data-->

    OEM Activation 1.0 Data-->
    BIOS string matches: yes
    Marker string from BIOS: 81DC:Equus Computer Systems Inc|81DC:Equus Computer Systems Inc
    Marker string from OEMBIOS.DAT: Equus Computer Systems,Equus Computer Systems,Equus,Equus

    OEM Activation 2.0 Data-->

    My company recently sperated from a large parent company to form an independent entity. Part of the divestiture settlement included 5 licenses for MS Office 2003. The parent company purchased licenses for our small business through Dell, we used a third party IT team to install the software and set up our computers. Unfortunately, Dell butchered the sell and left the licenses under the parent company and our third party IT team installed non-genuine versions of the software on our machines. So after the SP3 upgrade we are consistently receiving error messages that our software is not genuine.

    After WEEKS of correspondence with Dell, the IT company, the original parent company, and Microsoft, we were able to determine what the the correct product activation keys are. I've registered and gained access to the Volume Licensing Service Center as well as MS Live. This was not easy, Microsoft operators consistently provided me with false information, lies, and excuses to pass the buck onto Dell. Dell was almost as bad. Finally, I set up a conference call with Dell, Microsoft, and the original parent company at which point I was able to gain access to the VL Service Center and finally found the product keys. However, I was still given conflicting information by Dell and Microsoft regarding the transfer of ownership. Microsoft insists that this is something Dell needs to fill out and complete, Dell insists the customer needs to fill this out and go directly to Microsoft. I'm siding with Dell on this because they have provided me with an official looking form that even has directions and an address to submit it to Microsoft.

    So now that I have the correct product keys, I should be good to go right? WRONG! reading through these forums, it appears that Microsoft does not have a tool to update product keys for MS Office software. Users need to edit their computer's registries in order to update product keys. This seems a bit outrageous to me. So I have the following questions:

    Am I missing something?

    Is there a tool out there that will make this easier?

    Why is MS using this Genuine Software Validation if there is not an easy way to fix the errors that it recognizes?

    I am trying to do the proper thing here, and we have spent quite a bit of money to ensure that all of our software is legal, and genuine. Any advice or answers to the above questions would be greatly appreciated.     

    Friday, February 19, 2010 7:18 PM


  • Hello Zdub1983,

    This MS KB provides the instructions for changing Office product keys:  http://support.microsoft.com/default.aspx/kb/895456

    My understanding is that this only works if the version, edition, and licensing of the installed Office are not changing, only the product key.

    It should take no more than 3-5 minutes per installation to export the registry key for backup, delete the two entries, close the registry editor, open an Office program, and then enter your new product key.
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    • Marked as answer by Darin Smith MS Friday, February 19, 2010 8:21 PM
    Friday, February 19, 2010 7:42 PM