|
1689 | 1689 | <entry lang="zh-cn" key="SYSENC_EFI_UNSUPPORTED_SECUREBOOT_CA">安全启动已启用，但固件的安全启动数据库不信任 VeraCrypt EFI 引导加载程序支持的任何 Microsoft UEFI CA 集合。请启用 Microsoft Corporation UEFI CA 2011，或同时启用 Microsoft UEFI CA 2023 和 Microsoft Option ROM UEFI CA 2023，然后运行 VeraCrypt 的“修复/重新安装”。或者，请禁用安全启动。</entry> |
1690 | 1690 | <entry lang="zh-cn" key="MACOSX_CHECK_FILESYS">按下“确定”后，将打开“终端”窗口，并使用 'diskutil' 检查所选 VeraCrypt 卷上的文件系统。结果将显示在该窗口中。\n\n如果无法开始检查，则将改为启动“磁盘工具”。</entry> |
1691 | 1691 | <entry lang="zh-cn" key="MACOSX_REPAIR_FILESYS">按下“确定”后，将打开“终端”窗口，并尝试使用 'diskutil' 修复所选 VeraCrypt 卷上的文件系统。结果将显示在该窗口中。\n\n如果无法开始修复，则将改为启动“磁盘工具”。</entry> |
1692 | | - <entry lang="en" key="SYSENC_EFI_LOADER_NOT_TRUSTED_BY_SECUREBOOT">Warning: VeraCrypt could not validate the installed EFI bootloader files against one complete embedded resource set and confirm that all known required signing CAs are present in db and not listed by dbx. Firmware may reject VeraCrypt when Secure Boot is enabled.\n\nBefore booting with Secure Boot enabled, restore the required Microsoft certificates and current dbx as needed, then run VeraCrypt Repair/Reinstall. Do not remove Microsoft Corporation UEFI CA 2011 until db contains both Microsoft UEFI CA 2023 and Microsoft Option ROM UEFI CA 2023 and the actual installed files match VeraCrypt's 2023 set. This check cannot model every image-hash or security-version revocation. Make sure you have an up-to-date VeraCrypt Rescue Disk.</entry> |
1693 | | - <entry lang="en" key="SYSENC_EFI_WINDOWS_LOADER_NOT_TRUSTED_BY_SECUREBOOT">Warning: VeraCrypt could not validate the embedded signature and known-CA compatibility of the Windows Boot Manager it chainloads (bootmgfw_ms.vc). The file may be missing, unreadable, not a Windows Boot Manager, have an unrecognized embedded signer, or use a known signing CA that is absent from db or listed by dbx. The handoff to Windows may fail when Secure Boot is enabled.\n\nComplete or repair the Windows Secure Boot certificate and boot-manager update, keep the VeraCrypt System Favorites service enabled, and run VeraCrypt Repair/Reinstall. Repair also checks Windows' serviced EFI_EX/EFI copies for a compatible current Boot Manager. If Windows cannot start, temporarily disable Secure Boot to recover. Make sure you have an up-to-date VeraCrypt Rescue Disk.</entry> |
1694 | | - <entry lang="en" key="SYSENC_EFI_WINDOWS_LOADER_PCA2011_MIGRATION_NEEDED">Warning: The embedded signature of the Windows Boot Manager used by VeraCrypt (bootmgfw_ms.vc) is still issued by Microsoft Windows Production PCA 2011, although firmware db already contains Windows UEFI CA 2023. Its known CA is currently allowed, but it will no longer start after the PCA 2011 certificate is added to dbx.\n\nDo not apply the PCA 2011 revocation (AvailableUpdates bit 0x80, including combined value 0x280) yet. First complete the Windows 2023 boot-manager update while the VeraCrypt System Favorites service is enabled, then run VeraCrypt Repair/Reinstall so VeraCrypt can import a compatible serviced EFI_EX/EFI copy. Verify the embedded issuer of bootmgfw_ms.vc is Windows UEFI CA 2023 and make sure you have an up-to-date VeraCrypt Rescue Disk.</entry> |
1695 | | - <entry lang="en" key="MOUNT_SERVICE_INCOMPATIBLE">The service running this volume does not support the requested unmount operation.\n\nUnmount the volume using the version of VeraCrypt that mounted it, then mount it again with this version. Close files using the volume if necessary. Always unmount volumes before upgrading VeraCrypt.</entry> |
1696 | | - <entry lang="en" key="MOUNT_SERVICE_CLEANUP_FAILED">VeraCrypt could not complete cleanup after a failed mount. The volume may still be accessible.\n\nUnmount the volume in VeraCrypt. If unmounting fails, restart the computer before relying on the volume being locked.</entry> |
1697 | | - <entry lang="en" key="DISMOUNT_SERVICE_CLEANUP_FAILED">The volume's auxiliary mount has been removed, but VeraCrypt could not confirm that its service has stopped. Encryption keys may still be in memory.\n\nIf the service does not stop, restart the computer before relying on the volume being locked.</entry> |
1698 | | - <entry lang="en" key="MOUNT_SERVICE_UNAVAILABLE">VeraCrypt could not contact or verify the volume service.\n\nIf this occurred while dismounting, close files using the volume and retry. If cleanup cannot be confirmed, restart the computer before relying on the volume being locked.</entry> |
1699 | | - <entry lang="en" key="VOLUME_DISCOVERY_FAILED">VeraCrypt could not verify all volume information. A volume service or disk image may be unavailable or inaccessible.\n\nAny volumes shown are only the entries VeraCrypt could verify. Wait for pending disk operations to finish and retry. An incomplete list does not confirm that all volumes are dismounted.</entry> |
1700 | | - <entry lang="en" key="VOLUME_IN_USE">The volume is in use. Close files and applications using it, then retry unmounting.</entry> |
1701 | | - <entry lang="en" key="OPERATION_TIMED_OUT">The operation did not finish in time. Check the volume's status before retrying.</entry> |
1702 | | - <entry lang="en" key="VOLUME_STATUS_UNKNOWN">Status unavailable</entry> |
1703 | | - <entry lang="en" key="VOLUME_IMAGE_ABSENT">Image detached; unmount to finish</entry> |
1704 | | - <entry lang="en" key="VOLUME_DISCOVERY_PENDING">Refreshing volume status…</entry> |
1705 | | - <entry lang="en" key="VOLUME_DISCOVERY_STALLED">Volume status unavailable; retrying…</entry> |
1706 | | - <entry lang="en" key="VOLUME_DISCOVERY_PARTIAL">Some volume information is unavailable; retrying…</entry> |
1707 | | - <entry lang="en" key="LINUX_ELEVATION_BLOCKED">The current launcher or sandbox blocks VeraCrypt from obtaining administrator privileges (Linux NoNewPrivs).\n\nClose VeraCrypt and start it outside this restricted environment. On NixOS, use the native VeraCrypt package instead of appimage-run.</entry> |
1708 | | - <entry lang="en" key="LINUX_REQUESTER_BACKED_VOLUME">VeraCrypt could not open the volume file with administrator privileges, so it opened the file with your user account's access rights:\n{0}\n\nKeep the source share mounted and your user session active until this VeraCrypt volume is unmounted. Ejecting the share or logging out can lose data. For regular use, store the volume where VeraCrypt can open it with administrator privileges, for example on a share mounted with the kernel CIFS client.</entry> |
1709 | | - <entry lang="en" key="PCSC_ERROR">Smart card error</entry> |
| 1692 | + <entry lang="zh-cn" key="SYSENC_EFI_LOADER_NOT_TRUSTED_BY_SECUREBOOT">警告：VeraCrypt 无法依据一整套完整的嵌入资源来验证已安装的 EFI 引导加载程序文件，也无法确认所有已知必需的签名 CA 都存在于 db 中且未被 dbx 列出。启用安全启动时，固件可能会拒绝 VeraCrypt。\n\n在启用安全启动的情况下启动前，请根据需要恢复必需的 Microsoft 证书和当前 dbx，然后运行 VeraCrypt 修复/重新安装。在 db 同时包含 Microsoft UEFI CA 2023 和 Microsoft Option ROM UEFI CA 2023，且实际安装的文件与 VeraCrypt 的 2023 集匹配之前，请勿移除 Microsoft Corporation UEFI CA 2011。此检查无法模拟每一种映像哈希或安全版本撤销情况。请确保您有最新的 VeraCrypt 应急盘。</entry> |
| 1693 | + <entry lang="zh-cn" key="SYSENC_EFI_WINDOWS_LOADER_NOT_TRUSTED_BY_SECUREBOOT">警告：VeraCrypt 无法验证其链式加载的 Windows 启动管理器（bootmgfw_ms.vc）的嵌入签名和已知 CA 兼容性。该文件可能缺失、无法读取、不是 Windows 启动管理器、具有无法识别的嵌入签名者，或使用了不存在于 db 中或被 dbx 列出的已知签名 CA。启用安全启动时，向 Windows 的交接可能会失败。\n\n请完成或修复 Windows 安全启动证书和启动管理器更新，保持 VeraCrypt 系统收藏加密卷服务启用，并运行 VeraCrypt 修复/重新安装。修复还会检查 Windows 维护的 EFI_EX/EFI 副本中是否存在兼容的当前启动管理器。如果 Windows 无法启动，请临时禁用安全启动以进行恢复。请确保您有最新的 VeraCrypt 应急盘。</entry> |
| 1694 | + <entry lang="zh-cn" key="SYSENC_EFI_WINDOWS_LOADER_PCA2011_MIGRATION_NEEDED">警告：VeraCrypt 使用的 Windows 启动管理器（bootmgfw_ms.vc）的嵌入签名仍由 Microsoft Windows Production PCA 2011 颁发，尽管固件 db 已包含 Windows UEFI CA 2023。其已知 CA 当前仍被允许，但在将 PCA 2011 证书添加到 dbx 后，它将不再启动。\n\n暂勿执行 PCA 2011 证书撤销操作（AvailableUpdates 位 0x80，包括组合值 0x280）。请首先在 VeraCrypt 系统收藏加密卷服务启用的情况下完成 Windows 2023 启动管理器更新，然后运行 VeraCrypt 修复/重新安装，以便 VeraCrypt 可以导入兼容的、经过维护的 EFI_EX/EFI 副本。请验证 bootmgfw_ms.vc 的嵌入颁发者是 Windows UEFI CA 2023，并确保您有最新的 VeraCrypt 应急盘。</entry> |
| 1695 | + <entry lang="zh-cn" key="MOUNT_SERVICE_INCOMPATIBLE">运行此加密卷的服务不支持请求的卸载操作。\n\n请使用加载此加密卷的 VeraCrypt 版本卸载它，然后使用此版本重新加载它。如有必要，请关闭正在使用该加密卷的文件。升级 VeraCrypt 前请始终卸载加密卷。</entry> |
| 1696 | + <entry lang="zh-cn" key="MOUNT_SERVICE_CLEANUP_FAILED">VeraCrypt 无法在加载失败后完成清理。此加密卷可能仍可访问。\n\n请在 VeraCrypt 中卸载此加密卷。如果卸载失败，请重启计算机，然后再认为此加密卷已锁定。</entry> |
| 1697 | + <entry lang="zh-cn" key="DISMOUNT_SERVICE_CLEANUP_FAILED">此加密卷的辅助挂载已被移除，但 VeraCrypt 无法确认其服务已停止。加密密钥可能仍在内存中。\n\n如果服务未停止，请重启计算机，然后再认为此加密卷已锁定。</entry> |
| 1698 | + <entry lang="zh-cn" key="MOUNT_SERVICE_UNAVAILABLE">VeraCrypt 无法联系或验证加密卷服务。\n\n如果这是在卸载时发生的，请关闭正在使用该加密卷的文件并重试。如果无法确认清理已完成，请重启计算机，然后再认为此加密卷已锁定。</entry> |
| 1699 | + <entry lang="zh-cn" key="VOLUME_DISCOVERY_FAILED">VeraCrypt 无法验证所有加密卷信息。加密卷服务或磁盘映像可能不可用或无法访问。\n\n显示的加密卷仅包含 VeraCrypt 能够验证的条目。请等待挂起的磁盘操作完成，然后重试。不完整的列表并不确认所有加密卷均已卸载。</entry> |
| 1700 | + <entry lang="zh-cn" key="VOLUME_IN_USE">此加密卷正在使用中。请关闭正在使用它的文件和应用程序，然后重试卸载。</entry> |
| 1701 | + <entry lang="zh-cn" key="OPERATION_TIMED_OUT">操作未及时完成。重试前请检查加密卷状态。</entry> |
| 1702 | + <entry lang="zh-cn" key="VOLUME_STATUS_UNKNOWN">状态不可用</entry> |
| 1703 | + <entry lang="zh-cn" key="VOLUME_IMAGE_ABSENT">映像已分离；请卸载以完成</entry> |
| 1704 | + <entry lang="zh-cn" key="VOLUME_DISCOVERY_PENDING">正在刷新加密卷状态…</entry> |
| 1705 | + <entry lang="zh-cn" key="VOLUME_DISCOVERY_STALLED">加密卷状态不可用；正在重试…</entry> |
| 1706 | + <entry lang="zh-cn" key="VOLUME_DISCOVERY_PARTIAL">部分加密卷信息不可用；正在重试…</entry> |
| 1707 | + <entry lang="zh-cn" key="LINUX_ELEVATION_BLOCKED">当前启动器或沙箱阻止 VeraCrypt 获取管理员权限（Linux NoNewPrivs）。\n\n请关闭 VeraCrypt，并在此受限环境之外启动它。在 NixOS 上，请使用原生 VeraCrypt 软件包，而不要使用 appimage-run。</entry> |
| 1708 | + <entry lang="zh-cn" key="LINUX_REQUESTER_BACKED_VOLUME">VeraCrypt 无法以管理员权限打开该加密卷文件，因此以您的用户账户的访问权限打开了该文件：\n{0}\n\n在此 VeraCrypt 加密卷被卸载之前，请保持源共享挂载状态并且您的用户会话处于活动状态。弹出该共享或注销可能会导致数据丢失。如需日常使用，请将加密卷存储在 VeraCrypt 能够以管理员权限打开的位置，例如使用内核 CIFS 客户端挂载的共享上。</entry> |
| 1709 | + <entry lang="zh-cn" key="PCSC_ERROR">智能卡错误</entry> |
1710 | 1710 | </localization> |
1711 | 1711 | <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema"> |
1712 | 1712 | <xs:element name="VeraCrypt"> |
|
0 commit comments