search

Scrut1ny / Malwarebytes-Premium-Bypass

Confuse Malwarebytes
307 stars 50 forks source link

Trial Reset Failed #11

Closed deltaxsingh closed 9 months ago

deltaxsingh commented 9 months ago

Powershell script indicates

Last Run Status: Malwarebytes Trial Reset Failed. Last Result: 267011

Scrut1ny commented 9 months ago

This is a simple logic error or something, the script works just fine though. It throws this error no matter what for some reason.

@ammarsaa can assist you with this.

deltaxsingh commented 9 months ago

Is it? Because when the scheduled task runs, it reverts MB back to "free" and I need to manually run the bat file, launch MB and click "try for free". I tested this several times.

Scrut1ny commented 9 months ago

yeah that's what it's supposed to do, when it runs it spoofs the GUID and MB no longer recognizes you so it reverts back to free mode and then all you gotta do is click the "Try now for free" button, and premium is reactivated. That's the process.

deltaxsingh commented 9 months ago

For further clarification, I'm saying neither the scheduled task nor the PowerShell script do not do this.

Only manually running the .bat results in a reset.

Scrut1ny commented 9 months ago

Interesting, I personally just tested it and the powershell script created the scheduled task and when I ran the scheduled task it spoofed the GUID successfully...

Only "issue" I'm getting:

Last Run Status: Malwarebytes Trial Reset Failed. Last Result: 267011

I just want to let you know I didn't program the powershell script, @ammarsaa did.

AmmarSAA commented 9 months ago

Last Run Status: Malwarebytes Trial Reset Failed. Last Result: 267011

267011 This value means that the task has not yet run but has been created successfully and waiting to be run.

P.S. Script has been updated. Current Up To Date Branch: Here Pull Request: https://github.com/Scrut1ny/Malwarebytes-Premium-Bypass/pull/12

Scrut1ny commented 9 months ago

Thank you for the update @ammarsaa! @deltaxsingh hopefully your issues have been resolved with this update, if not let us know.