Have anyone have installed Office 2016 and Office 2019 in the same Windows 10 PC? Please let me know. Thanks.
expand "%installfolder%\Office\Data\16.0.10325.20003\i640.cab" -F:* "%CommonProgramFiles%\Microsoft Shared\ClickToRun" >nul 2>&1 expand "%installfolder%\Office\Data\16.0.10325.20003\i641045.cab" -F:* "%CommonProgramFiles%\Microsoft Shared\ClickToRun" >nul 2>&1 start "" /MIN [...] version=16.0.10325.20003 [...] start_setup.cmd does not automatically detect the new version, you have to replace it manually
My x86 installation is working again, thanks! Small note: Seems like you left your last test values in OfficeRTool.ini
Only by using the other install method which needs OfficeC2RClient.exe. OfficeC2RClient.exe has no OS version check. But we face some unsolved errors with this (32bit/x86 install not working in some environments). Microsoft clearly said, they don't support Office 2019 on older Windows. OK.. This statement is based more on marketing Win10, than technical reasons. But, even if install may work at the moment, it could break with the next new build containing an restricted OfficeC2RClient.exe or using Win10 only libraries.
@ratzlefatz I actually like your new way of installing office, and I was hoping (and confident) you will sort out the reported issues. One thing I noticed, while I did not take readings, the Office installation was faster to install using the new method over using setup.exe.
I haven't quit testing the new method. But 32bit/x86 install malfunction is a hard nutshell and it seems, opening and using it will take a lot of time and effort. And missing documentation is a problem, too. Extremely strange: ODT setup.exe is calling OfficeC2RClient.exe with all command line parameters set. But when OfficeRTool (new method) uses the same command-line and parameters for 32bit/x86 install, it fails. As pressure for a working OfficeRTool version is lower with the old method now, I will have some more time for inspecting OfficeC2RClient.exe for interaction with ODT setup.exe. But new method will only return, if there were no big showstoppers.
I downloaded the Office 365 Pro Plus Click to Run offline installer and installed Office 365 Pro plus. Then used MDT to install Project Pro 2016 from Microsoft. I used mtk 2.6.7 beta 5 to activate the office 2016 pro plus vlk family licence. Then had to use a simple script using kms server to activate Project Pro 2016. Well then I have come across this OfficeRTool. This tool can detect Office 365 Pro Plus but it does not detect the Project Pro 2016. Wondering is thinking Project Pro as part of the Office 365 Pro plus? Or what have I done wrong?
Project Pro is detected by OfficeRTool. Both, Click2Run- and Volume VLSC versions. No clue, what happened on your system. If ProjectPro is activated and works, then you have installed correct. If it doesn't work or you are unsure, then remove Office and Project with FixIt-tool from Microsoft (see post #4) and start anew.
the old method with the new setup.exe does not work, the older version of setup.exe was available in the script the new window turns on the cmd window to get permission, the first orange window turns on, disappears and then nothing In turn, the new method (x64) is a strange error: - I click start_setup.cmd nothing happens, - after a while, the error will pop up that you can not stream, no file bla bla bla, - followed by installation I also noticed the error: If you have files from an older version in C: \ Program Files \ Common Files \ microsoft shared \ ClickToRun, they are not replaced with a new version
== Activating ... == KMS-Server OK. ---Processing-------------------------- --------------------------------------- Installed product key detected - attempting to activate the following product: SKU ID: 0bc88885-718c-491d-921f-6f214349e79c LICENSE NAME: Office 19, Office19ProPlus2019XC2RVL_KMS_ClientC2R edition LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel Last 5 characters of installed product key: KTQRG <Product activation successful> --------------------------------------- Installed product key detected - attempting to activate the following product: SKU ID: 500f6619-ef93-4b75-bcb4-82819998a3ca LICENSE NAME: Office 19, Office19VisioPro2019XC2RVL_KMS_ClientC2R edition LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel Last 5 characters of installed product key: Q3X4H <Product activation successful> --------------------------------------- Installed product key detected - attempting to activate the following product: SKU ID: fc7c4d0c-2e85-4bb9-afd4-01ed1476b5e9 LICENSE NAME: Office 19, Office19ProjectPro2019XC2RVL_KMS_ClientC2R edition LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel Last 5 characters of installed product key: W2RMW <Product activation successful> --------------------------------------- --------------------------------------- ---Exiting----------------------------- one more tool to download and activate office 2019 https://forums.mydigitallife.net/th...nstall-activation.62571/page-124#post-1447207