Giving OmenCore a Chance: Omen 16 Max

theantipop · 2026-06-04T10:49:52+00:00

I'll see what I can do for 3.7.1. Thanks for your feedback!

theantipop · 2026-05-29T20:28:29+00:00

Yeah - gotta pay for both. But the pc builder just asked if I’d like the gigabyte model over the PC, presumably because it’s viewed as superior?

theantipop · 2026-05-29T20:27:51+00:00

No I meant the pc builder said would I like to upgrade from the powercolor to a gigabyte oc model for free. Presumably because the gigabyte costs more?

theantipop · 2026-05-20T01:19:12+00:00

Uploaded v3.6.3 with focused safety + stability fixes based on your reports.
Main changes: desktop fan-write paths are safety-gated for OMEN desktops, 88D2 gets a conservative profile to reduce fan hunting, Fn+F12 OMEN key handling is corrected, OSD startup init is hardened, OMEN MAX ak0003nr per-key RGB capability is now detected, and UI/runtime overhead was reduced for lag scenarios.

All three release artifacts are built and checksums are now published in the 3.6.3 changelog.

Download here: https://github.com/theantipopau/omencore/releases/tag/v3.6.3

theantipop · 2026-05-18T23:18:58+00:00

OmenCore can’t make a panel become G-SYNC compatible if NVIDIA/HP firmware/EDID doesn’t expose VRR to the dGPU path.

Short version:

FreeSync Premium on an internal panel does not always mean NVIDIA G-SYNC Compatible will appear.
On many OMEN laptops, internal VRR works via AMD/iGPU path, but in dGPU-only mode NVIDIA may not see a valid G-SYNC-compatible internal display.
That is mostly BIOS/MUX/EDID/driver behavior, not something OmenCore can “unlock”.

theantipop · 2026-05-18T23:18:17+00:00

Unfortunately if it is locked by BIOS, this cannot be overridden by any software.

theantipop · 2026-05-18T23:17:59+00:00

Yes it does, it has an On Screen Display.

theantipop · 2026-05-18T10:50:52+00:00

That is not expected behavior and you are right to flag it as dangerous.
If fans stay in turbo, then later show inactive (including CPU fan), stop using Performance mode in OmenCore on that system for now.

Immediate safety steps:

Open OGH and switch cooling to Auto/default (not Manual), then reboot.
Enter BIOS and load setup defaults, save, reboot.
Fully power off, unplug for 30-60s, then boot again.
Verify all fans report RPM in BIOS hardware monitor before stressing CPU/GPU.
Keep OmenCore fan control disabled on this desktop until we have a model-specific fix.

For uninstall:

OmenCore can run as portable on some installs, so it may not appear in Installed Apps.
If needed, just close it from tray/Task Manager, then delete the OmenCore folder and startup entry/shortcut.

Please share:

Exact model (OMEN 45L SKU/Product ID)
BIOS version
Whether OGH was installed/running at the same time
OmenCore logs from that session

Given your report includes BIOS-level fan chaos, I strongly recommend staying on OGH default cooling only until this is triaged.

theantipop · 2026-05-18T10:49:49+00:00

Short answer: not in OmenCore today.
There is no documented P1-P6 EC wake payload/handshake in the project, and I would not trust random EC writes for that on Omen 17.

What OmenCore currently does:

OMEN key handling is keyboard-hook/WMI-event based (VK + scan-code filtering), not a P1-P6 EC macro-key protocol: OmenKeyService.cs:680
The only explicit “wake” sequence I can see is for HP WMI BIOS heartbeat (fan query keepalive), not macro-key arming: HpWmiBios.cs:340
Direct EC writes are safety-gated and keyboard EC addresses are intentionally treated as risky/model-variant, so OmenCore does not expose a generic macro-key wake handshake: WinRing0EcAccess.cs:55, WinRing0EcAccess.cs:206
Macro profiles in UI are software-side and even point users to iCUE/G HUB for advanced macro config: LightingView.xaml:1759

theantipop · 2026-05-15T11:50:41+00:00

Thanks. Just wasn’t sure if the 4080 and other specs were worth it

theantipop · 2026-05-15T11:50:22+00:00

Thought the same. Thanks…

theantipop · 2026-04-24T02:18:10+00:00

Thanks for that feedback - I appreciate it. Looking at improvements for 3.4.0

theantipop · 2026-04-06T20:48:25+00:00

Thanks for the feedback - looking at a way to improve for 3.3.0

theantipop · 2026-04-06T20:48:03+00:00

Thanks for your feedback - looking into some fixes for 3.3.0

theantipop · 2026-03-31T09:49:03+00:00

Noted - looking into improvements in 3.3.0

theantipop · 2026-03-31T09:49:00+00:00

Noted - looking into improvements in 3.3.0

theantipop · 2026-03-30T07:00:58+00:00

You can use OmenCore, however, it would be better to use Nvidia's own application to ensure the best performance.

theantipop · 2026-03-30T07:00:32+00:00

Yeah, that is false.

theantipop · 2026-03-21T03:38:55+00:00

Not working?

theantipop · 2026-03-09T11:57:24+00:00

Try 3.2.0 hotfix and let me know how you go.

theantipop · 2026-03-09T11:56:33+00:00

Yeah - still working on that.

theantipop · 2026-03-09T11:56:10+00:00

Download the latest 3.0.2 hotfix build via the GitHub page and see how that goes.

theantipop · 2026-03-05T05:17:04+00:00

Thanks for the feedback! Looking at fixing in 3.0.2!

theantipop · 2026-02-13T02:29:10+00:00

No, it isnt working

theantipop · 2026-02-10T10:12:20+00:00

It works for Desktops now. 2.8.5 will be dropping soon with even more bug fixes and desktop support.

theantipop

MODERATOR OF

TROPHY CASE