BIOS Update for the Intel® NUC M15 Laptop Kit - LAPRCx10 [RCADL357]

735631
8/2/2022

Introduction

This download record provides options for updating the Intel® Aptio* V UEFI Firmware of Intel® NUC M15 Laptop Kit - LAPRCx10

Available Downloads

  • Windows 11*, Windows 10, 64-bit*
  • Size: 13.6 MB
  • SHA1: C9D898650A6938BA1632D2E64E6ABFCE47E7BC9A
  • OS Independent
  • Size: 37.1 MB
  • SHA1: 41EFBD20DE4C6A1851996452C858619FE6A85204
  • OS Independent
  • Size: 13 MB
  • SHA1: 7F532F7E46767BCA259DF7ED0A186E9EB903241F

Detailed Description

Purpose
This download record provides options for updating the BIOS of Intel® NUC M15 Laptop Kit - LAPRCx10.

Which file to choose?

  • Express BIOS update [RCADL357.0056.EBU.exe] - Self-extracting Windows*-based update file, designed to be used on Windows systems.
  • F7 BIOS update [RC0056.CAP] - .CAP file to be used for F7 BIOS Update method. It requires a USB flash device.
  • BIOS Recovery [RCADL357.0056.RECOVERY.zip] - In the unlikely event that a BIOS update is interrupted, it's possible the BIOS may be left in an unusable state. Use the recovery BIOS update to recover from this condition. It requires a USB flash device. Follow the recovery instructions in the Readme file. 

Note

  • The Intel® Aptio* V Integrator Tools are designed to assist integrators (who usually work in manufacturing or enterprise environment) with the process of BIOS/SMBIOS customization, OEM Windows* product key injection (OEM Activation 3.0, OA3), changing the Logo, and so on of Intel® NUC AptioV based products.
  • The readme file includes BIOS update instructions for advanced users. You can also find detailed step-by-step instructions on how to use each of these BIOS update methods.
  • See the release notes for installation instructions, supported hardware, what's new, bug fixes, and known issues in this BIOS version.  

Product and Performance Information

1

Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.