What I did: - Use O2016RTool to install Office 16.0.6366.2062; - Don't convert to Volume, delete token file in C:\Windows\System32\spp\store_test\2.0 (shutdown service Software Protection first); - Convert to Volume version; - Activate with KMS; - Re-activate Windows (using commands: slmgr /upk; slmgr /ipk ...; slmgr /atp ...)
It is definitely "cleanospp.exe" from MS-Office 2016 FixIt-Tool which changes an existing "tokens.dat" in a way, that KMS activation on Win10 versions >= 10586 fails. For sure it worked with former Win10 versions, so something in Windows has changed here. "cleanospp.exe" is dated year 2014 and there exists no newer version. I modified O2016RTool in my internal test just to bypass/not run "cleanospp.exe" and guess what happened? KMS activation succeeded! To help yourself, you can modify O2016RTool lines 855 / 859. Place "::" at the beginning to deactivate. Code: ::=============================================================================================================== echo: echo Cleanup - Removing Current Office 2016 - Licenses echo: :: "%o2016rtoolpath%\OfficeFixes\%winx%\cleanospp.exe" -PKey echo __________________________________________________________________ echo: echo: :: "%o2016rtoolpath%\OfficeFixes\%winx%\cleanospp.exe" -Licenses ::=============================================================================================================== "cleanospp.exe" is used for removing all the retail-/trial-product-keys and -licenses during Retail2VL conversion. It doesn't harm if all the retail traces remain in the system. So a quick - but not so elegant - solution will be to simply skip the cleanup and remove only any existing retail-/trial-/grace-keys. But I don't like this idea. I will try to find a solution to get cleanup working again.
--2016-02-03 22:24:25-- (try:87028) h t t p : / / officecdn.microsoft.com/pr/492350f6-3a01-4f97-b9c0-c7c6ddf67d60/Office/Data/16.0.6366.2062/stream.x86. x-none.dat.cobra Connecting to officecdn.microsoft.com (officecdn.microsoft.com)|212.205.126.17|:80... failed: Bad file descriptor. Connecting to officecdn.microsoft.com (officecdn.microsoft.com)|212.205.126.9|:80... failed: Bad file descriptor. Retrying. Is it a bug?? (or a future..)
Is there a way to specify different installation location in a "install package"? "C:\program files" is not always desirable.
I haven't changed any of the default hosts. But after an hour with the same (212.*) hosts worked normal.
With 2016,things just arent as simple as they used to be? Download the VL ISO or EXE then run the KMS activator and updates will be included with Windows Update?
The updates will be installed automatically while you are not using an Office application, and the installation process isn't really hard if you read the guide on this thread.
It was in the signature up until 3 or 4 days ago i had to make a room for more recent stuff i'll add it to KMS_VL_ALL post
Hello. It downloads well but when trying to install I get the error Error Code 30029-1 How can I solve it?
