Арч линукс установка рядом с windows — Ваш верный помощник с OS Windows

Скачай образ Windows, которой ты захочешь пользоваться.
Тоже самое сделай с Arch Linux.

Создание загрузочной флешки

Форматируй флешку используя ventoy.
Закинь образы на неё.

Установка Windows

Перезагрузи ПК и войди в BIOS.
Поставь флешку первой в очереди запуска или запустись с неё через Boot menu.
В меню выбери образ Windows.
Дойди до меню выбора диска и создания разделов.
Форматируй диск на который хочешь поставить Windows и Arch Linux.
Создай Раздел для Windows (120гб по желанию если 1TB как у меня).
(необязательно) Создай раздел для игр и хранения файлов.
Начни установку на раздел для Windows.

Подготовка к установке Arch Linux

После успешной установки Windows опять перезагрузись с загрузочной флешки.
В меню выбери образ Arch Linux.
Проверь разметку:

* lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINT
* fdisk -l # для уверенности

Найди раздел, который ты оставил для Arch Linux.
Форматируй его в ext4:

mkfs.ext4 /dev/nvme0n1p5 # имя раздела может отличаться

Монтируй этот раздел:

mount /dev/nvme0n1p5 /mnt

Найди загрузочный раздел

Монтируй раздел загрузчика:
Обычно он самый первый в списке, но смотри по его максимальному размеру, у меня был 96мб.

mount --mkdir /dev/nvme0n1p1 /mnt/boot/efi

Установка системы

pacstrap /mnt base linux linux-firmware nano

Настройка системы

* genfstab -U /mnt >> /mnt/etc/fstab
* arch-chroot /mnt
* ln -sf /usr/share/zoneinfo/Europe/Moscow /etc/localtime # Укажи свой часовой пояс
* hwclock --systohc
* echo "мой-хостнейм" > /etc/hostname # имя пользователя
* nano /etc/locale.gen  # Раскомментируй en_US.UTF-8 и ru_RU.UTF-8, потом:
* locale-gen
* echo "LANG=en_US.UTF-8" > /etc/locale.conf
* passwd  # Задай пароль root

Установка загрузчика

* pacman -S grub efibootmgr
* grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
* grub-mkconfig -o /boot/grub/grub.cfg

Перезагрузка

* exit
* umount -R /mnt
* reboot

Добавление Windows в GRUB

Установи os-prober, если его нет:

Включи его в настройках GRUB (по умолчанию в Arch он отключён):

 echo 'GRUB_DISABLE_OS_PROBER=false' | sudo tee -a /etc/default/grub

Запусти поиск систем:

Если всё работает, он должен вывести путь к Windows, например:

 /dev/nvme0n1p1:Windows Boot Manager:Windows:efi

Обнови конфигурацию GRUB:

 sudo grub-mkconfig -o /boot/grub/grub.cfg

Перезагрузи систему:

Если при запуске Arch Linux не получается войти в root или другого пользователя

В GRUB выбери Arch Linux, но нажми e, чтобы отредактировать параметры загрузки.
Найди строку, которая начинается с linux, и добавь в конец:
init=/bin/sh
Нажми F10 или Ctrl+X, чтобы загрузиться.
Когда загрузится консоль, смонтируй файловую систему на запись:

Сбрось пароль root:

Введи новый пароль дважды.

Перезагрузи систему:

После этого сможешь войти как root с новым паролем. Потом лучше создать обычного пользователя:

* useradd -m -G wheel -s /bin/bash твой_логин 
* passwd твой_логин

И дать ему sudo:

Там найди строку %wheel ALL=(ALL:ALL) ALL и убери #.
Попробуй сбросить пароль и зайти.

Источник

In this guide, you will learn how to Dual boot Arch Linux with Windows 10 on UEFI system. This guide assumes that you already have Windows 10 installed on your system.

Prerequisites

Before you begin configuring the dual-boot setup, ensure that the following requirements are met:

A bootable installation medium of Arch Linux (Either USB or DVD). To download the latest Arch Linux ISO, proceed to the official Arch Linux download page. Once you have downloaded the ISO image, grab an 8GB USB drive and make it bootable using Rufus tool or any other application that can create a bootable USB drive.
A fast and stable internet connection for downloading and installing software packages.

Step 1) Create a separate partition for installation of Arch Linux

For the dual boot setup to work, we need to create a separate partition on the hard drive on which Arch Linux will be installed. To do so, head over to the disk management utility by pressing Windows Key + R. In the dialogue box, type diskmgmt.msc and hit ENTER.

This launches the disk management utility displaying the various disk partitions on your hard drive. We are going to create an unallocated partition by shrinking the C drive. If you have a bigger partition than the C drive, feel free to use it for creating the separate partition,

So, we are going to right-click on drive C and select the ‘Shrink Volume’ option as shown

On the pop-up dialogue box that appears, we are going to specify the amount to shrink as shown. This is the amount that will be designated for the installation of Arch Linux. In our example, we have shrunk 20 GB of hard disk space will serve as the unallocated space.

Once you are satisfied, click on the ‘Shrink’ button.

Your unallocated space will be indicated as shown below. In our case, we have set aside approximately 20G for the installation of Arch Linux.

With the unallocated partition in place, plug in your bootable USB and reboot your PC.

Step 2) Configure BIOS to boot from bootable medium

Before you begin with the installation process, it’s prudent to set the boot priority in the BIOS to select your bootable medium as the most preferred option. Depending on your vendor, you can press the Esc, or F10 key to enter the BIOS and navigate to the boot priority Menu.

Also note that we are using the UEFI mode for installation.

Once you have selected your boot medium, press the ESC button to continue with the booting process.

Step 3) Begin the installation of Arch Linux

On the bootup screen, you will be presented with options as shown below. Select the first option – Arch Linux install medium (x86_64, UEFI) and hit ENTER.

This initialize Arch Linux as evidenced by the boot messages on the screen.

After a few seconds, this ushers you to the prompt as shown below.

To confirm that you have EFI support, run the command:

# ls /sys/firmware/efi/efivars

You should get some entries on the screen as shown. If nothing is listed on your screen, then it means you are using MBR and this guide won’t work for you in configuring up a dual boot setup.

As you begin the installation, you might want to ensure that you have internet connectivity. Internet connectivity is crucial in setting time and date.

You can ping Google’s DNS as shown:

# ping 8.8.8.8 -c 4

