WinMgmtR.dll.mui WMI a48ca33cdc5957b9ebcc1d21261bd48b

File info

File name: WinMgmtR.dll.mui
Size: 31232 byte
MD5: a48ca33cdc5957b9ebcc1d21261bd48b
SHA1: c67d5613cadaadb3716346de35b274c3bc573a2d
SHA256: 800c2ca5ed937c43de72dbae4b9500e48bbffa9d753984b98a4e6647a6376c09
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in Danish 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 Danish English
0x4Fejlen %1 opstod under forsøg på at indlæse MOF %2, mens .MOF-fil, der er markeret med autorecover, blev genoprettet. Error %1 encountered when trying to load MOF %2 while recovering .MOF file marked with autorecover.
0xAHændelsesfilteret med forespørgslen \"%2\" kan ikke genaktiveres i navneområdet \"%1\" pga. fejlen %3. Hændelser kan ikke leveres gennem dette filter, før problemet er løst. 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.
0x15Hændelsesprovideren %1 forsøgte at registrere den syntaktisk ugyldige forespørgsel \"%2\". Forespørgslen ignoreres. Forespørgslen kan rettes ved at undersøge WMI-lageret med CIM-studio og opdatere de permanente abonnementer for den anførte provider og forespørgsel. Hvis det permanente abonnement er oprettet med en MOF-fil, der kommer fra et installeret produkt, skal du kontakte programleverandøren for at få rettet den fejlagtige registrering. 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.
0x16Hændelsesprovideren %1 forsøgte at registrere den indbyggede hændelsesforespørgsel \"%2\" i %3-navneområde, hvis sæt af målobjektklasser ikke kunne bestemmes. Forespørgslen ignoreres. 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.
0x17Hændelsesprovideren %1 forsøgte at registrere forespørgslen \"%2\" i %3-navneområde, som er for bredt. Hændelsesprovidere kan ikke levere hændelser, der leveres af systemet. Forespørgslen ignoreres. Kontakt programleverandøren. 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.
0x18Hændelsesprovideren %1 forsøgte at registrere forespørgslen \"%2\", hvis målklasse \"%3\" i %4-navneområde ikke findes. Forespørgslen ignoreres. Event provider %1 attempted to register query \"%2\" whose target class \"%3\" in %4 namespace does not exist. The query will be ignored.
0x19Hændelsesprovideren %1 forsøgte at registrere forespørgslen \"%2\", hvis målklasse \"%3\" ikke er en hændelsesklasse. Forespørgslen ignoreres. Kontakt programleverandøren. 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.
0x1CWMI Core eller Provider SubSystem eller Event SubSystem blev ikke initialiseret med fejlnummer %1. Det kan skyldes en forkert installeret version af WMI, en fejl i opgradering af WMI-lager, utilstrækkelig diskplads eller for lidt hukommelse. 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.
0x1DFejlnummer %1 blev returneret under forsøg på at initialisere tjenesten Windows Management Instrumentation. Det kan skyldes en forkert installeret version af WMI, en fejl i opgradering af WMI-lager, utilstrækkelig diskplads eller for lidt hukommelse. 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 kan ikke oprette forbindelse til navneområdet %1 med fejlen %2 Windows Management Instrumentation ADAP failed to connect to namespace %1 with the following error %2
0x30Windows Management Instrumentation-ADAP kan ikke gemme objektet %1 i navneområdet %2 pga. fejlen %3 Windows Management Instrumentation ADAP was unable to save object %1 in namespace %2 because of the following error %3
0x3AWindows Management Instrumentation-ADAP kan ikke oprette Win32_Perf-basisklassen i %1:Resultat = %2 Windows Management Instrumentation ADAP was unable to create the Win32_Perf base class in %1:Result=%2
0x3BWindows Management Instrumentation-ADAP kan ikke oprette Win32_PerfRawData-basisklassen %1 Windows Management Instrumentation ADAP was unable to create the Win32_PerfRawData base class %1
0x3FEn provider, %1, er registreret i Windows Management Instrumentation-navneområdet %2 til at bruge LocalSystem-kontoen. Denne konto er beskyttet, og provideren kan forårsage en sikkerhedsbrist, hvis den ikke repræsenterer brugeranmodninger korrekt. 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.
0x41Tjenesten Windows Management Instrumentation (WMI) går i gang med at gendanne WMI-lageret Windows Management Instrumentation (WMI) Service is starting to restore the WMI repository
0x42Tjenesten Windows Management Instrumentation har genoprettet følgende sikkerhedskopi af lageret: %1. The Windows Management Instrumentation Service has recovered from the following backup repository: %1.
0x43Tjenesten Windows Management Instrumentation (WMI) starter sikkerhedskopieringen for WMI-lageret og kopierer data til følgende fil: %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
0x44Sikkerhedskopieringen af Windows Management Instrumentation-lageret har udført kopiering af data til %1 med fejlen %2. The Windows Management Instrumentation repository backup operation completed copying data to %1 with error %2.
0x15E0Tjenesten Windows Management Instrumentation (WMI) har fundet en uoverensstemmelse med WMI-lageret i følgende mappe: %windir%\\system32\\wbem\\repository. WMI-tjenesten kunne ikke genoprette lageret. WMI-lageret slettes nu, og et nyt lager oprettes på basis af den automatiske genoprettelsesmekanisme. 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.
0x15E1Tjenesten Windows Management Instrumentation Service kunne ikke indlæse lagerfilerne under mappen %windir%\\system32\\wbem\\repository. Det kan skyldes en beskadigelse af lagerfilerne, sikkerhedsindstillingerne på mappen, manglende diskplads eller andre problemer med systemressourcer som f.eks. manglende hukommelse. Hvis denne fejl opstår, hver gang computeren genstartes, skal administratoren af denne computer måske stoppe WMI-tjenesten, gennemgå sikkerhedsindstillingen på denne mappe og filerne under denne mappe og køre WMIDiag for at validere tilstanden af 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
0x15E2Tjenesten Windows Management Instrumentation har fundet en uoverensstemmelse i følgende sikkerhedskopifil: %1. The Windows Management Instrumentation service detected an inconsistency in the following backup file: %1.
0x15E4Tjenesten Windows Management Instrumentation har fundet fejlen %2 og kan ikke gendanne data fra følgende sikkerhedskopilager: %1. The Windows Management Instrumentation service encountered the error %2 and was not able to restore from the following backup repository: %1.
0x15E5Navneområdet %1 er markeret med flaget RequiresEncryption. Adgang til dette navneområde kan blive nægtet, hvis scriptet eller programmet ikke har det rette godkendelsesniveau. Skift godkendelsesniveau til Pkt_Privacy, og kør scriptet eller programmet igen. 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.
0x15E6Tjenesten Windows Management Instrumentation kunne ikke levere resultater asynkront for navneområdet %1. Navneområdet er markeret med RequiresEncryption, men WinMgmt kunne ikke oprette en sikker forbindelse tilbage til klientcomputeren. Sørg for, at der er et tillidsforhold mellem klient- og servercomputeren, så klienten genkender servercomputerens konto. 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.
0x15EBTjenesten Windows Management Instrumentation har fundet en uoverensstemmende systemlukning. The Windows Management Instrumentation service has detected an inconsistent system shutdown.
0x15ECWindows Management Instrumentation har stoppet WMIPRVSE.EXE, fordi en kvote har nået en advarselsværdi. Kvote: %1 Værdi: %2 Maksimumværdi: %3 WMIPRVSE PID: %4 Providere, der har denne proces som vært: %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
0x15EEUnder starten af tjenesten kunne tjenesten Windows Management Instrumentation ikke finde lagerfilerne. Der oprettes et nyt lager på basis af den automatiske genoprettelsesmekanisme. 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.
0x15EFTjenesten Windows Management Instrumentation er startet Windows Management Instrumentation Service started sucessfully
0x15F0Windows Management Instrumentation-lageret (WMI) er genoprettet af den automatiske genoprettelsesmekanisme. The Windows Management Instrumentation (WMI) repository was successfully re-created by the auto-recovery mechanism.
0x15F1Windows Management Instrumentation-tjenestens undersystemer er initialiseret Windows Management Instrumentation Service subsystems initialized successfully
0x15FFDen WMI-interoperative navneområdeklasse \"%1\" er overskrevet. Nogle af de interoperative scenarier virker måske ikke korrekt. Udsted følgende kommandoer fra en kommandoprompt med administratorrettigheder for at gendanne funktionaliteten.\"mofcomp %windir%\\system32\\wbem\\interop.mof\" og lignende mofcomp af alle interop.mfl under %windir%\\system32\\wbem og dets undermapper. 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.
0x10000038Klassisk Classic
0x50000002Fejl Error
0x50000003Advarsel Warning
0x50000004Oplysninger Information
0x90000001Microsoft-Windows-WMI Microsoft-Windows-WMI
0x90000002Program 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-hændelser blev mistet. ConsumerType = %1; Possiblecause = %2 WMI Events were dropped. ConsumerType = %1; Possiblecause = %2
0xB1000013Foretager slettehandling på WMI-lageret. OperationID = %1; Operation = %2 Performing delete operation on the WMI repository. OperationID = %1; Operation = %2
0xB1000014Foretager opdateringshandling på WMI-lageret. OperationID = %1; Operation = %2; Flags = %3 Performing Update operation on the WMI repository. OperationID = %1; Operation = %2; Flags = %3
0xB1000015WMI-hændelser blev bundet. ConsumerType = %1; Possiblecause = %2 WMI Events were bound. ConsumerType = %1; Possiblecause = %2
0xB1000032Aktivitetsoverførsel 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 er startet med resultatkode %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
0xB10016E5Navneområde = %1; eventfilter = %2 (se dets aktive eventid:5859); forbruger = %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_da-dk_3fbefc3f0fc31835\
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:Danish
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. Alle rettigheder forbeholdes.
Original File Name:WinMgmtR.dll.mui
Product Name:Microsoft® Windows® Operativsystem
Product Version:10.0.15063.0

What is WinMgmtR.dll.mui?

WinMgmtR.dll.mui is Multilingual User Interface resource file that contain Danish 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. Alle rettigheder forbeholdes.
Original Filename:WinMgmtR.dll.mui
Product Name:Microsoft® Windows® Operativsystem
Product Version:10.0.15063.0
Translation:0x406, 1200