@manuel I have Windows 10 and Antregos installed on my laptop, thx!

chroot and then reinstall intel-ucode, grub mkconfig will not work.
Also tried to update again under chroot and still no luck.

@joekamprad I only have one Windows 10 installation on partition sdb3, the one on sda1 is the data disk (my /D haha). I mounted the EFI/boot to sdb1 for the sake of dual booting

I haven’t tried out chroot into installed Antergos yet, I will try it out as soon as I have free time, I think it might be the solution to it.

sdb–120G SSD (Windows 10 + EFI + recovery)
sda–1TB HDD (Windows storage + Antergos)

@joekamprad I did this and it would print out “file ‘/intel-ucode.img’ not found”

@manuel

(sorry for using manjaro xD too lazy to remake the LiveUSB)

[manjaro-gnome manjaro]# fdisk -l
Disk /dev/loop0: 64.9 MiB, 67997696 bytes, 132808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 290.9 MiB, 304984064 bytes, 595672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 875.2 MiB, 917659648 bytes, 1792304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop3: 399.4 MiB, 418775040 bytes, 817920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A307AC73-93CE-4EF3-8427-D0F9E51794EA

Device Start End Sectors Size Type
/dev/sda1 2048 1543921663 1543919616 736.2G Microsoft basic data
/dev/sda2 1748719616 1937901255 189181640 90.2G Linux filesystem
/dev/sda3 1937901256 1953525134 15623879 7.5G Linux filesystem

Disk /dev/sdb: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 7D74A3C4-2BF9-40ED-8E68-5A6A31720C7D

Device Start End Sectors Size Type
/dev/sdb1 2048 534527 532480 260M EFI System
/dev/sdb2 534528 567295 32768 16M Microsoft reserved
/dev/sdb3 567296 249047039 248479744 118.5G Microsoft basic data
/dev/sdb4 249047040 250068991 1021952 499M Windows recovery environment

Disk /dev/sdc: 7.2 GiB, 7707033600 bytes, 15052800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x117a4ae7

Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 64 3453131 3453068 1.7G cd unknown
/dev/sdc2 3453132 3461323 8192 4M ef EFI (FAT-12/16/32)

@manuel I am not sure but I do know that I mounted boot on the ESP partition of Windows 10 for the sake of dual booting. So I think that means they are on different partition right?

EDIT1: When I use LiveUSB to find the intel-ucode.img file, i did find it under this route: /boot/intel-ucode.img

@paul.fabre3000 Yes I just tried them both again but still the same results, it still said file not found. Really weird

@paul.fabre3000 I just boot into LiveUSB and I the intel-ucode.img file is right there in the boot folder, so why would I get error message that said no such file when I add /boot/intel-ucode.img to my grub initrd line?

@paul.fabre3000 May I ask that how can I install new packages without being able to enter tty? Or can I do it with LiveUSB? Thanks!

Thanks a lot for the find method, it might help out

@manuel It should be but when I add the initrd lines it told me that system cannot find the file, but still thanks for your suggestion, it is surely a good idea and I will try it out~~

But paul.fabre3000 might also be right that the problem of being unable to boot may be caused by the other error I added.