This download record contains options for updating the BIOS of Intel® Compute Sticks STK2m364CC and STK2m3W64CC (0064).
- OS Independent
- Size: 6.8 MB
- SHA1: 679B19FC99182ED27147E25E49C20BA06D7D145B
- OS Independent
- Size: 6 MB
- SHA1: 21D0F60DA7BDBB261EAFD0D8F37E0B44801488C6
Find options for updating the BIOS of Intel® Compute Sticks STK2m364CC and STK2m3W64CC. You only need to download one.
The readme includes BIOS update instructions for advanced users. If you need complete step-by-step instructions on how to use each of these BIOS update methods, refer to BIOS update instructions.
Which file to choose?
- Recovery BIOS update [CC0064.bio] - A .BIO file to be used for the F7 BIOS Update method or a BIOS recovery process. 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.
- UEFI BIOS update [CCSKLm30.86A.0064.UEFI.zip] - Allows updating of the BIOS from the EFI shell. It requires a USB flash device.
- When beginning a BIOS update process, it can take up to 30 seconds for messages to appear on the screen.
- Don't power down your system before the update is complete. The update process will take up to 3 minutes.
- The BIOS for an Intel® Compute Stick cannot be customized with Intel® Integrator Toolkit.
- Due to a security enhancement, it will not be possible to go to any BIOS earlier than BIOS 0053.
- Optional: The UQI list file included in this record provides UQI values that can be used by Intel Integrator Toolkit and VCUST.
See the release notes for installation instructions, supported hardware, what is new, bug fixes, and known issues.
Not sure if this is the right driver for your Intel® Compute Stick?
Run Intel® Driver & Support Assistant to automatically detect updates.
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.