Found on the Windows VM while testing #258 (4 October 2026). With Smart App Control enforcing (HKLM\SYSTEM\CurrentControlSet\Control\CI\Policy VerifiedAndReputablePolicyState = 1), moho.exe doesn't start at all: no window, no error, nothing in moho's log. Code Integrity logs event 3033/3077, did not meet the Enterprise signing level requirements, followed by a 3118 Smart App Control block.
Earlier builds ran on the same VM the same day, so Smart App Control most likely moved itself from evaluation to enforcing, which it does on its own. Any Windows 11 user with it on can't run moho, and an unsigned installer already shows SmartScreen's "Windows protected your PC" on download.
The fix is code signing: an Authenticode certificate (OV or EV, or a cloud signing service) applied by electron-builder to moho.exe, nobilis.exe and the installer, in the rolling-release workflow. The uninstaller, interestingly, wasn't blocked.
Don't switch Smart App Control off on the VM to work around this: it can't be switched back on without reinstalling Windows, and the VM is now a faithful reproduction.
Found on the Windows VM while testing #258 (4 October 2026). With Smart App Control enforcing (`HKLM\SYSTEM\CurrentControlSet\Control\CI\Policy` VerifiedAndReputablePolicyState = 1), `moho.exe` doesn't start at all: no window, no error, nothing in moho's log. Code Integrity logs event 3033/3077, *did not meet the Enterprise signing level requirements*, followed by a 3118 Smart App Control block.
Earlier builds ran on the same VM the same day, so Smart App Control most likely moved itself from evaluation to enforcing, which it does on its own. Any Windows 11 user with it on can't run moho, and an unsigned installer already shows SmartScreen's "Windows protected your PC" on download.
The fix is code signing: an Authenticode certificate (OV or EV, or a cloud signing service) applied by electron-builder to `moho.exe`, `nobilis.exe` and the installer, in the rolling-release workflow. The uninstaller, interestingly, wasn't blocked.
Don't switch Smart App Control off on the VM to work around this: it can't be switched back on without reinstalling Windows, and the VM is now a faithful reproduction.
Salastil
added this to the v1.0 milestone 2026-10-03 23:04:31 -04:00
Finished, by decision: moho won't be code-signed. People with Smart App Control on will be told to turn it off.
When Smart App Control is on, the installer now warns before the first page. It says moho won't start, gives the path to turn it off (Windows Security > App & browser control > Smart App Control settings), and notes that Windows won't let it be switched back on without a reset. OK installs anyway; Cancel quits with nothing installed.
The README and the rolling release's notes say the same, and include the SmartScreen More info > Run anyway / Unblock step.
Checked on the Windows VM, which has Smart App Control enforcing.
Finished, by decision: moho won't be code-signed. People with Smart App Control on will be told to turn it off.
- When Smart App Control is on, the installer now warns before the first page. It says moho won't start, gives the path to turn it off (*Windows Security > App & browser control > Smart App Control settings*), and notes that Windows won't let it be switched back on without a reset. OK installs anyway; Cancel quits with nothing installed.
- The README and the rolling release's notes say the same, and include the SmartScreen *More info > Run anyway* / Unblock step.
Checked on the Windows VM, which has Smart App Control enforcing.
https://git.salastil.com/Salastil/moho/commit/5a8d7f7
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found on the Windows VM while testing #258 (4 October 2026). With Smart App Control enforcing (
HKLM\SYSTEM\CurrentControlSet\Control\CI\PolicyVerifiedAndReputablePolicyState = 1),moho.exedoesn't start at all: no window, no error, nothing in moho's log. Code Integrity logs event 3033/3077, did not meet the Enterprise signing level requirements, followed by a 3118 Smart App Control block.Earlier builds ran on the same VM the same day, so Smart App Control most likely moved itself from evaluation to enforcing, which it does on its own. Any Windows 11 user with it on can't run moho, and an unsigned installer already shows SmartScreen's "Windows protected your PC" on download.
The fix is code signing: an Authenticode certificate (OV or EV, or a cloud signing service) applied by electron-builder to
moho.exe,nobilis.exeand the installer, in the rolling-release workflow. The uninstaller, interestingly, wasn't blocked.Don't switch Smart App Control off on the VM to work around this: it can't be switched back on without reinstalling Windows, and the VM is now a faithful reproduction.
Finished, by decision: moho won't be code-signed. People with Smart App Control on will be told to turn it off.
Checked on the Windows VM, which has Smart App Control enforcing.
https://git.salastil.com/Salastil/moho/commit/5a8d7f7