101 | 文件所有权 |
File ownership |
102 | 工作单位(%1) |
Work (%1) |
103 | 个人 |
Personal |
0x1118 | EFS 服务启动失败。错误代码: %3。 |
EFS Service failed to start. Error code: %3. |
0x111B | EFS 服务无法填充 SID 信息。错误代码: %3。 |
EFS service was unable to populate SID information. Error code: %3. |
0x111C | EFS 服务无法确定计算机名称。错误代码: %3。 |
EFS service was unable to determine the computer name. Error code: %3. |
0x111D | EFS 服务无法初始化缓存锁定。错误代码: %3。 |
EFS service was unable to initialize cache lock. Error code: %3. |
0x111E | EFS 服务无法初始化 BCrypt 算法提供程序。错误代码: %3。 |
EFS service was unable to initialize the BCrypt Algorithm Provider. Error code: %3. |
0x111F | EFS 服务无法查询软件授权中的缓存大小。错误代码: %3。 |
EFS service was unable to query Software Licensing for the cache size. Error code: %3. |
0x1120 | EFS 服务无法打开 MS_DEF_PROV 提供程序的句柄。错误代码: %3。 |
EFS service was unable to open handle to the MS_DEF_PROV provider. Error code: %3. |
0x1121 | EFS 服务无法设置来自 LSA 的通知。错误代码: %3。 |
EFS service was unable to setup notifications from LSA. Error code: %3. |
0x1122 | EFS 服务无法初始化恢复策略资源。错误代码: %3。 |
EFS service was unable to initialize the recovery policy resource. Error code: %3. |
0x1123 | EFS 服务无法处理恢复策略。错误代码: %3。 |
EFS service was unable process the recovery policy. Error code: %3. |
0x1124 | EFS 服务无法向 NTFS 通知它的状态。错误代码: %3。 |
EFS service was unable to notify NTFS of its state. Error code: %3. |
0x1125 | EFS 服务无法设置组策略更改通知。错误代码: %3。 |
EFS service was unable to setup group policy change notifications. Error code: %3. |
0x1126 | EFS 服务无法处理活动用户会话。错误代码: %3。 |
EFS service was unable to process active user sessions. Error code: %3. |
0x1128 | %1.%2: EFS 服务无法订阅 MDM 策略更新。索引: %3。 |
%1.%2: EFS service failed to subscribe for updates to an MDM policy. Index: %3. |
0x1129 | %1.%2: 无法初始化一个或多个同步对象。错误代码: %3。 |
%1.%2: Failed to initialize one or more synchronization objects. Error code: %3. |
0x1130 | %1.%2: EFS 服务无法处理 MDM 策略更新。错误代码: %3。 |
%1.%2: EFS service failed to process MDM policy updates. Error code: %3. |
0x1131 | %1.%2: EFS 服务无法针对 Windows 信息保护预配用户。错误代码: %3。 |
%1.%2: EFS service failed to provision a user for Windows Information Protection. Error code: %3. |
0x1132 | %1.%2: EFS 服务无法为 DPL 预配用户。错误代码: %3。 |
%1.%2: EFS service failed to provision a user for DPL. Error code: %3. |
0x1133 | %1.%2: EFS 服务无法初始化文件加密队列。错误代码: %3。 |
%1.%2: EFS service failed to initialize file encryption queues. Error code: %3. |
0x1134 | %1.%2: 恢复策略数据的格式无效。错误代码: %3。 |
%1.%2: Recovery policy data is in an invalid format. Error code: %3. |
0x1142 | %1.%2: EFS 服务无法针对 Windows 信息保护预配 RMS。错误代码: %3。 |
%1.%2: EFS service failed to provision RMS for Windows Information Protection. Error code: %3. |
0x1B58 | 无法确定计算机角色。%1 |
Machine role cannot be determined. %1 |
0x1B5A | 无法创建默认组策略对象。%1 |
Default group policy object cannot be created. %1 |
0x50000002 | 错误 |
Error |
0x50000003 | 警告 |
Warning |
0x50000004 | 信息 |
Information |
0x50000005 | 详细 |
Verbose |
0x90000001 | Microsoft-Windows-EFS |
Microsoft-Windows-EFS |
0x90000002 | Application |
Application |
0xB0000001 | 在 %1.%2 的 API 调用失败。错误代码: %3 |
An API call failed at %1.%2. Error code: %3 |
0xB0000002 | 在 %1.%2 的 API 调用失败。错误代码: %3,数据: %4 |
An API call failed at %1.%2. Error code: %3, Data: %4 |
0xB0000003 | 在 %1.%2 的 API 调用失败。错误代码: %3,数据: %4,%5 |
An API call failed at %1.%2. Error code: %3, Data: %4, %5 |
0xB0000004 | %1.%2: 无法分配 %3 字节。 |
%1.%2: Failed to allocate %3 bytes. |
0xB0000100 | EFS 密钥已从当前密钥提升。CertValidated: %1,cbHash: %2,pbHash: %3,ContainerName: %4,ProviderName: %5,DisplayInformation: %6,dwCapabilities: %7,bIsCurrentKey: %8,eKeyType: %9 |
EFS key promoted from current key. CertValidated: %1, cbHash: %2, pbHash: %3, ContainerName: %4, ProviderName: %5, DisplayInformation: %6, dwCapabilities: %7, bIsCurrentKey: %8, eKeyType: %9 |
0xB0000101 | EFS 密钥已从当前密钥降级。CertValidated: %1,cbHash: %2,pbHash: %3,ContainerName: %4,ProviderName: %5,DisplayInformation: %6,dwCapabilities: %7,bIsCurrentKey: %8,eKeyType: %9 |
EFS key demoted from current key. CertValidated: %1, cbHash: %2, pbHash: %3, ContainerName: %4, ProviderName: %5, DisplayInformation: %6, dwCapabilities: %7, bIsCurrentKey: %8, eKeyType: %9 |
0xB0000102 | EFS 密钥已从缓存中刷新。CertValidated: %1,cbHash: %2,pbHash: %3,ContainerName: %4,ProviderName: %5,DisplayInformation: %6,dwCapabilities: %7,bIsCurrentKey: %8,eKeyType: %9 |
EFS key flushed from cache. CertValidated: %1, cbHash: %2, pbHash: %3, ContainerName: %4, ProviderName: %5, DisplayInformation: %6, dwCapabilities: %7, bIsCurrentKey: %8, eKeyType: %9 |
0xB0000103 | %1.%2: 指定的密钥对于 EFS 来说无效 |
%1.%2: The specified key is not valid for EFS |
0xB0000104 | %1.%2: 尝试创建一个新 EFS 密钥 |
%1.%2: Attempt to create a new EFS key |
0xB0000105 | %1.%2: 已成功创建新 EFS 密钥 |
%1.%2: A new EFS key was successfully created |
0xB0000106 | %1.%2: 开始搜索“我的存储”中的有效 EFS 密钥 |
%1.%2: Begin searching the MY store for a valid EFS key |
0xB0000108 | %1.%2: 正在从注册表中删除当前密钥 |
%1.%2: Deleting currentkey from registry |
0xB0000109 | %1.%2: EFS 证书是自签名证书,但是自签名证书已被策略所禁用 |
%1.%2: The EFS cert is self-signed, but self-signed certs are disabled by policy |
0xB0000110 | %1.%2: 策略要求使用 RSA,但是该密钥不支持 RSA 加密 |
%1.%2: RSA is required by policy, but the key does not support RSA encryption |
0xB0000111 | %1.%2: 策略要求使用 MASTERKEY,但是该密钥不支持 MASTERKEY 加密 |
%1.%2: MASTERKEY is required by policy, but the key does not support MASTERKEY encryption |
0xB0000112 | %1.%2: 策略要求使用 SMARTCARDS,但是该密钥不基于 SMARTCARD |
%1.%2: SMARTCARDS are required by policy, but the key is not SMARTCARD-based |
0xB0000113 | %1.%2: 密钥已过期 |
%1.%2: key is expired |
0xB0000114 | %1.%2: 密钥有效 |
%1.%2: key is valid |
0xB0000115 | %1.%2: 尝试基于证书哈希查找匹配的密钥 |
%1.%2: try and locate the matching key based on cert hash |
0xB0000116 | %1.%2: 已从注册表中成功加载密钥 |
%1.%2: key successfully loaded from registry |
0xB0000117 | %1.%2: 尝试在缓存中查找匹配的密钥 |
%1.%2: try and locate the matching key in cache |
0xB0000118 | %1.%2: 正在尝试加载主密钥历史记录 |
%1.%2: trying to load the masterkey history |
0xB0000119 | %1.%2: 主密钥历史记录已加载 |
%1.%2: masterkey history loaded |
0xB0000120 | %1.%2: 无法加密: SIS 或 HSM 文件 |
%1.%2: failed to encrypt: SIS or HSM file |
0xB0000121 | %1.%2: 策略已禁用 Suite B,但是该密钥是 Suite B 密钥 |
%1.%2: Suite B is disabled by policy, but the key is a Suite B key |
0xB0000122 | %1.%2: 策略要求使用 Suite B,但是该密钥不是 Suite B 密钥 |
%1.%2: Suite B is required by policy, but the key is not a Suite B key |
0xB0000200 | %1.%2: 正在释放用户缓存对象。引用计数: %3 |
%1.%2: releasing user cache object. Refcount: %3 |
0xB0000201 | %1.%2: 正在尝试停止缓存轮询线程 |
%1.%2: trying to stop cache polling thread |
0xB0000202 | %1.%2: 在缓存中无解密状态 |
%1.%2: no decryption status in cache |
0xB0000203 | %1.%2: 在缓存中找到匹配的解密状态 |
%1.%2: found matching decryption status in cache |
0xB0000204 | %1.%2: 正在尝试将密钥添加到用户缓存 |
%1.%2: attempting to add key to user cache |
0xB0000205 | EFS 密钥已添加到用户缓存。CertValidated: %1,cbHash: %2,pbHash: %3,ContainerName: %4,ProviderName: %5,DisplayInformation: %6,dwCapabilities: %7,bIsCurrentKey: %8,eKeyType: %9 |
EFS key added to user cache. CertValidated: %1, cbHash: %2, pbHash: %3, ContainerName: %4, ProviderName: %5, DisplayInformation: %6, dwCapabilities: %7, bIsCurrentKey: %8, eKeyType: %9 |
0xB0000206 | %1.%2: 正在确保用户具有缓存节点 |
%1.%2: ensuring user has cache node |
0xB0000207 | %1.%2: 在用户信息中找到缓存节点 |
%1.%2: found cache node in user info |
0xB0000208 | %1.%2: 在全局缓存中找到缓存节点 |
%1.%2: found cache node in global cache |
0xB0000209 | %1.%2: 正在为用户创建新的缓存节点 |
%1.%2: creating new cache node for user |
0xB0000300 | %1.%2: 策略设置已指定在移除卡时刷新。正在开始轮询线程... |
%1.%2: Policy settings specified flush on card removal. Starting the polling thread... |
0xB0000301 | %1.%2: 策略设置已指定在超时时不进行刷新。正在停止轮询线程... |
%1.%2: Policy settings specified NO flush on timeout. Stopping the polling thread... |
0xB0000302 | %1.%2: 策略设置已指定在超时时刷新。正在开始轮询线程... |
%1.%2: Policy settings specified flush on timeout. Starting the polling thread... |
0xB0000303 | %1.%2: 策略设置已指定新的缓存刷新间隔: %3。停止轮询(将在有活动用户缓存时重新开始) |
%1.%2: Policy settings specified new cache flush interval: %3. Stop polling (will restart if there are active user caches) |
0xB0000304 | %1.%2: 轮询线程已停止 |
%1.%2: Polling thread stopped |
0xB0000305 | %1.%2: 刷新策略指定的缓存,并且我们有活动用户缓存。开始轮询。 |
%1.%2: Flush cache specified by policy, and we have active user caches. Start polling. |
0xB0000306 | %1.%2: 轮询线程已开始 |
%1.%2: Polling thread started |
0xB0000307 | %1.%2: 检测到用户登录。正在开始 SSO 处理。 |
%1.%2: User logon detected. Beginning SSO processing. |
0xB0000308 | %1.%2: 检测到用户登录,但它不是基于智能卡。不需要进行任何 SSO 处理。 |
%1.%2: User logon detected, but is not smartcard-based. No SSO processing required. |
0xB0000309 | %1.%2: 检测到智能卡通知。正在开始 SSO 处理。 |
%1.%2: Smartcard notification detected. Beginning SSO processing. |
0xB0000310 | %1.%2: 检测到智能卡通知,但是已缓存登录证书。不需要进行任何处理。 |
%1.%2: Smartcard notification detected, but the logon cert is already cached. No processing required. |
0xB0000311 | %1.%2: 当前密钥与登录证书匹配。正在设置 PIN 缓存。 |
%1.%2: Current key matches the logon cert. Setting up the PIN cache. |
0xB0000312 | %1.%2: 用户当前尚未拥有密钥。如果策略要求使用智能卡,将缓存登录证书和 PIN。 |
%1.%2: User does not yet have a current key. If smartcard is required by policy, the logon cert and PIN will be cached. |
0xB0000313 | %1.%2: 在 DC 上检测到登录通知。正在开始 DRA 安装。 |
%1.%2: Logon notification detected on DC. Beginning DRA install. |
0xB0000314 | %1.%2: 用户尚未具有缓存: 现在正在生成 |
%1.%2: user does not already have a cache: generating one now |
0xB0000315 | %1.%2: 正在生成 PIN 和登录证书的预先缓存 |
%1.%2: generating pre-cache for PIN and logon cert |
0xB0000316 | %1.%2: 已尝试安装登录证书,但是它不可用(非智能卡登录或已移除智能卡) |
%1.%2: tried to install logon cert, but it's not available (not a smartcard logon, or the smartcard was removed) |
0xB0000317 | %1.%2: 登录证书已成功安装 |
%1.%2: logon cert successfully installed |
0xB0000318 | %1.%2: 正在尝试安装登录证书 |
%1.%2: trying to install logon cert |
0xB0000319 | %1.%2: 检测到用户锁定。正在开始 SSO 处理。 |
%1.%2: User lock detected. Beginning SSO processing. |
0xB0000320 | %1.%2: 检测到用户注销。正在开始 SSO 处理。 |
%1.%2: User logoff detected. Beginning SSO processing. |
0xB0000321 | %1.%2: 正在刷新用户缓存 |
%1.%2: Flushing the user cache |
0xB0000322 | %1.%2: 用户已锁定工作站,但策略指示不刷新缓存 |
%1.%2: User has locked workstation, but policy says not to flush cache |
0xB0000323 | %1.%2: 正在检查过期缓存项 |
%1.%2: Checking for expired cache entries |
0xB0000324 | %1.%2: 恢复策略中的证书已过期 |
%1.%2: Expired certificate in recovery policy |
0xB0000325 | %1.%2: 恢复策略中的证书尚未生效 |
%1.%2: Certificate in recovery policy is not yet valid |
0xB0000400 | %1.%2: SL 策略已成功更新 |
%1.%2: SL policy successfully updated |
0xB0000410 | %1.%2: EFS 被 SL 策略禁用 |
%1.%2: EFS is disabled by SL policy |
0xB0000411 | %1.%2: EFS 尚未初始化 |
%1.%2: EFS is not yet initialized |
0xB0000412 | %1.%2: 已禁用 EFS |
%1.%2: EFS is disabled |
0xB0000500 | %1.%2: API 收到的数据过大。期望: %3,实际: %4 |
%1.%2: the data received by the API was too large. Expected: %3, Actual: %4 |
0xB0000501 | %1.%2: API 收到的数据过小。期望: %3,实际: %4 |
%1.%2: the data received by the API was too small. Expected: %3, Actual: %4 |
0xB0000502 | %1.%2: 检测到可能存在 EFS 攻击: %3,%4,%5 |
%1.%2: POSSIBLE EFS ATTACK DETECTED: %3, %4, %5 |
0xB0000503 | %1.%2: 正在尝试验证 EFS 流 |
%1.%2: attempting to validate EFS stream |
0xB0000504 | %1.%2: 已验证 EFS 流 |
%1.%2: EFS stream validated |
0xB0000600 | PIN 提示对话框已关闭 |
PIN prompt dialog has closed |
0xB0000601 | 提示用户选择基于智能卡的 EFS 证书 |
Prompt the user to select a smartcard-based EFS cert |
0xB0000602 | 用户已成功选择基于智能卡的 EFS 证书 |
Smartcard-based EFS cert successfully selected by the user |
0xB0000603 | 提示用户输入 PIN |
Prompt the user for PIN |
0xB0000604 | 已成功获取用户的 PIN |
PIN successfully acquired from the user |
0xB0000605 | 在缓存中找到完美匹配。 |
Perfect match found in cache. |
0xB0000606 | 已加载主密钥历史记录 |
Masterkey history already loaded |
0xB0000607 | 已从缓存中加载当前密钥 |
Current key loaded from cache |
0xB0000608 | 已从注册表中加载当前密钥 |
Current key loaded from registry |
0xB0000609 | %1.%2: 主密钥历史记录: 大小一致性检查失败。%3,%4,%5 |
%1.%2: Masterkey history: failed size consistency check. %3, %4, %5 |
0xB0001000 | %1.%2: 加密密钥不相等 |
%1.%2: Encrypted keys not equal |
0xB0001001 | %1.%2: 正在执行重新生成密钥,但 DDF 条目已存在 |
%1.%2: doing a REKEY, but the DDF entry already exists |
0xB0001002 | %1.%2: 替换操作添加了一个 DDF (意外) |
%1.%2: replace operation added a DDF (unexpected) |
0xB0001003 | %1.%2: 用户正在修改不匹配 PoP 条目的 DDF 条目。要求使用 WRITE_ATTRIBUTES |
%1.%2: user is modifying a DDF entry not matching the PoP entry. Require WRITE_ATTRIBUTES |
0xB0001004 | %1.%2: 用户正在修改匹配 PoP 条目的 DDF,或者 DRF。不要求使用 WRITE_ATTRIBUTES |
%1.%2: user is modifying a DDF matching the PoP entry, or the DRF. Don't require WRITE_ATTRIBUTES |
0xB0001005 | %1.%2: 意外情况: SC 无 ENCRYPTED_KEY 失败 |
%1.%2: UNEXPECTED condition: no ENCRYPTED_KEY for SC failure |
0xB0001006 | %1.%2: 即插即用服务未就绪。EFS 服务器将不会尝试检测中断的加密/解密操作。 |
%1.%2: Plug-n-Play service not ready. EFS server will not try to detect interrupted encryption/decryption operation(s). |
0xB0001101 | %1.%2: 无法打开日志文件。无法恢复加密/解密操作。 |
%1.%2: Cannot open log file. Encryption/decryption operation(s) cannot be recovered. |
0xB0001102 | %1.%2: 无法读取日志文件。无法恢复加密/解密操作。 |
%1.%2: Cannot read log file. Encryption/decryption operation(s) cannot be recovered. |
0xB0001103 | %1.%2: 找到已受损或不同格式的日志文件。未采取任何操作。 |
%1.%2: A corrupted or different format log file has been found. No action was taken. |
0xB0001104 | %1.%2: 无法以非缓存 IO 形式打开日志文件。未采取任何操作。 |
%1.%2: The log file cannot be opened as non-cached IO. No action was taken. |
0xB0001105 | %1.%2: 在卷上找到中断的加密/解密操作。恢复过程已开始。 |
%1.%2: Interrupted encryption/decryption operation(s) found on a volume. Recovery procedure started. |
0xB0001106 | %1.%2: EFS 恢复服务无法打开文件 %3。无法恢复中断的加密/解密操作。 |
%1.%2: EFS recovery service cannot open the file %3. The interrupted encryption/decryption operation cannot be recovered. |
0xB0001107 | %1.%2: EFS 服务已成功恢复 %3。 |
%1.%2: EFS service recovered %3 successfully. |
0xB0001108 | %1.%2: EFS 服务无法打开文件 %3 上的所有流。未恢复该文件。 |
%1.%2: EFS service could not open all the streams on file %3 The file was not recovered. |
0xB0001109 | %1.%2: 无法完全恢复 %3。EFS 驱动程序可能已丢失。 |
%1.%2: %3 could not be recovered Completely. EFS driver may be missing. |
0xB0001110 | %1.%2: 在恢复流的过程中发生 IO 错误。未恢复 %3。 |
%1.%2: IO Error occurred during stream recovery. %3 was not recovered. |
0xB0001111 | %1.%2: EFS 恢复服务无法按名称打开备份文件 %3。可能已恢复中断的加密/解密操作(在文件 %4 上)。将不删除该备份文件。如果恢复操作成功完成,则用户应删除该备份文件。 |
%1.%2: EFS recovery service cannot open the backup file %3 by name. The interrupted encryption/decryption operation (on file %4) may be recovered. The backup file will not be deleted. User should delete the backup file if the recovery operation is done successfully. |
0xB0001112 | %1.%2: 首次成功地按文件 ID 打开了 %3,但是第二次未能成功。未在文件 %4 上尝试执行任何恢复操作。这是一个内部错误。 |
%1.%2: %3 was opened by File ID successfully the first time but not the second time. No recovery operation was tried on file %4. This is an internal error. |
0xB0001113 | %1.%2: EFS 恢复服务无法获取备份文件名。可能已恢复中断的加密/解密操作(在文件 %3 上)。将不删除临时备份文件 %4。如果恢复操作成功完成,则用户应删除该备份文件。 |
%1.%2: EFS recovery service cannot get the backup file name. The interrupted encryption/decryption operation (on file %3) may be recovered. The temporary backup file %4 is not deleted. User should delete the backup file if the recovery operation is done successfully. |
0xB0001114 | %1.%2: 无法打开 %3。未恢复 %4。 |
%1.%2: %3 could not be opened. %4 was not recovered. |
0xB0001115 | %1.%2: 无法从 %3 获取流信息。未恢复 %4。 |
%1.%2: Stream Information could not be got from %3. %4 was not recovered. |
0xB0001116 | %1.%2: EFS 服务无法打开文件 %3 上的所有流。未恢复 %4。 |
%1.%2: EFS service could not open all the streams on file %3. %4 was not recovered. |
0xB0001117 | %1.%2: EFS 服务收到登录通知。 |
%1.%2: EFS Service received logon notification. |
0xB0001119 | %1.%2: 已清除用户缓存项。引用计数: %3。 |
%1.%2: User cache entry purged. Reference count: %3. |
0xB000111A | %1.%2: 已清除所有用户缓存项。引用计数: %3。 |
%1.%2: All user cache entries purged. Reference count: %3. |
0xB0001127 | 加密文件系统服务器已准备接受调用。 |
Encrypting File System server ready to accept calls. |
0xB0001135 | %1.%2: 启动: %3。 |
%1.%2: Start: %3. |
0xB0001136 | %1.%2: 完成: %3。代码: %4。 |
%1.%2: Complete: %3. Code: %4. |
0xB0001137 | %1.%2: 错误代码: %3。 |
%1.%2: Error Code: %3. |
0xB0001138 | %1.%2: 状态代码: %3。 |
%1.%2: Status Code: %3. |
0xB0001139 | %1.%2: 输入: %3。 |
%1.%2: Enter: %3. |
0xB000113A | %1.%2: 离开: %3。 |
%1.%2: Leave: %3. |
0xB000113B | %1.%2: 离开: %3。代码: %4。 |
%1.%2: Leave: %3. Code: %4. |
0xB000113C | %1.%2: 错误: %3。代码: %4。 |
%1.%2: Error: %3. Code: %4. |
0xB000113D | %1.%2: 警告: %3。代码: %4。 |
%1.%2: Warning: %3. Code: %4. |
0xB000113E | %1.%2: %3。代码: %4。 |
%1.%2: %3. Code: %4. |
0xB000113F | %1.%2: %3。值: %4。 |
%1.%2: %3. Value: %4. |