Microsoft Office 2010 activation code Archives

ProduKey v1.93 - Recover lost Windows product key (CD-Key) and Office 2003/2007 product key. Copyright (c) 2005 - 2018 Nir Sofer

Related Links

Description

Download links are on the bottom of this page

Versions History

• Version 1.93
  • Added 'Office Product Name Extraction Mode' option, which controls the way that the product name of MS-Office is extarcted from the Registry:
    'Prefer the product name from Uninstall Registry key' - ProduKey tries to extract the product name from the Uninstall Registry entry, like it did until version 1.85
    'Prefer the product name from Office Registry key' - ProduKey first tries to extract the product name from 'ProductNameNonQualified' and 'ConvertToEdition' Registry values, like it did starting from version 1.86
• Version 1.92
  • Added 'Build Number' column (For Windows entries only).
• Version 1.91
  • When loading product keys from remote computer or external drive, the name of the computer or external path is now displayed in the window title.
• Version 1.90
  • When the 'Temporarily start the remote registry service on the remote computer' option is turned on, ProduKey now starts the Remote Registry service even if it's disabled.
• Version 1.88
  • Added 'Save All Items' option.
• Version 1.87
  • Fixed to display Office version if the product name is not stored in the Registry.
• Version 1.86
  • Fixed bug: ProduKey displayed wrong product name of Microsoft Office taken from another Registry key.
• Version 1.85
  • Added 'Auto Size Columns+Headers' option.
  • Added 'Auto Size Columns On Load' option.
• Version 1.83
  • Added support for SQL Server 2012/2014.
• Version 1.82
  • Added 'Run As Administrator' option (Ctrl+F11), which is needed to get a product key from external drive on Windows Vista and later.
• Version 1.81
  • You can now export the product keys list to JSON file.
• Version 1.80
  • Added option to temporarily start the remote registry service on the remote computer (For reading the product keys from the Registry on the remote computer).
• Version 1.75
  • Added support for some Adobe and Autodesk products.
• Version 1.70
  • Added support for BIOS OEM Key (Windows 8).
• Version 1.67
  • The DefaultProductKey Registry key support added on v1.61 is now turned off by default (You can turn it on with 'Load Default Product Key' option).
• Version 1.66
  • Added /NoErrorMessage command-line option. If you specify it with a save command-line option, an error message won't be displayed if the save action is failed. Instead, the error code will be returned to the caller.
• Version 1.65
  • Added support for Visual Studio.
• Version 1.62
  • Fixed bug from v1.61: ProduKey crashed in some systems.
• Version 1.61
  • ProduKey now tries to extract the key from DefaultProductKey Registry key if the product key cannot be found in the standard location of Windows 7 product key.
• Version 1.60
  • Added support for SQL Server 2008.
• Version 1.56
  • Fixed a bug with the 'N' character location on the product key of Windows 8.
• Version 1.55
  • Fixed ProduKey to decode properly the product key of Windows 8.
• Version 1.54
  • Fixed issue: The properties and 'Select Source' windows opened in the wrong monitor, on multi-monitors system.
• Version 1.53
  • Fixed bug: ProduKey displayed wrong product name string for Exchange Server 2003.
• Version 1.52
  • Decreased the height of the 'Select Source' window to fit the netbook screen size of 1024x600.
• Version 1.51
  • Added 'Show Time In GMT' option.
  • Added 'Mark Odd/Even Rows' option, under the View menu. When it's turned on, the odd and even rows are displayed in different color, to make it easier to read a single line.
• Version 1.50
  • Added 'Show the computer name for every IP address' option. This option is useful when you scan a range of IP addresses, and you want to view the computer name of every IP address. Be aware that the computer names will appear a few seconds after finishing to scan the product keys.
• Version 1.46
  • Added accelerator keys for 'Copy Product ID' (Ctrl+I) and for 'Copy Product Key' (Ctrl+K).
• Version 1.45
  • Added 'Add Header Line To CSV/Tab-Delimited File' option. When this option is turned on, the column names are added as the first line when you export to csv or tab-delimited file.
• Version 1.43
  • When the product key is not stored in the Registry (like in volume licenses of Windows 7), ProduKey will display 'Product key was not found' instead of wrong 'BBBBB-BBBBB-BBBBB-BBBBB-BBBBB' key
• Version 1.42
  • Added 'Copy Product ID' and 'Copy Product Key' options.
• Version 1.41
  • Added /ExtractEdition command-line option.
• Version 1.40
  • Fixed ProduKey to display the right product key of Microsoft Office 2010 Beta (Office 14)
• Version 1.38
  • Added sorting options from command-line.
• Version 1.37
  • Fixed issue with x64 systems - The 32-bit version of ProduKey can now also retrieve the product key when you run it on x64 system.
