the error is already visible at the beginning I choose office 2019 installations and visio and project in the script is proposed as 2016 ProjectPro2019Retail VisioPro2019Retail yes it should be, using xml installs correctly
First: Please collect your error reports and write 1 post. I still didn't get where's your problem. Please elaborate. An example showing all steps you take and what result you expect would be nice. Again I didn't get it. What is this "Helper"? Where can I find it? Script shows all possible options based on the selected distribution channel. It starts with standard Visio 2016 and Project 2016 versions. Afterwards (using valid distribution channel and if Visio 2016/Project 2016 were not selected) it shows Visio 2019 and Project 2019 versions for selection. That's all fully described in the readme.pdf file. I've tested and 32bit install is working. If you have problems, then help me to reproduce them. But I need more info than your one line "not working" report. At all others out there: Anyone else having such problems and want to contribute?
Is there a download of Office 2016 UWP Version from MS STORE? On MS Store, Word 2016 takes 2.0GB of hard disk.
OfficeRTool doesn't support MS store UWP apps, sorry. An Office install package always contains all products. Even if you need only Word, you must downlaod the full package (2 GB).
1 - You start the option to create the installer - option 5 - Office 2019, during the configuration in the place where he asks whether to add Visio and Project are badly marked - immediately as 2016 - in the setup cmd are badly marked - no additional note 2019 - without him are as 2016 After choosing the option to create Office 2019 installer, the script should ask about Visio and Project 2019, not 2016 and instead of typing commands: projectproretail visioproretail should projectpro2019retail visiopro2019retail that's how it works so far on xml 2 - When files do not exist are copied, but after pressing the setup cmd, nothing happens, nothing installs, the window disappears after the stage of obtaining the admin rights / UAC - uac is disabled the method from ODT and XML the testimony is checked and works 3. Office Helper - UWP application, uploaded using the new method - you can find it in Add / Remove
Is there any tutorial which shows how can I activate my Office 2016 VL with MAK key over chat? Thanks.
Perhaps it would make more sense if the 'extra' Office 2016 apps (Visio and Project) were automatically disabled if the user is installing Office 2019 From my experience you can mix Office 2019 apps with the 'extra' apps from Office 2016 , but this fails activation.
Don't select 2016 versions and only select 2019 versions: The above selections gives the following productstoadd= in command line (no 2016 versions!): Code: productstoadd=proplus2019retail.16_en-US_x-none^|projectpro2019retail_en-US_x-none^|visiopro2019retail_en-US_x-none I wanted the user to have total control of what to install, either 2016 or 2019 or a mixture. Update: as requested, I will change to disable Visio/Project 2016 if Office 2019 is selected. Unfortunatedly - after testing various scenarios - I've found no errors. Do you have any special characters like brackets () or ampersand & in filepath or the username? If YES, that's the reason for the error. You must rename it. Have not found a UWP app named "Office Helper". Did you mean this active tile called "My Office"? This one is already installed with Windows 10 (1803), not by OfficeRTool.
OK, I see, it is missleading. Will change OfficeRTool to disable Project/Visio 2016 if Office 2019 is selected. No problems here. Mixed installation gets activated without problems.
A new OfficeRTool version (2018/June/24) was released today Function "(I) INSTALL OFFICE SUITES OR SINGLE APPS" - (Change) - Now Visio 2016 / Project 2016 is not shown when Office 2019 is selected. - (Bugfix) - Install from file "start_setup.cmd" now possible from all drive/folder locations. When moved/copied from default install-folder, be sure, standard folder structure 16.0.xxxxx.yyyy\Office\Data remains intact. No other changes were made. Download-links and checksums in OP were updated.
No, the Office Helper application appears as a black icon with an orange logo, only when using the new method I do not have special characters in the user name, as I said the new method is faulty / worse and less intuitive - the old version using ODT works properly (username is Stanisław Kida) - the computer belongs to my friend One could add a function to the script, that if it detects a custom username and the new method fails, it will download files from the old method and start configuration (or move present to the xml file) and installation according to the old method - it also has an additional advantage: install office 2019, even on older systems, the new method will probably work for 2019 only on Windows 10 another suggestion is not to induce the user to maintain the structure 16.0.x.x.x.x because I, for example, change the name of the folder to a more friendly and then transfer. In its current form, it will not work again the more so because the default structure looks like this 16.0.10321.20003_pl-PL_x64_Dogfood_DevMain
I used the latest tool (24June18) to download 16.0.10313.20013 (Office + Project + Visio 2019) and uninstalled my current Office Pro Plus 16.0.10313.20013 which was kept to date through updates. When I try to install, I get the error message "System restart required". I did restart the system, to no avail. I then removed all traces of office using the Office Removal Tool, no luck either.. Renaming the installation folder to the original download name, allowed installation.
So I installed the ISO, converted to retail and then used the MTK to activate. The MTK app says its activated for 180 days but then when I open office is said it would be disabled in 24 hours and does not say activated in the account info section. What am I doing wrong? I Previously had a office 16 KMS edition installed which stopped working so i uninstalled and used the ISO+C2R+MTK and when I opened up word it auto logged me into my outlook.com account...i'm not sure if these two factors would affect the success.
Hello x64 works for me but not the x86. I make installation on virtual machine with seven up to date ; no kb detected by Windows Update. I use OfficeRTool to make an installation package. With OfficeRTool2018Jun22.7z, my installation package results in the 30125-4 error . I tried OfficeRTool2018Jun24.7z. Now, this is the 30182-39 error. More details : Seven Pro SPI in french. Office 2016 Pro Plus Monthly Channel fr-FR 16.0.9330.2124 with only Word, Excel, PowerPoint and Outlook selected. Note that Skype classic is already installed on my vm.
Hello I can confirm that the x86 installation (June 24 version) doesnt work. I have tried using an older version (March version) and the installation does work. The steps I did for both versions is this. 1. Install Office Suites or Single Apps. 2. Pick Directory 3. Pick Monthly Channel Package Retail 4. Pick Single Apps. 5. Pick Both Create Install Package Install and Install Local Now. The older version install but the newer one does not
"Thank you" to all who reported the errors in more detail. I will build new test environments (such as: Win7, x86) and check....