You should get a positive reply as shown.

Step 4) Update time and date

Next, we are going to update the system time and date using the timedatectl command as shown.

# timedatectl set-ntp true

You can thereafter confirm the time and date using the command

# timedatectl status

Step 5) Create & format Linux partitions

Next, we are going to partition our hard drive and create some Linux partitions. An easy way of doing this is using the cfdisk utility. Run the command:

# cfdisk

This displays all the partitions available including Windows partitions.

As you can see, we have some free space of 19.5G that we created earlier in step 1 from shrinking drive C on the Windows side. Using this partition, we shall create the following Linux partitions :

Root partition / 12G
swap partition 4G

To achieve this, we will navigate to the free space with 19.5G just after /dev/sda3 volume and hit ENTER. We will then specify the volume as 12G for the root partition as shown below. Then hit ENTER.

The root partition will be created with the Linux filesystem type as shown.

Next, we will create another partition for swap. Using the same method, we will proceed to the remaining free partition of 7G and select the ‘New’ option.

Specify the partition size as 4G

Since this will be our swap partition, we need to go the extra step and modify the partition type. Therefore, we will select the ‘type’ option and hit ENTER.

In the list that appears, select ‘Linux Swap’ and hit ENTER.

At this point, both the root and Linux swap partitions are created as seen from the partition table below.

To save the partitions, select the ‘Write’ option and hit ENTER.

When prompted if you want to write the partition to disk, simply type ‘yes’ and hit ENTER.

To exit cfdisk utility, select the ‘Quit’ option and hit ENTER.

Step 6) Format and mount the partitions

For the partitions to become usable and available for use, we need to format them and later mount them.

To format the root partition, run the command:

# mkfs.ext4 /dev/sda5

For swap partition, use the command:

# mkswap /dev/sda6

Then enable swap using the swapon command shown:

# swapon /dev/sda6

Next, mount the root partition to the /mnt directory

# mount /dev/sda5 /mnt

Additionally, we are going to create a directory for the EFI partition on which we will mount the Windows EFI system which , in our case is located on the /dev/sda1 partition.

# mkdir /mnt/efi

Then mount the EFI partition on the EFI mount point.

# mount /dev/sda1 /mnt/efi

Step 7) Install base system and other required Linux firmware packages

Next, we are going to install the central packages for our Linux system including the base and Linux-firmware packages.

# pacstrap /mnt base linux linux-firmware

This is going to take quite some time. At this point, you can take a much-deserved break and head out for a stroll and grab some coffee. When the installation is successful, you should get the following output.

Step Generate fstab file

The next step will be to generate the fstab file on the /mnt directory as follows.

# genfstab -U /mnt >> /mnt/etc/fstab

Step 9) Setup timezone

After generating the ftab file, navigate to the newly created root filesystem

# arch-chroot /mnt

You can verify that you are in the root filesystem using the command as shown.

# ls

Time zone information is found in the /usr/share/zoneinfo/ directory. To set your timezone, create a symbolic link to the /etc/localtime

Path.

# ln -sf /usr/share/zoneinfo/US/Pacific /etc/localtime

Next, sync the hardware clock using the command:

# hwclock --systohc

Step 10) Set up locale

The locale determines the system language, currency format, numbering and date on your system. This information is contained in the /etc/locale.gen file. So, open the file using the vim editor.

# vim /etc/locale.gen

NOTE: To install the vim editor, use the pacman command as follows:

# pacman -Sy vim

Once you have accessed the file, scroll and uncomment your preferred locale. In this case, we have decided to go with en_US.UTF-8 UTF-8

Save and exit the file. Next generate the locale configuration using the command.

# locale-gen

Next, create a new locale configuration file and save the locale as shown.

# echo "LANG=EN_US.UTF-8" > /etc/locale.conf

Step 11) Set up hostname

Next, we are going to configure the hostname of our Arch System. First, create a new file and specify the hostname as shown.

# echo linuxtechi > /etc/hostname

Afterwards, modify the /etc/hosts file as follows.

# echo "127.0.1.1  linuxtechi" >> /etc/hosts

Step 12) Install netctl Network Manager

To use the internet once the installation is complete and upon a reboot, we need to install a network manager. In this example we wil install the netctl network manager as follows

# pacman -Sy netctl

During the installation some optional dependencies for netctl are listed. We are going to install the following dependencies. These are:

dhcpcd – For DHCP support
wpa-supplicant – For wireless networking
ifplugd – For wired connections networking

These dependencies will help you set up networking without a problem when you next boot in to Arch Linux.

To install the optional dependencies, run the command below:

# pacman -Sy dhcpcd wpa-supplicant ifplugd

36-install-dhcpcd-wpa_supplicant-ifplugd

Step 13) Create a regular user

Next, we will create a regular user called linuxtechi and place him in the wheel group as follows.

# useradd -G wheel -m linuxtechi

The next step will be to assign a password to the user.

# passwd linuxtechi

Step 14) Install GRUB bootloader

We are getting close to the finish line. In this step, we will install the grub bootloader to enable us boot into our Arch Linux system upon a reboot.

We will install the grub bootloader package alongside the efi boot manager package since we are using the UEFI mode.

# pacman -S grub efibootmgr

Next, install the os-prober package which will enable Arch Linux to detect the Windows operating system.

# pacman -S os-prober

Then install grub on the EFI directory as shown.

# grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=GRUB

And install a grub configuration file as shown.

# grub-mkconfig -o /boot/grub/grub.cfg

The last line is an indication that Arch has detected the presence of Windows Boot manager on /dev/sda1 partition. Perfect!

The finally, set a password for the root user as shown.

# passwd

Then exit and reboot your system.

# exit
# reboot

Step 15) Boot into Arch Linux

When booting, the GRUB bootloader will display various options including booting into Arch Linux, which is the first option, and also booting into Windows which is the last option in my case.

Step 16) Post Installation tasks

One of the things I noted when I logged in is that I do not have any internet connection. This is an issue caused by the default dhcp profile settings which need to be modified to accommodate the network interface attached to the Arch Linux system.

To find the interfaces attached run the command:

$ ip link

The output confirms that our network interface is enp0s3

We need to modify the ethernet-dhcp file in the /etc/netctl/examples/ path and edit out network interface.

But first, lets copy the file to the /etc/netctl directory.

Switch to the root user

# su

Copy the ethernet-dhcp file to the /etc/netctl directory.

