Skip to content

Omen Gaming Hub Unlocker v3.0

Choose a tag to compare

@Avazbek22 Avazbek22 released this 15 Mar 16:34
· 24 commits to main since this release

Highlights

  • Added a real Reset OMEN app and reapply taming flow.
  • The reset now behaves like a Windows app reset and then immediately reapplies the tool's restrictions, which is especially useful after OMEN updates or lockouts.
  • Improved activation stability with extra post-reset and post-activate cleanup passes.

Fixed

  • Fixed Dry Run so it now performs the full deep inspection path.
  • Fixed a false WARN case where the unlocker could detect its own process as an OMEN process.
  • Fixed rollback behavior. Disable now restores the previously captured state instead of forcing generic defaults.
  • Improved task handling for cases where OMEN recreates temporary scheduled tasks after reset.
  • Improved external command execution and timeout handling to avoid hangs.
  • Improved service start mode changes by validating the real operation result instead of assuming success.

Reliability Improvements

  • Added a safer backup/restore model for modified services, scheduled tasks, and Run entries.
  • Improved process termination and stabilization logic around reset and activation flows.
  • Improved status reporting so the console output better reflects the actual system state.

UI and Documentation

  • Added a new Help screen.
  • Simplified the help text so each menu action is easier to understand.
  • Moved Help/About content out of UI code into separate embedded documentation files for cleaner maintenance.

Code Quality

  • Performed a broad refactor and formatting pass focused on cleaner structure, clearer naming, and safer error handling.
  • Added a proper .gitignore to keep repository noise out of source control.
  • Expanded automated test coverage across core logic, dry run behavior, process handling, console rendering, state storage, and Windows integration checks.

Release Package

  • Published as a self-contained single-file Windows executable.
  • No external runtime is required.
  • Administrator rights are still required for system-level operations.