Acer Aspire ES1
The Acer Aspire ES1 is a family of low-cost laptops that are powered by an Intel Celeron N2830 processor (formerly "Bay Trail").
- Aspire ES1 - Green (Console OS works well on this device - but you must upgrade your Wi-Fi card first)
Console OS Developer Release 1 will run on the Acer ES1. However, Wi-Fi and Bluetooth will not function. We recommend using the ASUS WL-330NUL for this release as a USB Wi-Fi card.
Alternatively, you can upgrade the Wi-Fi card with an Intel 3160 or 7260 mini-PCIe card. This takes about 15 minutes to do and costs as little as $15. Additionally, upgrading to a 7260-AC card will future-proof your laptop with 802.11ac dual-band Wi-Fi.
We are working to add support for more Wi-Fi cards to Console OS in the near future.
You must be running the latest BIOS from Acer.com before installing Console OS. We only test and validate Console OS using the latest system BIOS available, and BIOS updates are critical to the performance-tuning of Console OS and the underlying UEFI firmware.
Before installing, fully read the Release Notes - Including creating a Windows Recovery Drive, and disabling Secure Boot, as well as creating a Console OS Install Flash Drive.
Important: The Acer ES1 has a BIOS issue that prevents disabling UEFI Secure Boot normally. The Secure Boot option must be disabled to install Console OS Developer Release 1. To work around this issue, you must set a BIOS administrator password in BIOS settings. Once the BIOS password is set, the BIOS menu option to disable UEFI Secure Boot will appear.
To install Console OS, rapidly press the F12 key when booting the machine. Make sure a USB keyboard is connected (per the notes above) Make sure the Console OS Install Flash Drive that you built per the Release Notes is inserted prior to powering the machine up.
If the Console OS Install Flash Drive does not show up in the F12 boot menu, this is typically due to the machine not waiting long enough for your USB flash drive to enumerate. To work around this, press Control-Alt-Delete and try again. Do not cold boot the machine in this situation.
Running into an issue? See something that you think should be on this page? Hit the green Feedback | Contact Us button below and tell us! We’ll aggregate your feedback and integrate it into the support wiki.