Skip to content

feat!: 支持修改应用包服务的启动类型 - #112

Open
digital-bombyx wants to merge 4 commits into
Ray-lea:mainfrom
digital-bombyx:feat/packaged-service-start-type
Open

digital-bombyx wants to merge 4 commits into
Ray-lea:mainfrom
digital-bombyx:feat/packaged-service-start-type

Conversation

@digital-bombyx

Copy link
Copy Markdown
Contributor

改动内容 / Changes

MSIX 应用包安装的服务(SERVICE_PKG_SERVICE,例如 Claude 的 CoworkVMService)无法修改启动类型,管理员也不行。应用包为服务设置的安全描述符只允许 NT SERVICE\AppXSvc 修改配置:

D:(A;;CCLCSWRPWPDTLOCRRC;;;AU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;NT SERVICE\AppXSvc)

DACL 中没有 Administrators 和 SYSTEM,因此 Argus(无论以管理员身份运行还是通过特权服务)和 services.msc 都会被拒绝。但服务的注册表项仍是常规 ACL。

  • SCM 拒绝修改且目标是包服务时,界面先弹出确认框,再将 Start(自动启动时含 DelayedAutostart)写入该服务的注册表项。
  • 新增特权服务操作 ServiceStartTypeRegistry:先通过 SCM 确认目标是包服务,否则拒绝;服务名校验与其他服务操作相同。
  • 注册表值与 SCM 当前值不同时,“启动类型”列显示待生效状态(如“手动(重启后)”),菜单勾选所选的值。实测 SCM 会立即采用新值,但文档未作保证,待生效状态用于未立即生效的情况。
  • 修复:启停服务和修改启动类型失败时,此前沿用结束进程的文案(“无法结束 MBAMService…”)。现改用服务专属文案并显示服务的显示名称;已有管理员权限(或特权服务可用)时,不再建议以管理员身份运行,而是说明服务可能受其自身软件保护(例如 Malwarebytes 的自我保护)。

BREAKING CHANGE:特权服务 IPC 协议从 11 升至 12。


Packaged (MSIX) services deny SERVICE_CHANGE_CONFIG to everyone except NT SERVICE\AppXSvc, so their startup type couldn't be changed even as administrator. After the SCM refuses, Argus now asks and writes Start to the service's registry key; a registry value the SCM hasn't picked up shows as pending. Also fixes the error text for failed service actions (it said "Couldn't end…").

检查清单 / Checklist

  • 拉取请求标题与各个提交信息符合 Conventional Commits(<type>(<scope>): <描述>)/ The title and commit messages follow Conventional Commits
  • start.bat check 通过 / start.bat check passes
    • rustfmt、clippy -D warnings、i18n、Rust 测试通过(argus-service 中 3 个安装锁测试在干净的 main 上同样失败)。check:generated 在干净的 main 上也不通过:生成器会删掉 dispatch.rs 仍在使用的 TrayIcon、TrayMenu 导入,本 PR 新增的条目与生成结果一致。
  • 行为变化已同步到 docs/ 中对应的页面 / Behavior changes are reflected in docs/
  • 文案已写入 locales/ 的中文与英文目录 / New text is in both the Chinese and English catalogs under locales/(8 种语言均已添加)
  • 界面改动附有截图,并按性能基线测量了开销 / UI changes include screenshots and a measurement against the performance baseline
    • 采样路径无变化;服务配置缓存(60 秒)刷新时每个服务多读两个注册表 DWORD。

截图:确认框、待生效的启动类型、Malwarebytes 的新错误提示。

手动测试:CoworkVMService 经确认框在“自动”与“手动”间切换,用 sc qc 和注册表核对;普通服务仍直接通过 SCM 修改,不弹确认框;MBAMService 显示新的服务错误文案。

截图 / Screenshots

修改前 / Before 修改后 / After
before1 after1
before2 after2

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T18:00:13.199124Z da65f8d New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 60305212a5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src-gpui/src/frontend/dialogs.rs Resolved
Comment thread src-gpui/src/frontend/tables.rs Resolved
Comment thread src-gpui/src/frontend/tables.rs Resolved
MSIX 包安装的服务(如 Claude 的 CoworkVMService)的安全描述符只允许 NT SERVICE\AppXSvc 修改配置,管理员与 SYSTEM 修改启动类型均被 SCM 拒绝。SCM 拒绝且目标为包服务时,界面先确认,再将 Start(自动启动时含 DelayedAutostart)写入该服务的注册表项。注册表值与 SCM 当前值不同时,服务列表显示待生效的启动类型。

BREAKING CHANGE: 特权服务 IPC 协议从 11 升至 12,已有服务需要更新。
启停服务与修改启动类型失败时,此前沿用结束进程的错误文案(“无法结束…”)。现改用服务专属文案并显示服务的显示名称,访问被拒时提示安全软件可能保护自身服务。
以管理员身份运行或特权服务可用时,服务操作仍被拒绝,多半是服务自身的保护(如杀毒软件的自我保护)。此时提示改为说明这一点,不再建议启用特权服务或以管理员身份运行。
仅当 Argus 以管理员身份运行或特权服务可用时,SCM 拒绝修改应用包服务才询问是否写入注册表;写入同样需要管理员权限,其他情况直接显示原有的权限提示,不再在确认后出现第二次错误。

“启动类型”列的固定宽度一并计入“(重启后生效)”的待生效文案,较长的语言不再被截断;按启动类型排序时,有待生效值的服务按显示的类型排列。
@digital-bombyx
digital-bombyx force-pushed the feat/packaged-service-start-type branch from 5c86c93 to da65f8d Compare November 14, 2026 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant