I started looking through my Odyssey G65B’s service menu because the CRT-style startup animation and pop-ups were bothering me. I disabled the Game Bar and EU energy pop-ups, exposed the Peak Brightness setting, and got Cyberpunk 2077 to trigger HDR10+ Gaming over HDMI. My test setup was a G65B, RTX 4060, and Windows 11.
How I opened the service menu with ColorControl
I enabled IP Remote on the G65B and paired it in the Samsung Controller tab of ColorControl 11 using the secure connection. With the monitor on, I sent KEY_INFO followed by KEY_FACTORY from ColorControl. That opened Samsung’s service menu. The settings below are under FMS → Factory Menu App.
Photograph the original values before editing anything. Menu paths can vary by firmware. Avoid factory reset, panel type, white balance, and calibration actions.
What I changed in FMS
The full feature keys below start with com.samsung/featureconf/.
- Game Bar auto-popup — In Option → MRT Option, I set
game_bar.auto_launch_support_type to FMS_AUTO_LAUNCH_NOT_SUPPORT. - EU energy prompts — In Option → Production Option, I set
setting.eu_energy_regulation to false. - Peak Brightness — In SVC → Other Setting → Expert, I enabled
product.peak_brightness to expose the picture control. I didn’t measure a brightness gain. - HDR10+ Gaming — In Option → MRT Option, I enabled
setting.menuitem.game.hdr10plus_gaming_support to expose the monitor setting. The PC still needed the EDID override described below.
For the startup animation, welcome_mode.effect_type showed FMS_WM_EFFECT_DEF, FMS_WM_EFFECT_PROJECTOR, and FMS_WM_EFFECT_MLED. There was no visible Off option, and I didn’t verify a way to disable it.
How I edited the HDMI EDID
My original HDMI EDID didn’t advertise HDR10+ Gaming. I added an HDR10+ Source Side Tone Mapping (SSTM) data block to EDID block 1, the first CTA-861 extension on my unit. This was a Windows override.
- Back up your HDMI EDID and existing overrides. Identify the active HDMI entry for your monitor in Custom Resolution Utility (CRU) and export its EDID. Back up any existing registry override separately. Have DisplayPort or another screen available in case HDMI goes black.
- Locate the CTA-861 extension. On my EDID, it was the 128-byte block starting at file offset
0x80. The first byte was 02. Within that block, byte offset 2 points to the end of the data-block collection and the start of the detailed timing area. Offsets here are zero-based. - Add the SSTM data block. Insert
E5 01 8B 84 90 59 at that detailed timing offset. Shift the existing timing data six bytes later and use six bytes of trailing zero padding immediately before the checksum to keep the extension 128 bytes long. Increase the offset stored in byte 2 by six. Recalculate checksum byte 127 so the sum of all 128 bytes is zero modulo 256. Preserve the other EDID blocks and existing CTA data blocks. If your layout differs, there’s already an HDR10+ vendor block, or there isn’t enough padding, stop and inspect your EDID before applying these steps. - Apply only the patched extension. I wrote the edited 128 bytes as the
REG_BINARY value named 1 under HKLM\SYSTEM\CurrentControlSet\Enum\DISPLAY\<your HDMI monitor instance>\Device Parameters\EDID_OVERRIDE. Use your own HDMI instance and administrator rights. If a value named 1 already exists, save its exact bytes before replacing it. Microsoft’s EDID override documentation - Reload and verify. Reconnect HDMI or use CRU’s
restart64.exe to refresh the graphics driver. A monitor-device restart alone sometimes left NVIDIA using cached EDID data on my PC. Check that your usual resolution, refresh rate, and VRR are still available.
The final byte, 59, represents 600 nits peak and 240 nits full-screen in this test. Those were approximations based on my original EDID. They aren’t colorimeter measurements or calibration values I’d recommend copying to another monitor.
To roll back, restore the previous binary value 1 or remove that value if you created it. Then reconnect HDMI or refresh the graphics driver. Preserve your other overrides. If the screen stays black during a CRU driver restart, CRU documents an F8 recovery mode that temporarily unloads overrides. CRU instructions and recovery
What I actually saw
HDMI: With the override installed, I set the monitor’s HDR10+ Gaming option to Basic and started in regular HDR10. When I enabled HDR10+ inside Cyberpunk 2077, the monitor’s Info panel showed HDR10+ and Samsung’s Game Bar showed HDR10+ Gaming. I didn’t force NVIDIA mode 2 for that Cyberpunk test. While the mode was active, Game HDR (HGiG) was greyed out. Switching HDR10+ Gaming from Basic to Off dimmed the image. An earlier manual test had shown Mode Not Supported.
Here are the photos from Cyberpunk: https://imgur.com/a/db7JCgO
DisplayPort: With a separate DP override, NVIDIA reported HDR10+ Gaming capability and accepted mode 2. ColorControl showed that mode, but the monitor itself never showed HDR10+ Gaming over DP. I restored my previous DP settings and verified that regular HDR10 was back. NVIDIA’s HDMI-only guidance
The photos show the monitor’s indicators during a manual HDMI test. The Cyberpunk test was separate. Together, the tests show that my G65B recognized the mode over HDMI. I haven’t measured its tone curve or verified HDR10+ movie metadata passthrough from a Windows player.
If anyone reproduces this, I’d be interested in your G65B size, firmware, GPU, game, and what the monitor’s own Game Bar reports.
Edit: Added Cyberpunk proofs.