Do a full online office repair. Then Try using OfficeRTool to convert from retail to volume then kms activate. See if that makes a difference.
Do you guess or do you know it and verified? What is a "full online office repair"? The installation will be the same. The license was "repaird" until I R2V and kms it and features was gone agin. I will try the way with OfficeRTool in an vmware and report back. EDIT: I have tested and it's not working. Installed as O365, started to get the Small Ribbon in Outlook. Changed to Mondo License, Activated, started 3 times and the new function are gone. Also OfficeRTool wipe the 365 license completly and only installs Mondo license. EDIT2: And I tried the same for abbodi1406 Scripts on a clean machine. O365 functions only stays until it will be converted to Mondo, the change are undo. Even that C2R-R2V_10 keeps the O365 license which is still in trial mode.
OfficeRTool latest version bug??? I was downloading O365 x64, decided to manually expand the main window with my mouse to get a better look at the screen contents info during a download. The download status on each downloaded file goes a bit weird. I'll need to post a screenshot tonight.
It's a glitch between 3rd-party download module "wget.exe" and windowed OfficeRTool. I'm not able to control wget output of the progress bar, hence I defined a corresponding window for OfficeRTool to mostly fit (output varies due to length of path- and filename). Now if you change window size, progress bar output is getting "weird". This goes on until the next file to download is shown. So I suggest to leave window size as is. But if you want to change window size: Edit lines #43, #103 and #488 in OfficeRTool.cmd. (And don't forget to tell your Antivirus that it was a intended change .)
I just stumbled upon a potential answer to the problem you describe from the other office 2019 thread. And no, I have not personally tested out this guy's findings, but I may run a virtual install soon. I'm just now in the process of deciding if I'm going to bother "updating" from 2016. I've just skimmed the post, but I think the crucial solution comes from: Exploiting the ability to install both retail (to add and keep 365 features) and volume licenses (KMS) in Office. Also, keeping new features seems to require either injecting registry keys (offline) or allowing office to remain connected to the internet (not blocking MS office telemetry) "If you install Office 365, then inject a volume license product key (such as Office Mondo’s), you’ll be able to KMS activate Office AND use the Office 365 features, because Microsoft will think you have Office 365 and install the appropriate registry configs! It won’t matter if your Office 365 grace period expires either." As of March 2019 (when the post was last updated), C2R-R2V will install the Office Mondo key while keeping the Office 365 grace key intact. I don't know if other solutions (YAOCTRI, or OfficeRTool) also have this ability -- perhaps the developers of these programs can confirm? If one of you guys has your virtual machine 'pipeline' ready to go, than you should be able to quickly see if this guys answers are still valid. It's a very detailed, but clearly written post. Please let us all know if this 'method' solves your problem! https://forums.mydigitallife.net/th...nstall-activation.62571/page-157#post-1505161
Thanks for info. By following those steps looks like I did manage to keep Office 365 features active on a PC. Grace period set to 4 but office activated for 180 days.
All working fine for me with O365 features are active. Start clean: 01 OfficeRTool (Down and install O365) 02 C2R-R2V (Convert it to Volume) keeps grace key intact. 03 KMS_VL_ALL (Activate it) Make sure you are connected to internet, launch individual office apps, close and reopen it again, O365 features will pop up and stay.
OfficeRTool falls apart spectacularly on an ARM64 machine, as it seems to detect the processor's address width (which reports 64) and then based on that, runs an x64 program (which doesn't work on arm64, only x86 does!). I don't think anybody's noticed this until now. Hope there's a fix in the next version! (consider using the PROCESSOR_ARCHITECTURE cmd variable instead of a wmic call for address size. that might fix up the issue) edit: in fact, arm64 support doesn't exist at all. it's not even selectable as an architecture to download, even though it very much exists.