• Version 1.36
  • Added command-line options to control which types of product keys will be shown. (/WindowsKeys, /OfficeKeys, and others)
• Version 1.35
  • New option: Load the product keys of external Windows installations from all disks currently plugged to your computer. When using this option, ProduKey automatically scan all your hard-drives, find the Windows installation folder in them, and extract all product keys stored in these Windows installations.
  • New Command-Line Option: /external
• Version 1.33
  • Fixed bug: In 'Select Source' dialog-box, a disk drive error message displayed in some computers.
  • Added AutoComplete to Windows directoried combo-box.
• Version 1.32
  • You can now send the information to stdout by specifying an empty filename ("") in the command-line. (For example: produkey.exe /stab "" >> c:\temp\prd.txt)
• Version 1.31
  • Added the last modified time of the ProductID Registry key.
• Version 1.30
  • New option: display the edition (Standard/Professional/Enterprise) of Windows 2000/XP/2003. (doesn't work for remote computers)
  • Added AutoComplete for file selection.
  • Fixed bug: The main window lost the focus when the user switched to another application and then returned back to ProduKey.
• Version 1.26
  • Added support for saving comma-delimited (.csv) files.
  • Added new command-line option: /scomma
• Version 1.25
  • Added new source option: Load the product keys from all computers in the specified IP addresses range.
  • New command-line option: /iprange
  • New option: Check every remote machine with ping before trying to connect. (Only for Windows 2000 or above)
• Version 1.20
  • Added 'Select Source' (F9) option - user interface for loading the product keys from remote computers or from external drive.
• Version 1.15
  • Added 'Service Pack' column (Only for Windows entries)
  • Added 'Installation Folder' column (Only for Windows and Office entries)
• Version 1.10 - Added filters by product type.
• Version 1.08 - The configuration of ProduKey is now saved to a file instead of the Registry.
• Version 1.07
  • Added support for product key of Ms-Office under x64, when it's retrieved from external Registry file.
  • Added x64 build - for locally retrieving product keys of x64 versions of Windows.
• Version 1.06 - Added support for SQL Server 2005.
• Version 1.05
  • Display information in the status bar while scanning computers with /remoteall and /remotefile options
  • New option /remotealldomain - scan all computers in the specified domain.
  • Changes in the way that /remoteall scan all computers.
• Version 1.04 - Added product key of Exchange Server.
• Version 1.03 - new command-line option: /remoteall
• Version 1.02 - On newer versions of Office (XP/2003) - display the real product name, if it's written in the Registry.
• Version 1.01 - Added support for XP visual style.
• Version 1.00 - First release.

Known Problems

• When running produkey.exe, Some Antivirus programs display an alert and/or block you from running it. Click here to read more about false alerts in Antivirus programs
  If your Antivirus software shows a false alert, you can use the following article that explains how to send a report about a false positive issue to your Antivirus company:
  How to Report Malware or False Positives to Multiple Antivirus Vendors
• For some types of license keys under Windows 7/8/2008, the product key is not stored in the Registry, and thus 'Product key was not found' message will be displayed.
• If you bought your computer with installed operating system, you may find the Windows product key appeared in ProduKey utility is different from the product key on your Windows CD. This problem is mostly reported with Dell computers.
• From unknown reason, the product key of Visual Stuido .NET is written in the Registry as Office XP product...
• In old versions of Office (Office 2000 and below), the 'Product Key' value is not available.

Supported Products List

• Microsoft Windows 98/ME
• Microsoft Windows 2000
• Microsoft Windows NT
• Microsoft Windows XP
• Microsoft Windows Vista
• Microsoft Windows Server 2003
• Microsoft Windows 7 (Doesn't work with Microsoft Volume Licensing)
• Microsoft Windows 8 (Doesn't work with Microsoft Volume Licensing)
• Microsoft Windows 10 (Doesn't work with all types of licenses)
• Microsoft Office 2000 (Only ProductID is displayed)
• Microsoft Office 2003
• Microsoft Office 2007
• Microsoft Office 2010
• Microsoft SQL Server 2000
• Microsoft SQL Server 2005
• Microsoft Exchange Server 2000
• Microsoft Exchange Server 2003
• Visual Studio
• Some of the Adobe and Autodesk products.

System Requirements

License

Disclaimer

Using ProduKey

Command-Line Options

You can also combine the above command-line options with the following save options in order to save product key information to file:

Examples:
produkey.exe /remote \\Server01
produkey.exe /remotefile "c:\temp\computers.txt"
produkey.exe /regfile "F:\WINNT\system32\config\software"
produkey.exe /windir "c:\winnt" /shtml "c:\temp\pk.html"
produkey.exe /remoteall
produkey.exe /remotealldomain MyDomain
produkey.exe /iprange 192.168.1.10 192.168.1.50
produkey.exe /stab "" >> c:\temp\prd.txt
produkey.exe /OfficeKeys 0 /WindowsKeys 1 /shtml f:\temp\keys.html

Translating ProduKey to other languages

1. Run ProduKey with /savelangfile parameter:
   ProduKey.exe /savelangfile
   A file named ProduKey_lng.ini will be created in the folder of ProduKey utility.
2. Open the created language file in Notepad or in any other text editor.
3. Translate all string entries to the desired language. Optionally, you can also add your name and/or a link to your Web site. (TranslatorName and TranslatorURL values) If you add this information, it'll be used in the 'About' window.
4. After you finish the translation, Run ProduKey, and all translated strings will be loaded from the language file.
   If you want to run ProduKey without the translation, simply rename the language file, or move it to another folder.

Feedback

ProduKey is also available in other languages. In order to change the language of ProduKey, download the appropriate language zip file, extract the 'produkey_lng.ini', and put it in the same folder that you Installed ProduKey utility.

Michael Pietroforte is the founder and editor in chief of 4sysops. He has more than 35 years of experience in IT management and system administration.

Latest posts by Michael Pietroforte (see all)

Update: If you have to rearm Office 2013 SP1, please read my updated article. Things are quite different with Office 2013.

This article explains how you can rearm Office 2010 and for what you need this feature.

Office 2010 is certainly the best Office suite out there. However, compared to Office 2007 it has one major drawback: Like Vista and Windows 7, Office 2010 has to be activated. However, Office 2010 behaves a little different than Windows if it is not activated. Rearming Office 2010, that is resetting the grace period, works similar as rearming Windows.

Office 2010 Reduced Functionality Mode ^

Retail versions of Office 2010 will only run in Reduced Functionality Mode (RFM) after the grace period of 30 days has been exceeded. In RFM Office, documents can only be viewed but not modified.

Volume editions of Office 2010 don't have an RFM. However, Office will start nagging users with messages after 25 days. You can just imagine how many helpdesk calls it will provoke if you don't ensure that Office 2010 has been activated during this grace period.

Activating Office 2010 ^

You can use the latest version of the Key Management Host (KMS) or activate Office 2010 with VAMT. Either way shouldn't be doable within 25 days after the installation.

However, it might be difficult to activate Office 2010 during the grace period if you deploy a pre-installed Office with an OS image. The grace period begins immediately after you installed Office 2010 on your master PC. If you have to perform other configurations before you create the master image, then it is quite possible that 25 days is too short. You also have to take into account that it might take some time until Office finds a KMS host or until you activate it manually.

This is where Office 2010 rearm comes in. This features allows you reset the grace timer to 30 days grace. If you rearm Office right before you create the OS master image, you can be sure that you have the full 25 days before users will bothered with Office activation notifications or before the retail edition goes into Reduced Functionality Mode after 30 days.

How to rearm Office 2010 ^

You will find some complicated instructions on the Web of how to rearm Office 2010. Most of these articles were written before Office 2010 was released. There are also third party tools that allow you to rearm Office 2010. However, I recommend following Microsoft's instructions. This topic is too sensitive to rely on third party tools.

To rearm Office 2010, you only have to run ospprearm.exe in %installdir%\%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform from an elevated command prompt. "%Program Files%" has to be replaced with %Program Files (x86)% if you installed Office 2010 32-bit on Windows 64-bit.

Rearm Office 2010 - ospprearm.exe

Since you can rearm up to 5 times, you can run Office 2010 for 180 days (30 days + 5 x 30 days) without activating it, if you rearm it every time after the 30 days grace period has been reached.

Another effect of rearming Office 2010 is that the client machine ID (CMID) is reset. The KMS host uses the CMID to identify unique clients. This allows the KMS host to count Office 2010 correctly.

Rearming Office 2010 Trial ^

Office 2010 rearm could also be useful if you installed Office 2010 Trial. The Office 2010 Professional Plus Trial comes with a special activation code that will allow you to test Office 2010 for 60 days. There are reports on the web indicating that you can also rearm the trial version of Office 2010. Office 2010 Trial indeed comes with ospprearm.exe. However I doubt that rearming will work after you used the trial activation code because rearming makes only sense with an Office installation that hasn't been activated.

Office 2010 Activation Wizard

You can run Office 2010 Trial without activating it but every time you launch the Office 2010 Activation Wizard will pop up. If you cancel this dialog, you can continue using the Office application. I suppose this will only work for 30 days. If you have experience with rearming Office 2010 Trial, please let me know.

Poll: Does your organization plan to introduce Artifical Intelligence?

Read 4sysops without ads and for free by becoming a member!