System partition (EFI or ESP system partition).
The computer must contain one system partition on the disk. On EFI and UEFI based systems this partition is called the system partition EFI or ESP. This partition is usually stored on the main hard drive. The computer boots from the system partition. The minimum size of this partition is 100 MB and it must be formatted using the FAT32 file format. This partition is managed by the operating system and should not contain any other files, including Windows Recovery Environment tools. The standard configuration of disks in GPT layout on a UEFI system is shown in Fig. 1.
Rice. 1.Example of disk partition configuration on a PC with UEFI.
An EFI partition (ESP) formatted in FAT32 is required for GPT partitioning on UEFI systems. The standard EFI partition size is 100 MB, but on 4K Native Enhanced Format drives (4KB sectors) it is increased to 260 MB due to FAT32 limitations. PC manufacturers may store some of their tools on this section, so its size varies depending on the manufacturer.In GPT partitioning, the EFI partition performs one of the roles assigned to the System Reserved partition in MBR partitioning. It contains the Boot Configuration CD (BCD) store and the files needed to boot the operating system.
Basics principles of construction and operation of a file system based on FAT-32.
1) Each element of the FAT table (starting from the second) corresponds to a cluster in the data area with the same number.
2)Number initial file cluster indicated in catalog line, defining File. Thisnumber is also a link to the FAT table element that contains number next file cluster,and is a link to the FAT table element that contains the file's next cluster number etc.
3) A cluster is a continuous sequence of sectors (fixed size). This is an addressable "portion" of a file.
4) Code in FAT table element may still determine free cluster, defective cluster And end-of-file sign.
5) File in the FAT section - this is a sequence of clustersspecified usingdirectory strings and FAT table entries.
6) All operating systems can work with a FAT-32 partition (the main factor in using FAT-32 in ESP).
As a result high-level partition formatting, recording system information in row data blocksinitial sectors of the partition, is created logical drive (volume) file system type FAT32, which consists from three main areas( rice. 2) , arranged in the following order:
- “reserve” area (area of reserve sectors);
- file allocation tables area (FAT1 and FAT2);
- area of files and directories (data area).
Root directory is stored in the data area as a regular file and can be expanded as needed.
Hello! Windows 8.1 won’t boot on a laptop with a UEFI BIOS and I can’t do anything. When loading, an error appears on the screen File:\EFI\Microsoft\Boot\BCD... I studied all the Internet articles on this topic, but in my case nothing helps.
What have I done?
- Booted from installation Windows disk 8.1 and searched for the installed operating system with the command bootrec /RebuildBcd, error " Scanning of installed Windows systems completed successfully. Total number of detected Windows systems: 0»
- Deleted a partition (300 MB), an encrypted (EFI) system partition containing all Windows 8.1 bootloader files using the command del vol, then applied Automatic Boot Recovery, the system re-creates this partition, but does not boot. I made this section active in the command line, which also did not help.
- Also formatted the same partition (300 MB) Encrypted (EFI) with the command format fs=FAT3 and created it again.
- I tried to write a new download store for Windows 8.1 with the command bcdboot.exe C:\Windows, where (C:) is the partition with the Windows 8.1 operating system installed and I get an error againFailure to copy download files.
I entered commands that were successful, but Windows did not load.
bootrec /FixMbr
bootrec /FixBoot
I don’t know what else to do or how to restore the Windows 8.1 bootloader. Maybe you can give me some advice?
Hello friends! My name is Vladimir and I will answer this question.
If your Windows 8.1 does not boot and you have used all available tools to restore the bootloader, then you can delete the 300 MB encrypted (EFI) system partition, as well as the 128 MB MSR partition, and create them again.
In Disk Management you can only see encrypted (EFI) system partition 300 MB, MSR partition 128 MB visible only in the command line when entering the command"lis par".
Note: If you do not have experience, do not perform this operation unless necessary, use other methods from the about section first. If you want to experiment on a working laptop, then do not start working without first creating a backup copy of these partitions, but rather create a .
We will delete and recreate partitions:
1. Section (400 MB) containing the environment Windows recovery 8.1 (you can get rid of this section altogether and use, if necessary, the recovery environment located on bootable media with Win 8.1).
2. Section (300 MB), encrypted (EFI) system partition containing all Windows 8.1 boot loader files.
3. Service partition MSR (Microsoft System Reserved) 128 MB, required for GPT disk partitioning.
We boot the laptop from and in the initial system installation window, press the keyboard shortcut Shift + F10,
window opens command line, enter the commands:
diskpart
lis dis (lists physical disks).
sel dis 0 (select the laptop hard drive 931 GB, and the second drive 14 GB - bootable flash drive Windows 8.1).
lis par (shows all partitions of the selected disk, we will delete the first three partitions).
sel par 1 (select the first section
del par override (delete the partition, to delete the ESP and MSR partition or the laptop OEM partition, you must specify the override parameter)
sel par 2
del par override
sel par 3
del par override
That's it, we deleted all three hidden sections.
Now, if we select a disk and enter the lis par command, we will see only two partitions on the laptop’s hard drive:
Section 4 - installed Windows 8.1
Partition 5 is a hidden recovery partition with factory settings.
We create a new encrypted (EFI) system partition of 300 MB, as well as a 128 MB MSR partition
Enter the commands:
diskpart
lis dis (display a list of disks).
sel dis 0 (select the laptop hard drive).
create par efi size=300 (create an encrypted (EFI) system partition of 300 MB).
format fs=fat32 (format it to the FAT32 file system).
creat par msr size=128 (create a 128 MB MSR partition)
So, you specified in the settings BIOS loading from a CD/DVD or from USB, and when booting from Ubuntu LiveCD, instead of a purple screen with icons of a keyboard and a man, we received this screen:
It's okay, it happens. In this case, you need to take into account a number of points, which will be discussed in this section. By the way, the presence of a purple screen during boot does not mean that you do not have UEFI; it’s just that with a black screen all the features of UEFI are most clearly visible. So, in any case, reading this section will be very useful. In the meantime, feel free to select the top line “Try Ubuntu without installing” and press Enter. After a short wait, you'll be taken to the Ubuntu desktop, and while you wait for Ubuntu to boot, let's talk about UEFI.
Introduction to UEFI and GPT
You probably remember that one of the objectives of this manual is to teach the reader to use all the main tools of the system effectively and easily. But to do this, you need to dig deeper and talk about the hardware of your computer, and how this hardware works with the system. Therefore, again there is a theory, you cannot do without it.
What happens when you turn on your computer? First of all, the computer must correctly initialize itself, that is, its own hardware, and transfer control to the operating system loader. This process is handled by the “Extensible Firmware Interface” ( EFI) (Extensible Firmware Interface) - an interface between the operating system and firmware that controls low-level hardware functions. Previously, BIOS was responsible for this, and now EFI, which, after another change in the standard, became known as the “Unified Extensible Firmware Interface” ( UEFI) is the name and will be used further. It should be noted that UEFI, as a more modern interface, fully supports all BIOS functions; the opposite, unfortunately, is not true. In the settings, the BIOS support mode is most often called “Legacy” (“legacy” or “traditional” in English) or simply “UEFI Disabled” (“UEFI disabled”, as you might guess). For now, however, we are interested in the enabled UEFI mode.
So, when you turn on the computer, UEFI begins to initialize the hardware and finds some kind of block device, say, a hard drive. You probably know that the entire hard drive is almost never used - the disk is necessarily divided into sections, including for ease of handling. But today you can break it into sections in two ways: using standard methods: by using MBR or GPT. What is their difference?
MBR(“Master Boot Record” - the main boot record) uses 32-bit partition identifiers, which are placed in a very small piece of space (64 bytes) at the very beginning of the disk (at the end of the first sector of the disk). Due to such a small volume, only four primary partitions are supported (you can learn more about this in this article). Since 32-bit addressing is used, each partition can be no more than 2.2 TB. Additionally, the boot record does not have any spare MBR, so if an application overwrites the master boot record, all partition information will be lost.
GPT(“GUID Partition table” - table partition GUID) already uses 64-bit identifiers for partitions, so the piece of space in which information about partitions is stored is already more than 512 bytes, in addition, there is no limit on the number of partitions. Note that the limit on the partition size in this case is almost 9.4 ZB (yes, you read everything correctly - a zettabyte, one followed by twenty-one zeros!). And at the end of the disk there is a copy of GPT, which can be used to restore a damaged master partition table at the beginning of the disk.
So, when communication between the equipment and the operating system is carried out through the enabled UEFI mode (and not Legacy BIOS), using GPT for partitioning is practically compulsory, otherwise there will likely be compatibility problems with the MBR.
Well, it seems that the block devices have been sorted out, UEFI has initialized everything correctly, and now it should find the operating system bootloader and transfer control to it. To a first approximation, it looks like this: since UEFI is the successor to the BIOS, it searches for the bootloader in strict accordance with the established rules. If it finds an operating system bootloader that does not support UEFI, then BIOS emulation mode is activated (this is true, even if Legacy BIOS is not explicitly specified). And it all starts all over again, with the only difference that now emulated The BIOS checks the hardware status and loads firmware - simple drivers for individual hardware components. After that emulated The BIOS again searches for the OS boot loader and activates it. That, in turn, loads the operating system or displays a list of available operating systems.
But in the case of UEFI, everything happens a little differently. The fact is that UEFI has its own bootloader operating systems with integrated launch managers for installed operating systems. For this purpose, for it - for the UEFI bootloader - a small partition (100–250 MB) must be created on the disk, which is called “Extensible Firmware Interface System Partition” (system partition of the extensible firmware interface, ESP). In addition to the specified size, the partition must be formatted in the FAT32 file system and be bootable. It contains drivers for hardware components that can be accessed by the running operating system. And in this case, the download occurs directly from this section, which is much faster.
So, let's summarize: in order to fully use the UEFI functionality, the disk must be GPT, and it must have a special ESP partition. Pay attention to the phrase “so that full use the functionality” - there are many ways to install Ubuntu on a system with “stripped-down” UEFI to one degree or another, and they all depend on the presence or absence of pre-installed operating systems on your computer. For example, you want to leave Windows pre-installed. Which Windows - “Seven” or the newfangled 8.1? Or maybe, God forbid, you have “Peratian Windows” installed, activated with MBR, and does not want to run with GPT, and you, nevertheless, want to study it further? In addition, a lot depends on the bit depth of the operating systems - without dancing with a tambourine, it is impossible to make a 32-bit system work with UEFI. And there are quite a lot of such examples. Therefore, in this section we will only talk about installing Ubuntu in the “maximum full” mode of using UEFI capabilities, although even after reading this introduction, you will already be able to imagine the device of your computer and, if desired, implement your own installation scenario.
Well, shall we get started?
Disk partitioning
So, you booted into Ubuntu from a LiveCD in UEFI mode. Open the “GParted Partition Editor”, but for now let’s talk about very important features that you need to pay attention to.
The most important thing is that you must have a plan for your actions, believe me - the list of steps and the order of their implementation is quite extensive, so it is advisable to write down the main points of the plan somewhere on a piece of paper and periodically check them. So what do you know? For a normal installation of Ubuntu in UEFI mode, your computer's hard drive must be properly prepared, namely:
The disk must be GPT;
The disk must have a special ESP partition;
The disk must have standard partitions: system, swap, and a partition for the home directory.
In addition, you need to decide on the operating systems on your computer - whether Ubuntu will be the only system, or whether there will be other systems supporting UEFI mode nearby, will determine the layout and installation plan.
Let's start by answering the second question: about the availability of other operating systems. If your computer already has operating systems that support booting in UEFI mode (for example, Windows 8), and you do not intend to abandon them just yet, then the first two points of the plan have already been completed: the ESP partition probably already exists, and, of course, the disk with GPT. Let's check that this is indeed the case.
Let's assume that after launching the GParted partition editor, the following window opens:
What information can be obtained by carefully studying this window? First, look at the "File System" column: all partitions are formatted in ntfs, except for one partition with a fat32 file system - this appears to be the ESP partition. Windows 8 is already installed on the disk (partition /dev/sda4 - in Windows this is drive C:) - this indicates label disk (column “Label”). Secondly, the hard drive has a number of Windows service partitions - this can be found out not only by the labels (WINRE_DRV and LRS_ESP), but also by flags(Column "Flags") - all of these sections are hidden because they have the hidden flag set, which hints at the special nature of the information on them. And finally, take a closer look at the /dev/sda5 partition - have you accidentally lost the D: drive in Windows? Here he is, safe and sound.
So, the first two points of the plan have already been completed, and the implementation of the third point: creating partitions for Ubuntu is described in sufficient detail in the example of using GParted to repartition a hard drive. Let us briefly remind you that you need to “cut off” sufficient space from the data disk (in the example this is /dev/sda5, or drive D: in Windows) and in its place create three partitions: swap, system and a partition for the home directory. Please also note that your disk is GPT, so it does not have an extended partition containing logical drives, therefore, when creating partitions, select Primary partition(“Main Section”).
Do not perform any operations with Windows service partitions - they are intended for normal functioning this OS. Accidental or deliberate modification of these partitions is guaranteed to lead to problems in Windows, including its complete inoperability.
The end result should be something similar to this picture:
The additional sections created are shown here:
Please write down the purpose of the sections. In the example shown:
/dev/sda2- EFI section (ESP)
/dev/sda6- system partition (partition for the “root” of the system)
/dev/sda7- swap partition
/dev/sda8- section for user data.
This information will be very useful in the future when installing Ubuntu, because due to the large number of partitions, you can very easily get confused and assign the required mount point to the wrong “number”.
Nevertheless, we continue to work with the GParted editor. Your task is to delete all partitions and use the free space to create the disk configuration necessary for Ubuntu. To do this, you can right-click on each section and select “Delete” from the drop-down menu. But it’s better to do it differently: find the “Device” item in the menu bar of the GParted editor and select “Create Partition Table...” from the menu. A warning will appear:
WARNING: This will ERASE ALL DATA on the ENTIRE DISK /dev/sda
(WARNING: This will DELETE ALL DATA on THE ENTIRE /dev/sda DISK)
Don't worry, you took care of backups, right? Look just below - at the inscription “Advanced” (Details). Click on the triangle on the left and select gpt from the menu:
The entire disk space will turn gray. Right-click on it and start creating the necessary partitions by selecting “New” from the drop-down menu. The first of the new partitions is a special ESP partition, required, as you remember, for UEFI to work. Since it is formatted in a non-native Linux file system, and in addition, it must be bootable, then it must be located at the beginning of the disk space. Define its size in the “New size (MiB)” field ( New size in MiB) 100 MB, and the file system is fat32:
In the same way, create partitions for the future: system (15 GB with the ext4 file system), swap partition (4 GB with linux-swap) and for the home directory (all remaining space in ext4). As you remember, GParted does not apply changes immediately, but simply queues them for execution. So click on the green checkmark “Apply All Operations”:
Yes, it is not at all necessary to manage the boot flags at this stage - the Ubuntu installer will do everything as it should. Now read carefully about how to install Ubuntu, and when you are ready, we will continue.
Installing Ubuntu
After this preparatory work, installing Ubuntu will not be difficult, especially if you have carefully read the installation rules. Just take out a piece of paper with a list of partitions and note that for the special EFI partition (/dev/sda2 from the example about the joint installation of Ubuntu and Windows) you need to accurately assign the property EFI boot partition, not the BIOS backup boot area:
If you do not do this, the installer will show you this notification:
Correct the error, and if it doesn’t work, exit the installer, launch the GParted editor and check that everything described above has been completed.
The assignments for all other partitions required when installing Ubuntu are described in great detail in this section, so there is little point in going into more detail here.
Possible problems
Sometimes it happens that after installation one of the operating systems preinstalled on the computer does not start. Well, without going into the rather complicated ways of bringing everything back to normal, we note that there is a comprehensive solution possible problems with loading. The name of this solution is Boot-repair .
This small program is a very powerful tool that allows you to fix almost all errors that may occur when loading Ubuntu and other operating systems after installation.
Follow the golden rule: " Never fix something that isn't broken yet»!
Boot into Ubuntu. It doesn't matter how you do it - Boot-Repair works on both LiveCD and installed system. Of course, if you are having difficulty booting your newly installed Ubuntu, then the first method becomes the only one. First, Boot-Repair needs to be installed on your computer; this is done using the terminal. Press Ctrl + Alt + T and in the window that appears, type:
: Change the command closer to the release.
Sudo add-apt-repository "deb http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu saucy main"
Now, of course, you will say: “What are you doing there, at all? There are so many letters - I don’t understand anything and I’ll definitely make a mistake!” Of course, no one enters the presented command letter by letter into the terminal - just select it completely and click the middle mouse button in the terminal window, or drag the selected text there. Press Enter. If you are on an already installed Ubuntu, you will be prompted to enter your password. Please note that when entering a password, no symbols are displayed: no dots, no asterisks - nothing at all - there is probably no need to explain why this is done. After entering the password, press Enter again.
Download the public key of the repository with the program from the trusted key store:
Sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 60D8DA0B
Update the application list with the command:
Sudo apt-get update
Install and run Boot-Repair:
Sudo apt-get install -y boot-repair && (boot-repair &)
After a short scan, the main Boot-Repair window will appear:
: In the process of writing.
As soon as we turn on the computer, it immediately starts running a miniature operating system, which we know as BIOS. It deals with testing devices, memory, loading operating systems, and distributing hardware resources. Many of the features of this set of programs (usually about 256-512 KB in size) allow you to support older operating systems like MS-DOS, giving them many features. Since the days of the PC/AT-8086, the BIOS has changed very little, and by the time the first Pentiums were launched, its development had almost stopped. Actually, there was nothing to change in it except dual BIOS, support for network tools and the ability to flash the firmware. But there were a lot of disadvantages: initial entry into the real processor mode, 16-bit addressing and 1 MB of available memory, the inability to have a “repair” console. And, of course, the eternal problem of hard drive support. Even now, drives up to 2.2 TB are guaranteed to be supported, no more.
Back in 2005, Intel decided to change the BIOS to EFI/UEFI (Unified Extensible Firmware Interface). The EFI system is a more advanced base operating system. UEFI has been working on some Unix and Windows platforms for a long time, but a mass transition has not yet occurred, despite good intentions. And they are:
- Availability of the notorious console for repairing system parameters and installing the OS;
- The EFI partition makes it possible to perform some actions without loading the OS (watching movies, playing music);
- Internet access and, therefore, the presence of installed network drivers, TCP/IP stack, etc.);
- Presence of graphic mode and user scripts;
- Support for gigantic disks;
- UEFI storage on new format partitions (GPT);
- Full support for all equipment from the moment of launch.
UEFI can use a general-purpose execution engine like the JVM to run hardware-independent code, which opens up enormous possibilities for creating bootable software.
There is also criticism of this technology. In particular, its implementation may lead to cutting off new players from the operating system market: for this purpose there will always be some technological loophole in the code. Like, for example, the inability to boot Windows 98 from modern BIOSes. But what’s worse is that you’ll have to forget about the millions of MS-DOS programs and other systems that relied on BIOS functions to operate. Perhaps they will still be emulated, but there are doubts about this. And among them there are probably important programs that there will be no one to rewrite. However, all these issues can be resolved – at least through virtual operating systems. But it is certain that new types of viruses will appear, and we will be able to see this quite soon.
In this article, we will show you how to manually recover an accidentally deleted bootloader. Windows partition on a UEFI system. Initially, the article described my experience in restoring a bootable EFI partition on Windows 7, but the article is also relevant for modern operating systems Microsoft systems(from Windows 7 to Windows 10). It has helped me out more than once after accidentally formatting or deleting an EFI partition in Windows 10. In this article, we will show you a simple way to manually recreate bootable EFI and MSR partitions in Windows.
So, let's assume that somehow accidentally (or not so accidentally, for example, when trying) the EFI boot partition on a UEFI system (not BIOS) was deleted or formatted, as a result of which Windows 10 / 8.1 / 7 stopped booting, cyclically asking to select boot device (Reboot and select proper boot device or insert boot media in selected). Let's figure out whether it is possible to restore Windows functionality when deleting the partition with Boot Manager without reinstalling the system.
Warning. The instructions assume working with disk partitions and are not intended for beginners. If you misinterpret commands, you may accidentally delete all data on your hard drive. It is also highly recommended to create backup copy important data on a separate medium.
Partition structure on a GPT disk
Let's look at what the boot partition table should look like. hard drive with GPT markup on . At a minimum, the following sections should be present:
- EFI system partition (EFI System Partition or ESP - Extensible Firmware Interface) - 100 MB (partition type - EFI).
- Microsoft backup partition – 128 MB (partition type - MSR).
- The main Windows partition is the partition with Windows.
This is exactly the minimum configuration. These partitions are created by Windows Installer when installing the system on an unpartitioned disk. PC manufacturers or users themselves can additionally create their own partitions containing, for example, the Windows recovery environment in a file winre.wim(), a partition with a backup system image from the manufacturer (allows you to roll back to the original state of the computer), user partitions, etc.
EFI partition with the Fat32 file system is required on disks with GPT partitioning on UEFI systems. This partition, similar to the System Reserved partition on disks with MSR partitioning, stores the boot configuration storage (BCD) and a number of files necessary for Windows boot. When the computer boots, the UEFI environment loads the boot loader from the EFI partition (ESP) (EFI\Microsoft\Boot\ bootmgfw.efi) and transfers control to him. If this partition is deleted, the OS cannot be booted.
MSRchapter on GPT disk used to simplify partition management and is used for utility operations (for example, when converting a disk from simple to dynamic). This is a backup partition and does not have a partition code assigned to it. User data cannot be stored on this partition. In Windows 10, the MSR partition size is only 16 MB (in Windows 8.1, the MSR partition size is 128 MB), file system– NTFS.
Manually creating EFI and MSR partitions on a GPT disk
Because the system does not boot correctly, we will need an installation disk with Windows 10 (Win 8 or 7) or any other boot disk. So, boot from the installation disk and press the key combination on the installation start screen Shift+F10 . A command prompt window should open:
Let's launch the disk and partition management utility:
Let's display a list of hard drives in the system (in this example there is only one, disk 0 . Asterisk ( * ) in the Gpt column means that the disk uses a GPT partition table).
Let's select this disk:
Let's display a list of partitions on the disk:
In our example, there are only 2 partitions left in the system:
- MSR partition - 128 MB
- Windows system partition – 9 GB
As we can see, the EFI partition is missing (deleted).
Our task is to delete the remaining MSR partition so that at least 228 MB of free space remains unallocated on the disk (for MSR and EFI partitions). You can delete the remaining partition using graphical GParted or directly from the command line (that’s exactly what we’ll do).
Select the partition to delete:
Select partition 1
And delete it:
Delete partition override
Let's make sure that only the Windows partition remains:
Now we can manually recreate the EFI and MSR partitions. To do this, in the context of the diskpart utility, run the following commands:
Select a disk:
create partition efi size=100
Make sure that the 100 MB partition is selected (the asterisk opposite the Partition 1 line):
list partition
select partition 1
format quick fs=fat32 label="System"
assign letter=G
create partition msr size=128
list partition
list vol
In our case, the Windows partition is already assigned a drive letter C:, if this is not the case, assign a letter to it as follows:
select volume 1
assign letter=C
exit
Repairing EFI bootloader and BCD in Windows
Once you have created the minimum disk partition structure for the UEFI system, you can proceed to copying the EFI boot files to disk and creating a bootloader configuration file (BCD).
Let's copy the EFI environment files from the directory of your disk where your Windows is installed:
mkdir G:\EFI\Microsoft\Boot
xcopy /s C:\Windows\Boot\EFI\*.* G:\EFI\Microsoft\Boot
Let's recreate the Windows 10/7 bootloader configuration:
g:
cd EFI\Microsoft\Boot
bcdedit /createstore BCD
bcdedit /store BCD /create (bootmgr) /d “ Windows Boot Manager"
bcdedit /store BCD /create /d “Windows 7” /application osloader
You can replace the inscription “My Windows 10” with any other one.
Advice. If only the EFI environment files were damaged on the EFI partition, but the partition itself remained in place, you can skip the process of rebuilding partitions using diskpart. Although in most cases it is enough to restore the bootloader according to the article. You can manually recreate the BCD on regular MBR+BIOS systems.
The command returns the GUID of the created entry; in the next command, this GUID must be substituted instead of (your_guid).
bcdedit /store BCD /set (bootmgr) default (your_guid)
bcdedit /store BCD /set (bootmgr) path \EFI\Microsoft\Boot\bootmgfw.efi
bcdedit /store BCD /set (bootmgr) displayorder (default)
Further commands are executed in the context (default):
bcdedit /store BCD /set (default) device partition=c:
bcdedit /store BCD /set (default) osdevice partition=c:
bcdedit /store BCD /set (default) path \Windows\System32\winload.efi
bcdedit /store BCD /set (default) systemroot \Windows
exit
We reboot the computer... In our case, it did not boot the first time, we had to additionally dance with a tambourine:
- Turn off the power to the PC.
- Disable (physically) HDD.
- We turn on the PC, wait for the boot error window to appear, and turn it off again.
- We connect the disk back.
Then in our case (testing was carried out on) we had to add a new boot menu item by selecting the file EFI\Microsoft\Boot\bootmgrfw.efi on the EFI partition.
In some UEFI menus, by analogy, you need to change the priority of boot partitions.
After all the above manipulations, Windows should boot correctly.
