Switching an HP computer from Legacy mode to UEFI mode (or vice versa) is not just a matter of checking a box in the BIOS. The process involves the firmware, the disk partition style, and the secure boot chain.
Before making any changes, it is essential to assess the gap between the current configuration of the machine and what the target mode requires. This guide details the preliminary checks, the procedure in HP firmware, and the concrete risks of a poorly prepared change.
Further reading : How to Access Your Academic Webmail: Examples and Steps in Montpellier
Legacy or UEFI on HP: Concrete Differences in Firmware
| Criterion | Legacy Mode (CSM / Legacy Support) | Native UEFI Mode |
|---|---|---|
| Partition Table | MBR (Master Boot Record) | GPT (GUID Partition Table) |
| Secure Boot | Unavailable | Available and can be enabled |
| Old Hardware Compatibility | Unsigned graphics cards or devices recognized | Unsigned devices potentially blocked |
| Windows 11 Compatibility | Not supported (updates blocked) | Required by Microsoft |
| Boot Speed | Slower (sequential initialization) | Faster (parallel initialization) |
On HP machines shipped with Windows 10 or 11, secure boot is enabled by default. Disabling Secure Boot to revert to Legacy allows booting from an unsigned external medium or using older hardware, but it breaks the trust chain that Windows 11 requires for its updates.
The procedure to enable legacy support on HP always starts with identifying the currently configured mode and the partition type of the system disk. Without this verification, the risk of getting stuck during reboot is real.
Further reading : What to Do if Your Package is Held in UPS Warehouse: Practical Guide and Useful Contacts
Check Boot Mode and Partition Before Any Changes
Two pieces of information determine the success of the change: the active boot mode and the partition style of the main disk.
Identify the Current Boot Mode
Open the Run dialog (Windows + R), type msinfo32, and press Enter. In the System Information window, the “BIOS Mode” line displays either “UEFI” or “Legacy.” This information determines whether the firmware is already running in UEFI or using the legacy compatibility layer.
Check the Disk Partition Style
Open Disk Management (right-click on the Start menu). Right-click on the system disk, then Properties, Volumes tab. The “Partition Style” line indicates MBR or GPT.
- If the disk is in MBR and the current mode is Legacy, switching to UEFI requires converting the disk to GPT before modifying the firmware, or Windows will become unbootable.
- If the disk is already in GPT and the mode is UEFI, switching to Legacy without reverse conversion will cause the same blockage.
- The mbr2gpt command built into Windows allows this conversion without data loss, but it must be executed from the Windows Recovery Environment (WinRE) and not from a regular session.
Any inconsistency between the partition style and the boot mode prevents Windows from booting. This is the most common cause of black screens after a change in HP firmware.
Procedure in HP BIOS: Access and Navigation
The firmware menus vary depending on the HP range (consumer laptop, professional laptop, workstation, desktop). The logic remains the same, but the location of the setting changes.
Access the Firmware on a Consumer HP Laptop
Completely power off the machine. Press the power button, then repeatedly press the Escape key until the HP startup menu appears. From this menu, select the key corresponding to BIOS Setup (usually F10).
Locate the Boot Mode Setting
In the BIOS menu, look for the System Configuration or Boot Options tab. The setting appears under different names depending on the generations of HP firmware:
- “Legacy Support” or “Legacy Support”: enables CSM compatibility mode.
- “UEFI Boot Order” or “Legacy Boot Order”: determines the boot order in the selected mode.
- “Secure Boot”: can only be enabled if Legacy Support is disabled. The two settings are linked, and HP displays a warning if the chosen combination is inconsistent.
After modification, HP firmware often requests confirmation by entering a code displayed on the screen. This confirmation code is a specific HP security feature that prevents accidental changes. Do not confuse it with a BIOS password.
Risks and Precautions When Changing Legacy to UEFI on HP
Changing the boot mode affects the lowest layer of the system. Several situations can cause a complete blockage.
An MBR disk associated with firmware switched to UEFI produces a black screen or a “No boot device found” message. The machine can no longer find the Windows bootloader because the UEFI firmware cannot read an MBR table. The solution is to return to the firmware (Escape key then F10) and restore the previous mode, then convert the disk before retrying.
Enabling Secure Boot after switching to UEFI may block the booting of unsigned USB devices, including some recovery drives created with third-party tools. HP specifies that Secure Boot is meant to prevent the use of unverified hardware or boot media. Before enabling this option, ensure that the recovery media is UEFI compatible.
On HP professional machines (ProBook, EliteBook, Z series workstations), the BIOS may have an administrator password. Without this password, no changes to the boot mode are possible. This lock protects enterprise fleets from unauthorized changes.
When to Stay in Legacy Instead of Migrating to UEFI
Switching to UEFI does not always make sense. If the machine uses an old graphics card whose drivers are not signed, UEFI mode with Secure Boot enabled may render it unusable. HP indicates that disabling secure boot remains necessary to use trusted but unrecognized hardware.
Similarly, a system running Windows 10 that will not be migrated to Windows 11 gains no functional benefit from switching to UEFI. Disk conversion and firmware reconfiguration pose a risk without any return on investment for an end-of-life machine.
Changing the boot mode on HP requires as much preparation as execution. Checking the partition style, precisely identifying the setting in the firmware, and having recovery media compatible with the target mode: these three conditions determine whether the switch ends with a normal reboot or a black screen.