March 15 -> version 16.0.6471.2015 March 17 -> version 16.0.6741.2017 hope, they didn't continue running this loop every 2 days... Update (no, they did not...): March 24 -> version 16.0.6769.2011
I seem to be having trouble getting Office activated... I followed the O2016RTool all the way through, from downloading office 2016 32 bit to activating it. It seems to install just fine (and no other offices are installed), it *seems* to convert to KMS OK, but when I try to use the internal KMS server, it says "Activating Office 16...", then Activation failed. No indication why.
Clueless Absolutely unable to activate. At first I tried with just standalone Word, but am currently trying with ProPlus omitting everything but Word. Same symptoms either way. If I run [C]onvert, it says 16 SKUs found (was 4 with just Word), but Number of Keys uninstalled = 0. It then proceeds with a bunch of '... installed successfully' and GVLK 'Successfully installed XQ...' If I run [K]MS, I get 'No instance(s) available' twice, followed by Activation failed. If I run [C]onvert again (immediately or later), I never get 'All OK. No conversion needed.' Instead, I get the same 'successful' messages as noted above. If I run Microsoft Toolkit-> Activation-> (Tool=AutoKMS) Check, I get <No installed product keys detected> If I run Microsoft Toolkit-> Product Keys-> (Product=Any version, Edition=Any program) Check, I get a Product Key with Validity: Valid. This includes programs that were never installed- like AccessVL. This remains true even after clean uninstalls. If I run KMS_VL_ALL, I'm told that no VL products detected (post-conversion). Ran Uninstalls through CP and FixIt, checking with manual instructions. Ran cleanospp (which does nothing in my case; as above, always 4-16 SKUs with 0 keys uninstalled). Even tried renaming tokens.dat and cache.dat as per forums.mydigitallife.net/threads/62571-HOW-TO-SUPPORT-CHAT-OFFICE-2016-Download-Install-Activation?p=1188384&viewfull=1#post1188384, even though I'm on 10586. (data.dat did not exist) Please note that I first tried this with the September version of O2016Tool-BETA and ofc version 16.0.4229.1024_en-US_x86_x64. Since updated to current tool and 16.0.6741.2021_en-US_x86_x64_CurrentBranch. Note also that all installs were x64.
I would like you to do the following: - open admin elevated command-prompt / rightlick cmd.exe and run as administrator - navigate to O2016RTool/OfficeFixes/win-x32 - run "cleanospp" without! any additional command-line parameters (this will clean product-keys and Office licenses, but invalidates "tokens.dat" file) - stop service "Software Protection" - rename file "tokens.dat" in folder C:\Windows\System32\spp\store(_test)\2.0 to tokens.old - rename file "cache.dat" in folder C:\Windows\System32\spp\store(_test)\2.0\cache to cache.old - start service "Software Protection" - new activation token.dat file will be generated - convert again and redo Office KMS activation - Now it should work - If yes, then delete saved *.old files. If this doesn't work, then I'm afraid you must consider installing your messed up system with Windows fresh from scratch.
Hi. Long-time listener, first-time caller. First of all, thanks, Ratzlefatz for making O2106RTool. Unbelievably useful, this thing is! The most recent version to date (16.0.6568.2036) is refusing to install for reasons that are beyond me. I've tried it on two machines (one ThinkPad Edge E530c which has just been reformatted with Windows 10, and another i7 desktop I built) and am getting this error: This was a common error a while back when I first started using O2106RTool but hasn't reared its head for quite a while until today. No proxies, no old installations or anything else obviously impeding installation. Not sure how to proceed.
Thanks ratzlefatz. Note that I don't have store_test\2.0 as I'm on build 10586. I followed the instructions using the store\2.0 folder. However, the O2016RTool could still not convert the installed vnext image to VL. Incidentally, this is a clean Windows 10 image. Anyway, I was able to download a VL iso directly (november_rain's sticky) and your tool could successfully activate with its KMS. If you want any help debugging the Convert, let me know. Else, I'm happy. Regards.
Just FYI, I also am now getting this exact problem as canufrank.... Bought a brand new Surface Book the other day and did a full reset to defaults. It's a completely fresh install of 10586 Win10 Pro which is then updated with Windows Update to 10586.164. I've run O2016RTool on other PCs in the past, and everything works a treat, but this machine with the fresh install is having trouble. I am installing x64 Office 2016 Current Branch 16.0.6741.2021_en-US_x86_x64_CurrentBranch. I have my own instance of VLMCSD running on a server, which seems to still work for all my other PCs. Even if I use the internal activator, this occurs: Use internal O2016RTool KMS server (1/0)? >1 __________________________________________________________________ No Instance(s) Available. No Instance(s) Available. Activation failed __________________________________________________________________ No Instance(s) Available. No Instance(s) Available. Activation failed __________________________________________________________________ I tried resetting the tokens....and I used the "store" folder instead of "store_test" because it is 10586, but still no success. Also of note, I am trying to also install Visio Professional....and when I "Convert VNEXT and Web Office To Volume", it successfully installs the Office Pro Plus key, but the Visio Pro key fails.... EDIT: If I use the script in the KMS_VL_ALL post Retail2VL64.cmd, then I get the following output __________________________________________________________________ Activating Office 16, Office16ProPlusVL_KMS_Client edition Activation failed __________________________________________________________________ Activating Office 16, Office16VisioProVL_KMS_Client edition Activation failed __________________________________________________________________ I feel that's an improvement...but not really....
A fresh install of Windows 10 Pro Insider build 14265 and Office 2016 Insider 16.0.6769.2015, x86 is already running fine here. But that's not your system setup... I will build a new test environment using Win10Pro 10586.164 and Office 16.0.6741.2021_en-US_x86_x64_CurrentBranch. Give me some time for testing... UPDATE: Test finished. New VMware-Player-Image with Windows Pro 10586.164. Office 2016 Pro, Project and Visio (all "Current Branch") installed and activated using O2016RTool MARCH 09 (internal KMS-VLMCSD). Deleted License Files and Keys using cleanospp.exe and tried conversion and activation again. This second try succeeded, too.
Not sure if it makes any difference....but the Windows 10 Pro install is OEM activated.....since it's a Surface Book EDIT: Now......I did a full uninstall of Office, restarted, redownloaded the whole thing and installed. This time, the internal activator activated Visio Pro 2016 successfully....but OfficeProPlus 2016 Activation Failed.... EDIT2: Still not sure why everything is very inconsistent....but I did the conversion to VL with O2016RTool 2016/MARCH/09. It seems Visio Pro key was successfully installed, but the OfficeProPlus key failed...but, all the licenses were installed, so I went to CMD and did it all manually with ospp.vbs cscript ospp.vbs /sethst:<host> cscript ospp.vbs /setprt:1688 cscript ospp.vbs /actype:2 cscript ospp.vbs /inpkey:<ProPlus 2016 GVLK key> cscript ospp.vbs /act I'm honestly not sure what changed before and after install......or why O2016RTool was failing to activate.....but....it works now....
Hi, How to create an installation usb media with fr_office_professional_plus_2016_x86_x64_dvd_6967915.iso ?? Windows 7 USB/DVD Download Tool works but setup.exe doesn't launch... Maybe Rufus tool ? Sorry for my poor english.
Rufus is a very good tool. How many installations created by Rufus are failed? Btw, If you use Windows 8 or above, you shall directly launch ISO with Windows Explorer which will then launch a virtual DVD ROM allows you to install directly inside OS without a need of third party tool to boot from USB.
Thank you. I am a Win7 user, so I didn't know that Win8 and above could launch iso directly. About Rufus, yes, it should be a good tool, but in my case, I don't need it in fact.