This download record provides options for updating the Intel® Aptio* V UEFI Firmware of the Intel® NUC X15 Laptop Kits - LAPAC71G, LAPAC71H.
- Windows 11 Family*, Windows 10, 64-bit*
- Size: 13.3 MB
- SHA1: F1C9656636A54DD20AFCAF37E56E422555271C16
- OS Independent
- Size: 37.1 MB
- SHA1: 0C9C637BF66BC84B78F8E05003995891A24AC217
- OS Independent
- Size: 12.6 MB
- SHA1: A799DF7942D4712A9A5F83385428982DE51329D7
This download record provides options for updating the BIOS of Intel® NUC X15 Laptop Kits - LAPAC71G, LAPAC71H.
Which file to choose?
- Express BIOS update [ACADL357.0059.EBU.exe] - Self-extracting Windows*-based update file, designed to be used on Windows systems.
- F7 BIOS update [AC0059.CAP] - .CAP file to be used for F7 BIOS Update method. It requires a USB flash device.
- BIOS Recovery [ACADL357.0059.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.
- 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.
Automatic Driver and Software Updates
Identify your products and install Intel driver and software updates for your Windows* system.
Product and Performance Information
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.