# cp /etc/netctl/examples/ethernet-dhcp  /etc/netctl/custom-dhcp-profile

Next, navigate to the /etc/netctl directory.

# cd /etc/netctl

Use the vim editor to edit the file.

# vim custom-dhcp-profile

The interface attribute is set to eth0.

However, as we saw earlier, our network interface is enp0s3. Therefore, modify it to enp0s3. Additionally, uncomment the line starting with the DHCPClient parameter.

DHCPClient=dhcpcd

This enables the system to accept IP addresses using the dhcp service.

Save and exit the configuration file. Next, enable the custom dhcp profile.

# netctl enable custom-dhcp-profile

And finally enable the dhcp service.

# systemctl enable dhcpcd.service

Your interface should now pick an IP address from the router and you should have an internet connection.

You can install an X windows system as shown,

$ sudo pacman -S xorg xorg-server

Then install a display manager. For example, to install GNOME, run:

$ sudo pacman -S gnome

Then start and enable gdm service

$ sudo systemctl start gdm
$ sudo systemctl enable gdm

This brings us to the end of this lengthy topic. Hopefully, you are now in a position to Dual boot Arch Linux with Windows on UEFI system.

Read Also : How to Create and Configure Sudo User on Arch Linux

Источник

This is an article detailing different methods of Arch/Windows coexistence.

Important information

Windows UEFI vs BIOS limitations

Microsoft imposes limitations on which firmware boot mode and partitioning style can be supported based on the version of Windows used:

Note: The following points only list configurations supported by the Windows Setup even though Windows itself may still work on these unsupported configurations. A good example of this is Windows 11 which still works on a BIOS/MBR configuration once the Windows Setup check is bypassed.

Windows 8/8.1 and 10 x86 32-bit support booting in IA32 UEFI mode from GPT disk only, OR in BIOS mode from MBR disk only. They do not support x86_64 UEFI boot from GPT/MBR disk, x86_64 UEFI boot from MBR disk, or BIOS boot from GPT disk. On market, the only systems known to ship with IA32 (U)EFI are some old Intel Macs (pre-2010 models?) and Intel Atom System-on-Chip (Clover trail and Bay Trail) Windows Tablets, which boot ONLY in IA32 UEFI mode and ONLY from GPT disk.
Windows 8/8.1 and 10 x86_64 versions support booting in x86_64 UEFI mode from GPT disk only, OR in BIOS mode from MBR disk only. They do not support IA32 UEFI boot, x86_64 UEFI boot from MBR disk, or BIOS boot from GPT disk.
Windows 11 only supports x86_64 and a boot in UEFI mode from GPT disk.

In case of pre-installed Systems:

All systems pre-installed with Windows XP, Vista or 7 32-bit, irrespective of Service Pack level, bitness, edition (SKU) or presence of UEFI support in firmware, boot in BIOS/MBR mode by default.
MOST of the systems pre-installed with Windows 7 x86_64, irrespective of Service Pack level, bitness or edition (SKU), boot in BIOS/MBR mode by default. Very few late systems pre-installed with Windows 7 are known to boot in x86_64 UEFI/GPT mode by default.
ALL systems pre-installed with Windows 8/8.1, 10 and 11 boot in UEFI/GPT mode. Up to Windows 10, the firmware bitness matches the bitness of Windows, ie. x86_64 Windows boot in x86_64 UEFI mode and 32-bit Windows boot in IA32 UEFI mode.

An easy way to detect the boot mode of Windows is to do the following[1]:

Boot into Windows
Press Win+R keys to start the Run dialog
In the Run dialog type msinfo32 and press Enter
In the System Information windows, select System Summary on the left and check the value of BIOS mode item on the right
If the value is UEFI, Windows boots in UEFI/GPT mode. If the value is Legacy, Windows boots in BIOS/MBR mode.

In general, Windows forces type of partitioning depending on the firmware mode used, i.e. if Windows is booted in UEFI mode, it can be installed only to a GPT disk. If Windows is booted in Legacy BIOS mode, it can be installed only to an MBR disk. This is a limitation enforced by Windows Setup, and as of April 2014 there is no officially (Microsoft) supported way of installing Windows in UEFI/MBR or BIOS/GPT configuration. Thus Windows only supports either UEFI/GPT boot or BIOS/MBR configuration.

Tip: Windows 10 version 1703 and newer supports converting from BIOS/MBR to UEFI/GPT using MBR2GPT.EXE.

Such a limitation is not enforced by the Linux kernel, but can depend on which boot loader is used and/or how the boot loader is configured. The Windows limitation should be considered if the user wishes to boot Windows and Linux from the same disk, since installation procedure of boot loader depends on the firmware type and disk partitioning configuration. In case where Windows and Linux dual boot from the same disk, it is advisable to follow the method used by Windows, ie. either go for UEFI/GPT boot or BIOS/MBR boot. See https://support.microsoft.com/kb/2581408 for more information.

Boot loader UEFI vs BIOS limitations

Most of the Linux boot loaders installed for one firmware type cannot launch or chainload boot loaders of the other firmware type. That is, if Arch is installed in UEFI/GPT or UEFI/MBR mode in one disk and Windows is installed in BIOS/MBR mode in another disk, the UEFI boot loader used by Arch cannot chainload the BIOS installed Windows in the other disk. Similarly if Arch is installed in BIOS/MBR or BIOS/GPT mode in one disk and Windows is installed in UEFI/GPT in another disk , the BIOS boot loader used by Arch cannot chainload UEFI installed Windows in the other disk.

The only exceptions to this are GRUB in Apple Macs in which GRUB in UEFI mode can boot BIOS installed OS via appleloader command (does not work in non-Apple systems), and rEFInd which technically supports booting legacy BIOS OS from UEFI systems, but does not always work in non-Apple UEFI systems as per its author Rod Smith.

However if Arch is installed in BIOS/GPT in one disk and Windows is installed in BIOS/MBR mode in another disk, then the BIOS boot loader used by Arch can boot the Windows in the other disk, if the boot loader itself has the ability to chainload from another disk.

Note: To dual-boot with Windows on same disk, Arch should follow the same firmware boot mode and partitioning combination used by the Windows installation.

Windows Setup creates a 100 MiB EFI system partition (except for Advanced Format 4K native drives where it creates a 300 MiB ESP), so multiple kernel usage is limited. Workarounds include:

