# System stuck on "Network Manager Script Dispatcher Service" after updating & rebooting **URL:** \ **Category:** Kernel, boot, graphics & hardware\ **Created:** [July 26, 2024, 6:27pm UTC](https://forum.endeavouros.com/t/system-stuck-on-network-manager-script-dispatcher-service-after-updating-rebooting/58519 "2024-07-26T18:27:34Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![BluishHumility](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/bluishhumility/32/70412_2.png) [@BluishHumility](https://forum.endeavouros.com/u/BluishHumility)\ **Post date:** [July 27, 2024, 3:23pm UTC](https://forum.endeavouros.com/t/system-stuck-on-network-manager-script-dispatcher-service-after-updating-rebooting/58519/2 "2024-07-27T15:23:15Z")
This post describes some of the “usual” things to try: > [@\[FAQ\] Computer doesn’t boot, boots to a black screen, or stops at a message](https://forum.endeavouros.com/t/faq-computer-doesn-t-boot-boots-to-a-black-screen-or-stops-at-a-message/6887): > > While there are many potential reasons why your installation doesn’t boot to a desktop, the primary reason is that the graphics drivers haven’t loaded correctly so your login/display manager (DM) doesn’t start. This is why you get a “black screen” or stuck at an [OK] Started some service message. The normal reason for this is that you have the incorrect driver version for the kernel. This can happens when the mirror you are updating from is not fully synchronised, or times out, and so y… If you can’t log in to a TTY you may have to work through the suggestions from a [chroot](https://endeavouros.com/docs/system-rescue/rescue-non-booting-system-with-arch-chroot/) instead. --- _[View the full topic](https://forum.endeavouros.com/t/system-stuck-on-network-manager-script-dispatcher-service-after-updating-rebooting/58519)._