> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/bios/boot-qi-dong/fast-boot.md).

# Fast Boot（快速启动）

本选项用于优化系统启动速度，但可能会影响部分硬件的初始化。启用该功能可以显著缩短开机时间，但需要注意可能带来的兼容性问题。

可用选项如下：

Enabled（启用）

Disabled（禁用）

具体说明：

用于启用或禁用在启动过程中仅初始化启动活动选项所需的最小设备集合。该设置对 BBS（BIOS 启动规范，BIOS Boot Specification）启动选项（非 UEFI（统一可扩展固件接口，Unified Extensible Firmware Interface）启动选项）无效。如果使用外置显卡，则其 VBIOS（视频 BIOS，Video BIOS）需要支持 UEFI GOP（图形输出协议，Graphics Output Protocol）。

警告：开启此选项后可能无法再次进入 BIOS，因为启用快速启动后，系统在启动阶段会忽略所有 USB 设备（如键盘）。通常可通过重置 CMOS（互补金属氧化物半导体，Complementary Metal-Oxide-Semiconductor），或使用 Windows 的高级启动功能进入 UEFI 固件设置。参见：华硕. Windows 11/10 如何进入 BIOS 设置界面\[EB/OL]. \[2026-03-26]. <https://www.asus.com.cn/support/faq/1008829/>. 提供通过 Windows 高级启动功能进入 BIOS 设置的详细步骤。需要注意的是，此方法并非对所有主板均有效，部分主板仍无法通过该方式进入 BIOS。

## Boot Failure Guard（启动故障防护）

该机制用于在多次启动失败后自动恢复默认 BIOS 设置，避免因配置错误导致系统无法启动的循环。

### Boot Failure Guard Message（启动故障防护消息）

选项：

Disable（禁用）

Enable（启用）

说明：

启用后，当系统检测到启动失败并进入 Boot Failure Guard 流程时，BIOS 会在屏幕上显示提示消息，告知用户当前正在执行启动故障防护恢复。

### Boot Failure Guard Count（启动故障防护计数）

值：

2 - 250

说明：

设置触发 Boot Failure Guard 的连续启动失败次数阈值。当连续启动失败次数达到该阈值时，BIOS 自动恢复默认设置（或上次已知正常配置），以恢复系统可启动性。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://book.bsdcn.org/bios/boot-qi-dong/fast-boot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
