How to Fix the 2.19 GHz CPU Lock Bug on Snapdragon X Elite Laptops (Galaxy Book4 Edge)

If you recently performed a clean installation of generic Microsoft Windows 11 ARM64 on your shiny new Samsung Galaxy Book4 Edge (or another Snapdragon X Elite laptop), you might have noticed a frustrating bottleneck: your CPU clock speed is completely stuck at exactly 2.19 GHz.

No matter how many times you change the Samsung Settings app to “High Performance,” cycle your Windows power modes, or throw heavy stress tests like Cinebench at it, the clock refuses to budge past that 2.19 GHz ceiling.

Here is exactly why this happens and the definitive terminal command to fix it.

The Symptom: Stuck at 2.19 GHz

You open Task Manager or HWiNFO64 under a heavy workload. Your CPU utilization might spike, but the speed indicator sits perfectly frozen at 2.19 GHz. Even stranger: if you drop down to “Power Saver,” the speed fluctuates lower, but the moment you demand maximum power, it slams into an invisible wall at 2.19 GHz.

How to Diagnose the “Smoking Gun”

To prove this is a hardware-level lockdown rather than a simple visual bug, check Windows Event Viewer:

1. Right-click the Start button and select Event Viewer.
2. Navigate to Windows Logs > System.
3. Click Filter Current Log… in the right-hand sidebar.
4. Type 37 into the <All Event IDs> field and click OK.

If you see a flood of warning events stating: “The speed of processor X in group Y is being limited by system firmware,” your motherboard’s Embedded Controller (EC) is actively throttling the chip.

Why a Clean Windows Install Breaks the Power Management

On traditional Intel or AMD x86 laptops, a clean Windows ISO handles standard CPU power states reasonably well out of the box. Snapdragon X Elite architectures operate completely differently. They rely on an incredibly tight three-way handshake:

• Windows Kernel Power Engine Plug-in (PEP)
• Qualcomm Collaborative Processor Performance Control (CPPC) driver
• The Manufacturer’s Embedded Controller (EC) firmware

When you format your drive and install a generic Microsoft Windows 11 ARM64 ISO, you completely wipe out the original OEM Provisioning Packages (.ppkg) and extension drivers.

Even if you manually run through Device Manager to install baseline drivers afterward, Windows often maps generic Microsoft driver stubs instead of the custom manufacturer calibration profiles. Because the Qualcomm CPPC driver cannot establish a secure, calibrated handshake with the motherboard, the laptop enters a protective fallback state. It treats the environment as uncalibrated and caps the processor at its safest base hardware clock: exactly 2.19 GHz.

The Fix: Force-Injecting the True OEM Driver Stack

Updating drivers one by one via Device Manager frequently fails because Windows assumes its generic stubs are “already the best driver.” The definitive solution is to use the Windows Device Console (pnputil) to force-inject the entire factory driver framework—including the vital extension .inf files—back into the Windows image.

Step-by-Step Guide

Step 1: Gather the Factory Drivers

Make sure you have your laptop’s official factory driver package downloaded and extracted into a folder on your main drive (for example, C:\Drivers).

Step 2: Open an Administrator Terminal

1. Click your Windows Start button and type cmd.
2. Right-click Command Prompt from the results and select Run as administrator.

Step 3: Run the Pnputil Injection Command

Copy and paste the following command into your terminal window. Make sure to replace C:\Drivers with the exact path to the folder where your extracted driver files live:

DOS

pnputil /add-driver "C:\Drivers\*.inf" /subdirs /install

Step 4: Let Windows Re-Map the Architecture

Hit Enter. Windows will force-scan every single subfolder in that directory. It bypasses the standard installer restrictions and directly links the custom manufacturer configurations to their corresponding Qualcomm hardware IDs.

You will see it rapidly installing the core missing links, specifically:

• Qualcomm Power Engine Plug-in Device (PEP)
• Qualcomm Collaborative Processor Performance Control (CPPC) Device
• Qualcomm System Manager

Step 5: Clean Cold Reboot

Once the terminal finishes running, restart your laptop. To ensure the hardware completely reinitializes its power states, it is best to perform a full shutdown rather than a warm restart. Run this command in your prompt:

DOS

shutdown /s /f /t 0

The Verdict

Once your laptop boots back up, open Task Manager or HWiNFO64 and throw a multi-threaded task at it. With the proper handshake restored between Windows, the Qualcomm chip, and the Samsung firmware, you should instantly see your clock speed dynamically break past the 2.19 GHz barrier and spike up to its native turbo boost frequencies.