This entry in registry is set by using CHANGE OFFICE UPDATE-PATH (SWITCH DISTRIBUTION CHANNEL). @Simple07: O2016RTool's Retail2VL-conversion only installs the needed license files, the product key and adjusted branding if Office 365 ProPlus was installed. At the moment it doesn't default to any "branch" because it relys on the assumption, that Office setup.exe will handle all the needed configuration parameters. Now it seems, setup.exe needs some help. Was a "Current Retail/RTM" Office version installed on this system, before you tried "Insider Fast" and you didn't remove it completely with FixTool? This would explain the "downgrade" because the modification "UpdateBranch"="Current" is part or responsibilty of Group Policy Editor and therefore the registry entry is not changed by Office setup. Thats the culprit by "manually" modifying configuration. I will change O2016RTool to always set/correct this entry during install- or Retail2VL-conversion- step and overwrite a (maybe) existing one from a prior installed version.
I was actually investigating a freeze/lockup in VMware Workstation 12.5.1. So, the Windows 14955 is a fresh clean installation as well as the office 2016 Pro Plus, only MS Paint 3D is installed. I used Ratiborus's tool to save time, as it downloads (x86 or x64) only, but I used O2016RTool to convert from Retail to Volume and I used a remote KMS to activate so that I can perform an update and I was expecting to receive a message that all is up to date. Now I am aware that I downloaded the latest release, but I noticed 16.0.7369.2038 tries to update One Drive immediately after installation..
I downloaded and created the ISO, then I installed manually having mounted the ISO. I am aware of changing the channel through both the Registry and the Group Policy settings, I am posting this as it may help someone.
I have been using Office Insider for a bit now. One thing I noticed is that if I download a new Office build using a tool, and upgrade from it, then for some reason my Office will roll back to the previous install, but if I upgrade using the Upgrade Now button in the Account section the upgrade sticks.
Thanks dhjohns, what I was suggesting is along these lines. However, if there is a conflict between information in the registry and the the group policy, the registry will be acted upon until such time when the information in the GP is committed and registry info will be over written to reflect what's in the GP. I know that we have addressed this somewhere, but it is for the benefit of other readers.
Hmm, RTool doesn't seem to work for me. I had the Cygiso version, I guess it's the untouched ISO Image of 2016 ProPlus de-DE installed. Tried to activate it with RTool but it fails. What can I do? ALso just tried to use RTool to download office .... also fails. Any ideas?
Besides, that I don't know what a "Cygiso version" means, I have no ideas. That's because you didn't provide any info about your system environment, what steps you already tried, what data input you made and what results you got. For example: If O2016RTool fails at download, then you should tell us the error-message. I know, O2016RTool shows a message in red if there are problems during download. Conclusion: The more infos you give, the better we can help you.
Does 02016rtool install any files/registry entries and how do I uninstall it? Also is there any real difference between all these kms activators that would make one preferable to the others?
Alright, RTool worked just fine for me now on a second test. Downloaded de-DE version, installed it and it activated ok. One question though, is there any way to set the install path, where the actual office files are installed? It seems to default to C:\Program Files\... But I'd like to install the package on my d: drive. I can't choose a path, Installation, Setup doesn't let me choose where it installs to. Any ideas? thanks polford
There are a couple of issues with update process.. Having installed 7369.2038, I attempted to convert the license Retail to VL, using Ratuborus's tool, then I removed Office and reinstalled and attempted to convert from Retail to VL using O2016RTool.. Whenever I start Office application, I get need to repair and it asks for license (meaning the Retail to VL conversion failed). Neither tool was able to successfully convert, in spite of reinstalling Office using Microsoft's cleaning tool. I had to reinstall Windows and used O2016RTool again for a successful conversion.. Also, When starting any Office application (Word for example) and choosing File -> Account -> Office Updates -> Update now.. I get the message "You are up to date"!! I know that Office 7369.2055 is already available, why is Office not picking it?? I changed the channel (manually) to First Release Current and performed update from the application, it updated to 16.0.7466.2038. Then set it back to Current and it updated through the application, It performed an update to 16.0.7369.2038!!! If I click on update, I get "You are up to date".. I have downloaded and installed 7369.2055, converted it to VL and activated it, it kept the version, and when I click on update it responds as expected; "You are up to date"..
@ratzlefatz, you are right.. Installed a fresh copy of Windows 10 14965, then Office 16.0.7369.2055. I ran O16-C2R-Retail2Volume+ to convert to VL -- Office gave me a message that it needs to be repaired -- Clicked on repair, it then requested to enter a license -- Started O2016RTool and applied "Convert to VL", still the same error "corrupt needing repair" -- Clicked on repair, it requested a license. For the benefit of other readers: Closed Office and navigated to "C:\Windows\System32\spp\store_test\2.0\tokens.dat" (..\store\2.0\ in GA Windows) and renamed "tokens.dat" to "tokens.dat.old" -- Started Office again to recreate "tokens.dat" -- Ran O2016RTool and selected "U" to convert Retail to VL -- activated using "cscript ospp.vbs /act"; went fine without errors. By the way, I reinstalled 16.0.7369.2038 again and it is updating.. Probably I was attempting to update soon after the release of 16.0.7369.2055 and before servers have been fully propagated!.
I'm not sure if things have changed but is there a reason why when I try to update Office 2016 I get an error that Something went wrong and it tells me to check my network connection and try again.