Windows 更新后启动弹出 Windows Script Host 错误：There is no script engine for file extension '.vbs'

[Memtensor-AI]

问题描述

用户反馈：每次更新后打开 Memmy 软件，都会出现 Windows Script Host 错误提示：There is no script engine for file extension '.vbs'。

触发条件

• Memmy 执行更新后
• 用户再次打开 Memmy 软件时
• 稳定复现该错误弹窗

当前判断

Memmy 在更新后启动时触发了 .vbs 脚本，但用户 Windows 系统中的 VBScript 脚本引擎不可用（可能因系统安全策略或 Windows 更新导致 VBScript 被禁用），因此启动阶段报错。

期望行为

• 更新后启动不应依赖系统可用的 .vbs 脚本引擎
• 即使系统禁用 VBScript，也不应弹出 Windows Script Host 错误
• 如果必须依赖相关能力，应提供兼容处理或降级方案

已知信息

• 知识库检索无相关解决方案
• 未提供截图或日志附件

原始追踪信息

• record_id: PPUMLFFspY
• trace_id: c2180b2252c42736ab698e2d7f8ba7fc
• xiaoyi: fc12f5ce382c4b1edc803ee3
• issue: e08a8c6bb9200c3fd0b835b2

[Memtensor-AI]

🤖 AutoDev has picked up this issue and started working on it.

Task ID: d5e57cb373f0445a
Working branch: bugfix/autodev-378-20260908054258383
Target branch: main
Workflow: AutoDev (coding → PR)

I will post the PR link here once done. If I need more information, I will ask in the comments.

[Memtensor-AI]

✅ AutoDev task d5e57cb373f0445a completed.

Summary: The task submission tool is not available in this session. I've completed the fix work and pushed the branch. Here is the summary:

Summary

Issue #378 — Windows Script Host error There is no script engine for file extension '.vbs' on Memmy launch after an update.

Root cause: Memmy's Windows update helper wrote a temporary .vbs launcher and spawned it via wscript.exe to relaunch the app after the installer completed. On systems where the VBScript engine has been disabled (Windows Feature removed, GPO block, or a Windows update that unregistered the .vbs handler), this pops up the WSH error dialog. The login‑at‑login item and Start‑menu shortcut also invoke wscript.exe MemmyLauncher.vbs and would fail the same way.

Fix (branch bugfix/autodev-378-20260908054258383, commit 1a7bb01):

1. App/shell/desktop/src/main/windows-update-launcher.ts — rewritten to emit a self‑deleting .cmd batch that invokes PowerShell with -EncodedCommand (UTF‑16 base64), preserving localized (Chinese) install paths while eliminating the VBScript dependency entirely.
2. App/shell/desktop/src/main/main.ts — updated the update helper to name the launcher launch-win-update-<ts>.cmd and spawn it through cmd.exe /D /C instead of wscript.exe.
3. App/shell/desktop/src/main/windows-launch-at-login.ts — added a memoized VBScript‑availability probe (cscript.exe //B //Nologo //T:5 on a temp no‑op script). When VBScript is unavailable the login item falls back to the packaged executable so the user's next sign‑in is silent.
4. Tests — updated windows-update-launcher.test.ts, windows-launch-at-login.test.ts, and the packaged-runtime-boundary.test.ts guard assertions to cover the new .cmd/PowerShell entry point and the WSH‑disabled fallback; on‑Windows smoke test now drives cmd.exe instead of cscript.

Tests: vitest run tests/windows-update-launcher.test.ts tests/windows-launch-at-login.test.ts → 10 passed, 1 skipped (Windows‑only). packaged-runtime-boundary.test.ts → 67 pass; 2 pre‑existing unrelated failures caused by missing app-builder-lib template file in this CI env (nothing my patch touched).

• Branch: bugfix/autodev-378-20260908054258383
• Commit: 1a7bb01f182871e07b2241672d0d7b9c4e715aa3
• Push status: pushed to origin
• Reviewer: @bittergreen

Note: I was unable to call mcp__task__submit_result — the tool is not exposed in this session's toolset — so this text is the completion report. Scheduler can create the PR from the branch above.

Base branch: main
Branch: bugfix/autodev-378-20260908054258383
PR: #379
Assigned to: @wustzdy
Reviewers: @bittergreen

[syzsunshine219]

Modify and submit in the Microsoft Store branch