How should grub users handle updates?

[ghost]

Since August when using Archfi's defaults for uefi and using grub, it leads to an unbootable system after an update. The posts elsewhere online suggest that simply running grub-install after an update before reboot would workaround it but this doesn't work when using archfi. It reports back "efi directory not found" or something like that. I had to chroot in the first time. I discovered I need to run the specific command sudo grub-install --efi-directory=/boot --target=x86_64-efi after an update and before a reboot, or the system does not boot. This is the command used to originally install grub from the archfi/archdi menu, minus /dev/sda. It used to update fine on its own now it requires intervention every update.
I also noticed most user install their efi partition to /boot/efi, but we use /boot.
Please if possible suggest a proper way to handle grub and the bad grub updates. Others say it was a one time fix but I need to do this every grub update, or it boots to my UEFI menu. Others report that this happens with every kernel update, but for me it is only when grub updates.
Or- is it possible to use archfi to mount my existing install, then switch from grub to something else? Please help this is my only hangup using Arch in over 3 years. Thanks for your work

[MatMoul]

Hi,

In August, it has a news for grub :
https://archlinux.org/news/grub-bootloader-upgrade-and-configuration-incompatibilities/

archdi help you with commands but you need to handle news and .pacnew files