So, as the title said, I am having troubles in installing Manjaro (or any distro for that matter) in my Zenbook, I deactivated Secure Boot in the BIOS settings, but I still have errors. I am unaware if I have to also deactivate TPM.
P.S: Apparently I can’t add links, so I can’t share the log
Boot into a live ISO and post output of
inxi -Fza
so that we better understand your hardware. Any other OS installed already on the Zenbook?
Sure, I am trying to dual boot with Windows if possible. Here are the output of the command
System:
Kernel: 6.12.4-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64
lang=en_US keytable=us tz=UTC misobasedir=manjaro
misolabel=MANJARO_KDE_2421 quiet systemd.show_status=1 splash
driver=nonfree nouveau.modeset=0 i915.modeset=1 radeon.modeset=1
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.8.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: Zenbook UX5401ZA_UX5401ZA v: 1.0
serial: <superuser required>
Mobo: ASUSTeK model: UX5401ZA v: 1.0 serial: <superuser required>
uuid: <superuser required> UEFI: American Megatrends LLC. v: UX5401ZA.311
date: 10/25/2023
Battery:
ID-1: BAT0 charge: 52.5 Wh (100.0%) condition: 52.5/63.0 Wh (83.3%)
volts: 12.9 min: 12.0 model: ASUSTeK ASUS Battery type: Li-ion serial: N/A
status: full cycles: 64
CPU:
Info: model: 12th Gen Intel Core i7-12700H bits: 64 type: MST AMCP
arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0x9A (154) stepping: 3
microcode: 0x42C
Topology: cpus: 1x dies: 1 clusters: 8 cores: 14 threads: 20 mt: 6 tpc: 2
st: 8 smt: enabled cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32
KiB, 8x64 KiB L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB
desc: 1x24 MiB
Speed (MHz): avg: 400 min/max: 400/4600:4700:3500 scaling:
driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
15: 400 16: 400 17: 400 18: 400 19: 400 20: 400 bogomips: 107560
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
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: Vulnerable: No microcode
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
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: Enhanced / Automatic IBRS; IBPB:
conditional; RSB filling; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: ASUSTeK
driver: i915 v: kernel alternate: xe arch: Gen-12.2 process: Intel 10nm
built: 2021-22+ ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1
bus-ID: 0000:00:02.0 chip-ID: 8086:46a6 class-ID: 0300
Device-2: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-9:3 chip-ID: 13d3:5460
class-ID: fe01 serial: <filter>
Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 2880x1800 s-dpi: 96 s-size: 762x476mm (30.00x18.74")
s-diag: 898mm (35.37")
Monitor-1: eDP-1 model: Samsung 0x4154 built: 2020 res: 2880x1800 hz: 90
dpi: 242 gamma: 1.2 size: 302x189mm (11.89x7.44") diag: 356mm (14")
ratio: 16:10 modes: 2880x1800
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.8-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
device-ID: 8086:46a6 memory: 7.47 GiB unified: yes
API: Vulkan v: 1.4.303 layers: N/A device: 0 type: integrated-gpu
name: Intel Graphics (ADL GT2) driver: N/A device-ID: 8086:46a6
surfaces: xcb,xlib
Audio:
Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: ASUSTeK
driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel, snd_soc_avs,
snd_sof_pci_intel_tgl bus-ID: 0000:00:1f.3 chip-ID: 8086:51c8
class-ID: 0401
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 Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 0000:00:14.3 chip-ID: 8086:51f0 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 8087:0033
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
RAID:
Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
Drives:
Local Storage: total: 505.76 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVL2512HCJQ-00B00 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: GXA7401Q temp: 32.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: DataTraveler 3.0
size: 28.82 GiB block-size: physical: 512 B logical: 512 B type: USB
rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter>
scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
Src: /sys System Temperatures: cpu: 34.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 15.3 GiB used: 2.05 GiB (13.4%)
Processes: 372 Power: uptime: 1h 30m states: freeze,mem,disk
suspend: s2idle avail: deep wakeups: 0 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 6.08 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1248 libs: 327 tools: pamac pm: flatpak pkgs: 0
Compilers: N/A Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.36
Idk, the laptop has only one NVMe SSD. Can this come pre-activated?
The installation always fails in the grub installation part
You have the computer, You can give this answer yourself. 
You need to use AHCI for linux.
But i do not know what will happen to your existing windows if you switch this.
Have you disabled Fast startup in Windoze and really fully shut it down? Otherwise Windoze is only in hibernate mode with could block access to the ESP. What Win version are you using? Is TPM required? As asked by @andreas85 already, why RAID is enabled, could it be switched off in your firmware? Only you know the requirements of your Win install…
When I enter the BIOS and goes to the said drive it says “Non-RAID” in “Status” so I would suppose it isn’t enabled
Wow, I forgot to disable that part. I think that might have been the problem, I will try again and give the feedback.
check that all disks are AHCI , not Raid
Also, make sure to boot the live ISO in the same mode as your Win install (most likely UEFI install). So, when you boot the USB key, use the UEFI entry, otherwise you boot in BIOS mode (if your firmware allows this).
Also, make sure to prepare the / partition upfront (also /home if you want to use a separate partition) and only assign all these (and the ESP) partitions in Calamares.
So, the problem appeared to be the Fast Startup. As soon as I disabled it, the installation finished successful, thank you for your support!
As @Wollie has mentioned Fast Startup, it’s worth noting for passers-by that there is often confusion between Fast Startup and Fast Boot, which are two completely separate technologies:
Fast Startup
Fast Startup is a hibernation variant that 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 play 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
Fast Boot
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.
A quick Internet search for information about Fast Boot (the BIOS option) revealed the following articles:
It is is generally recommended (but not compulsory) to disable Fast Boot when using Linux either standalone or in a multiboot scenario.
Mod edit:- Context updated.
sounds like a bug to me, and if a computer shuts down while sleeping, it should lose all state and deal with it.
The most intriguing aspect here is WTF is windows doing that prevents a normal boot? This should be guarded against.
Windows does not allow this if Fast Startup is enabled.
It is not a bug, it’s a feature (of Windows).
Pssst… it’s called Fast Startup.
(my post above already addresses this).
windows should not be able to in any way prevent the startup of Linux. It might do so currently, but this is a bug/malware functionality that should be worked around in Linux.
There is very little other software can do to a system still currently locked down by software thats already running and has not relinquished the hardware.
You might as well ask ‘why cant linux just run without me needing to reboot from windoze?’.
Given that windoze does not shut down with this feature enabled … its essentially the same situation.
Yeah, my mistake. It was a typo, already fixed it, thanks!
I should mention that the popularity of multibooting has only gained traction in recent years, albeit possible for much longer. There are very few operating systems that actually take multibooting into account, so few, that I cannot even name one as I write.
Of course, there are bootloaders that support multibooting; Grub 2, rEFInd and OpenCore come to mind; and some UEFI bootloaders are more like a mini-OS in their own right.
Windows, Linux (using Grub 2) and several other major OS are multiboot capable, but the more commercial of these platforms generally have little interest in playing nicely.
An OS such as Windows or Linux, or any other for that matter, is expected to be installed to a disk as the sole operating system for any given computer.
Technically:
because Windows and Linux should not be installed on the same machine concurrently.
The fact that they can be (what we call multiboot) does not negate that these operating systems are not designed to do so.
Waving your hands in the air and shouting (I’m speaking figuratively here) words like ‘bug’ and ‘malware’ doesn’t change that.
Of course, anyone is welcome to approach M$ and encourage them to support multibooting generally, and perhaps change their Secure Boot* licensing to be more favourable for Linux; and completely scrap their Fast Startup technology; and more;
but, I wouldn’t hold much hope for success. 