Rather strange. I just removed my test-environment and re-installed Office 2016 ProPlus, x86 on Windows 10 Pro, x64 using latest OfficeRTool 2018/January/14 without any issues. Conversion, KMS-activation and all checks work ok. Did you succeed on the other PC? Anyone else out there having similar problems?
Hi, I have a question about the SWITCH DISTRIBUTION CHANNEL / MANUALLY START UPDATE TO GET A NEWER VERSION feature. AFAIK, those channels (which you listed as 1-5) are for office 365 subscribers. I'm pretty sure about this, because I've searched all over the web for a way to set the update channel for a VL edition of Office 2016 to semi-annual, but I've been repeatedly met with the same answer: it's only reserved for office 365-based installations. I'm not asking if this feature of OfficeRTOOL provides the same functionality as Microsoft's built-in ways of setting update channels. Those are for automatic updates without requiring user intervention while the OfficeRTOOL's feature is, as far as I undestand, meant for manual updates. What I'm asking is this: EVEN AFTER a C2R version is converted to VL and activated with KMS, would it be possible to update Office to the latest version offered within user-defined channel with this ? If yes, then that would be a great news to me since, I've been longing to keep my copy of Office 2016 in track, but only twice a year, out of concern for stability. Thanks in advance for your reply.
Thanks a lot for this app. I think, I've found a bug. Today I wanted to activate Office on my other system, and my other system's username is like this: "A & B" (w/o the quotation marks) When I clicked on "OfficeRTool.cmd", PowerShell windows popped up and then gone after like 1 second, so I tried to run it manually (Ran PowerShell as administrator, cd to the directory I've put the files and finally ./OfficeRTool.cmd). After doing that, I got an error something like this, Could not find A ... . I think, the problem is, that my username contains "Spaces" AND "Ampersand", which caused this bug. Thanks.
We are talking about starting of OfficeRTool? OfficeRTool window opens and closes immediatedly? What naming has full path and directory OfficeRTool was saved in? 1.) OfficeRTool cannot run from root \. You always must use a directory and start it from there. 2.) Filename and Path must not contain any special characters such as brackets (). Related to your case: Ampersand "&" as special character is the problem. VB-Script- and Powershell-commands to check/get admin rights have restrictions here. I haven't found a solution to circumvent this. To get OfficeRTool up and running, you could de-activate admin-check in OfficeRTool.cmd by commenting out the complete block "check admin rights" (= lines 012 to 036) and start OfficeRTool with rightclick -> run as administrator. Not very comfortable, because you need to do that on every new OfficeRTool release. OR You create a new environment, where directory/path names are without "special characters" and move OfficeRTool to it. This is the best.
Thanks for replying, and sorry for my late reply. Yeah, OfficeRTool closes immediately. My problem was number 2. My Path had special characters and this has prevented OfficeRTool from opening. This is the error, I was getting -> No destination specified for: C:\Users\A. Even though my user name is A & B, which means OfficeRTool was looking only for the string before "& B". But apparently this is VB-Script & PowerShell restrictions. I changed my windows altogether and chose an username which didn't have any "Special Chars and/or Spaces" . Everything is all good now. Thanks a lot.
Hi, First of all: Thanks for this nice tool! It made it easy to download and install exactly those Office programs that I want. While most of the things are self explanatory or documented in the readme, I have a few questions: Using OfficeRTool version 2018/January/13 I've downloaded the version "16.0.8431.2153_de-DE_x86_Semi_Annual_Channel" and installed "Office 365 Business" with everything excluded except for Word, Excel and Powerpoint. But after installation all 3 installed programs only show version 16.0.8431.2110 in their information dialogs. Is this version difference expected? Because of the version difference, I tried to update Office from within itself. It seems like it starts to download something (says it's downloading and that I can continue using Office while it's updating) but after a few seconds it shows an error. The error is always the same, it says it couldn't download the update. The error code is 30125-28 (404). Should this update work? Is the included activation tool only for one time activation? Because if I check my activation status the remaining days are decreasing each day. Lastly, a small improvement suggestion: When you install Office it offers the installation of the various suites step by step. I'd suggest to instead present this like the selection of the channel before you download Office. That way you see all available choices without having to look in the readme.
Info in Account/About-window is sometimes not adjusted to main install version. So the answer is: Yes. If you want to know exactly what is installed, then either look at build-number shown in Control Panel -> Programs and Features. Or use (A) Show activation status function in OfficeRTool. This lists correct build as installed. Yes, manually started updates should work without errors. You could check, if Antivirus and/or Firewall interfere update process. This could help, too: - Open Control Panel and select Programs and Features. - Click on the Office product that you want to repair. - Click Change. - Select Quick Repair and click on Repair. If Quick Repair didn’t fix the error, - Select Online Repair and click on Repair (= full setup, this will take time) Internal OfficeRTool KMS-solution does not provide an automatic renewal. If you want such an automatism, then use one of the other KMS-programs offered here at MDL. These create a service/scheduled task for this purpose. Of course manual activation for another 180days period using OfficeRTool's internal KMS is always possible. Will think about it.
Thanks for the fast answer! I've already tried it with disabled antivirus and it didn't help. I'm only using the integrated firewall from Windows 10, so that shouldn't block anything. And my router isn't blocking any outgoing connections either. I can see in the task manager that the update uses my full internet connection bandwith for a few seconds. So it definitely downloads something before it fails. I've tried the quick repair but it also didn't help. Online repair is running now, I'll update once it's done. I've also installed this Office after a clean reinstall of Windows. So there are no old files that could cause problems. Does no one else have problems with Office updates? Maybe it's the specifc combination of settings that I used? (Semi annual channel, de-DE, x86, Office 365 Business, exclude everything except Word, Excel and Powerpoint, no Project or Visio installed.)
There are no severe errors reported. My standard test environments: Windows 10 Pro, Office 2016 ProPlus and Office 365 ProPlus from Monthly(Retail) and Insider channels using full and selected Apps. Any combination of x86/x64 architectures. I will create a new one using your setup. But this will happen a little later as I'm short in time today. For self help I send you to first page of this thread. Read posts #4 to #5. Maybe some infos there help you to move further on.
Hello, Thanks a lot for your wonderfull tool ! I have just a question : did you change the licence files in your last version ? Because I obtain different results with same Office Editions (Latest Monthly channel x64 and x86) : with previous version (january 6 and previous version, when it was called O2016RTool), if I install Office 2016 (Full suite or single app), once converted to volume licence and activated, the 4 themes are proposed (ie Black theme too, as it was an Office 365 active account) and I have some additional infos in "account" section, but if I do the exactly same thing (ie. same Office Edition and version and same virtual machines running Windows 7 pro and 10 pro) with the latest OfficeRTool version, the black theme is not available. Surprising, no ?
Spoiler: CDN ID AudienceId ID Version CAB-file data >> LTSC2019 f2e724c1-748f-4b47-8fb8-8e0d210e9208 16.0.8827.2117 11.01.2018 Insiders_FRDC/FirstReleaseCurrent/Insiders 64256AFE-F5D9-4F86-8936-8840A6A4F5BE 16.0.9001.2080 19.01.2018 FirstReleaseDeferred/Targeted B8F9B850-328D-4355-9145-C59439A0C4CF 16.0.8431.2153 15.01.2018 Production_DC/Current/Monthly 492350F6-3A01-4F97-B9C0-C7C6DDF67D60 16.0.8827.2148 19.01.2018 Production_DCEXT/Deferred/Broad 7FFBC6BF-BC32-4F92-8982-F9DD17FD3114 16.0.8431.2153 19.01.2018 Dogfood_O16ProPlus-O15Visio_DevMain EA4A4090-DE26-49D7-93C1-91BFF9E53FC3 16.0.9015.1000 18.01.2018 Dogfood_OfficeGroup 55C44C35-878E-4C43-83EE-B666BF4261A4 16.0.8209.3000 15.05.2017 Dogfood_OfficeGroup_FRDC F3260CF1-A92C-4C75-B02E-D64C0A86A968 16.0.9001.2083 19.01.2018 Dogfood_OfficeGroup_DCEXT 834504CC-DC55-4C6D-9E71-E024D0253F6D 16.0.8431.2153 28.12.2017 Microsoft_Unsigned C4A7726F-06EA-48E2-A13A-9D78849EB706 16.0.8201.2217 09.01.2018 Microsoft_Elite_DevMain 5462EEE5-1E97-495B-9370-853CD873BB07 16.0.9001.2083 19.01.2018 Microsoft_FRDC B61285DD-D9F7-41F2-9757-8F61CBA4E9C8 16.0.9001.2068 17.01.2018 Microsoft_DC 9A3B7FF2-58ED-40FD-ADD5-1E5158059D1C 16.0.8431.2153 09.01.2018 F4F024C8-D611-4748-A7E0-02B6E754C0FE 16.0.8431.2153 09.01.2018 5440FD1F-7ECB-4221-8110-145EFAA6372F 16.0.9001.2068 18.01.2018 O15_MOD_Dogfood 50CFADF4-6AD2-4BD2-9981-C7B5C05A8C67 16.0.8326.2037 10.07.2017 DSAPI_FastFork E404F044-0870-4935-8B00-1F59A813F7D6 16.0.7030.1000 01.06.2016 Speed_Of_Light_Test 285A35E5-58C8-4579-A9FF-4E791E21691D 16.0.6366.2050 13.12.2015 dev15main_signed 133DBEB4-3C56-4C67-9D80-F240C53D7D20 16.0.4229.1028 24.09.2015 Tech_Preview_Canary 7D632000-B182-4E05-A91D-763D282C24DE 16.0.4229.1031 04.10.2015 Dogfood_Canary A1D255FE-49BB-4A88-ADE8-4EC08D98FBD4 16.0.4229.1031 04.10.2015 MSIT_Canary 185CDAE3-CA39-40C1-BA12-DCDDDA72A0DC 16.0.4225.4752 26.06.2015 Technical Preview 0F72FECE-4E67-432D-B9A8-2393C8522FB7 16.0.3327.1020 15.11.2014 >>> +: "CMValidation2" 2C508370-A266-4CFC-8877-AF06FDEB0C24 16.0.8067.2032 21.04.2017 CBC7891E-9126-44DE-8A56-2BD6D2E06C48 16.0.8067.2032 21.04.2017 Office_Small_Experiment_CDN 89815E81-C82E-49A3-99DC-2B99229CF632 - - >>> 2013: O15_PU 9981A3FE-BBC6-41C7-86F4-89DC69E477E2 15.0.5007.1000 18.01.2018 Cedexis_Test_Object 39168d7e-077b-48e7-872c-b232c3e72675 15.0.4997.1000 13.12.2017 O16_Aggregator_Signed C67D6333-12A1-463E-8011-1493FF26FED2 15.0.4997.1000 13.12.2017 O15_O16_AutoUpgrade_O16 6115E8D2-FDDF-4F64-9F23-B73451A1A97E 15.0.4797.1000 13.01.2016 O15_O16_AutoUpgrade_O15 CDAFF0F1-63B9-4630-BC32-90BF5B2F8308 15.0.4753.1003 14.09.2015 Secondary_PU_bootstrapper 6BB97ACC-EC9F-4EC2-8DC3-3A398BBC93DB - - >>>Other ID lyncentryretai D85263CB-A813-4A8F-9895-E2EC9CA47293 15.0.4128.1025 12.09.2012
Yes. I thought, it is a good idea to have the latest ones (Office 2019) available. Confirmed. Same here. I've just done a quick test and copied the older Volume license files from O2016RTool back to OfficeRTool and it worked again. I will do some more checks. Thank you for testing and reporting!
Thank you (again) for updated list. For all others not knowing what's this for, look in this history for further information.
Thanks for the offer. Looking forward to your results. I've read through those posts and the linked articles but couldn't find anything that would relate to my situation. In the meantime, I can report what the full online repair did on my machine: After the online repair finished, my Office showed "Monthly 1712 (build 8827.2148)" on the "Account" page. So the online repair switched my Office from semi-annual channel to monthly channel and updated to the latest version. Not really what I wanted since I chose the semi-annual channel on purpose. But it gets even better! The update function in Office now worked and it started to download something. After a few minutes it finished and restarted Office. And then I was back to version 16.0.8431.2110! So the update actually did a downgrade After this adventure, it seems like I'm in a state that I want. I have the semi-annual channel installed and the update function is working (it says I'm on the latest version now). But that is way too much effort if that is required after each fresh install.
Will definitely take care of your case right this day. I'm a little puzzled because you said you installed Semi-Annual-channel and Online-Repair reverted it back to Monthly channel. Then the next manual update reverted it back again to Semi-Annual-channel. OK, I will see if I can reproduce this and I will do my very best, that this won't happen again.
Now that you say it, I'm not really sure if the online repair really switched me to the monthly channel. Office just showed "Monthly 1712 (build 8827.2148)" on the "Account" page, but I didn't check this in detail. Maybe it was still in semi-annual channel and therefore the update downloaded the latest semi-annual channel version, which then was the downgrade? If that really was the case it would mean that the online repair is bugged and ignores the chosen release channel.
Testing finished. Environment: Windows 10 Pro x64, "16.0.8431.2153_en-US_x86_Semi_Annual_Channel" Installed Office 365 Business (Word, Excel, Powerpoint) Here are the testresults: Started manual update. As the newest Semi-Annual version 16.0.8431.2153 is already installed, I expected the message "You're up to date". But surprise, update started and initated a new download and failed: It's the same error you got. Then I started "Online Repair". Next surprise: Online repair installed version 16.0.8827.2148 (which is Monthly-channel) Started a new manual update, which succeeded. Now Office has Semi.Annual-channel version 16.0.8431.2153 and update tells me "You're up to date". During all steps Office has correct settings for Semi-Annual channel. I checked OfficeRTool back and forth, but found no obvious errors. When I install 16.0.8431.2153 over "repaired/updated" version some- thing is changed and update started again. I try to find what triggered this behaviour. Update (after hours of testing spent/wasted): As always... My hostile attitude toward Microsoft's quality assurance was fully reconfirmed. "Semi-Annual Channel" is working (but only if configured as "Deferred" channel). In September 2017 Microsoft announced that they will change all distribution channel names. OfficeRTool was changed to follow the new naming convention. Unfortunatedly not every Office build is properly designed to support this new configuration variable-names. This leads to the situation, that the newest Office build is installed with the new channel-naming and when internal update is started, then there is a new build detected, because OLD naming is used by this Office build (or by the called update server). OK, I'm totally fed up with this. As the old naming works perfect, I will change OfficeRTool back to use the old channel names for install and update. But it will show the new naming in all dialogue- screens to match MS online documents. To be sure, I will test several other combinations now. In case every- thing works ok, a new OfficeRTool will be released. Waiting until MS wakes up and removes support for the old naming...
A new OfficeRTool version (2018/January/21) was released today Error corrections: - Added correct Volume Licenses files (thanks user rhahgleuhargh for reporting) - Changed distribution channel naming back to old naming convention (problem reported by user cremor) Enhancement: - Changed Full Suite setup dialogue to display all available Suites for selection (suggested by user cremor) No other changes were made. Download-links and checksums in OP were updated.
I just did a clean install with the new OfficeRTool and can confirm that the update check now works. Thanks for your work! I was interested in how your script works and had a look at the files that are generated before the Office installation is started. There I noticed a small mistake: The "Channel" attribute in the configuration XML file contains a space at the end of its value, e.g. Channel="Deferred ". Both the "Add" and "Update" tags are affected. Seems like this doesn't hurt but I thought I mention it anyway.