If you are installing Windows from scratch, you can dictate the size of the EFI system partition during installation. See #The EFI system partition created by Windows Setup is too small
Mount ESP to /efi and use a boot loader that has file system drivers and is capable of launching kernels that reside on other partitions.
Reduce the size of the Windows partition and replace the existing ESP with a new, larger one.
Backup and delete unneeded fonts in esp/EFI/Microsoft/Boot/Fonts/ [2].
Backup and delete unneeded language directories in esp/EFI/Microsoft/Boot/ (e.g. to only keep en-US).
Use a higher, but slower, compression for the initramfs images making sure to decompress the loadable kernel modules and firmware. E.g.

COMPRESSION="xz"
COMPRESSION_OPTIONS=(-9e)
MODULES_DECOMPRESS="yes"

UEFI Secure Boot

All pre-installed Windows 8/8.1, 10 and 11 systems by default boot in UEFI/GPT mode and have UEFI Secure Boot enabled by default. This is mandated by Microsoft for all OEM pre-installed systems.

Arch Linux install media does not support Secure Boot yet. See Secure Boot#Booting an installation medium.

It is advisable to disable UEFI Secure Boot in the firmware setup manually before attempting to boot Arch Linux. Windows 8/8.1, 10 and 11 SHOULD continue to boot fine even if Secure boot is disabled. The only issue with regards to disabling UEFI Secure Boot support is that it requires physical access to the system to disable secure boot option in the firmware setup, as Microsoft has explicitly forbidden presence of any method to remotely or programmatically (from within OS) disable secure boot in all Windows 8/8.1 and above pre-installed systems

Note:

If Windows used BitLocker and stored the key in the TPM for automatic unlock on boot, it fails to boot when Secure Boot is disabled, instead showing a BitLocker recovery screen. This is not permanent however, and you can easily boot Windows again by simply re-enabling Secure Boot.
On Windows 11, disabling Secure Boot after install will not cause problems as long as TPM is working normally.

Warning:

The factual accuracy of this article or section is disputed.

Reason:

Secure Boot changes should not affect BitLocker: the issue might be self-signing the windows boot loader and chain-loading it from a boot loader: as long as the Windows boot loader stays signed with MS keys, and the Microsoft certs enrolled it should be fine.
Is the issue disabling it and booting Windows or disabling, reenabling it and then booting Windows?
The first one would be understandable, the second one is something to warn about.

(Discuss in Talk:Dual boot with Windows)

If you intend to use Secure Boot for Linux as well, you may need to perform changes to the Secure Boot settings. Those changes prevent unlocking the BitLocker disk without the recovery key, leading to permanent data loss. Before proceeding, check if this is the case and save your BitLocker recovery key if not already done. This is especially important if Windows was preinstalled by the vendor.

Fast Startup and hibernation

There are two OSs that can be hibernated, you can hibernate Windows and boot Linux (or another OS), or you can hibernate Linux and boot Windows, or hibernate both OSs.

Warning: Data loss can occur if Windows hibernates and you dual boot into another OS and make changes to files on a filesystem (such as NTFS) that can be read and written to by Windows and Linux, and that has been mounted by Windows [3]. Similarly, data loss can occur if Linux hibernates, and you dual boot into another OS etc. Windows may hibernate even when you press shutdown, see section #Windows settings.

For the same reason, if you share one EFI system partition between Windows and Linux, then the EFI system partition may be damaged if you hibernate (or shutdown with Fast Startup enabled) Windows and then start Linux, or hibernate Linux and then start Windows.

ntfs-3g added a safe-guard to prevent read-write mounting of hibernated NTFS filesystems, but the NTFS driver within the Linux kernel has no such safeguard.

Windows cannot read filesystems such as ext4 by default that are commonly used for Linux. These filesystems do not have to be considered, unless you install a Windows driver for them.

Windows settings

Fast Startup is a feature in Windows 8 and above that hibernates the computer rather than actually shutting it down to speed up boot times.

There are multiple options regarding the Windows settings for Fast Startup and hibernation that are covered in the next sections.

disable Fast Startup and disable hibernation
disable Fast Startup and enable hibernation
enable Fast Startup and enable hibernation

The procedure of disabling Fast Startup is described in the tutorials for Windows 8, Windows 10 and Windows 11. In any case if you disable a setting, make sure to disable the setting and then shut down Windows, before installing Linux; note that rebooting is not sufficient.

Disable Fast Startup and disable hibernation

This is the safest option, and recommended if you are unsure about the issue, as it requires the least amount of user awareness when rebooting from one OS into the other. You may share the same EFI system partition between Windows and Linux.

In a Windows command-line shell with administrator privileges:

> powercfg /H off

Disable Fast Startup and enable hibernation

This option requires user awareness when rebooting from one OS into the other.
If you want to start Linux while Windows is hibernated, which is a common use case, then

you must use a separate EFI system partition (ESP) for Windows and Linux, and ensure that Windows does not mount the ESP used for Linux. As there can only be one ESP per drive, the ESP used for Linux must be located on a separate drive than the ESP used for Windows. In this case Windows and Linux can still be installed on the same drive in different partitions, if you place the ESP used by linux on another drive than the Linux root partition.
you can not read-write mount any filesystem in Linux, that is mounted by Windows while Windows is hibernated. You should be extremely careful about this, and also consider Automount behaviour.
If you shut down Windows fully, rather than hibernating, then you can read-write mount the filesystem.

Note: You can avoid this issue for a drive by mounting a drive as an external drive in Windows and ejecting the drive in Windows before hibernating.

Enable Fast Startup and enable hibernation

The same considerations apply as in case «Disable Fast Startup and enable hibernation», but since Windows can not be shut down fully, only hibernated, you can never read-write mount any filesystem that was mounted by Windows while Windows is hibernated.

Note: Windows updates may re-enable Fast Startup, as reported in [4]^{[dead link 2024-07-30 ⓘ]}.

Windows filenames limitations

Windows is limited to filepaths being shorter than 260 characters.

Windows also puts certain characters off limits in filenames for reasons that run all the way back to DOS:

< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)

These are limitations of Windows and not NTFS: any other OS using the NTFS partition will be fine. Windows will fail to detect these files and running chkdsk will most likely cause them to be deleted. This can lead to potential data-loss.

NTFS-3G applies Windows restrictions to new file names through the windows_names option: ntfs-3g(8) § Windows_Filename_Compatibility (see fstab).

