# Secure boot mode?

**URL:** <https://forum.chuwi.com/t/secure-boot-mode/55809>\
**Category:** Larkbox X\
**Created:** [June 12, 2026, 9:32am UTC](https://forum.chuwi.com/t/secure-boot-mode/55809 "2026-06-12T09:32:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![JavierPa](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@JavierPa](https://forum.chuwi.com/u/JavierPa)\
**Post date:** [June 12, 2026, 9:32am UTC](https://forum.chuwi.com/t/secure-boot-mode/55809/1 "2026-06-12T09:32:06Z")

</div>

Hi!

How should I enable Secure Boot? Custom or standard?

[![](https://us1.discourse-cdn.com/flex020/uploads/chuwi/original/2X/f/fcf8d3e6dac86362531dd6ab9d77192996fd0831.jpeg)](https://ibb.co/DgYBYmNb)  
[código html para imagen](https://es.imgbb.com/)

---

<div class="post-metadata">

**Author:** ![bentPencil](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.chuwi.com/bentpencil/32/11444_2.png) [@bentPencil](https://forum.chuwi.com/u/bentPencil)\
**Post date:** [June 16, 2026, 8:36pm UTC](https://forum.chuwi.com/t/secure-boot-mode/55809/2 "2026-06-16T20:36:57Z")

</div>

Standard should be used unless signing the boot uefi files with a custom key.

---

<div class="post-metadata">

**Author:** ![JavierPa](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@JavierPa](https://forum.chuwi.com/u/JavierPa)\
**Post date:** [June 17, 2026, 10:36am UTC](https://forum.chuwi.com/t/secure-boot-mode/55809/3 "2026-06-17T10:36:28Z")

</div>

Thinking about it, I’m not sure if enabling Secure Boot is risky with the Windows CA certificate issue. Chuwi doesn’t seem likely to release a BIOS update to adapt to the new certificates.

What do you think?

---

<div class="post-metadata">

**Author:** ![bentPencil](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.chuwi.com/bentpencil/32/11444_2.png) [@bentPencil](https://forum.chuwi.com/u/bentPencil)\
**Post date:** [June 18, 2026, 2:26am UTC](https://forum.chuwi.com/t/secure-boot-mode/55809/4 "2026-06-18T02:26:52Z")

</div>

Windows should be able to update the certs in the firmware database regardless of Chuwi releasing an update.

---

<div class="post-metadata">

**Author:** ![JavierPa](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@JavierPa](https://forum.chuwi.com/u/JavierPa)\
**Post date:** [June 21, 2026, 3:17pm UTC](https://forum.chuwi.com/t/secure-boot-mode/55809/5 "2026-06-21T15:17:59Z")

</div>

I’ve read on several sites that if they can’t be updated, it’s the manufacturer who must implement it through a BIOS update.

---

<div class="post-metadata">

**Author:** ![bentPencil](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.chuwi.com/bentpencil/32/11444_2.png) [@bentPencil](https://forum.chuwi.com/u/bentPencil)\
**Post date:** [August 1, 2026, 11:22pm UTC](https://forum.chuwi.com/t/secure-boot-mode/55809/6 "2026-08-01T23:22:09Z")

</div>

I doubt Chuwi will release anything. The secure boot certificate database is user manageable, and worst case, there’s power shell commands that can force an update to the database from Windows if, for some reason, Windows does not perform the update automatically.