Hi. Can someone help me? I want to install office 2016 64 bit version instead off 32 bit version. Thanks.
Remove 32bit Office by using FixIt-Tool from post#4. Don't use standard uninstall from Control Panel / Programs and Features because it can be, that fragments remain which interfere a new install. Be sure to reboot after using FixIt-Tool. Then you can download, install, convert and activate Office 64bit using O2016RTool.
Does everyone else, following this install procedure, have the OfficeClickToRun service running at high memory use? I was looking around to see if it was safe/possible to disable the service at boot. Anyone follow up on this?
I have found this with other MSO products, not just VL. Service seems to run for short period with high resource usage. But it settles down within a few minutes or less. Disabling it, in my experience prevents any Office program from starting.
I do hope you can help me. I am having a problem converting a recently installed version of Office 2016 downloaded using the 02016RTool. The Office Retail version 16.0.8229.2073_en-US_x64_Current installed without errors but when I rebooted and ran the (C) Option to Convert retail to VL, I received this message "Supported Office 2016 product not found". This is on a clean installation of Windows 10 which I created using Microsoft's 'MediaCreationTool'. I have assumed that by using this tool that I performed a clean installation of Windows 10. Any suggestions will be gratefully received.
For some not yet known reasons, O2016RTool failed to detect your Office installation. Normally this should not happen. Especially not on a fresh new Windows 10 installation. I assume you built it from scratch and did not use a Recovery-DVD which mostly have a interfering Office 30day trial preinstallation. If you used Recovery then it may be wise to uninstall any containing Office by using FixIt-Tool from post#4. In case you did a clean Windows install, then please specify your Windows 10 version (Home, Professional, Enterprise) and language. Run program "winver.exe" and provide output. I will build a test scenario with the same configuration as yours to get a clue. And I'm interested at the the following info: - open elevated Command Prompt (rightclick, run as admin) - enter the following commands: cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus and reg query "HKLM\Software\Microsoft\Office\ClickToRun\Configuration" /v "ProductReleaseIds - provide complete output of the commands
Thanks for replying so promptly. Please find attached the output as requested. Windows 10 Pro was installed via a DVD created via Microsoft MediaCreationTool to create the media which was performed on a Windows 10 installation with Office 2010 installed. I understood that using the MediaCreationTool a clean install wouldbe performed and therefore I didn't need to remove Office 2010. However, I did notice that I have a Folder that I didn't expect - "Program Files\Microsoft Office 15\ClientX64" with two exe's, namely, IntegratedOffice.exe and OfficeClickToRun.exe. Based on what you have written above .....would it be appropriate to recover the Backup I took of the initial installation of windows 10 and run both the fix it tools 2010 and 2016 (run twice for each and rebooting in between) prior to creating another DVD and installing Windows 10 again. Once complete I could provide and update. I wait for your guidance on this one. Cheers
If you used a DVD - and not having MediaCreationTool update an already installed system - and the new target harddisk is empty ( = no Office installed on it) this indeed should result in a clean Windows 10 Pro install and O2016RTool should work. "Office 15" --> Office 2013 - Did you test Office 2013 ? I'm a big fan of a good grounded basement. My test environments are clean setups on empty harddisk from official Win10-ISO's (MediaCreationTool ISO's are ok!). During my Office tests I always use FixIt-Tool to remove Office. From own experiences I can tell you, this is the best way to go. I would suggest, you follow me on this track. Regarding the output you provided from Registry: I have seen, that first Project was installed, then Office Professional Plus and afterwards Visio. I've never done it this way. I will do the same and check what will happen. Further info in ospp.vbs /dstatus output about Project and Visio is missing. The partially listed key "BTDRB" for ProPlus shows that the ProPlus-RETAIL-/Trial-key (and not the needed KMS-Volume-key) was active. I think, it's really urgent time for the FixIt-Tool to cleanup this mess. Update after finishing my own tests: Removed Office from my test-system with FixIt-Tool. (D)ownloaded 16.0.8229.2073_en-US_x64_Current with O2016RTool. Used O2016RTool to (I)nstall ProjectPro first, then Office ProPlus and VisioPro as last. I did not start any Office App. Registry query output is the same as yours. But ospp.vbs /dstatus output shows nothing. That's correct because at this time I have not used (C) to convert and insert the KMS-Keys. Still I didn't start any Office App. Pressing (C) detects and shows ProPlus, Project and Visio as FOUND. Retail2VL-Conversion and KMS-key insertion went successfully through. Checking activation status (A) says 30days OOBE grace. Then started (K)MS activation. This works, too. Checking activation status (A) says 180days LICENSED. Now I started Project, ProPlus and Visio. All 3 were working. My ospp.vbs /dstatus output: Code: C:\Windows\system32>cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /dstatus Microsoft (R) Windows Script Host, Version 5.812 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. ---Processing-------------------------- --------------------------------------- PRODUCT ID: 00338-00000-00000-AA314 SKU ID: 4f414197-0fc2-4c01-b68a-86cbb9ac254c LICENSE NAME: Office 16, Office16ProjectProVL_KMS_Client edition LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel BETA EXPIRATION: 01.01.1601 LICENSE STATUS: ---LICENSED--- REMAINING GRACE: 180 days (259200 minute(s) before expiring) Last 5 characters of installed product key: G83KT Activation Type Configuration: ALL DNS auto-discovery: KMS name not available Activation Interval: 120 minutes Renewal Interval: 10080 minutes KMS host caching: Disabled --------------------------------------- PRODUCT ID: 00341-50000-00000-AA771 SKU ID: 6bf301c1-b94a-43e9-ba31-d494598c47fb LICENSE NAME: Office 16, Office16VisioProVL_KMS_Client edition LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel BETA EXPIRATION: 01.01.1601 LICENSE STATUS: ---LICENSED--- REMAINING GRACE: 180 days (259200 minute(s) before expiring) Last 5 characters of installed product key: RJRJK Activation Type Configuration: ALL DNS auto-discovery: KMS name not available Activation Interval: 120 minutes Renewal Interval: 10080 minutes KMS host caching: Disabled --------------------------------------- PRODUCT ID: 00339-10000-00000-AA290 SKU ID: d450596f-894d-49e0-966a-fd39ed4c4c64 LICENSE NAME: Office 16, Office16ProPlusVL_KMS_Client edition LICENSE DESCRIPTION: Office 16, VOLUME_KMSCLIENT channel BETA EXPIRATION: 01.01.1601 LICENSE STATUS: ---LICENSED--- REMAINING GRACE: 180 days (259200 minute(s) before expiring) Last 5 characters of installed product key: WFG99 Activation Type Configuration: ALL DNS auto-discovery: KMS name not available Activation Interval: 120 minutes Renewal Interval: 10080 minutes KMS host caching: Disabled --------------------------------------- --------------------------------------- ---Exiting----------------------------- This truly looks as if something is broken on your side. Please use an empty harddisk as target or use FixIt-Tool to remove and cleanup existing Office fragments.
I really appreciate all your time and effort investigating my query. I will follow your advice and get back to you.
UPDATE. Weird or what... 1. I reinstalled windows from the DVD on a newly formatted hard disk. 2 Ran the FixIt Tool just to be sure there were no traces of Office (twice, rebooting in between each) . 4 No traces of Office were reported. Rebooted. 5 Ran o2016RTool and installed Word, Excel and Outlook from a previously downloaded file 16.0.8229.2073_en-US_x64_Current located on another hard drive. 6. Once installation was complete and without opening an office app, or rebooting, I ran the Registry queries. See output attached. 7. Ran option (C) the conversion : Supported Office 2016 product no found? I also noted that an Office 15 folder was created (described previously) during the installation. I am absolutely sure of this because I triple checked its existence beforehand. I have also performed an Acronis restore of the system and can confirm this directory did not exist prior to installation. Next steps: Disconnect all other hard drives. Run a new download, try another installation and report back. Thanks
Disconnected all other hard drives. Ran a new download of Office, tried another partial installation (Word, Excel, Outlook). Same results as before!
My PowerShell output is the same as yours, see attached file. Retail2VL successfully converted. However KMS_VL_ALL, Ver. 6.9. beta(3), reported that activation has failed. Microsoft Toolkit 2.6.2 also reported activation failure after installing AutoKMS Hell I appreciate all your help to date. I too am interested to dig around as to why the 02016RTool does not seem to be working in this instance. However, getting Office 2016 to activate on Windows 10 is not a huge priority for me at the moment as my main system is still Windows 7 based. With your guidance, I would be happy to provide input to help resolve this but please bare in mind that my responses may be spasmodic for the following reasons: 1. Live coverage of the Tour de France on tele. 2. Wimbeldon fortnight: Nadal vs Muller yesterday was truly amazing 3. I'm bass fishing on the Jurassic coast here in the U.K. most mornings at dawn. Life is busy but in a very pleasant way. I'm no expert but it would appear that 'a clean image' created by Microsoft's MediaCreationTool also includes historical references of office installations.
I have already installed and activated Office 2016 Proplus, project pro and visio pro using MTK. If I upgrade from Windows 7 to Windows 10, will that break the autoKMS activation?