Installation

The recommended way to set up a Linux/Windows dual booting system is to first install Windows, only using part of the disk for its partitions. When you have finished the Windows setup, boot into the Linux install environment where you can create and resize partitions for Linux while leaving the existing Windows partitions untouched. The Windows installation will create the EFI system partition which can be used by your Linux boot loader. If you are installing Windows from scratch, do note that the EFI System partition created by Windows Setup will be too small for most use cases. See #The EFI system partition created by Windows Setup is too small.

Windows before Linux

BIOS systems

Using a Linux boot loader

You may use any multi-boot supporting BIOS boot loader.

Using the Windows Vista/7/8/8.1 boot loader

This section explains how to:

install a linux boot loader on a partition instead of the MBR;
copy this boot loader to a partition readable by the Windows boot loader;
use the windows boot loader to start said copy of the linux boot loader.

Note: Some documents state that the partition being loaded by the Windows boot loader must be a primary partition but usage of an extended partition has been documented as working.

When installing the boot loader, install it on your /boot partition rather than the MBR. For details on doing this with GRUB, see GRUB/Tips and tricks#Install to partition or partitionless disk, for Syslinux, see the note at Syslinux#Manually, for LILO see LILO#Install to partition or partitionless disk.

Make a copy of the VBR:
```
dd if=/dev/disk of=/path/to/linux.bin bs=512 count=1
```
where /dev/disk is the path of the partition on which your boot loader is installed and /path/to/ is the mounted filesystem on which you want the copy to be readable by the Windows boot loader.

On Windows, the linux.bin file should now be accessible. Run cmd with administrator privileges (navigate to Start > All Programs > Accessories, right-click on Command Prompt and select Run as administrator):
```
bcdedit /create /d "Linux" /application BOOTSECTOR
```
BCDEdit will return a UUID for this entry. This will be referred to as UUID in the remaining steps.
```
bcdedit /set UUID device partition=c: (or the drive letter on which linux.bin is kept)
bcdedit /set UUID path \path\to\linux.bin
bcdedit /displayorder UUID /addlast
bcdedit /timeout 30
```

On reboot, both Windows and Linux should now show up in the Windows boot loader.

Note: On some hardware, the Windows boot loader is used to start another OS with a second power button (e.g. Dell Precision M4500).

For more details, see https://www.iceflatline.com/2009/09/how-to-dual-boot-windows-7-and-linux-using-bcdedit/

UEFI systems

If you already have Windows installed, it will already have created some partitions on a GPT-formatted disk:

a Windows Recovery Environment partition, generally of size 499 MiB,
an EFI system partition with a FAT32 filesystem, containing the Windows Boot Manager,
a Microsoft Reserved Partition, generally of size 128 MiB,
a Microsoft basic data partition with a NTFS filesystem, which corresponds to C:,
potentially system recovery and backup partitions and/or secondary data partitions (corresponding often to D: and above).

Using the Disk Management utility in Windows, check how the partitions are labelled and which type gets reported. The Reserved Partition may not be visible in the Disk Management utility in which case it can be identified using diskpart in windows cmd. This will help you understand which partitions are essential to Windows, and which others you might repurpose. The Windows Disk Management utility can also be used to shrink Windows (NTFS) partitions to free up disk space for additional partitions for Linux.

Warning: The first 4 partitions in the above list are essential, do not delete them.

You can then proceed with partitioning, depending on your needs. The boot loader needs to support chainloading other EFI applications to dual boot Windows and Linux. An additional EFI system partition should not be created, as it may prevent Windows from booting.

Note: It only appears when Linux is installed on the second hard disk and a new EFI system partition is created on the second hard disk.

Simply mount the existing partition.

Tip:

rEFInd and systemd-boot will autodetect Windows Boot Manager (\EFI\Microsoft\Boot\bootmgfw.efi) and show it in their boot menu automatically. For GRUB follow either GRUB#Windows installed in UEFI/GPT mode to add boot menu entry manually or GRUB#Detecting other operating systems for a generated configuration file.
To save space on the EFI system partition, especially for multiple kernels, increase the initramfs compression.

Computers that come with newer versions of Windows often have Secure Boot enabled. You will need to take extra steps to either disable Secure Boot or to make your installation media compatible with secure boot (see above and in the linked page).

Linux before Windows

Even though the recommended way to set up a Linux/Windows dual booting system is to first install Windows, it can be done the other way around. In contrast to installing Windows before Linux, you will have to set aside a partition for Windows, say 40GB or larger, in advance. Or have some unpartitioned disk space, or create and resize partitions for Windows from within the Linux installation, before launching the Windows installation.

UEFI firmware

Windows will use the already existing EFI system partition.
Follows an outline, assuming Secure Boot is disabled in the firmware.

Boot into windows installation. Watch to let it use only the intended partition, but otherwise let it do its work as if there is no Linux installation.
Follow the #Fast Startup and hibernation section.
Fix the ability to load Linux at start up, perhaps by following #Cannot boot Linux after installing Windows. It was already mentioned in #UEFI systems that some Linux boot managers will autodetect Windows Boot Manager. Even though newer Windows installations have an advanced restart option, from which you can boot into Linux, it is advised to have other means to boot into Linux, such as an arch installation media or a live CD.

Windows 10 with GRUB

The following assumes GRUB is used as a boot loader (although the process is likely similar for other boot loaders) and that Windows 10 will be installed on a GPT block device with an existing EFI system partition (see the «System partition» section in the Microsoft documentation for more information).

Create with program gdisk on the block device the following three new partitions. See [5] for more precise partition sizes.

Min size	Code	Name	File system
16 MB	0C01	Microsoft reserved	N/A
~40 GB	0700	Microsoft basic data	NTFS
300 MB	2700	Windows RE	NTFS

Create NTFS file systems on the new Microsoft basic data and Windows RE (recovery) partitions using the mkntfs program from package ntfs-3g.

Reboot the system into a Windows 10 installation media. When prompted to install select the custom install option and install Windows on the Microsoft basic data partition created earlier. This should also install Microsoft EFI files in the EFI system partition.

After installation (set up of and logging into Windows not required), reboot into Linux and generate a GRUB configuration for the Windows boot manager to be available in the GRUB menu on next boot.

Troubleshooting

Couldn’t create a new partition or locate an existing one

See #Windows UEFI vs BIOS limitations.

Cannot boot Linux after installing Windows

