# US 2026/0099336 A1 · Remotely controlled bootloader using secure messages from sever

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0099336 A1
- Document ID: US20260099336A1
- Status: Published application
- Kind: A1
- Application number: 19/230,948
- Filed: 2025-06-06
- Published: 2026-04-09
- Earliest claimed: 2024-10-08
- Assignees: Absolute Software Corporation
- Applicants: Absolute Software Corporation
- Inventors: Eric WHEATLEY; Jeffrey BUSH; Eugene KHORUZHENKO; Pradeep SURGIMATH; Marcel LAFORCE; John HERREMA; Nicholas B VAN SOMEREN
- Web page: https://patentgrep.com/patent/US20260099336A1

## CPC

- G06F 11/1417: {Boot up procedures}
- G06F 9/4406: {Loading of operating system}
- G06F 9/4416: {Network booting; Remote initial program loading [RIPL]}
- H04L 63/04: {for providing a confidential data exchange among entities communicating through data packet networks}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- G06F 2201/805: Real-time
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A booting process on a client device in a client/server network, in which a custom bootloader is installed in place of a standard bootloader for an operating system of the client device. The method includes receiving a signal instructing the client device to boot; writing UEFI variable(s) from the signal on the device; evaluating the UEFI variables. When the UEFI variables do not identify a security flag, the custom bootloader performs a direct boot to the operating system. When the UEFI variables identify a security flag, the custom bootloader executes one of a programmed bootloader process to determine whether: a correct boot sequence involves a separate bootable image present on the client device; or to connect to the server and receive a correct playbook for execution. The method also includes executing one of the separate bootable image or the correct playbook to boot the operating system.

## Claims

### Claim 1

A method of booting/rebooting a client device, in which a custom bootloader has been installed on the client device that is configured to issue one or more instructions that supersede one or more instructions issued by a standard bootloader currently installed at the client device, the method comprising:
receiving a signal instructing the client device to update unified extensible firmware interface (UEFI) variables and reboot;
writing one or more UEFI variables based on the received signal;
evaluating the one or more UEFI variables to identify if a security flag has been set;
provided
the security flag has been set, the custom bootloader executes a process to determine whether
a desirable boot sequence uses a separate bootable image present on the client device; or
to connect to a deterministic network endpoint and receive a desirable playbook for execution at the client device, and
executing one of the separate bootable image or the desirable playbook to boot the client device into an operational state.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the signal originates as a message in a secure format from the network or from another program or API call on the client.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising determining whether a sender and content of the signal is trusted by performing signing and cryptographic tests on the client.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the one or more UEFI variables are written in a secure messaging format.

### Claim 5 (depends on 1)

The method according to claim 1, wherein the deterministic network endpoint comprises a server and the client device connects to the server at a pre-OS level and, upon connecting to the server, the client device is authenticated to the server.

### Claim 6 (depends on 5)

The method according to claim 5, wherein the authenticated client shares data with the server about the current state of the client device.

### Claim 7 (depends on 6)

The method according to claim 6, wherein the data includes values of the one or more UEFI variables, and the method further comprises deriving the desirable playbook on the server based on the shared values of the one or more UEFI variables.

### Claim 8 (depends on 7)

The method according to claim 7, wherein the desirable playbook comprises at least one of a desirable boot sequence and a desirable bootable disk image.

### Claim 9 (depends on 8)

The method according to claim 8, wherein the desirable playbook further comprises a set of variables or instructions evaluated by the desirable playbook in executing the desirable playbook.

### Claim 10 (depends on 7)

The method according to claim 7, wherein the desirable playbook is transmitted to the client from the server.

### Claim 11 (depends on 7)

The method according to claim 7, wherein the server initiates a download of the desirable playbook to the client for execution.

### Claim 12 (depends on 7)

The method according to claim 7, wherein the desirable playbook instructs the custom bootloader to one of:
reinstall the operating system;
restore system to a state from an earlier backup;
remove selected files, change registry settings and reboot;
download and boot into a separate operating system to repair operating system;
add or update files to the OS;
change device settings both at the BIOS and OS level;
install or remove programs;
run third-party applications;
install, re-install or update the OS;
collect usage data or logs from the device and send to a server;
install, update or remove user profiles from the device;
enroll the device in certain databases or directories as part of onboarding a new device;
perform certain offboarding activities such as unregistering a device and backing up user data before deleting from the device;
execute a custom script to perform a custom action; or
retrieval of forensic information.

