WWAHost.exe ‎‎میزبان Microsoft WWA a1421b51d61a0807b971fc7d33c1538d

File info

File name: WWAHost.exe.mui
Size: 19456 byte
MD5: a1421b51d61a0807b971fc7d33c1538d
SHA1: 9d0102b16f32c47bd913b3efeaec5f5f8d711593
SHA256: 93f4119613af293a5c629c505a4f8ca4ee10784b07d185cd019ddc230cd38438
Operating systems: Windows 10
Extension: MUI
In x64: WWAHost.exe ‎‎میزبان Microsoft WWA ‏(32-بیت)‎

Translations messages and strings

If an error occurred or the following message in Farsi language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id Farsi English
700‏‏امکان بارگذاری وجود ندارد. یک برنامه قادر نیست محتوای وب راه دور را در مفاد محلی بارگذاری کند. Can’t load . An app can’t load remote web content in the local context.
701'javascript:' is an invalid attribute value and will be ignored. Don’t use 'javascript:' URIs in the local context. 'javascript:' is an invalid attribute value and will be ignored. Don’t use 'javascript:' URIs in the local context.
702Can’t load the ActiveX plug-in that has the class ID '%1!s!'. Apps can't load ActiveX controls. Can’t load the ActiveX plug-in that has the class ID '%1!s!'. Apps can't load ActiveX controls.
703Can’t navigate to because it uses an invalid character encoding. An app can navigate only to UTF8-encoded files. Can’t navigate to because it uses an invalid character encoding. An app can navigate only to UTF8-encoded files.
704Can’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. 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.
705Can’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. 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.
706Invalid 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. 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.
707The app can't launch the URI at %1!s! because of this error: %2!d!. The app can't launch the URI at %1!s! because of this error: %2!d!.
708The app couldn’t navigate to the about:blank page because of this error: %1!d!. The app couldn’t navigate to the about:blank page because of this error: %1!d!.
710The app found an error while preparing to navigate to a custom error page: %1!d!. The app found an error while preparing to navigate to a custom error page: %1!d!.
711The app couldn’t navigate to a custom error page because of this error: %1!d!. The app couldn’t navigate to a custom error page because of this error: %1!d!.
713The app couldn’t navigate to %1!s! because of this error: %2!s!. The app couldn’t navigate to %1!s! because of this error: %2!s!.
714The 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. 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.
715This 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. 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.
716This 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. 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.
717This 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. 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.
718The app can’t download the file at because it was invoked programmatically outside of the local context. The app can’t download the file at because it was invoked programmatically outside of the local context.
719The 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. 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.
720This 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. 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.
721The app couldn’t resolve %1!s! because of this error: %2!s!. The app couldn’t resolve %1!s! because of this error: %2!s!.
722App unhandled script exception App unhandled script exception
723The 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. 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.
724The 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. 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.
725The app was unable to navigate the top-level document to %s because of the following error: %s. The app was unable to navigate the top-level document to %s because of the following error: %s.
726The 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. 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 برای این برنامه شامل نشده است پیمایش کند. به جای آن، از یک عنصر x-ms-webview برای مشاهده URI استفاده کنید، یا URI موردنظر را به قسمت ApplicationContentUriRules اظهارنامه بسته اضافه کنید تا iframe موردنظر بتواند به آن مکان پیمایش نماید. (در Visual Studio، این URI را به زبانه «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.)
728The app was unable to navigate an iframe to %s because of the following error: %s. The app was unable to navigate an iframe to %s because of the following error: %s.
729A direct reference to resource file %1!s! was detected. This reference causes failures when used outside of the debugging environment. A direct reference to resource file %1!s! was detected. This reference causes failures when used outside of the debugging environment.
730‏‏برنامه به رفت که دارای یک فرابرچسب تأیید هویت بدشکل است: %2!s! The app navigated to which contains a malformed authentication meta tag: %2!s!
731‏‏این URI نمی تواند از APIهای قفل نشانگر استفاده کند. APIهای قفل نشانگر را می توان فقط از URI فراخواند که بخشی از بسته است یا در عنصر ApplicationContentUris بیانیه آمده است. 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.
733‏‏URI %1!s! نیم تواند پنجره سطح بالایی برنامه را ببندد. پنجره های سطح بالایی که بخشی از بسته هستند یا در عنصر ApplicationContentUris بیانیه آمده اند را فقط می توان از URIهایی بست که هم بخشی از بسته هستند و هم در ApplicationContentUris بیانیه آمده اند. 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 نمی‌تواند از API های اعلان وب استفاده کند. API های اعلان وب را فقط می‌توان از URI که خود بخشی از بسته باشد یا در عنصر ApplicationContentUris از مانیفست قرار گرفته باشد، دریافت کرد. 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
0x10000001AppHost AppHost
0x10000002AppHostApplication AppHostApplication
0x10000003AppHostDiagnostic AppHostDiagnostic
0x10000031Response Time Response Time
0x30000000Info Info
0x30000001Start Start
0x30000002Stop Stop
0x3000000BAppHost Operation Succeeded AppHost Operation Succeeded
0x3000000CAppHost Operation Failed AppHost Operation Failed
0x3000000DAppHost Warning AppHost Warning
0x3000000EAppHost Information AppHost Information
0x3000000FAppHost Application Error AppHost Application Error
0x30000010AppHost Application Warning AppHost Application Warning
0x30000011AppHost Application Information AppHost Application Information
0x50000002Error Error
0x50000003Warning Warning
0x50000004Information Information
0x90000001Microsoft-Windows-AppHost Microsoft-Windows-AppHost
0x90000002Admin Admin
0x90000003AppTracing AppTracing
0xB0000066The App Host has encountered an unexpected error and will terminate. The error is %1. The App Host has encountered an unexpected error and will terminate. The error is %1.
0xB0000070WWAJSE report submitted with parameters 1: 2: 3: 4: 5: 6: . (PID: . Process Creation Time: . App Binary Path: .) Report Id: WWAJSE report submitted with parameters 1: 2: 3: 4: 5: 6: . (PID: . Process Creation Time: . App Binary Path: .) Report Id:
0xB0000079The 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. 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.
0xB000007AThe App Host failed to enumerate WinRT namespaces due to unknown error. (%1) The App Host failed to enumerate WinRT namespaces due to unknown error. (%1)
0xB000007EApp 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. 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.
0xB000007FApp 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. 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.
0xB0000080This app was closed because of a critical infrastructure failure. This app was closed because of a critical infrastructure failure.
0xB0000081This app was closed because one or more packages were modified. Please reinstall the app. This app was closed because one or more packages were modified. Please reinstall the app.
0xB0000083App 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: 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:
0xB0000084App 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: 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:
0xB0000085The App Host could not start because the host module %2::%1 failed with %3. The App Host could not start because the host module %2::%1 failed with %3.
0xB0000086The App Host could not start because the web module %3::%2::%1 failed with %4. The App Host could not start because the web module %3::%2::%1 failed with %4.
0xB0000087The App Host could not start because the platform (%1) failed with %2. The App Host could not start because the platform (%1) failed with %2.
0xB0000088The App Host could not start because WinRT failed to initialize with %1. The App Host could not start because WinRT failed to initialize with %1.
0xB0000089Pending resume event was signaled to the Host. Pending resume event was signaled to the Host.
0xB0000203The App has subdownloads remaining to complete during suspension. Host has requested the system for more time. The App has subdownloads remaining to complete during suspension. Host has requested the system for more time.
0xB0002710%6%10 : %11 %6%10 : %11
0xB0002713Suspending Deferral Increment. Suspending Deferral Increment.
0xB0002714Suspending Deferral Decrement. Suspending Deferral Decrement.

