-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HWID method for Office 365 apps #481
Comments
|
So in other words, HWID license cannot be applied to Office because Office activation status is gained from server side and an Microsoft account already needs to have linked license/product key that will be downloaded by Office programs and if valid to flag Office apps as activated. So, everything is server-side while Windows 10/11 provides ability to trick activation status, sent it to servers and servers will automatically in server-side generate an digital license for specific hardware and link it to Microsoft account so that everytime if the hardware is the same can be automatically re-activated with digital license (simply via connecting to the internet and linking Microsoft account with PC) |
Yes, the digital license concept doesn't exist for Office. |
Can we instead of breaking HWID and replacing it with KMS servers to activate both Windows and Office 365 to actually keep HWID method, not register our host machine to the KMS servers and still somehow via HWID method to activate Office 365 too.
Is there any way how Office 365 can be patched so that we don't need to gave up on HWID Windows activation just because of Office 365 or not and why not or why it can be done.
Thanks in advance for explaining the HWID method and exploit possibilities!
The text was updated successfully, but these errors were encountered: