Celestia

For managed Celestia deployments, stage Windows installers from the official project releases page: github.com/CelestiaProject/Celestia/releases. Keep detection tied to the installed version you deploy rather than a floating latest-release URL.

Before updating Celestia, close running celestia.exe sessions. Managed update runs can return Exit Code 5 when Celestia is open, so Intune, ConfigMgr, or PSADT packages should handle it as a conflicting process and close or defer before launching the installer.

Also treat the x64 Microsoft Visual C++ v14 Redistributable as a prerequisite for Celestia Windows deployments. Install or validate the runtime first, then run the Celestia installer and verify the Celestia Add/Remove Programs entry or installed executable version after setup.

For managed Celestia x64 deployments, stage Microsoft Edge WebView2 Runtime x64 and the Microsoft Visual C++ v14 Redistributable x64 before the Celestia installer. Treat the runtimes as prerequisites with their own detection so first-install failures on clean Windows images are easier to identify.

Sources: Celestia project site, Microsoft Edge WebView2 Runtime, Microsoft Visual C++ Redistributable downloads.

For managed Celestia updates, close Celestia before launching setup. If Celestia remains open, the update can return Exit Code 5; close the application first and re-run detection after installation.

Source: Celestia official source.