Are Visio and Project suppose to report 2019 when they start, or is it known from the version number?
A new OfficeRTool version (2018/May/06 - 3rd Ed.) was released today Function "(D) DOWNLOAD OFFICE OFFLINE INSTALL PACKAGE - Error Correction - Corrected bug: Install of Visio 2019 Pro and Project 2019 Pro is not shown when Manual Override (MS Internal Use Only) distribution channel setup package was selected. Instead Office 2016 versions are installed. (reported by user Simple07) Corrected unexpected behaviour: If non Office 2016 / 2019 distribution channel was selected OfficeRTool continues to download unsupported Office (ie 2013). Now OfficeRTool aborts download and returns to main menu. (reported by user Dolmatov) (A) SHOW CURRENT ACTIVATION STATUS Corrected bug: Function aborts and OfficeRTool closes in some configurations when selected. (U) CHANGE OFFICE UPDATE-PATH (SWITCH DISTRIBUTION CHANNEL) Corrected bug: Function aborts and OfficeRTool closes in some configurations when selected. No other changes were made. And this should be the last version for today (hopefully). Download-links and checksums in OP were updated.
Visio 2019 and Project 2019 are not fully branded. So no "2019" is shown in the small startup-window (like it is when for ex. Word starts). But I found a logical bug in OfficeRTool's download-function while I was checking.
I found one more error. Well, you can not set as the download path of a bare partition, e.g. D: \ There must be some existing folder specified because otherwise an error will pop up that the path is not found or is invalid
Surprisingly, without reporting a mistake to find out about her finding me. I just noticed the accidental closing of the window due to the peculiarities of cmd commands. ! It's not a mistake =)
That works as designed. You cannot start a ODT "setup.exe" install from root of a drive. A subdir is always needed. Therefore OfficeRTool checks if download path is root \ and complains. But you can specify a new folder and it will be created. No need to use a existing directory.
Can I make it possible to download all available languages with automatic skip missing stream-file, like for CDN in the screenshot above?
And that's what I get: Code: Set Channel-Index-# (1,2,3,4,5,M) or X >m "Microsoft Internal Use Only" Beta/Testing distribution channels Internal Naming Channel-ID: Index-# ___________________________________________________________________________ Dogfood::DevMain -----> ea4a4090-de26-49d7-93c1-91bff9e53fc3 (1) Dogfood::CC -----> f3260cf1-a92c-4c75-b02e-d64c0a86a968 (2) Dogfood::DCEXT -----> c4a7726f-06ea-48e2-a13a-9d78849eb706 (3) Dogfood::FRDC -----> 834504cc-dc55-4c6d-9e71-e024d0253f6d (4) Microsoft::CC -----> 5462eee5-1e97-495b-9370-853cd873bb07 (5) Microsoft::DC -----> f4f024c8-d611-4748-a7e0-02b6e754c0fe (6) Microsoft::DevMain -----> b61285dd-d9f7-41f2-9757-8f61cba4e9c8 (7) Microsoft::FRDC -----> 9a3b7ff2-58ed-40fd-add5-1e5158059d1c (8) Production::LTSC -----> f2e724c1-748f-4b47-8fb8-8e0d210e9208 (9) Exit to Main Menu (X) Set Channel (enter Channel-ID or Index-#) >A1D255FE-49BB-4A88-ADE8-4EC08D98FBD4 --> Checking channel: Manual_Override Last known good Build: 16.0.4229.1031 No newer Build available Set Office Build - or press return for 16.0.4229.1031 > Seems, it looks correct.
This requires some effort to modify OfficeRTool to become such smart. At the moment I would say this won't happen soon...
In my output above, all looks good. What problems do you exactly have? hhmm.. Repairing/catching every user error during input is hardly impossible.
For all those who have been facing activation problems in the latest builds, here's how I got over the problem: 1) Install Office 2019 or 2016 2) Start elevated command prompt and execute the following command: "net stop sppsvc" 3) Search for all instances of tokens.dat and cache.dat in the Windows drive and delete them (or rename them) 4) In the elevated command prompt, execute the following commands: "net start sppsvc" and "cscript.exe %windir%\system32\slmgr.vbs /rilc" 5) Reboot the PC and activate (I used O2016RTool)
Not needed to delete ALL occurrences of tokens.dat. The only important location is: Windows 10 ->C:\Windows\System32\spp\store(_test)\2.0 ("store_test" only available in Windows Insider) Windows 7 needs special action -> look here. Additional info (regarding Windows activation error) from abbodi1406 in KMS_VL_ALL-thread -> look here.
Thank you, I will give it a try. I couldn't believe one works and the other doesn't. I always use Microsoft Toolkit, and it worked well. This time, I will give a try on KMSpico. I thought fundamentally both are the same theory. Interesting.