| 104 | @(BrandName) |
@(BrandName) |
| 108 | Anvender handlinger... |
Applying actions... |
| 160 | Søger... |
Scanning... |
| 161 | Validerer Windows på denne computer... |
Validating Windows running on this PC... |
| 2166 | Opdaterer... |
Updating... |
| 2167 | Rydder op... |
Cleaning... |
| 3001 | &Åbn |
&Open |
| 3003 | A&nnuller scanning |
&Cancel scan |
| 5019 | &Vis detaljer |
&Show details |
| 5020 | U&dfør de anbefalede handlinger |
T&ake recommended actions |
| 6108 | Søger efter opdateringer... |
Checking for updates... |
| 7070 | Computerstatus: |
PC status: |
| 8000 | Beskyttet |
Protected |
| 8001 | Risikobetonet |
At risk |
| 8002 | Potentielt ubeskyttet |
Potentially unprotected |
| 8003 | @(BrandName) er slået fra |
@(BrandName) is OFF |
| 8004 | Periodisk scanning i @(BrandName) er slået til |
@(BrandName) Periodic Scanning is ON |
| 20000 | Failed to open the local machine Group Policy |
Failed to open the local machine Group Policy |
| 20001 | Failed to save the local machine Group Policy |
Failed to save the local machine Group Policy |
| 20002 | Failed to create registry key "%1" in the local machine Group Policy |
Failed to create registry key "%1" in the local machine Group Policy |
| 20003 | Failed to delete registry key "%1" from the local machine Group Policy |
Failed to delete registry key "%1" from the local machine Group Policy |
| 20004 | Failed to open registry key "%1" in the local machine Group Policy |
Failed to open registry key "%1" in the local machine Group Policy |
| 20005 | Failed to convert value "%1" to 32-bit DWORD |
Failed to convert value "%1" to 32-bit DWORD |
| 20006 | Failed to convert value "%1" to 64-bit DWORD |
Failed to convert value "%1" to 64-bit DWORD |
| 20007 | Failed to set registry value "%1" under registry key "%2" in the local machine Group Policy |
Failed to set registry value "%1" under registry key "%2" in the local machine Group Policy |
| 20008 | Failed to connect to WMI namespace "%1" |
Failed to connect to WMI namespace "%1" |
| 20009 | Failed to load WMI singleton instance of WMI class "%1" |
Failed to load WMI singleton instance of WMI class "%1" |
| 20010 | Failed to load WMI instance "%1" of WMI class "%2" |
Failed to load WMI instance "%1" of WMI class "%2" |
| 20011 | Failed to save WMI instance "%1" |
Failed to save WMI instance "%1" |
| 20012 | Failed to get current value for WMI property "%1" |
Failed to get current value for WMI property "%1" |
| 20013 | Failed to convert the value of WMI property "%1" to type "%2" |
Failed to convert the value of WMI property "%1" to type "%2" |
| 20014 | Failed to set WMI property "%1" to "%2" |
Failed to set WMI property "%1" to "%2" |
| 20015 | Failed to load policy XML. Verify the file exists and is a valid XML file |
Failed to load policy XML. Verify the file exists and is a valid XML file |
| 20016 | Policy XML schema validation failed. Verify that the policy XML file was exported from the FEP console and was not manually modified |
Policy XML schema validation failed. Verify that the policy XML file was exported from the FEP console and was not manually modified |
| 0x3E8 | %1 anvendte sikkerhedspolitikken: \"%2\".%0 |
%1 successfully applied security policy: \"%2\".%0 |
| 0x3E9 | %1 kunne ikke anvende sikkerhedspolitikken: \"%2\". Fejl: %3. Fejlkode: %4.%0 |
%1 failed to apply security policy: \"%2\". Error: %3. Error Code: %4.%0 |
| 0x7D0 | Antallet af registreringsforekomster overskrider grænsen på %1. Yderligere forekomster blev kasseret.%0 |
The number of detection instances exceeds the limit of %1. Additional instances were discarded.%0 |
| 0x7D1 | Størrelsen af den genererede registreringsforekomst var mere end %1KB, og det overskrider grænsen på %2KB. Registreringsforekomsten blev kasseret.%0 |
The size of the generated detection instance was more than %1KB, which exceeds the limit of %2KB. The detection instance was discarded.%0 |
| 0x7D2 | Der opstod en fejl %1 under oprettelse af WMI-forekomst for antimalwarens infektionstilstand.%0 |
There was an error %1 in creating the Antimalware Infection State WMI instance.%0 |
| 0x7D3 | Der opstod en fejl %1 under oprettelse af WMI-forekomst for antimalwarens sundhedstilstand.%0 |
There was an error %1 in creating the Antimalware Health State WMI instance.%0 |
| 0xBBA | Der opstod en fejl %1 under oprettelse af registreringsforekomsten.%0 |
There was an error %1 in generating the detection instance.%0 |
| 0xFA0 | Der opstod en fejl %1 i initialiseringen af %2 WMI-provideren.%0 |
There was an error %1 in the %2 WMI provider initialization.%0 |
| 0xFA1 | Der opstod en fejl %1 i %2 WMI-providerens AccessCheck-metode.%0 |
There was an error %1 in the %2 WMI provider AccessCheck method.%0 |
| 0xFA2 | Der opstod en fejl %1 i %2 WMI-providerens ProvideEvents-metode.%0 |
There was an error %1 in the %2 WMI provider ProvideEvents method.%0 |
| 0xFA3 | Der opstod en fejl %1 i %2 WMI-providerens FireEvent-metode.%0 |
There was an error %1 in the %2 WMI provider FireEvent method.%0 |
| 0xFA4 | Der opstod en fejl %1 i %2 WMI-providerens metoder til forekomsthentning.%0 |
There was an error %1 in the %2 WMI provider instance retrieval methods.%0 |
| 0xFA5 | Der opstod en fejl %1 i %2 WMI-providerens ExecMethodAsync-metode.%0 |
There was an error %1 in the %2 WMI provider ExecMethodAsync method.%0 |