Discussion in 'Microsoft Office' started by Edward266, Oct 2, 2015.
Thanks, corrected my post.
I suppose that once I got the 'C:\Program Files\Microsoft Office\root\Licenses16' folder backed up, i can also do a clean installation of W10 (Retail key), install office 2016 with VL ISO, and follow your instructions to insert the Retail license of office 2016?
Yes, I think that should be fine.
At least with Windows 10 this did not work. I tried before with an installed Windows 10 and Office 2016 VL.
In both cases I followed the list but ended up with every Office application crashing after die Dialog box to choose the update behavior from.
The ospp.vbs /dstatus reports it is now retail but also that there are 29 days grace period remaining, ignoring the accepted key.
Any ideas ?
IIRC that crash on startup is an unrelated problem, it was mentioned in the beta tests. Paste the following into a text file, name it crashfix.reg and merge it into the registry:
Windows Registry Editor Version 5.00
It's probably still showing you're in the grace period because you've not yet activated.
Windows Registry Editor Version 5.00
So, it mean there is no any manual way to convert a office 2016 pro retail C2R to a VL?
abbodi's Retail2VL converter in my sig will do the job for you.
Guys ive been asked to come to this thread to understand how i remove all traces of the O2016Tool inc KMS server?
I dont mind reinstalling office from scratch, i need to get shut of the KMS server please?
I think that I and/or you may have misunderstood my suggestion to come here to this thread.
You asked what to do to use a legit Office 2016 key instead of VL KMS-activation and how to get id of O2016RTool
and it's KMS-server.
O2016RTool and its included KMS-Server can simply be removed by deleting the folder you saved the files. Nothing
more must be done. So this is the (already given) answer to the second part (remove O2016RTool and KMS).
The first part (how to use legit Office key) is handled in this thread, so I suggested to move here.
You said now, that you don't mind installing Office totally new.
You can use Office 2016 VLMSC ISO, then you need VL to Retail conversion as described here.
Or you just take Office 2016 MSDN-Retail ISO and enter your legit Office key and all is set.
Clearly my understanding of the KMS is non existent. So deleting the folder would then assume that there has never been a KMS server running in the background on my system, other than when authenticating the install ?
YES, in case of O2016RTool that's correct. Here nothing is installed or permanently running as service in the background. Other KMS-solutions may work different.
ok cool - now you can see why ive over complicated a simple question.
Appreciate your support - thank you
Is there a way to convert from Retail to Volume License Manual and How can I Convert Office 2016 from Retail to Volume License Manual, please ?
Thanks in advanced
If you're talking about converting a retail ClickToRun install to VL, there's a tool to do that for you which was mentioned earlier in this thread.
If you wanted to do it manually for some reason, you could follow the guide I posted, but when you reach step 6 instead of deleting the VL license files, delete the non-VL licenses. But that's only for VL ProPlus, not other kinds of VL licenses, you'd be better off using the tool.
Thanks for your info and help.
What about switching C2R ProductKeyChannel via registry?
This doesn't work for me. I installed VL ran CleanOSPP.exe from admin CMD and then ran the next thing. Opened Office and a configuration window opened up. It failed. Could not enter new CD KEY in the gui. Entering it in CMD caused Office to have two different versions. One activated (retail) and another saying "office is not activated"
You don't use the GUI at all, or it will fail. I'm not sure what you've done to get it partially activated ("two different versions?"), but start over, and only install the licenses you want to activate.
It worked. However, I have a bunch of updates that were installed twice some even four times...
Sorry, I've no idea what's going on there. Maybe your Windows Update needs fixing.