This specifies how hardware invoke startup software or an operating system to start charging. However, the starter no longer depends on an operating system loader as before. UEFI can load multiple operating systems without the need for a charger like NTLDR (Windows) or LILO (Linux). UEFI select the partition with the operating system and loads it from there. For this to happen, both the hardware and the software should be UEFI-compatible.
In the boot process, UEFI has menus that are much more friendly than the old BIOS menus, and allows certain hardware configuration tasks can be done without loading the main operating system. This has nothing to do with the current capabilities of certain machines to load a browser without booting the main OS since they achieve these teams carrying a mini-operating system from the BIOS that allows these tasks. By contrast, with the new specification, not loading a mini-operating system but you select which drivers to load to get it to run a particular application. Thus, the selective loading, may initiate web browsers, email clients, which will start much faster than if you had to throw quite a full OS. These applications are called "missing operating system applications." On the contrary, once the system starts operating and applications are used on a regular basis, these applications are called "applications with this operating system."
To better understand this, we see the following image, which shows the building blocks of a generic or universal PC. In the bottom of the figure, in the lower layer fits the hardware. For the hardware, some portion of it can be accessed from fixed code called firmware, and another portion is accessible directly from the operating system. Here ends what would be called "platform", defined by the dotted line. Then, above this layer is the operating system, and above it, the applications that we use every day:
