Who have successful install office 16.0.8225.1000/16.0.8226.1000/16.0.8227.1000/16.0.8229.1000(channel-id:EA4A4090-DE26-49D7-93C1-91BFF9E53FC3)? Is it Office Insider Fast Ring?
All these (incl. newest 16.0.8231.1000) are MS-internal use only versions. Not Insider. They are not meant to be used by public! But now, as you let the (channel-id) cat out of the bag, I confirm: You can use O2016RTool to download, install, convert and activate. For instructions look into this post. A little reminder: Be careful, one never knows what's hidden in these "internal use only" builds.
It's written in Download-post, hidden behind the spoiler-tag. I marked it better now to avoid further confusion.
Does anyone aware that my.visualstudio.com, earlier on MSDN subscriptions has started pushing out the new perpetual licensed Office 365 to subscribers as a replacement for Office Pro Plus 2016, Project Pro 2016 and Visio Pro 2016 which has been discontinued? With the latest change, subscribers needs to sign in with their MS Account to redeem the keys from setup.office.com.
It seems that way at the moment. I'm asking MSDN Customer Support to clarify, why the new keys are listed as Office Pro Plus 2016, Project Pro 2016 and Visio Pro 2016 but when I cross-check the keys with VAMT, it's showing Office 365 (Office16_O365HomePremR_PIN32).
This is a substitutive for Office 2016. The same build on Current/Retail branch matches Office 365 current/retail branch. The insider builds are actually accessible through Office 365 service actually. I am wondering about the unification of Office 2016 and Office 365 builds at this time. And possibly VL builds will be labeled as XC2RVL in Project and Visio seems to that point. Activating Office 365 is more difficult than Office 2016 using O2016RTool???
I don't know anything about office insider builds or the O2016RTool. Primarily, what I want to know is why MS is now pushing Office 2016 users towards Office 365 when they have already announced that mainstream support for Office 2016 will end in October 13, 2020 which is 3+ years from now.
Some companies think, that subscription/cloud based services will be THE future money train. So it is logical for MS to retire retail products and push Office (365) for rent. But it's still some time left until 2020. Let us wait what happened until then. In the meantime we enjoy retail Office while it lasts.
@ratzlefatz Just checked and noticed the old links for the branches work again nicely (still use the inside JATD).
Don't worry, I don't expect that Channel-id's / branches will retire too soon. And in case it will happen earlier, we will deal with it.
The push has already started months ago via MSDN subscriptions. 3+ years ahead of their plan to end mainstream support for Office 2016.
Some subscription services is a niche for some persons. I have subscribed to Office 365 Home for one year and liked the service. @ratzlefatz, How is the mean for obtaining Office Insider builds outside being an Office 365 subscriber? The Office Insider program is restricted to Office 365 subscribers, but O2016RTool identifies Office Insider builds.
- A new O2016RTool version was released today (2017/June/04) - Changes: PROGRAM-STARTUP - Improved "New Version available Check" on all official distribution channels: As O2016RTool's "new version"-check now relys on Microsoft's Office content delivery server and I'm not sure whether the information will be always correct, I have implemented a more detailed error detection- / info-routine. (D) DOWNLOAD OFFICE 2016 OFFLINE INSTALL PACKAGE - Improved "New Version available Check": As already known from official channels, "new current version" is now checked and preselected at manual channel-id selection, too. You don't need to know the version number, you always get the newest version from unknown channels. (K) START KMS ACTIVATION - updated KMS solution VLMCSD from hotbird64 to build 1110 (May 31, 2017) (T)] DISABLE ACQUISITION AND SENDING OF TELEMETRY DATA - corrected error in settings for shown "First Things First" window No other changes were made. Download links in OP and checksums were updated.
Hi I picked up this morning... Version 1705 (Build 8201.2075) though the in prog update feature (Current Channel). However when I tried to download this with the latest Tool (4th June) no new version was reported on my machine. The latest current build .txt file also states 16.0.8067.2157 I am confused. Is there a problem or am I misinterpreting the way this should work? Thanks
After testing I'm confused, too. For "Current" channel, latest download version offered by MS is 16.0.8067.2157 (checked today), but internal Office update downloads new build 16.0.8201.2075. Update: This new version can be downloaded If build# 16.0.8201.2075 is manually entered (overriding preselected version 16.0.8067.2157) in download dialogue. But if I were you, I would resist and wait a few days. See my comments below. The "version check" in new O2016RTool downloads the file "V32.CAB" of all known distribution channels from official Microsoft Office content delivery server. Inside "V32.CAB" archive there is a file "VersionDescriptor.xml" and this file normally contains the following information "Available Build" stating the Office version number. O2016RTool relys on this information. So I'm sorry, but I can only deliver what is presented by Microsoft. To me it seems, there is some confusion at MS site's revisioning system affecting update and download. In the past I experienced that a new version was announced by O2016RTool and some hours later it changed back to the prior build. And considering the fact, "Insider Slow" had more recent builds than "Insider Fast" the last days, says it all. I would assume, that "Insider Fast" should have the newest features (build-#s), but apparently this is not MS's logic. Strange enough: "Current", "Insider Fast" and "Insider Slow" all have the same build now. That can't be correct! Oh Microsoft! First delivering an internal Windows 10 developer version as update, now this Office build chaos. What a mess!