# Need BIOS file and UEFI-flash utility for Hi10 X to recovery after Windows Update reflashed it to some incorrect (not Chuwi) version

**URL:** <https://forum.chuwi.com/t/need-bios-file-and-uefi-flash-utility-for-hi10-x-to-recovery-after-windows-update-reflashed-it-to-some-incorrect-not-chuwi-version/40084>\
**Category:** Hi10 X\
**Created:** [July 3, 2023, 10:02am UTC](https://forum.chuwi.com/t/need-bios-file-and-uefi-flash-utility-for-hi10-x-to-recovery-after-windows-update-reflashed-it-to-some-incorrect-not-chuwi-version/40084 "2023-07-03T10:02:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sergr](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@Sergr](https://forum.chuwi.com/u/Sergr)\
**Post date:** [July 3, 2023, 10:02am UTC](https://forum.chuwi.com/t/need-bios-file-and-uefi-flash-utility-for-hi10-x-to-recovery-after-windows-update-reflashed-it-to-some-incorrect-not-chuwi-version/40084/1 "2023-07-03T10:02:55Z")

</div>

Windows Update changed BIOS on the Hi10 X to some incorrect (not Chuwi) version (System Firmware G8320 vXX.XX.XX) dated 23.05.2023.  
Now the pad sees 3GB of RAM instead of 6GB and audio doesn’t work.  
I need the original Chuwi BIOS file and UEFI-utility to flash it back.  
I saw the same thread ([CHUWI BIOS Firmware Hi10 X N4120 - #5 by AgentM](https://forum.chuwi.com/t/chuwi-bios-firmware-hi10-x-n4120/39942/5)), but there is no official answer from Chuwi in this thread.  
I hope for a Chuwi official help.

---

<div class="post-metadata">

**Author:** ![DonPecarlo](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.chuwi.com/donpecarlo/32/7614_2.png) [@DonPecarlo](https://forum.chuwi.com/u/DonPecarlo)\
**Post date:** [July 7, 2023, 7:26pm UTC](https://forum.chuwi.com/t/need-bios-file-and-uefi-flash-utility-for-hi10-x-to-recovery-after-windows-update-reflashed-it-to-some-incorrect-not-chuwi-version/40084/2 "2023-07-07T19:26:46Z")

</div>

I’m just replying here in hopes I get notified whenever a solution is found.

It really looks like this firmware update was meant for a different device.
