Thanks again, @Enthousiast Your install has succeeded, it seems. Note however that your and mine sources are not the same. You use the Monthly channel, and I the Perpetual VL. Not sure how much this matters in practice, but strictly speaking the installs are not fully comparable. I have just completed the install of another recent build, this time C2R Monthly, and succeeded. Thus, I'm wondering why the Perpetual VL install eventually fails. Best luck
@symetricus Windows 7 require UCRT update and VC++ 2019 so Office C2R work properly additionally, OS itself must be updated (at least with 2018 updates)
This is on a simplixed september 2020 test install: https://forums.mydigitallife.net/th...osoft-office-2019.75232/page-161#post-1620740 I even installed and uninstalled .net fx48 ESU patcher to see if msiexec is affected.
Only perpetual VL failed, the others all installed fine: https://forums.mydigitallife.net/th...osoft-office-2019.75232/page-160#post-1620661
Yeah i ment that if you still have the *.log files from C:\Windows\Temp it may help knowing the cause Edit: Code: Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action CAInitSPPTokenStore.x64, entry: CAInitSPPTokenStore, library: SPPRedist.msi
Following up the PerpetualVL channel installation issue on Windows 7 the bundled SPPRedist.msi has dependency on api-ms-win-core-path-l1-1-0.dll (PathCchCombine), which only exist on Windows 8 and later copying the file itself won't help, because it's just stub for the function in kernelbase.dll i guess this is the end for Office 2019's PerpetualVL channel on Win7
According to YAOCTRU: Code: ============================================================= Channel : Monthly ============================================================= Selected channel offer different builds per OS level: 1. build: 16.0.13231.20262 [Windows 8.1 and 10] 2. build: 16.0.12527.21104 [Windows 7] ============================================================= > Enter Build option number, and press "Enter": But that was already established, with the extender the monthly 8.1/10 builds also work on 7, but not perpetual VL. Elite seems to offer a lesser build: Code: ============================================================= Channel : MicrosoftElite ============================================================= Selected channel offer different builds per OS level: 1. build: 16.0.13324.20000 [Windows 8.1 and 10] 2. build: 16.0.12513.20010 [Windows 7] ============================================================= > Enter Build option number, and press "Enter":
I have trouble with YAOCTRU / YAOCTRI: after installation the Help doesn't function. It says something like "Administrator doesn't allow Help" or something similar in localized language. If I install using official "setupproplus2019retail.x64.hu-hu_.exe" it works perfectly. Windows 10 and config: [configuration] SourcePath="C:\utils\1 YAOCTRU\C2R_Monthly" Type=Local Version=16.0.13231.20262 Architecture=x64 O32W64=0 Language=hu-HU LCID=1038 Channel=Monthly CDN=492350f6-3a01-4f97-b9c0-c7c6ddf67d60 Suite=ProPlus2019Retail ExcludedApps=Groove,Access,Lync,OneDrive,OneNote,Outlook,Publisher,Teams UpdatesEnabled=True AcceptEULA=False PinIconsToTaskbar=False ForceAppShutdown=False AutoActivate=False DisableTelemetry=True DisplayLevel=True AutoInstallation=False
I'm trying it out without that option set. So which is the most "stock" setting for the config? Only UpdatesEnabled=True?
Hi, in case of a retail purchased Office 2019, is there any way to backup the installed product keys into a file? Just because it takes quite a long time to activate manually.
I keep getting the message office 2019 pro is not compatible with this version of windows 20226 were the link for the latest build being use? thank u
Been getting a really bizarre problem. Had a laptop I started the process of using KMS and OfficeRTools on in case of emergencies, but due to travelling I had to leave it behind. Only had time, then, to download all the necessary files (still have all the 3Gb of selected Office tools I decided to install in my C: root folder), but couldn't just risk leaving the program behind running with the laptop plugged for weeks or months as the only thing turned on in my house. Well, now I'm back, and even without activated firewalls, antiviruses the weirdest thing I've ever seen in a cmd program is happening. Every time I open it something different happens and all of them disallow me from proggressing past the main menu, even the CLOSE (E) function. Sometimes officertools.cmd (both the new release check and the one without it) when opened vary in response to just opening cmd.exe and doing nothing else besides that Sometimes it gets to run the script, as the command prompt turns blue, but nothing else happens, and finally, sometimes the main menu of the script will run to completion, ask for my choice, to which I type in only to see the letter show up and... nothing. Nothing happens after that, not in a minute, not in an hour of the script "running" What the hell is causing this? I'm finally in need of the extra notebook and I'm now regretting not leaving this thing frying for months on its charger, at least it worked then.
Hello my friends, I'm little bit confused about installing Office 2019. I always used Office 2016 Standard VL (from VLSC), but now I just fresh installed Windows 10 2004 and would like to move on Office 2019. So, which tool should I use? I think that I should use YAOCTRI. Can I choose the same Standard version as on 2016? Which update channel should I use? I just would like to Office 2019 behave like my old 2016 which I installed from VLSC ISO. Thanks.