# Module Install/Updates/Removal and Gateway Reboots

**URL:** <https://forum.inductiveautomation.com/t/module-install-updates-removal-and-gateway-reboots/109220>\
**Category:** Ignition 8.3 Early Access\
**Created:** [July 31, 2025, 8:07pm UTC](https://forum.inductiveautomation.com/t/module-install-updates-removal-and-gateway-reboots/109220 "2025-07-31T20:07:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![carlos.girondasilva](https://avatars.discourse-cdn.com/v4/letter/c/4bbf92/32.png) [@carlos.girondasilva](https://forum.inductiveautomation.com/u/carlos.girondasilva)\
**Post date:** [July 31, 2025, 8:07pm UTC](https://forum.inductiveautomation.com/t/module-install-updates-removal-and-gateway-reboots/109220/1 "2025-07-31T20:07:09Z")

</div>

One of the new things i'm noticing on Ignition 8.3 is that for every module install, uninstall, it's forcing a reboot of the entire gateway. I saw this behavior while importing the kafka module, and when trying to import an 8.1 module into the gateway (it was an expected fail lol). I can think of a few reasons why it's okay for it, but for deployment of 3rd party modules, it may be disruptive in a running system, even if the 3rd party module doesn't affect core functionalities (alarm,history, opc-ua, etc).

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [July 31, 2025, 8:08pm UTC](https://forum.inductiveautomation.com/t/module-install-updates-removal-and-gateway-reboots/109220/2 "2025-07-31T20:08:54Z")

</div>

It's not 1 for 1 - you can install all the modules you want, and _then_ restart.

But yes, module changes are staged and take effect on the next restart.