I found a small bugfix for a new (held method) you must add content to the script C: \ Program Files \ Common Files \ microsoft shared \ ClickToRun because only when it is empty is start_setup.cmd is copying new files there and the installation starts immediately
That's working correct. "start_setup.cmd" checks for existance of OfficeClickToRun.exe in this folder. OfficeClickToRun.exe (and all the other needed files) are already available when there exists a valid Office installation. But then OfficeClickToRun.exe is in use and can't be overwritten. So it make no sense to expand/copy files when OfficeClickToRun.exe is detected. If you get problems here, then it may come from a corrupt Office installation. I would suggest to wipe Office with FixIt-Tool and start anew. And just to avoid such "problems", it's always good to use the FixIt-Tool between tests of different Office versions and channels (especially if non-standard channel such as "Dogfood_DevMain" was used).
this file is run by the service for quick office installation, you can add a command that stops this process, then it cleans the contents of this folder and uploads new versions when the folder is empty the installation takes place immediately and when it is not after a few minutes And the new version of setup.exe also works problematically, the installation turns on after a few minutes, the older version was turned on immediately
With OfficeRTool, you first must download a setup package (~2GB) containing all the Office products from any of the distribution channels. Exception: Don't use package downloaded from "Semi-Annual channel" and "Semi-Annual-Targeted channel". They don't contain Office 2019 at the moment (Office major version < 10000, see post#6). I suggest to take "Insider (FAST) channel" as download source. Then install Office 2019 and maybe Project 2019 / Visio 2019 if you like.
The point of having the password hidden is to have it available for members only. Inserting in your message text makes it available to all. Please remove it, and advise users to find it under the Spoiler..
Yes,in fact without doing that many versions won't activate at all(office365pro for example) so OfficeRTool/kms activators here does this automatically.
Bug fix for the new method (temporarily withdrawn). If nothing happens when you turn on start_setup.cmd: Delete everything in the folder C: \ Program Files \ Common Files \ microsoft shared \ ClickToRun It is necessary to stop the service - Quick installation of Microsoft Office (ClickToRunSvc) service and the process - Microsoft Windows Search Filter Host Installation will start immediately after starting start_setup.cmd Bug fix for not activating Choose the option to log in with a different account, then choose that you do not want to bet a new one just activate the key. After entering the Retail key, restart Office, do the same for Project and Visio Tested on x64
The tool works great, thank you. I am a bit confused with all the suites though. Which one has the most features/gets them quickest? Thank you. 1.) Office 2016 ProfessionalPlus 2.) Office 365 ProfessionalPlus 3.) Office 365 Business 4.) Office 2016 Mondo 5.) Office 2019 ProfessionalPlus
New version WOTOK with new support w64/o32 and generate windows digital license. https://forums.mydigitallife.net/posts/1414279 Edit: Why MDL makes asterisks (*****) instead of GENERIC Windows 10 professional MAK key (-*****) and instead of generic retail (-3V66T), oem (-8HV2C) and vl (-T83GX) not makes asterisks? Why MDL makes asterisks instead of slc.dll (slshim.dll) link in cmd? The original source code slc.dll (slshim.dll) is also on the github. Why does MDL external link to slc.dll (slshim.dll) in cmd is problem but link to SppExtComObjHook.dll and SppExtComObjPatcher.exe problem is not?
Use Insider (FAST) distribution channel and install 2.) Office 365 ProfessionalPlus If you accept some risk using alpha software from MS developers, then use one of the non-standard channels, where "Dogfood_DevMain" is the most current development channel.
Seems staff decision nowadays is declaring several topics as forbidden (including all related tools ands stuff) and restricting users from certain topics (You have insufficient privileges to reply here.). Sad but happens.