动手修改之前,
先看这一页。Before you change anything,
read this page.
系统优化改的是底层设置,有用,也有代价。花五分钟读完,能避开绝大多数问题。System tuning touches low-level settings — useful, but not free of risk. Five minutes here prevents most problems.
使用前,四步原则Before you start: four principles
01. 创建系统还原点01. Create a restore point
软件内置「系统还原点」工具,先建一个。这是修改失败时最直接的退路。Use the built-in “System Restore Point” tool first. It's the most direct way back if something goes wrong.
02. 备份重要个人文件02. Back up personal files
还原点保护的是底层系统设置,不包含个人文档、照片与存档。重要数据请自行备份到移动硬盘或网盘。A restore point covers Windows system settings, not personal files or saves. Back those up separately.
03. 首次启动只看不点03. Inspect before applying
首次打开先完整运行一次检测。只做检测绝不改动任何设置,先看清每一项的真实状态。Run inspection first. It touches nothing — see the current state of each item and what the app reports.
04. 只勾选你看得懂的项04. Only check what you understand
每一项都写明作用、风险与恢复方式。拿不准、看不懂的项先不动,查清楚再决定。Every item spells out purpose, risk and undo path. Leave anything unclear unchecked until verified.
读懂状态标签Reading the status labels
状态不是评分,它只是当前信息的完整程度。宇奇引擎从不给电脑打 90 分或 60 分,只客观陈述每一项是知道、不知道、还是不能动。 Status isn't a score — it's how complete the information is right now. Yuqi Engine never grades your PC with arbitrary scores, but truthfully reports whether each item is known, unknown, or locked.
| 状态Status | 含义Meaning | 你该怎么做What to do |
|---|---|---|
| 已确认Confirmed | 当前状态已读取到,作用与风险清晰,可判断是否符合目标Current state read successfully — can be evaluated | 可以正常判断和应用Safe to evaluate and apply |
| 读取中Reading | 正在检索底层系统接口,数字会随进度动态变化Querying low-level system APIs; counts change with progress | 等它读完,不要中途强制操作Wait for completion — don't act mid-read |
| 待确认Pending | 尚未得到可靠复核结果(需管理员提权、策略受限或待重启)No reliable verification yet (needs elevation, policy-locked or pending reboot) | 不能当作已生效;查看详情原因,必要时提权重试Do not treat as applied; check reasons or retry elevated |
| 不可用Unavailable | 权限不足、系统版本不支持,或当前硬件缺少对应单元Insufficient permissions, unsupported Windows build, or hardware absent | 置灰保护,不会误操作;可在详情中查看具体依赖条件Locked for safety — check details for specific dependencies |
| 已应用Applied | 修改已成功写入,并通过软件二次读取复核确认生效Changes written and verified through a second inspection read | 正常使用;若有不适应随时可在软件中点击恢复Active; can be reverted inside the app whenever needed |
原则只有一条:没有得到可靠确认的项目,不会被标成「已成功」,也请你自己别当成已生效。One principle: an item without reliable confirmation is never marked “successful” — and you shouldn't treat it as applied either.
出问题了?带上证据反馈Something wrong? Report it with evidence
问题包会收集A diagnostics package includes
- 系统版本与基础硬件信息OS version and hardware specifications
- 相关模块的检测与操作日志Inspection and execution logs of related modules
- 各项设置的最终复核状态Final verification results for each setting
问题包不包含It does not include
- 个人文件、文档、照片、浏览器数据Personal files, documents, photos, browsing data
- 账号密码与凭据信息Passwords, credentials or tokens
- 未经脱敏的原始用户名、计算机名与具体路径(生成时已在本地自动隐去)Raw unmasked usernames, machine names or file paths (masked locally before saving)
问题包在本地生成纯文本压缩包,绝不私自联网上传任何数据。你可以在本地解压审查每一行内容后,连同「做了什么操作、期望什么结果、实际发生了什么」一起发到 GitHub Issues。信息越具体,越容易排查。The diagnostic package is generated locally as a plain text ZIP and never uploaded without your consent. Inspect every line if you wish, then submit it to GitHub Issues with details on what happened.