See Unified Extensible Firmware Interface#Windows changes boot order.

Restoring a Windows boot record

By convention (and for ease of installation), Windows is usually installed on the first partition and installs its partition table and reference to its boot loader to the first sector of that partition. If you accidentally install a boot loader like GRUB to the Windows partition or damage the boot record in some other way, you will need to use a utility to repair it. Microsoft includes a boot sector fix utility FIXBOOT and an MBR fix utility called FIXMBR on their recovery discs, or sometimes on their install discs. Using this method, you can fix the reference on the boot sector of the first partition to the boot loader file and fix the reference on the MBR to the first partition, respectively. After doing this you will have to reinstall GRUB to the MBR as was originally intended (that is, the GRUB boot loader can be assigned to chainload the Windows boot loader).

If you wish to revert back to using Windows, you can use the FIXBOOT command which chains from the MBR to the boot sector of the first partition to restore normal, automatic loading of the Windows operating system.

Of note, there is a Linux utility called ms-sys^AUR that can install MBR’s. However, this utility is only currently capable of writing new MBRs (all OS’s and file systems supported) and boot sectors (a.k.a. boot record; equivalent to using FIXBOOT) for FAT file systems. Most LiveCDs do not have this utility by default, so it will need to be installed first, or you can look at a rescue CD that does have it, such as Parted Magic.

First, write the partition info (table) again by:

# ms-sys --partition /dev/sda1

Next, write a Windows 2000/XP/2003 MBR:

# ms-sys --mbr /dev/sda  # Read options for different versions

Then, write the new boot sector (boot record):

# ms-sys -(1-6)          # Read options to discover the correct FAT record type

ms-sys can also write Windows 98, ME, Vista, and 7 MBRs as well, see ms-sys -h.

Restoring an accidentally deleted EFI system partition

If you have a GPT-partitioned disk and erased (e.g. with mkfs.fat -F32 /dev/sdx) the EFI system partition, you will notice that Windows Boot Manager will either disappear from your boot options, or selecting it will send you back to the UEFI.

To remedy it, boot with a Windows installation media, press Shift+F10 to open the console (or click NEXT > Repair Computer > Troubleshoot… > Advanced > Command Prompt), then start the diskpart utility:

X:\Sources> diskpart
DISKPART> list disk

Select the appropriate hard drive by typing:

DISKPART> select disk number

Make sure that there is a partition of type system (the EFI system partition):

DISKPART> list partition

Select this partition:

DISKPART> select partition number

and assign a temporary drive letter to it:

DISKPART> assign letter=G:

DiskPart successfully assigned the drive letter or mount point.

To make sure that drive letter is correctly assigned:

DISKPART> list vol

 Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
 ----------  ---  -----------  -----  ----------  -------  ---------  --------
 Volume 0     E                       DVD-ROM         0 B  No Media
 Volume 1     C                NTFS   Partition    195 GB  Healthy    Boot
 Volume 2         WINRE        NTFS   Partition    400 MB  Healthy    Hidden
 Volume 3     G                FAT32  Partition    499 MB  Healthy    System

Close diskpart:

DISKPART> exit

Navigate to C:\ (or what your system drive letter is):

X:\Sources> cd /d C:\

Next is the «magic» command, which recreate the BCD store (with /s for the mount point, /f for firmware type, optionally add /v for verbose):

C:\> bcdboot C:\Windows /s G: /f UEFI

Tip: If it hangs up after a minute, hit Ctrl+c. This happens sometimes, but you will get a message like boot files successfully created and it will have worked just fine.

You should now have Windows Boot Manager working as a boot option, and thus have access to Windows. Just make sure to never format your EFI system partition again!

Note: Remove the drive letter G assigned to the EFI system partition to keep it from showing up in My Computer.

See [6], [7] and [8].

The EFI system partition created by Windows Setup is too small

By default, Windows Setup creates a 100 MiB EFI system partition (except for Advanced Format 4K native drives where it creates a 300 MiB ESP). This is generally too small to fit everything you need. You can replace the existing EFI system partition with a new, larger one.

If you are installing Windows from scratch, you can dictate the size of the EFI system partition during installation[9]:

Select your installation target and make sure it has no partitions.
Click New and then the Apply buttons. The Windows installer will then generate the expected partitions (allocating nearly everything to its primary partition) and just 100MB to the EFI.
Use the UI to delete the System, MSR, and Primary partitions. Leave the Recovery partition (if present) alone.
Press Shift+F10 to open the Command Prompt.
Type diskpart.exe and press Enter to open the disk partitioning tool.
Type list disk and press Enter to list your disks. Find the one you intend to modify and note its disk number.
Type select disk disk_number with the disk number to modify.
Type create partition efi size=size with the desired size of the ESP in Mebibytes (MiB), and press Enter. See the note at EFI system partition#Create the partition for the recommended sizes.
Type format quick fs=fat32 label=System and press Enter to format the ESP
Type exit and press Enter to exit the disk partitioning tool and exit followed by Enter again.

Once Windows is installed, you can resize the primary partition down within Windows and then reboot and go about your usual Arch install, filling the space you just created.

Alternatively, you can use the Arch install media to create a single EFI system partition of your preferred size before you install Windows on the drive. Windows Setup will use the EFI system partition you made instead of creating its own.

Unable to install Windows Cumulative Update on BIOS system

On BIOS systems, Windows cumulative updates may fail with the error We couldn’t complete the updates. Undoing changes. Don’t turn off your computer. In such case, while in Windows, you need to set the Windows partition as active.

C:\> diskpart
DISKPART> list disk
DISKPART> select disk number
DISKPART> list partition
DISKPART> select partition number
DISKPART> active
DISKPART> exit

After successfully installing the Windows update, mark back your Linux partition as active, using the commands above.

Note: Setting a partition as active in the diskpart tool in Windows has the same effect as setting the boot flag in GParted.

Time standard

Recommended: Set both Arch Linux and Windows to use UTC, following System time#UTC in Microsoft Windows. Some versions of Windows revert the hardware clock back to localtime if they are set to synchronize the time online. This issue appears to be fixed in Windows 10.
Not recommended: Set Arch Linux to localtime and disable all time synchronization daemons. This will let Windows take care of hardware clock corrections and you will need to remember to boot into Windows at least two times a year (in Spring and Autumn) when DST kicks in. So please do not ask on the forums why the clock is one hour behind or ahead if you usually go for days or weeks without booting into Windows.

