WinMgmtR.dll.mui WMI 517d632d70cb419ba9224acccede2352

File info

File name: WinMgmtR.dll.mui
Size: 31232 byte
MD5: 517d632d70cb419ba9224acccede2352
SHA1: f72ae872f9b2164a2e6bdf28fb79ba7aa98b56e1
SHA256: ef3d20f4f51c4a9c9a0f89c861ff3a39c531706f79274e883a4b144136f59e8c
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
0x4Error %1 encountered when trying to load MOF %2 while recovering .MOF file marked with autorecover. Error %1 encountered when trying to load MOF %2 while recovering .MOF file marked with autorecover.
0xAEvent filter with query \"%2\" could not be reactivated in namespace \"%1\" because of error %3. Events cannot be delivered through this filter until the problem is corrected. Event filter with query \"%2\" could not be reactivated in namespace \"%1\" because of error %3. Events cannot be delivered through this filter until the problem is corrected.
0x15Event provider %1 attempted to register a syntactically invalid query \"%2\". The query will be ignored. The query can be corrected by examining the WMI repository with CIM studio and updating the permanent subscriptions for the listed provider and query. If the permanent subscription is created with MOF file coming with an installed product, the application vendor must be contacted to correct the faulty registration. Event provider %1 attempted to register a syntactically invalid query \"%2\". The query will be ignored. The query can be corrected by examining the WMI repository with CIM studio and updating the permanent subscriptions for the listed provider and query. If the permanent subscription is created with MOF file coming with an installed product, the application vendor must be contacted to correct the faulty registration.
0x16Event provider %1 attempted to register an intrinsic event query \"%2\" in %3 namespace for which the set of target object classes could not be determined. The query will be ignored. Event provider %1 attempted to register an intrinsic event query \"%2\" in %3 namespace for which the set of target object classes could not be determined. The query will be ignored.
0x17Event provider %1 attempted to register query \"%2\" in %3 namespace which is too broad. Event providers cannot provide events that are provided by the system. The query will be ignored. Contact the application vendor. Event provider %1 attempted to register query \"%2\" in %3 namespace which is too broad. Event providers cannot provide events that are provided by the system. The query will be ignored. Contact the application vendor.
0x18Event provider %1 attempted to register query \"%2\" whose target class \"%3\" in %4 namespace does not exist. The query will be ignored. Event provider %1 attempted to register query \"%2\" whose target class \"%3\" in %4 namespace does not exist. The query will be ignored.
0x19Event provider %1 attempted to register query \"%2\" whose target class \"%3\" is not an event class. The query will be ignored. Contact the application vendor. Event provider %1 attempted to register query \"%2\" whose target class \"%3\" is not an event class. The query will be ignored. Contact the application vendor.
0x1CFailed to Initialize WMI Core or Provider SubSystem or Event SubSystem with error number %1. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory. Failed to Initialize WMI Core or Provider SubSystem or Event SubSystem with error number %1. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory.
0x1DError number %1 was returned in trying to initialize Windows Management Instrumentation Service. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory. Error number %1 was returned in trying to initialize Windows Management Instrumentation Service. This could be due to a badly installed version of WMI, WMI repository upgrade failure, insufficient disk space or insufficient memory.
0x2BWindows Management Instrumentation ADAP failed to connect to namespace %1 with the following error %2 Windows Management Instrumentation ADAP failed to connect to namespace %1 with the following error %2
0x30Windows Management Instrumentation ADAP was unable to save object %1 in namespace %2 because of the following error %3 Windows Management Instrumentation ADAP was unable to save object %1 in namespace %2 because of the following error %3
0x3AWindows Management Instrumentation ADAP was unable to create the Win32_Perf base class in %1:Result=%2 Windows Management Instrumentation ADAP was unable to create the Win32_Perf base class in %1:Result=%2
0x3BWindows Management Instrumentation ADAP was unable to create the Win32_PerfRawData base class %1 Windows Management Instrumentation ADAP was unable to create the Win32_PerfRawData base class %1
0x3FA provider, %1, has been registered in the Windows Management Instrumentation namespace %2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. A provider, %1, has been registered in the Windows Management Instrumentation namespace %2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
0x41Windows Management Instrumentation (WMI) Service is starting to restore the WMI repository Windows Management Instrumentation (WMI) Service is starting to restore the WMI repository
0x42The Windows Management Instrumentation Service has recovered from the following backup repository: %1. The Windows Management Instrumentation Service has recovered from the following backup repository: %1.
0x43The Windows Management Instrumentation (WMI) Service is starting the backup operation for the WMI repository and is copying data to the following file: %1 The Windows Management Instrumentation (WMI) Service is starting the backup operation for the WMI repository and is copying data to the following file: %1
0x44The Windows Management Instrumentation repository backup operation completed copying data to %1 with error %2. The Windows Management Instrumentation repository backup operation completed copying data to %1 with error %2.
0x15E0The Windows Management Instrumentation (WMI) service detected an inconsistency with the WMI repository in the following directory: %windir%\\system32\\wbem\\repository. The WMI service was not able to recover the repository. The WMI repository will now be deleted and a new repository will be created based on the auto-recovery mechanism. The Windows Management Instrumentation (WMI) service detected an inconsistency with the WMI repository in the following directory: %windir%\\system32\\wbem\\repository. The WMI service was not able to recover the repository. The WMI repository will now be deleted and a new repository will be created based on the auto-recovery mechanism.
0x15E1The Windows Management Instrumentation Service failed to load the repository files under the directory %windir%\\system32\\wbem\\repository. This can be caused by a corruption in the repository files, security settings on this directory, lack of disk space, or other system resource issues like lack of memory. If this error happens every time the machine is rebooted then the administrator on this machine may need to stop WMI Service, review the security setting on this folder and files under this folder, and run WMIDiag to validate the health of Windows Management Instrumentation The Windows Management Instrumentation Service failed to load the repository files under the directory %windir%\\system32\\wbem\\repository. This can be caused by a corruption in the repository files, security settings on this directory, lack of disk space, or other system resource issues like lack of memory. If this error happens every time the machine is rebooted then the administrator on this machine may need to stop WMI Service, review the security setting on this folder and files under this folder, and run WMIDiag to validate the health of Windows Management Instrumentation
0x15E2The Windows Management Instrumentation service detected an inconsistency in the following backup file: %1. The Windows Management Instrumentation service detected an inconsistency in the following backup file: %1.
0x15E4The Windows Management Instrumentation service encountered the error %2 and was not able to restore from the following backup repository: %1. The Windows Management Instrumentation service encountered the error %2 and was not able to restore from the following backup repository: %1.
0x15E5The %1 namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again. The %1 namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again.
0x15E6Windows Management Instrumentation Service could not deliver results asynchronously for %1 namespace. The namespace is marked with RequiresEncryption but WinMgmt could not establish a secure connection back to the client computer. Ensure there is a trust relationship between the client and server computers so that the client recognizes the server computer account. Windows Management Instrumentation Service could not deliver results asynchronously for %1 namespace. The namespace is marked with RequiresEncryption but WinMgmt could not establish a secure connection back to the client computer. Ensure there is a trust relationship between the client and server computers so that the client recognizes the server computer account.
0x15EBThe Windows Management Instrumentation service has detected an inconsistent system shutdown. The Windows Management Instrumentation service has detected an inconsistent system shutdown.
0x15ECWindows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: %1 Value: %2 Maximum value: %3 WMIPRVSE PID: %4 Providers hosted in this process: %5 Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: %1 Value: %2 Maximum value: %3 WMIPRVSE PID: %4 Providers hosted in this process: %5
0x15EEDuring the service startup, the Windows Management Instrumentation service was unable to locate the repository files. A new repository will be created based on the auto-recovery mechanism. During the service startup, the Windows Management Instrumentation service was unable to locate the repository files. A new repository will be created based on the auto-recovery mechanism.
0x15EFWindows Management Instrumentation Service started sucessfully Windows Management Instrumentation Service started sucessfully
0x15F0The Windows Management Instrumentation (WMI) repository was successfully re-created by the auto-recovery mechanism. The Windows Management Instrumentation (WMI) repository was successfully re-created by the auto-recovery mechanism.
0x15F1Windows Management Instrumentation Service subsystems initialized successfully Windows Management Instrumentation Service subsystems initialized successfully
0x15FFWMI interop namespace class \"%1\" has been overwritten. Some of the Interop scenarios might not work properly. Please issue following commands from elevated command prompt to restore the behavior.\"mofcomp %windir%\\system32\\wbem\\interop.mof\" and similarly mofcomp all the interop.mfl under %windir%\\system32\\wbem and its subdirectories. WMI interop namespace class \"%1\" has been overwritten. Some of the Interop scenarios might not work properly. Please issue following commands from elevated command prompt to restore the behavior.\"mofcomp %windir%\\system32\\wbem\\interop.mof\" and similarly mofcomp all the interop.mfl under %windir%\\system32\\wbem and its subdirectories.
0x10000038Classic Classic
0x50000002Error Error
0x50000003Warning Warning
0x50000004Information Information
0x90000001Microsoft-Windows-WMI Microsoft-Windows-WMI
0x90000002Application Application
0x91000001Microsoft-Windows-WMI-Activity Microsoft-Windows-WMI-Activity
0xB1000001GroupOperationId = %1; OperationId = %2; Operation = %3; ClientMachine = %4; User = %5; ClientProcessId = %6; NamespaceName = %7 GroupOperationId = %1; OperationId = %2; Operation = %3; ClientMachine = %4; User = %5; ClientProcessId = %6; NamespaceName = %7
0xB1000002ProviderInfo for GroupOperationId = %1; Operation = %2; ProviderName = %3; ProviderGuid = %4; Path = %5 ProviderInfo for GroupOperationId = %1; Operation = %2; ProviderName = %3; ProviderGuid = %4; Path = %5
0xB1000003Stop OperationId = %1 Stop OperationId = %1
0xB100000BCorrelationId = %1; GroupOperationId = %2; OperationId = %3; Operation = %4; ClientMachine = %5; User = %6; ClientProcessId = %7; NamespaceName = %8 CorrelationId = %1; GroupOperationId = %2; OperationId = %3; Operation = %4; ClientMachine = %5; User = %6; ClientProcessId = %7; NamespaceName = %8
0xB100000CProviderInfo for GroupOperationId = %1; Operation = %2; HostID = %3; ProviderName = %4; ProviderGuid = %5; Path = %6 ProviderInfo for GroupOperationId = %1; Operation = %2; HostID = %3; ProviderName = %4; ProviderGuid = %5; Path = %6
0xB100000DStop OperationId = %1; ResultCode = %2 Stop OperationId = %1; ResultCode = %2
0xB100000EOperationId = %1; Operation = %2; Channel = %3; Message = %4 OperationId = %1; Operation = %2; Channel = %3; Message = %4
0xB100000FOperationId = %1; Operation = %2; ErrorID = %3; ErrorCategory = %4; Message = %5; TargetName = %6 OperationId = %1; Operation = %2; ErrorID = %3; ErrorCategory = %4; Message = %5; TargetName = %6
0xB1000010OperationId = %1; Operation = %2; ErrorID = %3; Message = %4 OperationId = %1; Operation = %2; ErrorID = %3; Message = %4
0xB1000011CorrelationId = %1; ProcessId = %2; Protocol = %3; Operation = %4; User = %5; Namespace = %6 CorrelationId = %1; ProcessId = %2; Protocol = %3; Operation = %4; User = %5; Namespace = %6
0xB1000012WMI Events were dropped. ConsumerType = %1; Possiblecause = %2 WMI Events were dropped. ConsumerType = %1; Possiblecause = %2
0xB1000013Performing delete operation on the WMI repository. OperationID = %1; Operation = %2 Performing delete operation on the WMI repository. OperationID = %1; Operation = %2
0xB1000014Performing Update operation on the WMI repository. OperationID = %1; Operation = %2; Flags = %3 Performing Update operation on the WMI repository. OperationID = %1; Operation = %2; Flags = %3
0xB1000015WMI Events were bound. ConsumerType = %1; Possiblecause = %2 WMI Events were bound. ConsumerType = %1; Possiblecause = %2
0xB1000032Activity Transfer Activity Transfer
0xB1000064ComponentName = %1; MessageDetail = %2; FileName = %3 ComponentName = %1; MessageDetail = %2; FileName = %3
0xB1000065ComponentName = %1; ErrorId = %2; ErrorDetail = %3; FileName = %4 ComponentName = %1; ErrorId = %2; ErrorDetail = %3; FileName = %4
0xB10016E1%1 provider started with result code %2. HostProcess = %3; ProcessID = %4; ProviderPath = %5 %1 provider started with result code %2. HostProcess = %3; ProcessID = %4; ProviderPath = %5
0xB10016E2Id = %1; ClientMachine = %2; User = %3; ClientProcessId = %4; Component = %5; Operation = %6; ResultCode = %7; PossibleCause = %8 Id = %1; ClientMachine = %2; User = %3; ClientProcessId = %4; Component = %5; Operation = %6; ResultCode = %7; PossibleCause = %8
0xB10016E3Namespace = %1; NotificationQuery = %2; OwnerName = %3; HostProcessID = %4; Provider= %5, queryID = %6; PossibleCause = %7 Namespace = %1; NotificationQuery = %2; OwnerName = %3; HostProcessID = %4; Provider= %5, queryID = %6; PossibleCause = %7
0xB10016E4Namespace = %1; NotificationQuery = %2; UserName = %3; ClientProcessID = %4, ClientMachine = %5; PossibleCause = %6 Namespace = %1; NotificationQuery = %2; UserName = %3; ClientProcessID = %4, ClientMachine = %5; PossibleCause = %6
0xB10016E5Namespace = %1; Eventfilter = %2 (refer to its activate eventid:5859); Consumer = %3; PossibleCause = %4 Namespace = %1; Eventfilter = %2 (refer to its activate eventid:5859); Consumer = %3; PossibleCause = %4

EXIF

File Name:WinMgmtR.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-wmi-core.resources_31bf3856ad364e35_10.0.15063.0_en-us_e5db677400777894\
File Size:30 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:30720
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:WMI
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:WinMgmtR.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:WinMgmtR.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0

What is WinMgmtR.dll.mui?

WinMgmtR.dll.mui is Multilingual User Interface resource file that contain English (U.S.) language for file WinMgmtR.dll (WMI).

File version info

File Description:WMI
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:WinMgmtR.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:WinMgmtR.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x409, 1200