Skip to content

Recommendation

Depends

On a personal gaming PC, the block can be enabled if you do not need OEM management.

On a corporate or specialized device, first determine the purpose of the manufacturer’s component.

Scope
OEM code from UEFI firmware
FPS and memory
FPS is not affected

WPBT (Windows Platform Binary Table) is a UEFI mechanism: a hardware manufacturer can place a binary component in the firmware, which Windows receives and executes at boot. This is how OEMs deliver low-level tasks tied to the hardware and automatically install their branded utilities.

The BoosterX setting blocks the supported execution of such code: automatic installation of manufacturer software stops. The mechanism itself remains in the firmware — what changes is Windows’ reaction to it.

Why the tick is under “Legacy”: the need is rare and narrowly OEM-specific. On a home gaming PC, the block is usually safe; on a corporate or specialized device, first determine what component the manufacturer uses. According to the visible description, BoosterX is more reliable to disable OEM code autostart directly in BIOS/UEFI, if such a function is available there. After enabling the block, you can remove the manufacturer programs and services that are already installed.

After enabling the block and rebooting, check the manufacturer’s branded utilities: updates, device management, branded centers. If a needed function is gone, revert the setting. The block does not provide an FPS increase.

In BoosterX, open “Optimization” → “Legacy” → “Windows Platform Binary Table”, move the toggle to the “Off” position to apply the block (the “On” position restores the standard execution of OEM code), and click “Apply”. If “Instant apply” is enabled, a separate click is not required. Reboot and check the branded functions.

Last checked: 2026-09-20.