EXIF

File Name:WWAHost.exe.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.15063.0_fa-ir_4c9bbf5b9263498b\
File Size:19 kB
File Permissions:rw-rw-rw-
File Type:Win32 DLL
File Type Extension:dll
MIME Type:application/octet-stream
Machine Type:Intel 386 or later, and compatibles
Time Stamp:0000:00:00 00:00:00
PE Type:PE32
Linker Version:14.10
Code Size:0
Initialized Data Size:18944
Uninitialized Data Size:0
Entry Point:0x0000
OS Version:10.0
Image Version:10.0
Subsystem Version:6.0
Subsystem:Windows GUI
File Version Number:10.0.15063.0
Product Version Number:10.0.15063.0
File Flags Mask:0x003f
File Flags:(none)
File OS:Windows NT 32-bit
Object File Type:Executable application
File Subtype:0
Language Code:Farsi
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:‎‎میزبان Microsoft WWA
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:WWAHost
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:WWAHost.exe.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Directory:%WINDIR%\WinSxS\wow64_microsoft-windows-web-app-host.resources_31bf3856ad364e35_10.0.15063.0_fa-ir_56f069adc6c40b86\

What is WWAHost.exe.mui?

WWAHost.exe.mui is Multilingual User Interface resource file that contain Farsi language for file WWAHost.exe (‎‎میزبان Microsoft WWA).

File version info

File Description:‎‎میزبان Microsoft WWA
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:WWAHost
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:WWAHost.exe.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x429, 1200