abbodi1406 / KMS_VL_ALL_AIO

Smart Activation Script
GNU General Public License v3.0
8.13k stars 1.08k forks source link

Non Genuine Office 2016 Pro Plus Warning #7

Closed SpaceBallz2k8 closed 3 years ago

SpaceBallz2k8 commented 3 years ago

Everything was fine yesterday, today I have a non genuine notice popping up whenever i start office. Its still activated but warns me I might be a victim of piracy. Maybe one of the VL keys has been flagged

abbodi1406 commented 3 years ago

https://infohost.github.io/office-license-is-not-genuine

greatquux commented 3 years ago

Yeah, the problem has generally been that if you install Office 2016 or 2019 from a retail ISO, then convert to VL, the update channel and the product don't match. Those two things get out of sync, and this is what Microsoft detects and complains about. If you follow those instructions to install 2019 using the ODT (or you have a VL ISO for 2016 and use that), then the channel stays on Perpetual2019 (in 2016 case it's using MSI patches) and there is no warning. Unfortunately, I don't know of any way to switch the channel to Perpetual2019, just have to uninstall and use the ODT if you want to stick to 2019. Or use those channel changing commands to get on 365 MonthlyEnterprise channel, which I guess does it in such a way to change the installed product from 2019 to 365?

WindowsAddict commented 3 years ago

Unfortunately, I don't know of any way to switch the channel to Perpetual2019, just have to uninstall and use the ODT if you want to stick to 2019. Or use those channel changing commands to get on 365 MonthlyEnterprise channel, which I guess does it in such a way to change the installed product from 2019 to 365?

We can't change the update channel to/from Perpetual2019 VL To avoid the banner, Monthly Enterprise channel can also be used on any product, which won't require reinstallation of the Office.

SpaceBallz2k8 commented 3 years ago

Thanks for the replies everyone. I'll follow the guide

Macleykun commented 3 years ago

@SpaceBallz2k8 don't forget to close the issue ;)