Feb 14, 2017 1. Install Office 2016. Start regedit.exe. Go to HKLM Software Wow6432Node. Create a new registry key. Right click on the new key and select Permissions. We receive the following Windows Security error: The permissions on [Name of Registry Key] are incorrectly ordered, which may cause some entries to be ineffective. Mar 07, 2013 Solved Hardware key location Forum Solved I have the Lenovo ideapad 110 and the LOCATION of the shift key is in the incorrect place. It is one key to the right, so whe Forum. Apr 11, 2016 When installing a 32bit version of office on a x64 version of Windows server, which registry key will contain the bitness variable? The thing is that when i installed office 2013 x86 and office 2010 x86 on x64 Windows Server 2008 R2, i found the bitness variable under HKLM Software Windows Office 14.0 Outlook. I am just looking for key: DigitalProductID of my Office 2016 in registry. – Defus Oct 26 '16 at 17:36 The location is in the identical location, except Office 2013 is 'Office 15: and Office 2016 would be Office 16 if I am not mistaken. Microsoft Office 2016 Pro Product Key. Microsoft Office 2016 product key is the best effective and beneficial tool which will provide you also work with office 2016. It helps the professionals to make presentations, powerpoint, Outlook, OneNote, creates excel, sheets. Office 2010 and Office 2013 offer a scripted method to lookup your Product Key. Changing Product Key for Office XP/2002, Office 2003 or Office 2007 Changing the Product Key for Office 2007 or previous requires you to go into the Registry.
Learning has never been so easy!
Sometimes after uninstalling older versions of Microsoft Office some registry keys are left behind. This causes Spiceworks to think that those older versions of Office are still installed, even though the actual program files are all removed. You can follow the steps here to clean up those old registry keys so Spiceworks can get a proper inventory of the software on the machine.
NOTE: Please make a backup of Registry before making any changes to it. You can severely damage a machine if an incorrect edit is made.
4 Steps total
Step 1: Open up RegEdit
Open up RegEdit by going to Start>Run and typing 'regedit' and pressing Enter or OK. You can also enter the 'regedit' command into a Command Prompt to open up the editor.
Step 2: Locate the Office Registry Key
Microsoft stores all of the installation information for Office Products in HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice. Underneath this key you will see various version numbers, each corresponding to different versions of Office. They are as follows:
-9.0 is Office 2000
-10.0 is Office XP
-11.0 is Office 2003
-12.0 is Office 2007
-14.0 is Office 2010
-10.0 is Office XP
-11.0 is Office 2003
-12.0 is Office 2007
-14.0 is Office 2010
Step 3: Locate the Corresponding Registration Key
Underneath each of the version number keys you should see a 'Registration' key. Depending on how many Office products you have installed (Visio, Project, etc. all will be stored underneath one of those version keys) on the machine there will be multiple hashed keys present underneath the Registration key. Each of these hashed keys should have a value underneath it called 'ProductName'. You can use this value to correctly determine which hashed key is related to the product you want to remove.
Step 4: Delete the Hashed Key
Location Of Office 2016 Serial Key In Registry Search
Once you have located the correct hashed registry key, delete it. As mentioned above, though, make sure you have a good backup before doing this!
Once you have performed the steps above run a scan on the device by either running a full network scan or a rescan underneath the Tools section of the device. Once the scan is complete you should see that the long deleted Office products are now gone from your Spiceworks Inventory. If the scan is still showing that the software is present, you might need to disable Incremental Scanning in Settings>Network Scan.
I hope this helps!
Published: Nov 15, 2011 · Last Updated: Jul 11, 2012
21 Comments
- CayenneMarciab Nov 15, 2011 at 04:50pmGreat How to.... Thanks for sharing
- Ghost ChiliKellanved Nov 15, 2011 at 04:55pmThank you so much! Finally someone narrowed down which keys to delete! I could only recommend a general registry cleaner to others having this issue.
- Ghost ChiliJustRob Nov 15, 2011 at 06:02pmNice. Good to know exactly what to look for, when even the M$ 'fix it' doesn't get it all.
- DatilBrian Steingraber Nov 15, 2011 at 11:45pmOffice 2010 is really bad about removing these keys so this is a all too common task for me!
- HabaneroJohn6020 Nov 16, 2011 at 06:14amBrilliant - thanks for the information.
- Serranotech_freak Dec 15, 2011 at 02:03pmGood One.
- Serranopnadon Jan 24, 2012 at 05:06pmThank you!!
- Macehsc5775 Apr 20, 2012 at 04:03amgreat work
thx for share - SerranoCraig Manske Apr 24, 2012 at 07:54amOn a 64bit machine it is under HKLMSOFTWAREWow6432NodeMicrosoftOffice.
- DatilPaolo0111 May 17, 2012 at 05:26amThank you very much, James B!
- Datilspike7 Aug 27, 2012 at 10:49pmNice.. thank you!
- MaceGabrielle.L Sep 20, 2012 at 01:31pmThank you for this! I've started doing Office upgrades on our workstation, and it was driving me crazy that my Spiceworks inventory showed multiple versions installed on a machine when there clearly was not.
- JalapenoDvir IT Nov 4, 2012 at 03:56pmIt didn't do it for me a first. Until now...
Solved!1. Disable Incremental Scanning in Settings>Network Scan. – Super Important!!!
2. Use Microsoft fixit http://go.microsoft.com/?linkid=9669698
3. Scan Device.
Thanx a lot!
Dvir - Pure CapsaicinJustin.Davison Nov 14, 2012 at 05:04pmNice one, just saw this and it is a good guide for a common issue people have.
- DatilAngus S-F Feb 28, 2013 at 04:38pmNirsoft has a free tool to retrieve the Office keys from your domain: Produkey. It has a command-line option to '...enumerate all computers in the specified domain, and load the product key information from them.'Get it here:
ProduKey - Recover lost product key (CD-Key) of Windows/MS-Office/SQL Server
http://www.nirsoft.net/utils/product_cd_key_viewer.html
- prev
- 1
- 2
- next