It's a complete operating system change. Depending on Win7 installed software basis, everything from no impacts to complete KMS activation malfunction can happen after upgrading Win7 system to Windows 10. From own experience in such a case, I always suggest to install Windows 10 fresh from scratch and not to use an upgraded system. And this always was a good advice. It pays, spending time to re-install OS and software. Of course all KMS activation solutions such as MTK, KMS_VL_ALL, KMSPico and all others (O2016RTool) work with Windows 10.
Propably, since Office licensing service differ between two OSs but it's easier to just uninstall autokms, upgrade, then re-install
I don't really agree that it is a complete operating system change, because Windows 10 is supposed to run everything Windows 7 can run, including drivers and apps which use different services. If Office 2016 does not create new services after the upgrade, it should not be able to break activation. The question is if Microsoft implemented such a switch or not. I think I will test it out. It's a matter of preference, but I do not like Windows 10 and I prefer to spend double the effort to install Windows 7 first.
If I don't uninstall autokms before upgrading, can I uninstall it after I upgrade? Edit: Office 2016 licensing services should only be created during install, but I'm not sure if there are any triggers implemented by Microsoft if one upgrades to Windows 10.
Hi everyone, Suppose I installed the Microsoft Office 2016 Professional Plus VL 16.0.4266.1001 (x86 / x64) [En] using the MTK 2.6.2. Would I have to deactivate automatic windows update in the future to possibly prevent detection that I am using an unlicensed version? Thank you!
Why don't you use your configuration.xml with that installer? it seems to accept it: Code: setupproplusretail.x86.en-us /? Office Deployment Tool SETUP [mode] [path] SETUP /download [path to configuration file] SETUP /configure [path to configuration file] SETUP /packager [path to configuration file] [output path] SETUP /help /download Downloads files to create an Office installation source /configure Adds, removes, or configures an Office installation /packager Produces an Office App-V package from an Office installation source /help Displays this message
Just curious: Did you try to use your HUP-keys to activate a regular C2R ProPlus install? You could use standard ODT and your configure.xml file for download and install.
With a little more patience waiting for download/install to finish, he should have got an activated Office corresponding to the HUP key. I wish luck to him.
Just for info regarding "Office not being detected" (problem from user Fortune, see some of the above posts): It turns out, that "Kaspersky Internet Security" was found to be guilty for that behavior. This (AV interference) is mentioned in pos. 1.) of post#4 "Causes for Office install errors". File "O2016RTool.cmd" and O2016RTool's folder must be excluded from AV's program activity scanning. MS-Defender does not show such a behaviour at the moment and therefore can stay active.
So, it doesn't accept it. Tried all /download /configure, etc, just shows the same /help information. However, I dragged the xml onto the exe, and it did run (i already have office installed on this pc, so i couldnt test further). wonder if that would work..
Doesn't work either, installed full suite. Oh well. Gonna test again the first method (where Office offered to "update product")
Hi, I was advised to ask for support here, so here is my question : On my PC, I first installed and EZ-activated Office 2010 VL. Later, I installed and EZ-activated Office 2016 VL. I had both installations activated and running fine. But now for some reason, Office 2010 tells me it's not licensed. MS Toolkit's check button seems to only know about Office 2016. Pressing "EZ-Activator" indeed did nothing for Office 2010. Is there a way to re-KMS-activate Office 2010 ?
I don't recommend using two Office Suites together on the same system. Even if you may get them running, the next update could (and most probably will) destroy this shaky construct. You could try KMS_VL_ALL (see post#4) or the License-Manager from hotbird64. Maybe one of these will help re-activating Office 2010. But for a hassle-free future, you should consider using only one Office Suite or you create a virtual machine and run the other Office from there.
I installed these one : SW_DVD5_Office_Professional_Plus_2016_64Bit_English_MLF_X20-42432.ISO on two machines. But Office 2016 doesn't appear in Windows Update any more.