Bluetooth pairing

When it comes to pairing Bluetooth devices with both the Linux and Windows installation, both systems have the same MAC address, but will use different link keys generated during the pairing process. This results in the device being unable to connect to one installation, after it has been paired with the other. To allow a device to connect to either installation without re-pairing, follow Bluetooth#Dual boot pairing.

Creating Free Space For ARCH LINUX

Open command prompt and type DISKMGMT to access disk manager.
View connected drives and their partitions.
Identify the target drive (e.g., Drive 0) with its partitions.
Choose the C Or D or Any Drive for ArchLinux and right-click on it.
Select “shrink volume” to allocate free space for ArchLinux.Allocate a minimum of 40GB or more (type in MegaBytes, e.g., 200,000 MB).Click “shrink” to create unallocated free space

Download ArchLinux & Make Bootable USB

Download the Arch ISO from HERE
Connect a USB stick to your computer.Use Rufus to burn the downloaded ISO image to the USB drive.

Create System Restore Point

It is recommended to create a System Restore point before installing Archlinux. This option allows you to take a snapshot of the current state of the system. If something goes wrong with the Arch installation, you can use this backup to restore your system to normal.

BIOS Settings

Reboot your computer.
During the reboot, enter the BIOS settings using the keyboard shortcut (commonly F2, F9, or ESC).
In UEFI BIOS, enable USB boot and set the USB drive as the primary boot order.
Disable secure boot in the BIOS settings.
If available, enable options like Microsoft’s third-party UEFI.
Consider clearing any keys or certificates after disabling secure boot.
Save the changes in the BIOS settings.
Your system should now boot into ArchLinux from the USB drive.
If the boot fails, use the boot menu to load Arch install media.

Increase Console FONT

Now, on your monitor, you will see a terminal expecting input. Note that the mouse functionality is disabled so you need to rely on the keyboard

Type setfont ter-132n and press enter to increase the size of the console.

Using iWCTL for WIFI Connection

If using built-in WiFi support, use the iwctl tool to connect to the internet.

To find list of network interfaces type: iwctl device list
To search for WIFI Networks type: iwctl station wlan0 get-networks
To connect to WIFI network type: iwctl station wlan0 connect WIFI_NAME
Once connected run : ping google.com to check internet connection (Interrupt Ping with CTRL + C)
Then type the command to syncnorize the package database: pacman -Sy
Then Type this command : pacman -S archlinux-keyring

Create Partitions For Arch Linux

Type lsblk to list all connected drives on the PC.
Identify the main drives, focusing on SDA or NVME (ignore loops).
NVME0n1 is MY drive with Windows 11, and SDA is the BootableUSB.

Create partitions for Arch Linux using earlier free space.
Type cfdisk /dev/nvme0n1 and press enter.
Use arrow keys for selection and enter key for confirmation.

Scroll to free space and create 3 partitions: EFI, ROOT, and swap.
Create EFI partition (e.g., 800MB) with type EFI System.
Create ROOT partition (e.g., 20GB or higher) with type Linux file system.
Use remaining free space for swap partition with type Linux SWAP.
Write changes to alter the disk and exit from CFDisk.

Formatting Partitions

Type lsblk to view all newly created partitions
NVME0N1P5 for EFI, NVME0N1P6 for Root, and NVME0N1P7 for Swap.
Format the Arch EFI Partition (e.g., NVME0N1p5)
mkfs.fat -F32 /dev/nvme0n1p5
Format the root partition (e.g., NVME0N1p6)
mkfs.ext4 /dev/NVME0N1p6
Format the swap partition (e.g., nvme0n1p7)
mkswap /dev/nvme0n1p7

Mount Partitions

Mount the root partition (e.g., NVME0n1p6) to the “mnt” directory.
mount /dev/nvme0n1p6 /mnt
Create a directory inside “mnt” and name it “boot,” then mount the EFI partition to this directory.

mkdir /mnt/boot

mount /dev/nvme0n1p5 /mnt/boot

Enable the swap partition by typing
swapon /dev/nvme0n1p7
Verify proper mounting of all partitions by typing lsblk

Installing ArchLinux

Now, it’s time to install the Arch Linux to the root partition which Is mounted to /mnt.

pacstrap -i /mnt base base-devel linux linux-headers linux-firmware amd-ucode sudo git nano vim neofetch htop cmake make bluez bluez-utils networkmanager cargo gcc mpv

Run the above command to start installing the base system of Arch Linux. Accept the defaults. This will take some time, sit back, relax, and don’t interrupt the computer.

Generate File System Table (FSTAB)

It’s time to generate a file system table. If you notice, the NVME partitions are mounted to the live session of USB, but when we boot arch from the main drive we need to tell the system to mount all these partitions to the same location.

genfstab -U /mnt >> /mnt/etc/fstab

CHROOT To Newley Installed system

So far we are running everything from the Live Session. It’s Time to enter, into the drive where we have installed Arch Linux. For that type:

 arch-chroot /mnt

Now you can see the prompt has changed to something else, which means we have entered into the actual drive as a root user.

Change Root Password

Then type passwd and set the root password. This is a superuser account and is known as a top-tier user in Linux.

Adding a Standard User

Also, we are going to create a standard user by tying the below command and replace the username placeholder with your name

useradd -m -g users -G wheel,storage,video,audio -s /bin/bash USER_NAME

Then set the password by typing

passwd USER_NAME

Now, we have added this new user to the wheel group and other groups. The Wheel group allows the user to access root privileges with a sudo command. For that, we need to edit the sudoers file. Type the below command

EDITOR=nano visudo

Uncomment the line in the image and save the changes with CTRL + O and CTRL + X to Exit.

SetupTimezone/Region

Use ln -sf /usr/share/zoneinfo/ and press tab to see the list of available options.
Choose the appropriate timezone, for example
ln -sf /usr/share/zoneinfo/Asia/Kolkata /etc/localtime
Synchronize the current time with the hardware clock using hwclock --systohc

Setup System Language

It’s time to set a system language by generating a locale. Type the below command

nano /etc/locale.gen

Scroll all the way and uncomment the below line in the image and save the changes. This is going to tell the system to use American English as the system locale.

Now type the below commands to generate a locale & Config file

locale-gen

echo "LANG=en_US.UTF-8" >> /etc/locale.conf

Setup Host Name

