Hi @ratzlefatz I just tried the new tool (9th Oct) to change the channel of an Insider (slow build) which was at the latest version. I appeared to successfully change it to Current Retail and indeed the branding (which recently seemed to become generic) has reverted to Microsoft Office Professional Plus. It is however showing "Current Channel" which is what I was expecting, but the build level is 16.0.7167.2060. I think this is two builds behind current as this version was current on 14th Sept? Yet when I try to update again I am told "You're up to date" Any idea what I may have done wrong? Many thanks
confirmed! Microsoft yesterday updated "Current" and "First Release for Current (Insider Slow Ring)" to version 16.0.7369.2038. But update always goes to 16.0.7167.2060. Before, it works. I will check if this is O2016RTools' fault...
Hi I did what you suggested and the update dialog appears momentarily before telling me that I am up to date. Seems to think that 16.0.7167.2060 is the latest build? A supplementary question if I may. Would it be possible (although I appreciate probably not, without some further work to the tool), to be able to change from ProPlus to 365 as well. (Keen to switch a couple of machines to 365 to get the Morph feature in PPT, although i realise I can do a clean uninstall / reinstall) Thanks
The "update" is working/thinking wrong. I will check who's responsible for that. And if it's O2016RTool then a fix will come. There are much too much replacements/changes to do (files and registry). I'm sure, that I won't find all occurencies and as result, this will leave behind a complete mess. So I'm sorry, but O2016RTool can't help you here. Better use FixIt-Tool and do a new, fresh install.
Hi Thanks for getting to the bottom of this in your usual meticulous manner. I confirm your findings that the integrity of the update process seesm to be restored. And the genric branding approach seems also to have returned to the "Product Information" screen under "Account"
I can't figure out which version to download. I just want the latest current branch. No 7369 is available, and 7369.2017 is only listed, see pic. ms-vnext.net hasn't been updated since your last post so I guess 7369.2024 should be there? Edit: Or 7369.2038? Sorry for my noob question! Haven't looked into Office 2016 until now.
There is a huge size difference between Current 16.0.7369.2038 and previous releases, even Insider_16.0.7512.1000 is much smaller!!
I am still sure, that something went deeply wrong with this 16.0.7369.xxxx Current / Retail RTM releases. Simple example regarding the size growing up from 16.0.7369.2025 -> 16.0.7369.2038: stream.x64.x-none.dat = 1.963.012 KB ~ 500 MB bigger than previous version stream.x86.x-none.dat = 1.498.363 KB ~ 330 MB bigger than previous version But even much bigger than latest FAST Insider 16.0.7512.1000 which lists as: stream.x64.x-none.dat = 1.193.314 KB stream.x86.x-none.dat = 1.004.076 KB There is no reason for Current / Retail RTM version to be that big. Compared to all other channel releases there were no extra special features added. The only thing that could explain this growth: MS Developers forgot to remove/disable debugging code. But this is wild guessing. I don't have any proof. Let's wait for the next Current Retail release. I will stay with Insider FAST 16.0.7512.1000 at the moment.
Hi, Few days back I downloaded office 2016 C2R 16.0.7369.2024_en-US_x86_x64_Current using O2016RTool. I saw a new version has came. I want to know is it possible to update the offline installer which was downloaded using O2016RTool without downloading the whole setup for new version. Thanks
Sorry, only loading individual files and preserving the rest is not possible. To get a complete setup package, you must always download all files of the new version.
Anyone experiencing problems running the latest version of O2016RTool? After launching O2016RTool, Windows 10 asks me for permission for the app to make changes. After granting permission, a blue windows is launched. However, it closes almost instantly. Unable to even reach the main menu. Running an older version, like the October 2015 version, works though. Not sure what is the problem? Could it be a Windows 10 issue?
I think the problem was because I ran the file from a sub-sub folder and also renamed the O2016RTool folder differently (e.g. Drive:\abc\O2016RTool(Oct)\O2016Rtool.cmd) Once I extracted the files to the root folder without any folder renaming, it works when i follow your example (e.g. Drive:\O2016RTool\O2016RTool.cmd Thanks for the explanation
I just tested and found that the brackets () [and umlauts äöüß, maybe other special characters, too] are the reason. But { [ and ] } are ok and can be used. At the moment I don't have a workaround for this. @all: till further notice don't use () and/or umlauts in foldernames.