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
Use ohook Activation Office 365 issue #315
Comments
It shouldn't show activation failure in any account. Let me know if you think that is not the case with relevant screenshots of error and ohook script screenshot. |
The problem occurs in the Microsoft 365 version pre-installed on the laptop. It is indeed a banner verification failure. If it is a known problem, you can only run ohook once. Thank you. |
If possible, please run ohook option and share a screenshot. Need to check something. |
As expected, you are using O365 Homeprem edition. I'll edit C:\Users\Default\NTUSER.DAT so that on new user account creation, Resiliency key will be auto-applied to solve banner issue. |
OK, thank you~ |
I see the same thing in a Win11 machine with 365ProPlus. Then ran Ohook 0.4 from MAS 2.3 on the Administrator user and all the other accounts are working fine since then. Official clean Win11 23H2 and ProPlus C2R - nothing else installed. |
@gthb96 |
Could be, not sure.If that would explain it and is expected, I probably did.Ohook 0.4 is safe or is there a real reason for AV detections you know of?If 0.4 is fine I just keep it like that.Am 14.12.2023 um 21:58 schrieb WindowsAddict ***@***.***>:
@gthb96
Did you login to the new non-admin user accounts before running the Ohook script in the administrator user account?
|
it wont let me use macro xD it says please select a school or work to identify as primary etc blah blah xD account. |
@TomieAi your issue is not related to this, create a new issue. |
use ohook to activate office 365 OK, but when you switch to a new account, the new account office will prompt an activation failure problem. need to re-run ohook. Is there any way to solve this problem?
The text was updated successfully, but these errors were encountered: