Cannot reboot from Windows 11 to Manjaro

I recently upgraded my PC and freshly installed Windows 11 and Manjaro. I confirmed that both work if they are booted, but there is a problem: I cannot reboot from Windows 11 to Manjaro.

Method to Reproduce

  1. Turn on the PC then select Windows 11 in GRUB.
  2. Windows 11 boots perfectly. Then shut down the PC.
  3. Turn on the PC again then select Manjaro in GRUB.
  4. The booting process hangs at “Started Network Manager Script Dispatcher Service” (may be inexact)
  5. The PC is shut down and reboots again.

The only way to boot Manjaro is to manually shut down the PC (by pressing the power button or disconnecting a power cable) during hanging. After that, Manjaro boots well without a problem.

I guess Windows does not unlock hardware resources so Manjaro is not able to use them after rebooting but I disabled fast boot and hibernation in Windows. What should I do further?

System Informations

Operating System: Manjaro Linux
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
Kernel Version: 6.5.7-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: A520I AC
System Version: -CF

… abondon the NxA client?

The problem is clearly not on Manjaro side, so what you expect to get help here? Better ask the provider of the malificous OS.

Most probably fast boot is not disabled (or got reenabled behind your back on update) in windows, so the machine is in semi hibernation and not completely shut down and the network card not properly powered off and cannot be turned on then by manjaro.

Look for the fast boot in the power profile settings, or use restart and not shutdown in windows.

1 Like

Fast boot is disabled in the power settings certainly, and restarting does not work too.

Disable Fast Startup in Windows:

powercfg /h off

Reboot, and if it appears to hang, open a TTY shell:
ctrl+alt+f2 (or f3/f4/f5/f6), enter your credentials and login to Manjaro

Get the NetworkManager status:

sudo systemctl status networkmanager

If the NetworkManager service is inactive, or failed:

sudo systemctl start networkmanager

Check the status again to verify the service is active:

sudo systemctl status networkmanager

If the service is active, enable NetworkManager:

sudo systemctl enable networkmanager

If not, check that all dependencies are installed:

sudo pacman -Qi networkmanager

Perform a system update, if needed:

sudo pacman -Syu

If everything seems OK, reboot.

If not, run the following to reinstall NetworkManager

sudo pacman -S networkmanager

Start NetworkManager again, and check status:

sudo systemctl start networkmanager
sudo systemctl status networkmanager

If NetworkManager is running, enable the service

sudo systemctl enable networkmanager


If it still doesn’t work after all above, disable NetworkManager:

sudo systemctl disable networkmanager


1 Like

Sorry for late reply; disabling NetworkManager works perfectly! But enabling it again make the boot process hang again. I’m so sad that the network is unavailable at this point.

Let’s try enabling Network Manager service at login, instead.

Firstly, disable NetworkManager, as before:

sudo systemctl disable networkmanager

Reboot, and login normally.

From this point forward do NOT use SUDO to prefix the commands.

Open Terminal:

Create a systemd user service file:

systemctl --user edit --force --full networkmanager.service

In whatever text editor opens, add the following:

Description=Network Manager


Complete the ExecStart= line with either of these options (but not both):

  • /usr/bin/nm-applet – Starts the NetworkManager GUI.
  • /usr/bin/networkmanager – Starts NetworkManager (without GUI).

→ Probably, you’ll want the first option.

Save and Exit the text editor.

Start the systemd user service:

systemctl --user start networkmanager.service

Enable the systemd user service at login:

systemctl --user enable networkmanager.service

At next login NetworkManager should start automatically; albeit with some possible delay.

If not, :person_shrugging:. Cheers.

This command didnt need it either.
In general systemctl does not require sudo and will prompt you when needed.

You missed an obvious mistake; which I found pursuant to your comment. Thanks.

I was wondering why your suggestion stated enable and the other poster said disabling works perfectly :person_shrugging:

1 Like

Using copy/paste even within the same post should always be triple-checked. (note to self).

While that’s true for user-level actions, when using such commands to effect boot services (therefore system-level), the use of sudo is usually appropriate.