I've written my own application to get and display the Windows and Office cd keys. It should also display the keys of the individually installed Office applications. I've tested it on my systems and it appears to be working fine, but I only have XP systems with Office 2003, That's were the MSFN community comes in, try it on your systems and let me know what works and what doesn't.



Post here with info for working/not working, and I'll add working apps and try and fix non working.

If you have found one not working, other than Office 2000, please post the registry path to the DigitalProductID key in the registry. Not the value of the key (which contains the CD-Key), just the path to it. For example the registry path for office 2003 is: HKLM\Microsoft\Office\11.0\Registration\{90110409-6000-11D3-8CFE-0150048383C9}\DigitalProductID
The 90110409 maybe different in yours depending upon language version and SP version during install.

For those who are curious, reverse base24 decode bytes 52 to 66 of the DigitalProductID gives yout your cd-key (not true for Office 2000).

Thanks to:
Stealth111 for testing and pushing for new features.

UPDATES:
10/25/2006 - v2.28 enterprise
- Removed white space from end of computername (no really I did this time)
10/24/2006 - v2.27 enterprise
- Removed white space from end of computername
- Fixed computername output problem 2 (really I did this time )
10/23/2006 - v2.23 enterprise
- Fixed compuername output problem

10/23/2006 - v2.2 enterprise
- Renamed to KeyDecoder Enterprise
- recursive search of entire local registry for DigitalProductID's
- changed format of saved data, computer name now on same line as other related data for easier reading
- reformatted help information

10/16/2006 - v1.9.9
- Almost too many updates to list.
- Added 6 ways to decode keys from machines other than the machine being run on.
- remote registry sinlge machine or machines pulled from list.
- pull machines from AD
- Pull from exported registry file
- Pull from loaded hive from offline machine
- Decode directly entered hex data

08/08/05
- fixed issue were it would break of after finding first office product per version and then ignore the rest.

08/06/05
- fixed issue with it not finding ProductName field for Office XP.

08/04/05
-Added Save function, save files as Comma Delimited
-Command Line Switches added [/iGAL] [Filename]
[/iGAL] (optional pick G,A, or L or any combination, default /iGAL)
G - GUID
A - Application Name
L - License Number
[Filename]
optional if not given and /i switch is used default.csv is used. File is saved
to the current directory if no path is given. If Filename is given and /i is
not /i defaults to /iGAL.

Original version with only the options to get local machine information.
 KeyDecoder.exe ( 40K ) Number of downloads: 2719

Keydecoder Enterprise v2.27 - local and remote machine data collection
 KeyDecoder2.28e.exe ( 116K ) Number of downloads: 834


This post has been edited by IcemanND: Oct 25 2006, 01:48 PM

Work On My XP Pick Up the Key for both XP And Office.
I will try it later on my Vista install.

BUMP

So this has either worked for everyone or no one needs this type of application anymore.

Windows XP Pro confirmed as working.

Works for XP 64, and Office 2K3

Worked On Vista and it read the key for Office on Vista
Nice Little App.

may this site help ? WPA

Windows 2003 Server Web Edition VLK: it works

Windows 2K3 Ent: Worked So Well!
Don't know why my Office 2K3 keys not displayed.

Check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Registration

and tell me what the GUID's listed there are and I'll update the app.

Works perfectly for XP pro VLK, OEM, XP Home, and Office 2K3 Pro.

This post has been edited by warrior1109: Sep 4 2005, 03:05 PM

Nice app, any chance you could add the facility to export to a text file or copy to clipboard?? I'm a Systems Engineer and this would be so handy for my everyday work.

@Gobby - Actually I thought the same thing earlier this evening, will add it and update main post sometime tomorrow. I was thinking about exporting a CSV file with the GUID, Application Name, CD-Key. Or possibly the option of which you want to export. Any preferences to a button in the app or a commandline switch?


@ALL - Does anyone have Visual Studio .NET? Does it work? If not can you get me the registry path to the GUID which contians the DigitalProductID and ProductName keys and I'll add it also if it doesn't already work.

- Updated with command line switches and save function, see first post.

Confirmed working on WinXP Pro Corporate SP2.

w2k , it got windows' key , but not office's key (office 2000)

Yep, here on win2k got Windows key but not MS project 2002 one.(I haven't the full Office installed, I use OpenOffice.Org)

Belarc advisor:
http://www.belarc.com/
and
Magical Jelly bean keyfinder:
http://www.magicaljellybean.com/
http://www.magicaljellybean.com/keyfinder.shtml
can both find it.

@IcemanND
Don't want to spoil the fun, but the latter works very well, it can print and save the info, though your code is much more compact, is it useful to have a YAAIATAEO (Yet Another App Identical To An Existing One)?

jaclaz

@ Jaclaz & saprouzy - if you get me the registry path to the DigitalProductID for Office 2000 and Project 2002, I'll edit there locations in the app.

@ jaclaz - I wrote my own because of the challenge for one. And when I looked at what keyfinder was doing it reads about 1200 registry keys to get what little information it does. The only keys you need to read are the DigitalProductID keys for the microsoft applications. Also Belarc is the only one I've seen that gets all of the license keys. You have to find the beta of keyfinder to get the office keys. And Belarc gets far more information than I'm interested in.


@ ALL - If you find an application it does not work for please post the registry path to the DigitalProductID of the application, do not post the DigitialProductID itself just the path to it.