Before an operating system can load, the computer has to wake up, check its hardware, and figure out what device it should start from. This early startup process is controlled by firmware built into the motherboard. On older computers, this firmware was usually called BIOS. On modern computers, it is usually called UEFI.
For an IT support technician, BIOS and UEFI settings are important because they control many low-level system functions. These settings can affect whether a computer starts correctly, whether storage drives are detected, whether USB devices are allowed, whether security features are enabled, and whether virtualization can be used.
A computer may look like it has a serious hardware problem when the real issue is a simple firmware setting. For example, a system may fail to boot because the wrong drive is selected, Secure Boot is blocking the installation media, or the storage device is not being detected properly. Understanding BIOS and UEFI helps technicians troubleshoot these problems more confidently.
What Are BIOS and UEFI?
BIOS stands for Basic Input/Output System. It is older firmware used to initialize hardware and start the boot process. When a computer powers on, BIOS checks basic hardware, looks for a bootable device, and passes control to the operating system.
UEFI stands for Unified Extensible Firmware Interface. UEFI is the modern replacement for BIOS. It performs the same general job, but it supports newer features, larger drives, better security options, faster startup, graphical menus, mouse support, and more advanced hardware management.
Many people still use the word “BIOS” casually, even when they are actually talking about UEFI. For example, a technician may say, “Go into the BIOS,” even on a modern computer that technically uses UEFI. In the real world, this is common. The important thing is to understand that both terms refer to motherboard firmware that controls startup and low-level hardware settings.
The Startup Process
When a computer is turned on, it does not immediately load Windows, Linux, or another operating system. First, the motherboard firmware begins the startup process.
The firmware checks key hardware components, such as the CPU, RAM, storage devices, keyboard, and video output. This early hardware check is often called POST, which stands for Power-On Self-Test. If the system finds a serious hardware problem, it may display an error message, show diagnostic lights, or produce beep codes.
After the hardware check, the firmware looks for a bootable device. A bootable device contains the files needed to start an operating system or installer. Common bootable devices include internal SSDs, hard drives, USB flash drives, optical discs, and network boot sources.
Once the firmware finds a valid boot device, it hands control over to the operating system. At that point, the operating system continues loading and eventually presents the login screen or desktop.
Boot Order and Boot Options
Boot order tells the computer which devices to check first when looking for an operating system. For example, the system may be configured to check the internal SSD first, then a USB drive, then a network boot option.
Boot order is important during repairs and installations. If a technician is installing Windows from a USB flash drive, the computer may need to boot from USB before it boots from the internal drive. If the internal drive is listed first, the computer may skip the USB installer and load the existing operating system instead.
Boot order can also cause problems. If the wrong drive is first in the boot list, the computer may show an error such as “No bootable device found” or “Operating system not found.” This does not always mean the drive has failed. It may simply mean the firmware is trying to boot from the wrong device.
A technician should always check boot settings when troubleshooting startup problems, especially after replacing storage drives, installing an operating system, or changing hardware.
USB Permissions and Booting from External Devices
BIOS and UEFI may include settings that control whether USB ports or USB boot devices are allowed. These settings are often used for security.
Allowing USB boot can be useful for technicians because many repair tools and operating system installers run from USB flash drives. However, USB boot can also be a security risk. If someone can start a computer from their own USB drive, they may be able to bypass some normal protections or access data if the system is not properly encrypted.
Some organizations disable USB boot or restrict USB devices to reduce risk. A technician working in a business or school environment should be careful before changing USB permissions. The setting may exist for a security reason.
Secure Boot
Secure Boot is a UEFI security feature that helps prevent unauthorized or untrusted software from loading during startup. It checks the boot process and only allows trusted bootloaders to run.
The purpose of Secure Boot is to protect the system from certain types of malware that try to load before the operating system. This kind of malware can be especially dangerous because it may hide from normal antivirus tools.
Secure Boot is helpful, but it can also create confusion during troubleshooting. Some operating system installers, older boot tools, or custom recovery environments may not start if Secure Boot is enabled.