@emet Don't bother with troubleshooting if you want to save time. Uninstall the office from the control panel and use OfficeScrubber to clean all the remnants. Now mount your ProPlus2019Retail.img and use YAOCTRI (YAOCTRI_Configurator.cmd) to directly install office as VL. It has lots of customization install option, p.s. you can install all the products from a single img. Activate it with KMS_VL_ALL-SppExtComObjPatcher you have and done.
Thanks @Windows_Addict for your response too. Now I had realized that even removing Office2019 is rocket science too. Why are there so many tools? Office2016 was easier to install and remove. Right?
Same message using Visio Pro image? Choose "Install 64-bit", no error using the Visio Pro image after first full install with ProPlus2019 image Tried to use exact same procedure/tools as you used
Thanks @Sajjo for your response again. I don't have that option to install 64-bit. https://forums.mydigitallife.net/threads/discussion-microsoft-office-2019.75232/page-94#post-1496764
Yes... I am wondering whole day. Thanks guys for your response about my issue. Both of you @Sajjo and @Windows_Addict are very kind.
I suggested to use officescrubber because you were facing errors, otherwise it's not necessary . Are you sure, you are facing errors in installation with yaoctri even after using scrubber?
@Windows_Addict I haven't used OfficeScrubber yet. I have understand you it is for removing the office.
So, are Visio and Porject NOT on the Office Pro Plus IMG but Office PP is on the Visio and the Project IMGs?
No. Visio img only install visio app (same with project) ProPlus img don't install visio or project. but that's when if you directly run the setup file from the img. ---------------- Office C2R setup contain every product and channel, but their setup is locked to install only mentioned product, You can officially bypass this lock with ODT, or better use more user friendly YAOCTRI with more capabilities. If anyone want to install every product then it's better to use Mondo 2016 option (which contain every product and have highest level of features) in YAOCTRI. or select ProPlus 2019 + Visio Pro 2019 + Project Pro 2019 and i'll create 3 entries in add/remove programs. p.s. You may think that mondo have '2016' in its name so it may be old but that's not the case actually. Mondo is equivalent to O365 which is near to 2016 branch but still have all the latest and more features than O2019.
Hi, I'm unable to install Office 20119 Pro Plus on my Win 7 SP 1 Ultimate x64. I will note down every step taken with details relevant or otherwise. I've used the latest OfficeRTool2018Dec02 - running from the C:\ drive and Ran as Adminstrator Downloaded the latest office Monthly Channel (Retail/RTM) version Download Path "C:\Office Install\" en-US x64 Installation: OfficeRTool2018Dec02 - Ran as Administrator Install Version Selection = 1 Install Method = OfficeClickToRun.exe "C" Office Edition Selection = #5 for Office 2019 Pro Plus No programs disabled from install Visio and Project disabled Start Local Install = 1 It creates the installation "Start_Setup.cmd" And nothing happens after that! Tried going to download destination and running "Start_Setup.cmd" as admin and CMD prompt shows: Stopping services "ClickToRun" and "Windows Search" then windows closes And nothing happens after that! Navigated to: C:\Program Files\Common Files\Microsoft Shared\ClickToRun Tried running "OfficeClickToRun.exe" and "OfficeC2RClient.exe" And nothing happens after that! Nothing related to office installation appears in Task Manager or task bar notification area. Tried rebooting many times and it was of no use System Info: Windows 7 Ultimate x64 MBR formatted Daz Windows Loader Activated Windows Updates done post activation
Office 2019/365 on Monthly Channel updated. Version 1812: January 15 Version 1812 (Build 11126.20226) Minor update.
no this is wrong this is 8 january the current build is : 11126.20266 january 15 and the changelog soon will updated in release notes.
You are right, it was clearly showing 11126.20266 for me, I might have misread that or copied the wrong value. Thanks, it is now fixed!