Try installing the whole package, including Project and Visio.. This is what I got (Office x64 16.0.9208.2010 on Windows 17120 x64 on VMWare WKSTN 14.1.1) ================= OFFICE PRODUCTS KMS ACTIVATION =========================== ____________________________________________________________________________ Use internal OfficeRTool KMS server (1/0)? >1 Adding KMS activation file exclusions to Windows 10 Defender Exclusion List ____________________________________________________________________________ Activating Office 19, Office19ProPlus2019XC2RVL_KMS_ClientC2R edition Activation failed ____________________________________________________________________________ Activating Office 16, Office16VisioProVL_KMS_Client edition Activation failed ____________________________________________________________________________ Activating Office 16, Office16ProjectProVL_KMS_Client edition Activation failed ____________________________________________________________________________ Removing KMS activation file exclusions from Windows 10 Defender Exclusion List
simple07: You are using Windos 10 Insider version. These versions sometimes have problems with the license files. Try recreating the files "tokens.dat" and "cache.dat". Then redo Office Retail2VL conversion and KMS activation. I'm sure it will work. Info's about license file recreation running Win10 you will find here in your own post -> https://forums.mydigitallife.net/th...install-activation.62571/page-61#post-1291243.
Thanks ratzlefatz, I am no longer getting old, I guess I am already old, probably with Altzheimer. I re-installed Windows again (to start with a clean slate), 1- Installed Office Pro Plus 2019 + Project + Visio. 2- converted the installations to VL 3- Activated.. , Started Word, got a message that something is wrong and it needs to fix it. Closed the message and Word. A- Navigated to "C:\Windows\System32\spp\store_test\2.0\tokens.dat" (the path in GA Windows is: "C:\Windows\System32\spp\store\2.0\tokens.dat") B- Renamed "tokens.dat" to "tokens.dat.old", C- Started Word again and closed it to recreate "tokens.dat" (being paranoid, I also started and closed Project and Visio) D- Ran O2016RTool and selected "C" to convert Retail to VL E- Activated using external KMS: "C:\Program Files\Microsoft Office\Office16\cscript ospp.vbs /act" (after setting the KMS IP address) All is working fine now.. About shows, Office 2019, Project 2016 and Visio 2016, but all have the same version number 16.0.9208.2010.
Why do not you install Office C2R VL? I tested: 1. Install Windows 17120 Pro (retail) x64 on VMWare W 14.1.1 2. Install KMS seco (wotok + and 1) 3. Install Windows VLK (if there is no digital license) (wotok / and 2) 4. Download Office 16.0.9208.2010 (wotok 2, id 5440FD1F-7ECB-4221-8110-145EFAA6372F) 5. Install ProPlus2019Volume (wotok 3, 16.0.9208.2010) 6. Install ProjectProVolume (wotok 3, 16.0.9208.2010) 7. Install VisioProVolume (wotok 3, 16.0.9208.2010) 8. Check Windows (wotok 0 and 1) = windows licensed = not problem 9. Check Office (wotok 0 and 3) = proplus2019 and visio and project licensed = not problem 10. Run word, not problem. wotok (new version 2018.03.16.01): https://forums.mydigitallife.net/posts/1414279
I actually tried WOTOK which is fine, but I just like to create my own ISO and activate using a central KMS.
This also happened to me, here is what I have done: 1- I uninstalled Office 2016 using the easy fix tool "o15-ctrremove.diagcab" from Microsoft. 2- Rebooted Windows and reinstalled Office 3- Opened Word, Visio and Project and closed them and performed the Token thingy again 4- Successfully activated I don't know what black magic the tool performs, probably fixes a registry entry or a path, but that helped.
Other than OfficeRTool and WOTOK, I used Ratiborus's "Office 2013-2016 C2R Install" (currently v6.0.3.1) which is a complete Toolkit GUI that gives slightly different file strucutre, but it works fine. Also there is "Office 365 ProPlus installation Toolkit", which is an application that will package an Office 365 ProPlus installation into a single Executable or Windows Installer Package (MSI) file that will download and install the chosen components and version of office I now manually download the needed x86 and x64 files to create one ISO, edit the xml files and write a batch file to install either 64bit or 32 bit Office.
What is better? 1. Installation with ODT (ODT, Office 2013-2016 C2R, OfficeRTool ...) Installation procedure: Office files + ODT (setup.exe + xml) -> run OfficeClickToRun.exe with xml limited settings xml settings only retail (volume? install retail and convert to volume), limited id... 2. Installation without ODT (wotok, simple cmd script...) Installation procedure: Office files -> run OfficeClickToRun.exe with unlimited settings retail or volume (without conversion), unlimited id... 2 is better for me. 1 is better for you. OK
I have no all-time particular preference, it all depends on the availability of the software and the most effecient way of deployment at the time.. I am sure this will continue to change as people bring new innovative ideas that utilise technology as it evolves.
Sorry if this was asked already, but what would be the best way to download/install and kms activate a single product (i.e. Word). As of now, the only way I know is to download ProPlusRetail, and exclude all other apps in the config.xml (the download size seems to be the same regardless of what I exclude). Is there a different/better way (in regards to download/installation size)? Most people that ask me to install office for them only want Word & Excel.. Edit: Can I modify the vlsc iso and remove programs?