Bug: Omi Windows desktop "Restart to install latest update" removes the app but does not reinstall it

[hugoaap-code]

Summary

On Omi Windows desktop, the update flow from Settings > About > Restart to install latest update does not complete correctly.

After clicking the button, Omi gets uninstalled and does not get installed back.

Environment

• Omi Desktop
• Windows
• Settings path: Settings > About
• Observed on Wednesday, July 29, 2026

Problem

The built-in updater appears to start, but instead of restarting and applying the latest update, it removes the current installation and fails to reinstall the app.

Expected behavior

• Clicking Restart to install latest update should close Omi
• The updater should install the new version
• Omi should reopen normally on the updated version

Actual behavior

• Click Restart to install latest update
• Omi closes
• The app is uninstalled
• The new version is not installed
• Omi is left missing instead of updated

Impact

This turns a normal update action into a broken install state.

A user trying to update through the app can end up without Omi installed at all.

Reproduction

1. Open Omi Desktop on Windows
2. Go to Settings > About
3. Click Restart to install latest update
4. Observe that Omi does not complete the reinstall/update flow
5. Observe that the app is removed and not installed back

Suggested investigation

• Check the Windows auto-update and installer handoff flow after the restart action
• Check whether the uninstall phase completes but the reinstall phase never starts
• Check logs around installer launch, update package validation, and post-restart execution
• Verify whether this affects a specific update channel or version transition
• Add a safer rollback or recovery path so a failed update does not leave the user without the app

Notes

This is not just a failed update notification. The current behavior can leave the machine with Omi uninstalled after pressing the in-app update button.

[hugoaap-code]

Correction / update to this report:

The behavior is slightly different than my original description.

After clicking Settings > About > Restart to install latest update, it does look like Omi installs a new version. However, when I try to open Omi after the update, I get a Windows error dialog:

A JavaScript error occurred in the main process
Error: Cannot find module 'ms'

So the issue is not simply that Omi gets uninstalled and never installed back. The updated state appears to be that the app installation/update completes, but the newly installed app then fails to launch because of a missing module/runtime packaging error.

This means the updater flow can leave the user with a broken installed version instead of a working updated app.

Additional note:

• The error stack trace shown in the dialog points into the packaged Windows app resources under the local install path
• The visible local username/path in the screenshot should be treated as redacted if copied into internal debugging notes

This may be related to the same startup failure pattern reported elsewhere with:
Cannot find module 'ms'

[hugoaap-code]

Marking this as superseded by the existing startup-crash issue: #10738

The more accurate behavior is:

• Settings > About > Restart to install latest update appears to install/update Omi
• But when opening the updated app, it fails with a main-process JavaScript error:
  • Error: Cannot find module 'ms'

So this report should be treated as a duplicate/superseded updater-path report pointing to #10738 rather than as a separate uninstall-only bug.

[hugoaap-code]

this is the error I see after clicking that update button