Troubleshooting
Challenges when restarting into Endless OS
If your computer starts back up in Windows, as opposed to restarting in Endless OS, or displays an error message, you might have an incompatible BIOS.
It’s also possible that you might not have the right type of processor to run Endless OS.
In all cases, it’s best to refer to the documentation that came with your computer. If you received your computer from your school or workplace, contact your IT department.
Do not duplicate or alter the Endless Key
- Please do not duplicate the Endless Key. It is manufactured using a special process that allows you to access the content on macOS/Windows, as well as reboot into Endless OS, and is not intended for duplication on a home computer.
- Do not delete any files from the Endless Key other than documents you have created.
Possible errors
- Your system does not have a 64-bit processor (CPU). The Endless Key cannot be used on this computer to restart into Endless OS.
- Your computer does not have a UEFI BIOS. The Endless Key cannot be used on this computer to restart into Endless OS.
- The Endless Key does not have the security privileges necessary to function.
- Remove and re-insert the Endless Key, and accept the Windows UAC prompt.
- Your computer’s version of Windows is not supported - The Endless Key only supports Windows 10. The Endless Key cannot be used on this computer to restart into Endless OS.
- Your computer does not have enough memory available (2GB of RAM is required). The Endless Key cannot be used on this computer to restart into Endless OS.
- Your computer’s processor (CPU) is not powerful enough - The Endless Key requires a multi-core processor. The Endless Key cannot be used on this computer to restart into Endless OS.
- Your computer has no USB 3.0 ports. The Endless Key cannot be used on this computer to restart into Endless OS.
- Make sure that you are running the Endless Launcher from the Endless Key, and that you have not copied it to your hard drive.
- Additionally, there might be an issue with your Endless Key, please refer to the resources in “Need more information,” below.
- Any error starting with error_firmware_
- The Endless Key is failing to communicate with your computer when attempting to boot Endless OS. Please contact us for additional support.
- For other errors not listed here, please contact us for additional support.
Need more information?
To learn more about Endless OS, visit the Help System by pressing the avatar in the lower right corner and choosing Help.
For more up-to-date information, you can browse this forum, as well as the Endless OS Help Center (https://support.endlessm.com).
Enjoy!
- The Endless OS Foundation Team
Appendix
How to identify USB 3.0 ports
- The Endless Key requires a USB 3.0 port if you want to Restart and Try Endless OS
- If you only want to use the Endless Key on Windows or macOS, a USB 3.0 port is recommended but not required.
- USB 3.0 ports are typically blue, with an “SS” or “3.0” imprinted near the port.
How to check if your computer uses a UEFI BIOS
- Press the Windows key, or open the Start Menu, and type msinfo32
- Click the application that shows up - this will open your System Information.
- Once you are in the System Information application, look through the info on the right - you need to find BIOS Mode
- If your BIOS Mode is UEFI, like the image above, then everything is fine.
- If BIOS Mode is something else (like Legacy) then yyour computer cannot use the Endless Launcher to Restart in Endless OS. All the other features of the Endless Key should still function.
How to check if your computer is a 64-bit system
- Press the Windows key, or open the Start Menu, and type msinfo32
- Click the application that shows up - this will open your System Information.
- In the System Information application, find System Type in the right pane.
- Your System Type must be a x64-based PC, like the image above. If System Type is something else, your computer cannot use the Endless Launcher to Restart in Endless OS. All the other features of the Endless Key should still function.
