I have 2 systems installed on separate drives - Windows and Linux. GRUB works fine. However, when I reboot from linux the GRUB menu does not appear, I have to do a reboot right away and then it is ok. With Windows there is no such effect - there it appears every time I reboot. Why does this happen and how to change it?
If I had to venture a guess… your monitor is not kicking on faster than the GRUB timer. After the reboot, your monitor is already on, and allows you to see GRUB quicker than the timer.
Get grub-customizer and turn off the timer, or set it for a longer duration.
[Arch Linux - grub-customizer 5.2.5-1 (x86_64)]
https://archlinux.org/packages/extra/x86_64/grub-customizer/
Mod: Warning - grub customiser is NOT an approved software. See the Tutuorial:
I would consider this bad advice - the general consensus based upon many bad experiences here seems to be to not touch grub-customizer, not even with a ten foot pole.
The timer can be adjusted easily by editing the file /etc/default/grub
the parameter:
GRUB_TIMEOUT= ...
and afterwards running:
update-grub
At least save all the relevant grub configuration and know what grub-customizer adds and changes - so you can revert it when things go sideways.
6 Likes
I agree 100% with this.
It makes changes which are not easy to reverse unless you really know what you are doing.
Seen this many times over the years. 
3 Likes
There could potentially be several reasons for what you describe. Some system information might help narrow it down; please provide:
System Information:
Output of the following command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --admin --verbosity=8 --filter --no-host --width
Be prepared to provide more information and outputs from other commands when asked.
General housekeeping:
As you are multibooting with Windows, please ensure that Windows Fast Startup is disabled.
With Fast Startup enabled, Windows does not actually shut down; instead it sleeps, and when the computer subsequently wakes from this hibernation state, it gives the illusion of a faster startup and shutdown experience.
This can cause havoc with GRUB 2 and related boot processes (as well as NTFS mounting functionality) in Linux.
- Fast Startup must be disabled in a multiboot scenario.
There are many documented ways to turn off fast startup in both Windows 10 and 11, however, the easiest is to use the following command from an administrative command prompt to disable all hibernation (other sleep states will not be affected):
powercfg /h off
Fast Boot is a BIOS option which (if present, and enabled) allows certain self-tests to be skipped during pre-boot (before handoff to a bootloader). Fast Boot settings may exist in varying locations, or not exist at all; as every BIOS has differing capabilities.
- It is is generally recommended to disable Fast Boot when using Linux (whether standalone or in a multiboot scenario).
Output of the following is potentially useful:
lsblk -f
Regards.
1 Like
As many people do not like to use the command line, I merely offered a GUI solution.
1 Like
I agree with the good sentiment, but I’ve seen too many people get bitten by this particular one. 
1 Like
I would agree in this instance. Grub-Customizer is not ideal. I also note that it is no longer available in Manjaro repositories;
pacman -Ss grub-customizer
However, it’s easy enough to edit the file /etc/default/grub and change the timeout value:
GRUB_TIMEOUT=
to whatever may be desired;
then close and save the file, and run:
sudo update-grub
and reboot (required).
- GRUB (Arch Wiki)
- Tips and Tricks
1 Like
I set the timeout to 30 seconds, disabled in the BIOS fast boot option. Still the same symptom. I don’t think the problem is with GRUB. Even the POST with the ASUS logo does not display. And it appears every time I reboot from Windows…
mike@ryzen ~> inxi --admin --verbosity=8 --filter --no-host --width
System:
Kernel: 6.12.4-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
root=UUID=5d538e50-a855-4622-a19a-66445f2be3d6 rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: Cinnamon v: 6.4.2 tk: GTK v: 3.24.43 wm: Muffin v: 6.4.1 tools:
avail: cinnamon-screensaver vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro
base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B550-I GAMING v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3702 date: 09/04/2024
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mobile Mouse MX Anywhere 2
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Memory:
System RAM: total: 32 GiB available: 31.25 GiB used: 2.69 GiB (8.6%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 128 GiB slots: 2 modules: 2 EC: None
max-module-size: 64 GiB note: est.
Device-1: DIMM_A1 type: DDR4 detail: synchronous unbuffered (unregistered)
size: 16 GiB speed: 3800 MT/s volts: note: check curr: 1 min: 1 max: 1
width (bits): data: 64 total: 64 manufacturer: Wilk Elektronik S.A
part-no: IRP3600D4V64L17/16G serial: <filter>
Device-2: DIMM_B1 type: DDR4 detail: synchronous unbuffered (unregistered)
size: 16 GiB speed: 3800 MT/s volts: note: check curr: 1 min: 1 max: 1
width (bits): data: 64 total: 64 manufacturer: Wilk Elektronik S.A
part-no: IRP3600D4V64L17/16G serial: <filter>
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA201210
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3717 min/max: 550/4663 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 3717 2: 3717 3: 3717
4: 3717 5: 3717 6: 3717 7: 3717 8: 3717 9: 3717 10: 3717 11: 3717 12: 3717
13: 3717 14: 3717 15: 3717 16: 3717 bogomips: 108858
Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms extapic
extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht
hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt
pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp succor
svm svm_lock syscall tce topoext tsc tsc_scale umip user_shstk v_spec_ctrl
v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq wbnoinvd wdt
x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves xtopology
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] vendor: ASUSTeK
driver: nvidia v: 550.135 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-09; EOL~2026-12-xx) arch: Ampere code: GAxxx
process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 1 speed: 2.5 GT/s
lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: none off: HDMI-A-1
empty: DP-1,DP-2,DP-3 bus-ID: 08:00.0 chip-ID: 10de:2504 class-ID: 0300
Display: x11 server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4 driver: X:
loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-size: <missing: xdpyinfo>
Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled res: 2560x1440 hz: 60
dpi: 109 size: 597x336mm (23.5x13.23") modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.135
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
memory: 11.72 GiB
Audio:
Device-1: NVIDIA GA106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 08:00.1 chip-ID: 10de:228e class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Thesycon System & Consulting GmbH SABAJ DA3 v1.2
driver: snd-usb-audio type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
bus-ID: 1-8:3 chip-ID: 152a:85df class-ID: fe01
Device-4: Dell Slim Soundbar SB521A driver: snd-usb-audio type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.4:5
chip-ID: 413c:a510 class-ID: 0102 serial: <filter>
API: ALSA v: k6.12.4-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp6s0 state: up mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: enp7s0 state: down mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 1.86 TiB used: 513.44 GiB (26.9%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:7 vendor: Lexar model: SSD NM790 1TB
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 18950 temp: 34.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Toshiba model: N/A
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 57HA4103 temp: 67.8 C
scheme: GPT
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 27.83 GiB (28.4%)
fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:9 label: N/A
uuid: 5d538e50-a855-4622-a19a-66445f2be3d6
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 292 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:8 label: N/A uuid: F539-6676
ID-3: /home raw-size: 853.37 GiB size: 838.9 GiB (98.30%)
used: 485.61 GiB (57.9%) fs: ext4 block-size: 4096 B dev: /dev/nvme0n1p3
maj-min: 259:10 label: N/A uuid: 29805870-7077-4ba5-8f9a-9aad706ce81f
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: file size: 32 GiB used: 0 KiB (0.0%) priority: -2
file: /home/swapfile
Unmounted:
ID-1: /dev/nvme1n1p1 maj-min: 259:1 size: 100 MiB fs: vfat label: N/A
uuid: 846F-30F7
ID-2: /dev/nvme1n1p2 maj-min: 259:2 size: 16 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-3: /dev/nvme1n1p3 maj-min: 259:3 size: 96.74 GiB fs: bitlocker
label: N/A uuid: N/A
ID-4: /dev/nvme1n1p4 maj-min: 259:4 size: 818 MiB fs: ntfs label: N/A
uuid: 769E193D9E18F779
ID-5: /dev/nvme1n1p5 maj-min: 259:5 size: 758.56 GiB fs: bitlocker
label: N/A uuid: N/A
ID-6: /dev/nvme1n1p6 maj-min: 259:6 size: 97.66 GiB fs: ntfs label: Share
uuid: 40EE28EBEE28DB44
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-6:2 info: ASUSTek AURA LED Controller type: HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:1939 class-ID: 0300
serial: <filter>
Device-2: 1-8:3 info: Thesycon System & Consulting GmbH SABAJ DA3 v1.2
type: audio driver: snd-usb-audio interfaces: 3 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 152a:85df
class-ID: fe01
Device-3: 1-10:4 info: Logitech Unifying Receiver type: keyboard,mouse,HID
driver: logitech-djreceiver,usbhid interfaces: 3 rev: 2.0
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
chip-ID: 046d:c52b class-ID: 0300
Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-4: 3-2:2 info: INGENICO 4-Port USB 2.0 Hub ports: 5 rev: 2.1
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0b00:5483
class-ID: 0900
Device-1: 3-2.3:4 info: QinHeng CH340 serial converter
type: <vendor specific> driver: ch341,ch341-uart interfaces: 1 rev: 1.1
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 104mA
chip-ID: 1a86:7523 class-ID: ff00
Device-2: 3-2.4:5 info: Dell Slim Soundbar SB521A type: audio
driver: snd-usb-audio interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
lanes: 1 mode: 2.0 power: 500mA chip-ID: 413c:a510 class-ID: 0102
serial: <filter>
Device-3: 3-2.5:6 info: Realtek USB2.0 HID type: HID
driver: hid-generic,usbhid interfaces: 1 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 0bda:1100 class-ID: 0300
Device-4: 3-4:3 info: HP HyperX Alloy Origins 65 type: keyboard,HID
driver: hid-generic,usbhid interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 500mA chip-ID: 03f0:038f class-ID: 0300
Hub-5: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-6: 4-2:2 info: INGENICO 4-Port USB 3.0 Hub ports: 4 rev: 3.2
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 0b00:0483
class-ID: 0900
Sensors:
System Temperatures: cpu: 36.0 C mobo: 34.0 C gpu: nvidia temp: 51 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Repos:
Packages: pm: pacman pkgs: 1526 libs: 366 tools: pamac pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://manjaro.kurdy.org/stable/$repo/$arch
2: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
3: http://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
4: https://mirrors.nic.cz/manjaro/stable/$repo/$arch
5: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
6: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
7: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
8: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
Processes:
CPU top: 5 of 355
1: cpu: 10.8% command: lightdm pid: 985 mem: 149.1 MiB (0.4%)
2: cpu: 10.6% command: vivaldi-bin pid: 1522 mem: 418.5 MiB (1.3%)
3: cpu: 5.5% command: vivaldi-bin pid: 1594 mem: 236.0 MiB (0.7%)
4: cpu: 4.0% command: vivaldi-bin pid: 1624 mem: 129.2 MiB (0.4%)
5: cpu: 3.9% command: vivaldi-bin pid: 1564 mem: 249.1 MiB (0.7%)
Memory top: 5 of 355
1: mem: 418.5 MiB (1.3%) command: vivaldi-bin pid: 1522 cpu: 10.6%
2: mem: 260.9 MiB (0.8%) command: vivaldi-bin pid: 1693 cpu: 2.0%
3: mem: 260.4 MiB (0.8%) command: cinnamon pid: 1274 cpu: 2.8%
4: mem: 254.5 MiB (0.7%) command: vivaldi-bin pid: 1905 cpu: 3.9%
5: mem: 249.1 MiB (0.7%) command: vivaldi-bin pid: 1564 cpu: 3.9%
Info:
Processes: 355 Power: uptime: 2m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.48 GiB services: csd-power,upowerd
Init: systemd v: 256 default: graphical tool: systemctl
Compilers: clang: 18.1.8 gcc: 14.2.1 alt: 13 Shell: fish v: 3.7.1
default: Bash v: 5.2.37 running-in: guake inxi: 3.3.36
mike@ryzen ~> lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme1n1
├─nvme1n1p1 vfat FAT32 846F-30F7
├─nvme1n1p2
├─nvme1n1p3 BitLocker 2
├─nvme1n1p4 ntfs 769E193D9E18F779
├─nvme1n1p5 BitLocker 2
└─nvme1n1p6 ntfs Share 40EE28EBEE28DB44
nvme0n1
├─nvme0n1p1 vfat FAT32 F539-6676 510,7M 0% /boot/efi
├─nvme0n1p2 ext4 1.0 5d538e50-a855-4622-a19a-66445f2be3d6 65G 28% /
└─nvme0n1p3 ext4 1.0 29805870-7077-4ba5-8f9a-9aad706ce81f 310,6G 58% /home
I suspect you actually mean:
sudo update-grub
However, I recommend using the install-grub package from the repository.
i found this in The kernel’s command-line parameters — The Linux Kernel documentation
acpi_rev_override [ACPI] Override the _REV object to return 5 (instead
of 2 which is mandated by ACPI 6) as the supported ACPI
specification revision (when using this switch, it may
**be necessary to carry out a cold reboot _twice_ in a**
** row** to make it take effect on the platform firmware).
reboot= [KNL]
Format (x86 or x86_64):
[w[arm] | c[old] | h[ard] | s[oft] | g[pio]] | d[efault] \
[[,]s[mp]#### \
[[,]b[ios] | a[cpi] | k[bd] | t[riple] | e[fi] | p[ci]] \
[[,]f[orce]
Where reboot_mode is one of warm (soft) or cold (hard) or gpio
(prefix with 'panic_' to set mode for panic
reboot only),
reboot_type is one of bios, acpi, kbd, triple, efi, or pci,
reboot_force is either force or not specified,
reboot_cpu is s[mp]#### with #### being the processor
to be used for rebooting.
I’m not at all familiar with bootloaders but do know that having two efi partitions is a source of issues. There seem to be two fat32 partitions, one on each drive, and fat32 partitions are usualy where the stuff to boot lives. Could there be some conflict in witch is chosen/active/used at boot time from the different OS’s that are on the disk?
Edit: I just noticed that the % on the fat32 partition on nvme0n1p1 is 0% used, this seems extremely low.
1 Like
this is because I first installed windows on one drive and then linux on the other and on the second drive bootloader. But GRUB works ok, only these reboots from linux are strange, kinda like warm reboot on android…
1 Like
I dual boot as well. What I make sure to do is have an /boot/efi partition on my Linux drive. Then tell the bios to boot from that drive instead of Windows.
What you need to be careful of, is having Grub install into your Windows boot sector. Windows 11 makes a boot sector on installation as well. Many Linux distributions will “auto” install /boot or /boot/efi over-top of your Windows boot sector.
Since you have two drives, I suggest letting Windows 11 install it’s happy little way on the first drive, then make sure that Manjaro installs only on the second drive. Make a separate /boot/efi partition (512mb ~ 1gb) as the first partition on this drive, and make sure to format it Fat32. Then partition the rest of your drive the way you like for your Linux installation.
Indeed. grub-customizer is not in the Manjaro repos for a reason.
By the way, I tried it out recently on my Arch install and it royally screwed up my boot entries. Not recommended.
Generally a good strategy when multibooting.
Complications arise with two $ESPs if they both on the same disk. However, in this scenario, one $ESP on each disk is indeed practical.
If the default $ESP (first in boot order) is set to the Manjaro $ESP (with the Manjaro UEFI boot files), then the Windows UEFI boot files are detected on the other $ESP and effectively chainloaded.
You noted that Fast Boot is disabled in BIOS.
Can you confirm that Fast Startup is disabled in Windows?
yes, its disabled.
i don’t know what windows settings have to do with linux? in windows everything is ok. the problem occurs when i power on computer, start linux and then try to reboot - the POST screen does not appear followed by the GRUB menu and immediately Linux starts up. however, if i reboot right away then it shows up.
you can live with it but I like to know why something is happening 
When the windoze ‘feature’ “Fast Startup” is enabled then what really happens is a true shutdown does not take place - instead the system hibernates - creating the illusion of a quicker startup time because it was never shut down.
This can cause various problems from holding the wireless card hostage to wonky boots etc.
2 Likes
Maybe I’m describing it wrong - that’s how it looks on video.
All the more reason to establish that it was disabled.
Fast Startup (Windows)
A hibernation variant known as Fast Startup may be enabled on Windows computers.
With Fast Startup enabled, Windows does not actually shut down; instead, it sleeps. When the computer subsequently wakes from the hibernation state, this gives the illusion of a faster startup and shutdown experience.
When multibooting, this can cause havoc with GRUB 2 and related boot processes, as well as NTFS mounting functionality, in Linux.
Fast Startup must be disabled in a multiboot scenario.
There are many documented ways to turn off fast startup in both Windows 10 and 11, however, the easiest is to use this command from an administrative command prompt to disable all hibernation (other sleep states will not be affected):
powercfg /h off
Note that we are going through a process of elimination here. If, as you say, Windows’ Fast Startup is disabled, then this isn’t the issue; something else is afoot.
Regards.
I just noticed I’d already given you the above information. Can we presume you didn’t bother to read it the first time?