sdiagprv.dll.mui Windows Scripted Diagnostic Provider API 1d79fb8049e55af1c89a870b281df9ba

File info

File name: sdiagprv.dll.mui
Size: 19456 byte
MD5: 1d79fb8049e55af1c89a870b281df9ba
SHA1: 6d7ff1da193d29eb6041c345be9cc1ed0e70b6d3
SHA256: 05028c7215a5619bbcc2b61afd0d9b7cf71eacbd728cf1bd313c60dd6a979d23
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in English (U.S.) 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 English (U.S.) English
101Windows Scripted Diagnostic Provider Library for discovering scripted diagnostic content packages. Windows Scripted Diagnostic Provider Library for discovering scripted diagnostic content packages.
0x10000009Search Search
0x1000000ACancel Cancel
0x1000000BErrors Errors
0x1000000CObject Object
0x30000001Start Start
0x30000002Stop Stop
0x50000002Error Error
0x50000003Warning Warning
0x50000004Information Information
0x50000005Verbose Verbose
0x90000001Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider
0x90000002Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider/Operational Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider/Operational
0x90000003Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider/Debug Microsoft-Windows-Diagnosis-ScriptedDiagnosticsProvider/Debug
0xB00003E8The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method succeeded. The input Culture/Locale was %1. The size of the result set was %2. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method succeeded. The input Culture/Locale was %1. The size of the result set was %2.
0xB00003E9The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the system ran out of memory. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the system ran out of memory.
0xB00003EAThe Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method was canceled by the caller. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method was canceled by the caller.
0xB00003EBThe Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed with error (%1). The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed with error (%1).
0xB00003ECThe Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed. The input Culture/Locale, %1, is not a valid Language identifier. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed. The input Culture/Locale, %1, is not a valid Language identifier.
0xB00003F2The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method succeeded. The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method succeeded.
0xB00003F3The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method failed with error (%1). The Windows Scripted Diagnostic Provider API IDiagnosticProvider Cancel method failed with error (%1).
0xB00003F4The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the connected diagnostic provider with error (%1). The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the connected diagnostic provider with error (%1).
0xB00003F5The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the local diagnostic provider with error (%1). The Windows Scripted Diagnostic Provider API IDiagnosticProvider failed to cancel the local diagnostic provider with error (%1).
0xB00003F7The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by Group Policy. The property will be interpreted as being set to VARIANT_FALSE. The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by Group Policy. The property will be interpreted as being set to VARIANT_FALSE.
0xB00003F8The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by the Administrator through a System Wide Preference. The property will be interpreted as being set to VARIANT_FALSE. The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is being overridden by the Administrator through a System Wide Preference. The property will be interpreted as being set to VARIANT_FALSE.
0xB00003F9The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is set to %1. The Windows Scripted Diagnostic Provider API IDiagnosticProvider object property QueryRemoteServer is set to %1.
0xB00003FAThe Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the input IDiagnosticMetadataCollection object was empty. The Windows Scripted Diagnostic Provider API IDiagnosticProvider FindDiagnosticsBySearchMetadata method failed because the input IDiagnosticMetadataCollection object was empty.
0xB00007D0The diagnostic package index information was successfully loaded from %1. The diagnostic package index information was successfully loaded from %1.
0xB00007D1Failed to scan diagnostic package index information from %2, with error (%1). Failed to scan diagnostic package index information from %2, with error (%1).
0xB00007D2Failed to load the resource (%2;%3) with error code (%1). Failed to load the resource (%2;%3) with error code (%1).
0xB0000BB8Sending request to the remote server %1 at the URL path %2. Contents of the request are: %3. Sending request to the remote server %1 at the URL path %2. Contents of the request are: %3.
0xB0000BB9Failed to connect to the remote server %1 at the URL path %2 due to lack of network access. Failed to connect to the remote server %1 at the URL path %2 due to lack of network access.
0xB0000BBAFailed to connect to the remote server %1 at the URL path %2 with error %3. Failed to connect to the remote server %1 at the URL path %2 with error %3.
0xB0000BBBTimed out while communicating with the remote server %1 at the URL path %2. Timed out while communicating with the remote server %1 at the URL path %2.
0xB0000BBCTimed out waiting for a response from the remote server %1 at the URL path %2. Timed out waiting for a response from the remote server %1 at the URL path %2.
0xB0000BBDResponse from the remote server %1 at the URL path %2 returned the following error response code: %3. Response from the remote server %1 at the URL path %2 returned the following error response code: %3.
0xB0000BBEReceived response from the remote server %1 at the URL path %2. Received response from the remote server %1 at the URL path %2.
0xB0000BBFParsed valid response from the remote server %1 at the URL path %2. Parsed valid response from the remote server %1 at the URL path %2.
0xB0000BC0Response received from the remote server %1 at the URL path %2 is invalid for the following reason: %3. Response received from the remote server %1 at the URL path %2 is invalid for the following reason: %3.
0xB0000BC1Response received from the remote server %1 at the URL path %2 is malformed. Response received from the remote server %1 at the URL path %2 is malformed.
0xB0000BC2Attempting to send data to remote server using the following proxy configuration: Access Type (%1); Proxy Server (%2); Proxy Bypass Server (%3). Attempting to send data to remote server using the following proxy configuration: Access Type (%1); Proxy Server (%2); Proxy Bypass Server (%3).
0xB0000BC3Failed to send data to remote server using the following proxy configuration: Access Type (%2); Proxy Server (%3); Proxy Bypass Server (%4) because of proxy failure (%1). Failed to send data to remote server using the following proxy configuration: Access Type (%2); Proxy Server (%3); Proxy Bypass Server (%4) because of proxy failure (%1).
0xB0000BC4Failed to send data to remote server because list of proxy servers was exhausted without receiving a response. The error code returned to caller is %1. Failed to send data to remote server because list of proxy servers was exhausted without receiving a response. The error code returned to caller is %1.
0xB0000BC5Connection to remote server has been reset or terminated while waiting for a response. The error code returned to the caller is %1. Connection to remote server has been reset or terminated while waiting for a response. The error code returned to the caller is %1.
0xB0000BC6The following system configuration will be used when querying content providers: OS Major Version (%1); OS Minor Version (%2); Service Pack Major (%3); Service Pack Minor (%4); Build Number (%5); Product Type (%6); Processor Architecture (%7); Culture (%8); System Type (%9); OEM (%10); Model (%11); IsMobilePc (%12); IsInternal (%13); GeoId (%14); Family (%15); OEM SKU (%16); Version (%17); Base Board OEM (%18); Base Board Model (%19); Base Board Version (%20); BIOS Vendor (%21); BIOS Version (%22); BIOS Release Date (%23); BIOS Major Release (%24); BIOS Minor Release (%25); Embedded Controller Firmware Major Release (%26); Embedded Controller Firmware Minor Release (%27). The following system configuration will be used when querying content providers: OS Major Version (%1); OS Minor Version (%2); Service Pack Major (%3); Service Pack Minor (%4); Build Number (%5); Product Type (%6); Processor Architecture (%7); Culture (%8); System Type (%9); OEM (%10); Model (%11); IsMobilePc (%12); IsInternal (%13); GeoId (%14); Family (%15); OEM SKU (%16); Version (%17); Base Board OEM (%18); Base Board Model (%19); Base Board Version (%20); BIOS Vendor (%21); BIOS Version (%22); BIOS Release Date (%23); BIOS Major Release (%24); BIOS Minor Release (%25); Embedded Controller Firmware Major Release (%26); Embedded Controller Firmware Minor Release (%27).
0xB0000FA0Starting to scan diagnostic package index information from %1. Starting to scan diagnostic package index information from %1.
0xB0000FA1Finished scanning diagnostic package index information from %1. Finished scanning diagnostic package index information from %1.
0xB0000FA6Starting to query content providers for scripted diagnostic content packages. Starting to query content providers for scripted diagnostic content packages.
0xB0000FA7Finished querying content providers for scripted diagnostic content packages with error code (%1). Finished querying content providers for scripted diagnostic content packages with error code (%1).
0xB0000FA8Starting to cancel content providers. Starting to cancel content providers.
0xB0000FA9Finished cancelling content providers with error code (%1). Finished cancelling content providers with error code (%1).
0xB0000FAAStarting to cancel local content provider. Starting to cancel local content provider.
0xB0000FABFinished cancelling local content provider with error code (%1). Finished cancelling local content provider with error code (%1).
0xB0000FACStarting to cancel remote content provider. Starting to cancel remote content provider.
0xB0000FADFinished cancelling remove content provider with error code (%1). Finished cancelling remove content provider with error code (%1).
0xB0000FAEStarting to gather system configuration necessary for scripted diagnostic content package query. Starting to gather system configuration necessary for scripted diagnostic content package query.
0xB0000FAFFinished gathering system configuration necessary for scripted diagnostic content package query with error code (%1). Finished gathering system configuration necessary for scripted diagnostic content package query with error code (%1).
0xB0000FB0Started to connect to remote server %1 using URL path %2. Started to connect to remote server %1 using URL path %2.
0xB0000FB1Finished connecting to remote server %1 using URL path %2. The operation completed with error %3. Finished connecting to remote server %1 using URL path %2. The operation completed with error %3.
0xB0000FB2Sending POST request to the remote server %1 using the URL path: %2 with request body: %3. Sending POST request to the remote server %1 using the URL path: %2 with request body: %3.
0xB0000FB3Response received from remote server. The HTTP response was %1. The operation completed with error %2. Response received from remote server. The HTTP response was %1. The operation completed with error %2.
0xB0000FB4Starting to parse response from the remote server %1 POST request to the URL path: %2 with request body: %3. Starting to parse response from the remote server %1 POST request to the URL path: %2 with request body: %3.
0xB0000FB5Finished parsing response from the remote server %1 POST request to the URL path: %2 with request body: %3 with error %4. Finished parsing response from the remote server %1 POST request to the URL path: %2 with request body: %3 with error %4.
0xB0000FB6Starting to acquire lock in function %1. Starting to acquire lock in function %1.
0xB0000FB7Finished acquiring lock in function %1. Finished acquiring lock in function %1.
0xB0000FB8Starting to add result to Diagnostic Collection. Starting to add result to Diagnostic Collection.
0xB0000FB9Finished adding result to Diagnostic Collection with error code (%1). Finished adding result to Diagnostic Collection with error code (%1).
0xB0000FBAStarting to load resource from %1. Starting to load resource from %1.
0xB0000FBBFinished loading resource from %1. Finished loading resource from %1.
0xB0001388%1 succeeded. %1 succeeded.
0xB0001389%1 succeeded. The corresponding object property was set to %2. %1 succeeded. The corresponding object property was set to %2.
0xB000138D%1 succeeded. The output parameter was set to %2. %1 succeeded. The output parameter was set to %2.
0xB0001392%1 failed because the system ran out of memory. %1 failed because the system ran out of memory.
0xB0001393%1 failed with error (%2) because the input parameter, %3, was NULL. %1 failed with error (%2) because the input parameter, %3, was NULL.
0xB0001394%1 failed with error (%2). %1 failed with error (%2).
0xB0001395%1 succeeded. The output parameter was set to the item in the collection at index %2. %1 succeeded. The output parameter was set to the item in the collection at index %2.
0xB0001396%1 failed with error (%2) because the index, %3, is out of bounds of the enumeration or the enumeration is empty. %1 failed with error (%2) because the index, %3, is out of bounds of the enumeration or the enumeration is empty.
0xB0001397%1 succeeded. The object was added to the collection at index %2. The new size of the collection is %3. %1 succeeded. The object was added to the collection at index %2. The new size of the collection is %3.
0xB0001398%1 failed with error (%2) because the collection already contains an object of type, %3, with value, %4. %1 failed with error (%2) because the collection already contains an object of type, %3, with value, %4.
0xB0001399%1 succeeded. The size of the collection increased by %2 object(s). The new size of the collection is %3. %1 succeeded. The size of the collection increased by %2 object(s). The new size of the collection is %3.
0xB000139A%1 failed with error (%2) because the collection already contains an object of with identifier, %3, and publisher, %4, with a greater version (%5). %1 failed with error (%2) because the collection already contains an object of with identifier, %3, and publisher, %4, with a greater version (%5).
0xB000139BLocal Content Diagnostic Provider search parameter: %1 has value: %2. Local Content Diagnostic Provider search parameter: %1 has value: %2.
0xB000139CSearch Result includes a diagnostic with the following identifier %1. The publisher of the Diagnostic is %2. The version of the Diagnostic is %3. The URL for the diagnostic is: %4. Search Result includes a diagnostic with the following identifier %1. The publisher of the Diagnostic is %2. The version of the Diagnostic is %3. The URL for the diagnostic is: %4.
0xB000139DDeserializing diagnostic from index file %2 failed with error code (%1) because the XML does not represent a valid Diagnostic. Deserializing diagnostic from index file %2 failed with error code (%1) because the XML does not represent a valid Diagnostic.
0xB00013A2Deserializing diagnostic failed index file %2 with error code (%1) because the XML does not contain valid XML. Deserializing diagnostic failed index file %2 with error code (%1) because the XML does not contain valid XML.
0xD0000001culture culture
0xD0000002id id
0xD0000003category category
0xD0000004keyword keyword

EXIF

File Name:sdiagprv.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-s..r-library.resources_31bf3856ad364e35_10.0.15063.0_en-us_1855deb084a06b60\
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:Dynamic link library
File Subtype:0
Language Code:English (U.S.)
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:Windows Scripted Diagnostic Provider API
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:SDIAGPRV.DLL
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:SDIAGPRV.DLL.MUI
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Directory:%WINDIR%\WinSxS\x86_microsoft-windows-s..r-library.resources_31bf3856ad364e35_10.0.15063.0_en-us_bc37432ccc42fa2a\

What is sdiagprv.dll.mui?

sdiagprv.dll.mui is Multilingual User Interface resource file that contain English (U.S.) language for file sdiagprv.dll (Windows Scripted Diagnostic Provider API).

File version info

File Description:Windows Scripted Diagnostic Provider API
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:SDIAGPRV.DLL
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:SDIAGPRV.DLL.MUI
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x409, 1200