### Claim 13 (depends on 1)

The method according to claim 1, wherein the server is the sender of the signal.

### Claim 14 (depends on 1)

The method according to claim 1, wherein the deterministic network endpoint and client device connect via one of a pre-OS level networking or OS-level networking.

### Claim 15 (depends on 1)

The method according to claim 1, wherein an extensible firmware interface (EFI) system partition on the client device is modified, the custom bootloader is installed on a client bootable storage device, and a boot order is updated inserting a preloader as a first boot entry.

### Claim 16 (depends on 1)

The method according to claim 1, wherein, after executing one of the separate bootable image or the desirable playbook to boot the operating system, the method further comprises one of unsetting the security flag or setting the UEFI variables to cause the client device to enter a different playbook on a next boot.

### Claim 17 (depends on 1)

The method according to claim 1, wherein the client device connects to the server via Bluetooth and, upon connecting to the server, the client device is authenticated to the deterministic network endpoint.

### Claim 18

A client device in a client/server network, comprising:
a processor;
one or more storage devices on which an operating system, a standard bootloader for the operating system and a custom bootloader are stored, the one or more storage devices including an extensible firmware interface (EFI) system partition with boot device select unified extensible firmware interface (UEFI) variables pointing to the custom bootloader, whereby one or more instructions issued by the custom bootloader supersede one or more instructions issued by the standard bootloader and computer readable instructions, which, when executed by the processor cause the processor to:
receive a signal instructing the client device to reboot;
write one or more UEFI variables based on the received signal on the device;
evaluate the one or more UEFI variables
when the security flag has not been set, the custom bootloader performs a direct boot to the operating system; and
when the security flag has been set, the custom bootloader executes a process to determine whether:
a desirable boot sequence uses a separate bootable image present on the client device and to execute the separate bootable image to boot into an operational state; or
to connect to the server and receive a desirable playbook for execution and to execute the desirable playbook to boot into an operational state.

### Claim 19 (depends on 18)

The client device according to claim 18, wherein, when executed, the computer readable instructions further cause the processor to evaluate whether a sender and content of the signal is trusted.

### Claim 20 (depends on 18)

The client device according to claim 18, wherein the signal originates as a message in a secure format from the network or from another program or API call on the client.

### Claim 21

A method of booting/rebooting a client device operable in a client/server network, in which a custom bootloader installed on the client device issues one or more instructions that supersede one or more instructions of a standard bootloader for an operating system of the client device, the method comprising:
receiving a manual interruption of a boot sequence;
executing a process to determine whether:
a desirable boot sequence uses a separate bootable image present on the client device; or
to connect to the server and receive a desirable playbook for execution, and
executing one of the separate bootable image or the desirable playbook to boot the client device into an operational state.

### Claim 22 (depends on 21)

The method according to claim 21, wherein, after executing one of the separate bootable image or the desirable playbook to boot the operating system, the method further comprises one of setting one or more UEFI variables for a next boot.

### Claim 23

A bootloader stored on a non-transient client device, wherein the bootloader is remotely controllable by secure messages received by the client device from a server to execute one or more instructions that supersede one or more instructions executed by a standard bootloader of an operating system of the client device.

### Claim 24 (depends on 1)

The method according to claim 1, wherein the security flag is set by one or more applications resident on the client device based at least in part on suspicious or anomalous activity detected at the client device.

### Claim 25 (depends on 24)

The method according to claim 24, wherein the security flag is set without any external intervention by a remote device.

### Claim 26 (depends on 1)

The method according to claim 1, wherein the custom bootloader is executed from a hard disk drive resident on the client device.

### Claim 27 (depends on 25)

The method according to claim 25, wherein the custom bootloader is executed from an Extensible Firmware Interface (EFI) partition resident on the hard disk drive.

### Claim 28 (depends on 1)

The method according to claim 1, wherein, when the security flag is not set, the method further comprises executing the operating system of the client device to boot the client device in an operational computing state.
