From a8bdaa4abfd617b55ed42e55ef4cea5df25d4691 Mon Sep 17 00:00:00 2001
From: nkh0472 <67589323+nkh0472@users.noreply.github.com>
Date: Fri, 6 Nov 2026 21:02:30 +0800
Subject: [PATCH] Update Language.zh-cn.xml
---
Translations/Language.zh-cn.xml | 50 ++++++++++++++++-----------------
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/Translations/Language.zh-cn.xml b/Translations/Language.zh-cn.xml
index f05beb2242..1891c9a1c0 100644
--- a/Translations/Language.zh-cn.xml
+++ b/Translations/Language.zh-cn.xml
@@ -1716,31 +1716,31 @@
VeraCrypt 无法移除其 Windows 功能更新注册项。\n\n请解决前面的配置错误，然后运行 VeraCrypt 修复/重新安装以重试清理。在这些注册项被移除之前，请勿启动 Windows 功能更新。
VeraCrypt 无法为已加密的系统配置 Windows 功能更新支持。\n\nVeraCrypt 会在其系统服务启动时自动重试。如果此警告再次出现，请解决前面的错误，然后运行 VeraCrypt 修复/重新安装。在此之前，请勿启动 Windows 功能更新。
VeraCrypt 无法更新其系统服务的可执行文件，该服务仍在使用先前的版本。\n\n请重启 Windows，然后再次运行 VeraCrypt 安装程序以修复安装。
- VeraCrypt could not complete the Secure Boot compatibility check. This does not establish an incompatibility. Keep Secure Boot settings unchanged until the firmware policy and installed boot files can be checked.
- VeraCrypt could not confirm that the boot loader update completed. The application installation may have succeeded while the boot loader still needs attention.\n\nSee the Windows Application event log for the cause. Restart Windows, then run VeraCrypt Repair/Reinstall. Keep a trustworthy VeraCrypt Rescue Disk available and do not change Secure Boot settings until the update has been confirmed.
- The boot loader update could not be confirmed. Restart Windows, then run Repair/Reinstall. Open VeraCrypt for recovery guidance; see the Windows Application event log for the cause.
- The system service update is pending a restart, so the boot loader update is not yet confirmed. Restart Windows, then run VeraCrypt Repair/Reinstall.
- VeraCrypt refused to update the boot loader because the firmware Secure Boot policy could not be validated for a supported loader set. The existing boot loader was retained.\n\nSee the Windows Application event log for details. If required signing CAs are missing from db, enable either Microsoft Corporation UEFI CA 2011, or both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023. A CA listed in dbx remains revoked even if it is enabled in db. If policy is unreadable or malformed, resolve that error first. Then run Repair/Reinstall. Keep trustworthy rescue media available before changing firmware settings.
- The boot loader update was refused because Secure Boot policy could not be validated. The existing loader was retained. Open VeraCrypt for guidance; see the Windows Application event log for details.
- VeraCrypt could not complete a system-service operation during installation. This can affect automatic boot loader maintenance and system favorite volumes, even if the boot loader update itself completed.\n\nSee the Windows Application event log for the failed operation. Restart Windows, then run VeraCrypt Repair/Reinstall.
- A VeraCrypt system-service operation failed. Restart Windows, then run Repair/Reinstall. Open VeraCrypt for guidance; see the Windows Application event log for details.
- Secure Boot compatibility could not be checked. Keep Secure Boot settings unchanged. Open VeraCrypt for guidance; see the Windows Application event log for details.
- The installed boot chain needs attention before using Secure Boot. Open VeraCrypt for recovery guidance; see the Windows Application event log for details.
- The Windows boot manager needs attention for the Secure Boot CA transition. Open VeraCrypt for guidance; see the Windows Application event log for details.
- Original loader backup could not be validated. Before decrypting or recreating rescue media, resolve this or obtain a trustworthy Rescue Disk. Do not back up the current boot area as a replacement. Open VeraCrypt for details.
- Windows feature update support could not be configured. Do not start a Windows feature update. Open VeraCrypt for guidance; see the Windows Application event log for details.
- Windows feature update registrations could not be removed. Do not start a Windows feature update until cleanup completes. See the Windows Application event log, then run VeraCrypt Repair/Reinstall.
- Recovery guidance could not be saved for the next VeraCrypt launch. Read the VeraCrypt entries in the Windows Application event log before decrypting, recreating rescue media, or changing Secure Boot settings.
- Windows denied access. Run the installer with administrator privileges and check permissions on the required files, folders, and devices.
- Windows reported a hardware error. Check the drive, its cable, and system memory. See the Windows Application event log for details and contact your hardware vendor for assistance.
- File system compression is not supported for VeraCrypt containers. In File Explorer, open the container's Properties > Advanced and clear 'Compress contents to save disk space'.
- An incompatible VeraCrypt driver is running. Restart Windows, then run this installer to update or repair VeraCrypt.
- Partition encryption or decryption is incomplete. Finish it before proceeding. In VeraCrypt, select Volumes > Resume Interrupted Process.
- Hidden-system volume headers cannot be changed this way. Boot the hidden OS, then use System > Change Password or System > Set Header Key Derivation Algorithm.
- This operation requires a fully decrypted system drive. In VeraCrypt, select System > Permanently Decrypt System Partition/Drive before proceeding.
- This check covers only the active Windows boot manager. Before revocation, also verify that decryption fallback and rescue backups are compatible. Creating a new VeraCrypt Rescue Disk can reuse an older stored boot-manager backup; creating the disk alone does not establish that backup's compatibility with the revocation.
- The Windows Boot Manager backup included in this Rescue Disk is signed by Microsoft Windows Production PCA 2011. Your firmware already contains Windows UEFI CA 2023.\n\nAfter PCA 2011 revocation (AvailableUpdates bit 0x80, including combined value 0x280), restoring this backup can leave Windows unable to start with Secure Boot enabled. Creating a new Rescue Disk reuses this stored backup; it does not update its signature.\n\nBefore applying the revocation, prepare compatible, updated Windows recovery media and verify the decryption fallback. Do not rely on this Rescue Disk to restore a compatible Windows Boot Manager. It remains useful for other VeraCrypt recovery tasks.
- VeraCrypt could not check the Windows Boot Manager backup in this Rescue Disk against the firmware Secure Boot policy.\n\nCreating or verifying this disk does not establish that its stored Windows Boot Manager is compatible with PCA 2011 revocation (AvailableUpdates bit 0x80, including combined value 0x280). Before applying the revocation, verify your recovery backups and prepare compatible, updated Windows recovery media.
+ VeraCrypt 无法完成安全启动兼容性检查。这并不表示存在不兼容。在能够检查固件策略和已安装的引导文件之前，请保持安全启动设置不变。
+ VeraCrypt 无法确认引导加载程序更新已完成。应用程序安装可能已成功，但引导加载程序仍需处理。\n\n请查看 Windows 应用程序事件日志以了解原因。重启 Windows，然后运行 VeraCrypt 修复/重新安装。请准备好可信的 VeraCrypt 应急盘，并在确认更新完成之前不要更改安全启动设置。
+ 无法确认引导加载程序更新。请重启 Windows，然后运行修复/重新安装。打开 VeraCrypt 获取恢复指导；请查看 Windows 应用程序事件日志以了解原因。
+ 系统服务更新正在等待重启，因此引导加载程序更新尚未确认。请重启 Windows，然后运行 VeraCrypt 修复/重新安装。
+ VeraCrypt 拒绝更新引导加载程序，因为无法针对受支持的引导加载程序集验证固件安全启动策略。现有引导加载程序已被保留。\n\n请查看 Windows 应用程序事件日志以了解详细信息。如果 db 中缺少所需的签名 CA，请启用 Microsoft Corporation UEFI CA 2011，或同时启用 Microsoft UEFI CA 2023 和 Microsoft Option ROM UEFI CA 2023。即使某个 CA 已在 db 中启用，只要它列在 dbx 中，就仍处于已撤销状态。如果策略无法读取或格式错误，请先解决该错误。然后运行修复/重新安装。更改固件设置前，请准备好可信的应急介质。
+ 由于无法验证安全启动策略，引导加载程序更新被拒绝。现有引导加载程序已被保留。打开 VeraCrypt 获取指导；请查看 Windows 应用程序事件日志以了解详细信息。
+ VeraCrypt 在安装期间无法完成系统服务操作。这可能影响自动引导加载程序维护和系统收藏加密卷，即使引导加载程序更新本身已完成。\n\n请查看 Windows 应用程序事件日志以了解失败的操作。重启 Windows，然后运行 VeraCrypt 修复/重新安装。
+ VeraCrypt 系统服务操作失败。请重启 Windows，然后运行修复/重新安装。打开 VeraCrypt 获取指导；请查看 Windows 应用程序事件日志以了解详细信息。
+ 无法检查安全启动兼容性。请保持安全启动设置不变。打开 VeraCrypt 获取指导；请查看 Windows 应用程序事件日志以了解详细信息。
+ 已安装的引导链在使用安全启动前需要处理。打开 VeraCrypt 获取恢复指导；请查看 Windows 应用程序事件日志以了解详细信息。
+ Windows 启动管理器需要处理安全启动 CA 过渡。打开 VeraCrypt 获取指导；请查看 Windows 应用程序事件日志以了解详细信息。
+ 无法验证原始引导器备份。在解密或重新创建应急介质之前，请解决此问题或获取可信的应急盘。请勿备份当前引导区域作为替代。打开 VeraCrypt 了解详细信息。
+ 无法配置 Windows 功能更新支持。请勿启动 Windows 功能更新。打开 VeraCrypt 获取指导；请查看 Windows 应用程序事件日志以了解详细信息。
+ 无法移除 Windows 功能更新注册项。在清理完成之前，请勿启动 Windows 功能更新。请查看 Windows 应用程序事件日志，然后运行 VeraCrypt 修复/重新安装。
+ 无法为下次启动 VeraCrypt 保存恢复指导。在解密、重新创建应急介质或更改安全启动设置之前，请阅读 Windows 应用程序事件日志中的 VeraCrypt 条目。
+ Windows 拒绝访问。请以管理员权限运行安装程序，并检查所需文件、文件夹和设备的权限。
+ Windows 报告了硬件错误。请检查驱动器、其线缆和系统内存。请查看 Windows 应用程序事件日志以了解详细信息，并联系硬件供应商寻求帮助。
+ VeraCrypt 容器不支持文件系统压缩。在文件资源管理器中，打开容器的“属性”>“高级”，清除“压缩内容以节省磁盘空间”。
+ 正在运行不兼容的 VeraCrypt 驱动程序。请重启 Windows，然后运行此安装程序以更新或修复 VeraCrypt。
+ 分区加密或解密未完成。请先完成该操作再继续。在 VeraCrypt 中，选择“加密卷”>“继续被中断的过程”。
+ 无法通过这种方式更改隐藏系统加密卷的头信息。请启动隐形操作系统，然后使用“系统”>“修改密码”或“系统”>“设置首密钥衍生算法”。
+ 此操作要求系统驱动器完全解密。在继续之前，请在 VeraCrypt 中选择“系统”>“永久解密系统分区/驱动器”。
+ 当前活动的 Windows 启动管理器。在撤销之前，还请验证解密回退和应急备份是否兼容。创建新的 VeraCrypt 应急盘可能会复用较早存储的启动管理器备份；仅创建该盘并不能证明该备份与撤销操作兼容。
+ 此应急盘中包含的 Windows 启动管理器备份由 Microsoft Windows Production PCA 2011 签名。您的固件已包含 Windows UEFI CA 2023。\n\n在 PCA 2011 撤销（AvailableUpdates 位 0x80，包括组合值 0x280）之后，恢复此备份可能导致 Windows 在启用安全启动时无法启动。创建新的应急盘会复用此已存储的备份；它不会更新其签名。\n\n在应用撤销之前，请准备兼容的、更新后的 Windows 恢复介质，并验证解密回退。请勿依赖此应急盘恢复兼容的 Windows 启动管理器。它对于其他 VeraCrypt 恢复任务仍然有用。
+ VeraCrypt 无法根据固件安全启动策略检查此应急盘中的 Windows 启动管理器备份。\n\n创建或验证此盘并不能证明其存储的 Windows 启动管理器与 PCA 2011 撤销（AvailableUpdates 位 0x80，包括组合值 0x280）兼容。在应用撤销之前，请验证您的恢复备份，并准备兼容的、更新后的 Windows 恢复介质。