Hi there, can someone please enlighten me about this OFFICE 2019 windows of mine.I have successfully converted my Retail copy into Volume using C2R-R2V_12.I also successfully activated my Volume copy using a license key online.Upon checking my overall activation status, i am somewhat lost as to what this Grace Period (8MBCX) status really means.Is it normal to see that after conversion of Retail to Volume?Thanks. Edit: thanks istighfar,that fix it. As for reference i used the latest img in my Office Installation which is Version 2002 (Build 12527.20482).
That's the key which is installed by default when you install office 2019 retail version. You can easily remove it from the system by doing this : open command prompt in admin mode and copy and paste these lines one by one :
1) you can use YAOCTRI to install office 365 but you need to know that not all features of office 365 will work when activating with kms, only some of them will work, that's what the author of the tool told me. 2) yes you can customize office installation by choosing only the needed programs to install through the tool.
Not really a Office problem. You are on the wrong track. Please present your question in the correct section = 'Scripting': -> https://forums.mydigitallife.net/forums/scripting.38/.
Oh please sorry. I found this https://forums.mydigitallife.net/th...ogon-silent-install.73131/page-6#post-1593253 Convert to .bat and call it in firstlogon. Should i delete this and the post before?
Hi I need some help, so I recently reinstalled windows with keeping my files on the pc, and had to reinstall office. What I did before is that I would download OfficeRtool and get the 365 proplus and then do all the steps like RL to VL and activate it with mondo etc. Now when I try to reinstall it with OfficeRtool it installs really slowly and eventually just stops at 51% and doesn't go any further. I cleaned with officescrubber and also googled around and tried all of the peoples solutions but nothing has worked, still sitting with 51%, any thoughts or can someone help me?
Have you Disabled all anti virus, disabled firewall, disabled malwarebytes and disable any other security software? "avg tuneup" also impacts O365 from my experience.
Disabled my whole windows antivirus but nothing changed, I also installed by accident a office 2019 pro plus and that one flew by in the installation with an ISO, but downloading and installing the 365 which I really want because of the autosave feature its still currently sitting at 51% so I thought I would mention that
Hi there, I am having the same issue. Fresh Windows install (Entreprise LTSC) 16.0.12730.20270_en-EN_x64_Monthly_Channel stucked at 51%. I have turned off windows defender and Comodo Firewall, activated .NET Framework 3.5... Option C or S for installation. Nothing helps...
Stuck at 51%. Same here! Tried all so called 'solved' tips. Nothing. Windows 10 1809 is running on this system. 2 others with 1909 are running fine. OfficeScrubber from abbodi1406 didn't help. New clean Windows 1809 setup doesn't help either. This behaviour starts with latest Office update. To me, it seems, newest Office build (Monthly) is buggy on older Windows 10 builds. I will try newest W10 2004 and hope this will bring back my wife's Office (otherwise I will get ).
Same issue on w10x64 20H1 19041.264, with or without AV or firewall. Redownloaded installer... same, dism reset base and health... same, sfc... same. Buggy channel. EDIT: I will try Semi-Annual Channel Targeted (Business Insider, C2R) -------------: 16.0.12527.20612... and later we can change update channel. EDIT2: Confirmed buggy channel. Installed semi, changed to rtm and updated.
I'm back. The system is running a complete new setup now. I've deleted system partition, installed Win10 2004 19041.264 and downloaded Office 16.0.12730.20270 from Monthly channel. Office install was fast and completed without errors. Hey MS: Instead of doing funny renaming of Office distribution- and update-channels (happened twice, incomprehensible) you should spend more attention to the fact that this may harm your content delivery network (and the users...)