# Got a output after updating GRUB

**URL:** <https://forum.endeavouros.com/t/got-a-output-after-updating-grub/32569>\
**Category:** Pacman & AUR helpers\
**Created:** [October 7, 2022, 6:45pm UTC](https://forum.endeavouros.com/t/got-a-output-after-updating-grub/32569 "2022-10-07T18:45:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\
**Post date:** [October 7, 2022, 6:49pm UTC](https://forum.endeavouros.com/t/got-a-output-after-updating-grub/32569/3 "2022-10-07T18:49:44Z")

</div>

The short answer is that the recommended action would be to run an appropriate `grub-install` for your install followed by `grub-mkconfig -o /boot/grub/grub.cfg`

The long answer is in all the responses to this topic:

> [@Grub Updated Seamlessly](https://forum.endeavouros.com/t/grub-updated-seamlessly/32514/8):
>
> You should probably use grub-install --no-nvram You shouldn’t do this via a script because you can’t guarantee that grub will be updated via your script. That is why hooks are better. Although it has only happened once, one of the things that came to light during this situation is that the grub devs expect grub-install to be run every time grub is updated. So issues could occur at any time in the future as well. Also, if you don’t run grub-install after a grub update, you would won’t be …

---

_[View the full topic](https://forum.endeavouros.com/t/got-a-output-after-updating-grub/32569)._
