Seems like the problem of installing O2019 preview is whitin the OfficeRTool since all the download tasks are fine, only the installation option is the problem, when you go through it and press 5: Code: (D) DOWNLOAD OFFICE OFFLINE INSTALL PACKAGE Set Channel-ID > 2=Insider_Channel (Office Insider Fast Ring) Start download now (1/0)? > 1 (I) INSTALL OFFICE SUITES OR SINGLE APPS Enter package number # > 1) 16.0.9026.2006_es-ES_x86_Insider_Channel Select Office Suite for install> 5) Office 2019 It return: Code: -Not available. Insider(FAST) distribution channel setup package required. No matter what channel you are using, InsiderFast or DogFood, neither build version or language (at least it doesn't install with the 32bit version). AFAIK is the internal name of the channel you are using for install office (f3260cf1-a92c-4c75-b02e-d64c0a86a968), is an "internal M$ use only". I think the best and easy way for install O2019 is through the Office 2016 Deployment Tool (setup.exe) and from the Insider fast channel with the Install mode like someone write before: Code: setup.exe /configure <XMLfile> XMLfile (x.xml) Code: <Configuration> <Add OfficeClientEdition="32"> <Product ID="ProPlus2019Retail"> <Language ID="en-us" /> <ExcludeApp ID="Access" /> <ExcludeApp ID="Excel" /> <ExcludeApp ID="Groove" /> <ExcludeApp ID="Lync" /> <ExcludeApp ID="OneDrive" /> <ExcludeApp ID="OneNote" /> <ExcludeApp ID="Outlook" /> <ExcludeApp ID="PowerPoint" /> <ExcludeApp ID="Publisher" /> <ExcludeApp ID="Word" /> </Product> </Add> </Configuration> You can delete the 'Exclude Apps IDs' that you want to install, and this install the current Insider Fast Build.
Right now I'm in "Insiders:: DevMain 16.0.9026.2006", Do you recomend switch to Perpetual2019? I am looking for a stable channel in the limits of the development's edge.
I don't use C2R stable channel would be current or broad perpetual2019 should get more developments soon, for now it's merely a branding/licensing
I tried to install on a fairly often updated channel Dogfood_O16ProPlus-O15Visio_DevMain EA4A4090-DE26-49D7-93C1-91BFF9E53FC3 license 2019. The license is installed, but there was a crash when trying to update. I do not know if this is due to the use of 2 licenses in 2019 (one was activated) and 5 licenses in 2016 at the office. But, I think that while you should use the license 2019 only on LTSC2019 f2e724c1-748f-4b47-8fb8-8e0d210e9208. --- Currently installed the latest version of 2016 office 1803 (build 9031.2004).
Hello, It seems that with latest Office version (ie 16.0.9001.2138 and later), convert retail to VL tool from january 22 OfficeRTool doesn't work anymore (it's not possible to activate Office). Tested with Monthly Channel Edition. But curiously, using previous O2016RTool from january 6, all is OK. Since licences are the same in the 2 tools versions, the only difference is the setup installer.
I am on Version 1802 (Build 9026.2006) but I cant update to Version 1802 (Build 9031.2004). I am getting error: 30088-28. Anyone same issue ?
winter2, if use OfficeRTool for change channel, then try delete in regedit HKLM\Software\Policies\Microsoft\Office\16.0\Common\OfficeUpdate UpdateBranch
I hope someone can help me with this. I installed a copy of Office 2016 from about a year ago from this forum using the OfficeRTool from here. I had trouble then uninstalling the previous copy of Office and putting in a new copy. I finally ended up formatting my hard drive and installing Windows all over again just get Office to install. Now a year later I had not tried to upgrade to any recent builds which might have something to do with what went wrong. My copy of Office was crashing and not responding and I could no longer get updates for the software I suspect due to the fact that I was using a year old version of the software. I tried to uninstall the older version and reinstall a new one using the latest OfficeRTool and no matter how hard I tried and even when I used the Microsoft uninstall tool from the Microsoft support website to uninstall my old copy of Office, I made sure there was nothing left of the old copy anywhere yet when the installation was almost complete, I would get an error message that the computer needed to be restarted and I had the error code: 30175-11 (5). I have just got done reformatting my hard drive and reinstalling Windows but before I try to put Office 2016 on here again, I was wondering if anyone can tell me why I got this error even though I'm 100% sure there was nothing left of my previous copy of Office before I tried installing the latest version and how can I maybe avoid this from happening again in the future? Anyone have any advice before I try to install Office again or can offer any help here? Thank you for any help in advance!
I have tested with latest (Jan 22nd) as you describe and not found a problem. What OS are you running?
Not exactly, they are simply obsolete and not relevant. I did not become a special person to comb the script, because I wanted to sleep, and the idea with the date check failed. If there is a desire, you can try again to parse the file with info, or try to time the files in the archive to assign the date of the version. --- In the final file there is no superfluous data?
I'm on 365 ProPlus-Insider Channel and also had some problems. First it wouldn't update to latest version, Error 30088-28. Decided to do a clean install (uninstalled via o15-ctrremove first). Everything seemed to be going well, but activation failed (without an error message in OfficeRTool!), status was "unlicensed". Uninstalled again via tool and on second try "Activation failed" came up in KMS. Doing more clean installs with WinDefender disabled and using older Office-versions didn't help. Activation status was always "unlicensed", never "grace period". What finally solved the problem was rebuilding tokens.dat & cache.dat, see here: [HOW-TO/SUPPORT/CHAT] OFFICE C2R Download/Install/Activation Before above troubles with Office started, system was updated to latest build on Win10 Insider Fast-Ring (17093), which I think could be another potential source. Something seems to have changed / got messed up in tokens at some point, that's for sure. Edit: All with OfficeRTool 22nd Jan.