Now, type the below command to set up the hostname of this computer. In this case, I am going to say “archlinux” and save the changes

echo "archlinux" >> /etc/hostname

Then type nano /etc/hosts and add the below lines.

Make sure you replace the GREEN part with your hostname and save the changes

Grub-Installation

It’s time to install the grub boot loader which is going to help boot arch Linux. Type the below commands

pacman -S grub efibootmgr dosfstools mtools

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB

grub-mkconfig -o /boot/grub/grub.cfg

Enable Services

systemctl enable bluetooth

systemctl enable NetworkManager

Then exit from Chroot by typing exit & Unmount the partitions by typing

umount -lR /mnt

Shutdown the computer and eject the USB Stick

Connecting TO WIFI Using NMCLI

Once the system is restarted you can see the grub menu. From here you can boot into only Arch for now and Windows 11 boot entry will be missing.

We are going to fix that issue in a moment. For now, let’s just boot into Arch Linux. Now log in with your user account & increase the console font by typing below command

setfont -d

Check the status of all network interfaces: nmcli dev status
Turn on the WIFI Radio: nmcli radio wifi on.
View available wifi networks with the command specified
nmcli dev wifi list
Connect to wifi using the relevant command, replace placeholders with your network information and enclosing the password in double-quotes
sudo nmcli dev wifi connect WIFI_NAME password "WIFI_PASSWORD"
Update the PACMAN database with: sudo pacman -Sy

Installing GUI

It’s time to install the desktop environment. For Plasma Desktop Run the below commands

sudo pacman -S xorg sddm plasma-meta plasma-wayland-session kde-applications noto-fonts noto-font-emoji ttf-dejavu ttf-font-awesome

sudo systemctl enable sddm

For GNOME Desktop

sudo pacman -S xorg gdm gnome gnome-extra

sudo systemctl enable gdm

Then Reboot the system

sudo reboot now

and this time Arch Linux will boot With a GUI Environment

Fix Discover App Backend

The first thing to do after installing ArchLinux is to fix the Discover app backend. To do so open KONSOLE and type the below command to install flatpak and use it as a backend for discover.

sudo pacman -Sy flatpak

Install NVIDIA Drivers (Optional)

If you have a modern NVIDIA graphic card, it’s recommended to install NVIDIA proprietary drivers.

"This is completely optional, installing this package on older systems may or may not work, so please refer to this article"

Anyway, inside the konsole you can type the below command to set up NVIDIA drivers.

sudo pacman -Sy nvidia

Once it’s done, reboot your computer. Now if I type nvidia-smi command inside the terminal you can see it shows the NVIDIA driver information.

Adding Windows Entry To GRUB

Install OS-Prober with the command provided
sudo pacman -Sy os-prober
Edit the grub file, sudo nano /etc/default/grub
Set the GRUB_TIMEOUT=20
Scroll to the bottom and uncomment the line related to os-prober.

Save changes with ctrl + o and exit with ctrl + x.

Run grub-mkconfig -o /boot/grub/grub.cfg to update the grub configuration.Verify that Windows boot manager is detected.

Reboot the system. Using the grub menu you can boot into either Arch or Windows 11

Removing ArchLinux From Dual Boot

Reboot your computer and boot into Windows 11.
Open Disk Management utility by typing diskmgmt in the search bar.
Delete each new partition by right Clicking created during ArchLinux installation, starting with swap and root partitions.

“Note that the LINUX EFI partition cannot be deleted using Disk Management“
Open Command Prompt as an administrator and type DISKPART
Type list disk to view all connected drives, select the appropriate drive with
select disk 0
Type list partition to view all partitions on the selected drive.
Identify the Arch EFI partition (e.g., partition 5).

Select the Arch EFI partition with select partition [number]
Type DELETE PARTITION OVERRIDE to remove the partition.
Verify the deletion in Disk Management; the free space is now available.
Utilize the gained free space to merge it back into Windows 11 partitions

Watch the YouTube Video:

Источник

Создание загрузочной флешки

Установка Windows

Подготовка к установке Arch Linux

Установка системы

Настройка системы

Установка загрузчика

Перезагрузка

Добавление Windows в GRUB

Если при запуске Arch Linux не получается войти в root или другого пользователя

Prerequisites

Step 1) Create a separate partition for installation of Arch Linux

Step 2) Configure BIOS to boot from bootable medium

Step 3) Begin the installation of Arch Linux

Step 4) Update time and date

Step 5) Create & format Linux partitions

Step 6) Format and mount the partitions

Step 7) Install base system and other required Linux firmware packages

Step Generate fstab file

Step 9) Setup timezone

Step 10) Set up locale

Step 12) Install netctl Network Manager

Step 13) Create a regular user

Step 14) Install GRUB bootloader

Step 15) Boot into Arch Linux

Step 16) Post Installation tasks

Important information

Windows UEFI vs BIOS limitations

Boot loader UEFI vs BIOS limitations

UEFI Secure Boot

Fast Startup and hibernation

Windows settings

Disable Fast Startup and disable hibernation

Disable Fast Startup and enable hibernation

Enable Fast Startup and enable hibernation

Windows filenames limitations

Installation

Windows before Linux

BIOS systems

Using a Linux boot loader

Using the Windows Vista/7/8/8.1 boot loader

UEFI systems

Linux before Windows

UEFI firmware

Windows 10 with GRUB

Troubleshooting

Couldn’t create a new partition or locate an existing one

Cannot boot Linux after installing Windows

Restoring a Windows boot record

Restoring an accidentally deleted EFI system partition

The EFI system partition created by Windows Setup is too small

Unable to install Windows Cumulative Update on BIOS system

Time standard

Bluetooth pairing

See also

Creating Free Space For ARCH LINUX

Download ArchLinux & Make Bootable USB

Create System Restore Point

BIOS Settings

Increase Console FONT

Using iWCTL for WIFI Connection

Create Partitions For Arch Linux

Formatting Partitions

Mount Partitions

Installing ArchLinux

Generate File System Table (FSTAB)

CHROOT To Newley Installed system

Change Root Password

Adding a Standard User

SetupTimezone/Region

Setup System Language

Setup Host Name

Grub-Installation

Connecting TO WIFI Using NMCLI

Installing GUI

Fix Discover App Backend

Install NVIDIA Drivers (Optional)

Adding Windows Entry To GRUB

Removing ArchLinux From Dual Boot

Watch the YouTube Video: