700 | 无法加载 。应用无法在本地上下文中加载远程 Web 内容。 |
Can’t load . An app can’t load remote web content in the local context. |
701 | "javascript:" 是无效属性值,将被忽略。请不要在本地上下文中使用 "javascript:" URI。 |
'javascript:' is an invalid attribute value and will be ignored. Don’t use 'javascript:' URIs in the local context. |
702 | 无法加载类 ID 为“%1!s!”的 ActiveX 插件。应用无法加载 ActiveX 控件。 |
Can’t load the ActiveX plug-in that has the class ID '%1!s!'. Apps can't load ActiveX controls. |
703 | 无法导航到 ,因为它使用无效的字符编码。应用只能导航到 UTF8 编码的文件。 |
Can’t navigate to because it uses an invalid character encoding. An app can navigate only to UTF8-encoded files. |
704 | 无法从 导航到 ,原因是目标 URI 位于安全性更高的区域。你无法从安全性较低的区域导航到安全性较高的区域,除非你正在从 Web 上下文 URI 导航到本地上下文 URI,并且已经使用 MSApp.addPublicLocalApplicationUri 方法注册过本地上下文 URI。 |
Can’t navigate to from because the destination URI is in a higher security zone. You can’t navigate from a zone with lower security to a zone with higher security unless you’re navigating to a local context URI from a web context URI and you’ve registered the local context URI with the MSApp.addPublicLocalApplicationUri method. |
705 | 无法加载 ,因为它使用 HTTP 连接,且存在 ms-https-connections-only 图元元素。仅当使用 ms-https-connections-only 图元元素时才允许 HTTPS 连接。请使用 HTTPS 连接,如果不需要安全连接,请删除此图元元素。 |
Can’t load because it uses an HTTP connection and the ms-https-connections-only meta element is present. Only HTTPS connections are allowed when you use the ms-https-connections-only meta element. Use an HTTPS connection or, if you don’t need a secure connection, remove the meta element. |
706 | 无效的 doc 模式。某个 iframe 中的文档请求 doc 模式,但系统强制 doc 模式。此 iframe 将使用 doc 模式。 |
Invalid doc mode. A document within an iframe requested the doc mode, but the system enforces the doc mode. The iframe will use the doc mode. |
707 | 由于此错误,应用无法启动 %1!s! 上的 URI: %2!d!。 |
The app can't launch the URI at %1!s! because of this error: %2!d!. |
708 | 由于此错误,应用无法导航到 about:blank 页面: %1!d!。 |
The app couldn’t navigate to the about:blank page because of this error: %1!d!. |
710 | 应用在准备导航到自定义错误页面 %1!d! 时发现错误。 |
The app found an error while preparing to navigate to a custom error page: %1!d!. |
711 | 由于此错误,应用无法导航到自定义错误页面: %1!d!。 |
The app couldn’t navigate to a custom error page because of this error: %1!d!. |
713 | 由于此错误,应用无法导航到 %1!s!: %2!s!。 |
The app couldn’t navigate to %1!s! because of this error: %2!s!. |
714 | 顶级文档请求 doc 模式,但系统强制 doc 模式。应用将使用 doc 模式显示文档。 |
The top level document requested the doc mode, but the system enforces the doc mode. The app will use the doc mode to display the document. |
715 | 此 URI 无法使用地理位置 API。只能从属于程序包的 URI 或包含在清单的 ApplicationContentUris 元素中的 URI 调用地理位置 API。 |
This URI can’t use geolocation APIs. Geolocation APIs can be invoked only from a URI that is part of the package or is included in the ApplicationContentUris element of the manifest. |
716 | 此 URI 无法使用剪贴板 API。只能从属于程序包的 URI 或包含在清单的 ApplicationContentUris 元素中的 URI 调用剪贴板 API。 |
This URI can’t use clipboard APIs. The clipboard APIs can be invoked only from a URI that is part of the package or is included in the ApplicationContentUris element of the manifest. |
717 | 此 URI 无法使用 window.close。只能从使用 ms-appx URI 方案加载的打包内容中调用 window.close 方法。 |
This URI can’t use window.close. The window.close method can be invoked only from packaged content that was loaded with an ms-appx URI scheme. |
718 | 应用无法在 上下载此文件,因为它是在本地上下文以外通过编程方式调用的。 |
The app can’t download the file at because it was invoked programmatically outside of the local context. |
719 | 应用无法导航到 %1!s!,因为 Web 上下文中的页面不能是应用的顶级文档。请加载 iframe 中的页面。 |
The app can't navigate to %1!s! because a page in the web context can't be the app's top level document. Load the page in an iframe instead. |
720 | 此应用已关闭,因为它使用 HTTP 连接并且存在 ms-https-connections-only 图元元素。当使用 ms-https-connections-only 图元元素时仅允许使用 HTTPS 连接。请使用 HTTPS 连接,如果不需要安全连接,请删除此图元元素。 |
This app was closed because it used an HTTP connection and the ms-https-connections-only meta element is present. Only HTTPS connections are allowed when you use the ms-https-connections-only meta element. Use an HTTPS connection or, if you don’t require a secure connection, remove the meta element. |
721 | 由于此错误,应用无法解析 %1!s!: %2!s!。 |
The app couldn’t resolve %1!s! because of this error: %2!s!. |
722 | 应用未经处理的脚本异常 |
App unhandled script exception |
723 | 应用无法使用脚本加载 %1!s! url,因为此 url 启动另一个应用。只有直接用户交互才能启动另一个应用。 |
The app can’t use script to load the %1!s! url because the url launches another app. Only direct user interaction can launch another app. |
724 | 应用使用 window.close 方法来终止。通常,由用户来终止此应用。当由于错误而需要终止此应用时,请使用 MSApp.terminateApp。 |
The app used the window.close method to terminate. In general, let the user terminate the app. When you need to terminate the app because of a critical error, use MSApp.terminateApp. |
725 | 由于以下错误,应用无法将顶级文档导航到 %s: %s。 |
The app was unable to navigate the top-level document to %s because of the following error: %s. |
726 | 由于以下错误,应用无法将 iframe 导航到 %s: %s。若要处理导航错误,我们建议在程序包的根目录中包括一个名为 msapp-error.html 的文件。在 iframe 中发生导航错误时,应用将导航到 msapp-error.html 页面,并将错误详细信息作为查询字符串参数传递。 |
The app was unable to navigate an iframe to %s because of the following error: %s. To handle navigation errors, we recommend including a file named msapp-error.html in the root of the package. When a navigation error occurs in an iframe, the app navigates to the msapp-error.html page and passes the error details as query string parameters. |
727 | 无法导航到: '%1!s!'。iframe 尝试导航到一个 URI,但此应用的 ApplicationContentUriRules 中未包含该 URI。请使用 x-ms-webview 元素查看该 URI,或者将该 URI 添加到程序包清单的 ApplicationContentUriRules 部分,以便 iframe 能导航到该 URI。(在 Visual Studio 中,将此 URI 添加到 Manifest Designer 的内容 URI 选项卡中。) |
Unable to navigate to: '%1!s!'. An iframe attempted to navigate to a URI that is not included in the ApplicationContentUriRules for this app. Use a x-ms-webview element to view the URI instead, or add the URI to the ApplicationContentUriRules section of the package manifest so that the iframe can navigate to it. (In Visual Studio, add this URI to the Content URIs tab of the Manifest Designer.) |
728 | 由于出现以下错误,该应用无法将 iframe 导航到 %s: %s。 |
The app was unable to navigate an iframe to %s because of the following error: %s. |
729 | 已检测到对资源文件 %1!s! 的直接引用。在调试环境外部使用时,此引用将导致失败。 |
A direct reference to resource file %1!s! was detected. This reference causes failures when used outside of the debugging environment. |
730 | 应用所导航到的 包含格式不正确的身份验证 meta 标记: %2!s! |
The app navigated to which contains a malformed authentication meta tag: %2!s! |
731 | 此 URI 不能使用指针锁定 API。指针锁定 API 只能从属于程序包或包含在清单的 ApplicationContentUris 元素中的 URI 调用。 |
This URI can’t use pointerlock APIs. Pointerlock APIs can be invoked only from a URI that is part of the package or is included in the ApplicationContentUris element of the manifest. |
732 | 此 URI 不能使用媒体捕获 API。媒体捕获 API 只能从属于程序包或包含在清单的 ApplicationContentUris 元素中的 URI 调用。 |
This URI can’t use media capture APIs. Media Capture APIs can be invoked only from a URI that is part of the package or is included in the ApplicationContentUris element of the manifest. |
733 | URI %1!s! 无法关闭应用程序顶级窗口。属于程序包或包含在清单的 ApplicationContentUris 元素中的顶级窗口只能通过也属于程序包或包含在清单的 ApplicationContentUris 中的 URI 关闭。 |
The URI %1!s! can’t close the application top level window. Top level windows that are part of package or are included in ApplicationContentUris element of the manifest can only be closed from URIs that are also either part of package or are included in ApplicationContentUris of manifest. |
734 | 此 URI 不能使用 Web 通知 API。Web 通知 API 只能从属于程序包或包含在清单的 ApplicationContentUris 元素中的 URI 调用。 |
This URI can’t use Web Notification APIs. Web Notification APIs can be invoked only from a URI that is part of the package or is included in the ApplicationContentUris element of the manifest. |
1701 | 复制 |
Copy |
1702 | 剪切 |
Cut |
1703 | 撤消 |
Undo |
1704 | 粘贴 |
Paste |
1705 | 全选 |
Select all |
0x10000001 | AppHost |
AppHost |
0x10000002 | AppHost 应用程序 |
AppHostApplication |
0x10000003 | AppHostDiagnostic |
AppHostDiagnostic |
0x10000031 | 响应时间 |
Response Time |
0x30000000 | 信息 |
Info |
0x30000001 | 开始 |
Start |
0x30000002 | 停止 |
Stop |
0x3000000B | AppHost 操作成功 |
AppHost Operation Succeeded |
0x3000000C | AppHost 操作失败 |
AppHost Operation Failed |
0x3000000D | AppHost 警告 |
AppHost Warning |
0x3000000E | AppHost 信息 |
AppHost Information |
0x3000000F | AppHost 应用程序错误 |
AppHost Application Error |
0x30000010 | AppHost 应用程序警告 |
AppHost Application Warning |
0x30000011 | AppHost 应用程序信息 |
AppHost Application Information |
0x50000002 | 错误 |
Error |
0x50000003 | 警告 |
Warning |
0x90000001 | Microsoft-Windows-AppHost |
Microsoft-Windows-AppHost |
0x90000002 | Admin |
Admin |
0x90000003 | AppTracing |
AppTracing |
0xB0000066 | 应用托管进程遇到意外错误,因此将终止。错误为 %1。 |
The App Host has encountered an unexpected error and will terminate. The error is %1. |
0xB0000070 | 已使用下列参数提交 WWAJSE 报告 1: 2: 3: 4: 5: 6: 。(PID: 。进程创建时间: 。应用二进制路径: 。) 报告 ID: |
WWAJSE report submitted with parameters 1: 2: 3: 4: 5: 6: . (PID: . Process Creation Time: . App Binary Path: .) Report Id: |
0xB0000079 | 由于 winmd 文件出现问题,应用托管进程无法枚举 WinRT 命名空间。如果你有第三方 winmd 文件,请确保这些文件未损坏并且其文件名与其相应的命名空间名称匹配。 |
The App Host failed to enumerate WinRT namespaces due to an issue with a winmd file. If you have third party winmd files ensure they are not corrupt and that their filenames match their corresponding namespace names. |
0xB000007A | 由于未知错误,应用托管进程无法枚举 WinRT 命名空间。(%1) |
The App Host failed to enumerate WinRT namespaces due to unknown error. (%1) |
0xB000007E | 应用 崩溃,具有未经处理的 Javascript 异常。应用详细信息如下: 显示名称:,AppUserModelId: 程序包标识符: PID:。JavaScript 异常的详细信息如下: 异常名称:,描述:,HTML 文档路径:,源文件名:,源行号:,源列号:,堆栈跟踪: %12。 |
App crashed with an unhandled Javascript exception. App details are as follows: Display Name:, AppUserModelId: Package Identity: PID:. The details of the JavaScript exception are as follows Exception Name:, Description:, HTML Document Path:, Source File Name:, Source Line Number:, Source Column Number:, and Stack Trace: %12. |
0xB000007F | 应用 通过调用 terminateApp API 来终止自己。应用详细信息如下: 显示名称:,AppUserModelId: 程序包标识符: PID:。API 是从以下 HTML 文档的上下文中调用的: 。传递给 terminateApp 的错误对象包含以下详细信息: 描述:,以及堆栈跟踪:- %8。 |
App terminated itself by calling terminateApp API. App details are as follows: Display Name:, AppUserModelId: Package Identity: PID:. The API was called from the context of the following HTML document: . Error object passed to terminateApp carried the following details Description:, and Stack Trace:- %8. |
0xB0000080 | 此应用已关闭,因为出现关键基础结构故障。 |
This app was closed because of a critical infrastructure failure. |
0xB0000081 | 此应用已关闭,因为一个或多个程序包被修改。请重新安装此应用。 |
This app was closed because one or more packages were modified. Please reinstall the app. |
0xB0000083 | 应用 通过 window.close() API 来终止自己,但这不是建议的方式。应用详细信息如下: 显示名称:,AppUserModelId: 程序包标识符: PID:。此 API 是从以下 HTML 文档的上下文中调用的: |
App terminated itself by window.close() API, which is not recommended. App details are as follows: Display Name:, AppUserModelId: Package Identity: PID:. The API was called from the context of the following HTML document: |
0xB0000084 | 由于目标 URL 的导航发生错误,因此应用 已终止,错误代码为 。应用详细信息如下: 显示名称:,AppUserModelId: 程序包标识符: PID:。此导航操作是从以下 HTML 文档的上下文中发起的: |
App was terminated due to a navigation error with target url and error code . App details are as follows: Display Name:, AppUserModelId: Package Identity: PID:. The Navigation was initiated from the context of the following HTML document: |
0xB0000085 | 应用托管进程无法启动,因为主机模块 %2::%1 失败,错误代码为 %3。 |
The App Host could not start because the host module %2::%1 failed with %3. |
0xB0000086 | 应用托管进程无法启动,因为 Web 模块 %3::%2::%1 失败,错误代码为 %4。 |
The App Host could not start because the web module %3::%2::%1 failed with %4. |
0xB0000087 | 应用托管进程无法启动,因为平台(%1)失败,错误代码为 %2。 |
The App Host could not start because the platform (%1) failed with %2. |
0xB0000088 | 应用托管进程无法启动,因为 WinRT 无法初始化,错误代码为 %1。 |
The App Host could not start because WinRT failed to initialize with %1. |
0xB0000089 | 已向主机发出挂起恢复事件信号。 |
Pending resume event was signaled to the Host. |
0xB0000203 | 应用在挂起期间尚有剩余的子下载要完成。主机已请求系统分配更多时间。 |
The App has subdownloads remaining to complete during suspension. Host has requested the system for more time. |
0xB0002710 | %6%10 : %11 |
%6%10 : %11 |
0xB0002713 | 正在暂停延期增加。 |
Suspending Deferral Increment. |
0xB0002714 | 正在暂停延期减少。 |
Suspending Deferral Decrement. |