.

KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY

Server : Apache/2.4.58 (Win64) OpenSSL/3.1.3 PHP/8.2.12
System : Windows NT SERVER-PC 10.0 build 26200 (Windows 11) AMD64
User : ServerPC ( 0)
PHP Version : 8.2.12
Disable Function : NONE
Directory : C:/Windows/System32/nb-NO/

Upload File :

Current File : C:/Windows/System32/nb-NO/efscore.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$�X=��9S��9S��9S������9S���Q��9S�Rich�9S�PEL�y���!&t

��*@ �q8.rdata�@@.rsrc�q r@@�y��
lPP�y��$����8.rdata8.rdata$voltmdP�.rdata$zzzdbg @.rsrc$01@!�m.rsrc$02 �{��Yv�O�����Mz���y��0�0�H�`�x���������� 8!���!X�H"�k�<�|�MUI���@{���j[�h�:�w��ZA;U���Lؑ���MUInb-NOFileierskapArbeid (%1)Privat!�&�()P 04�
BBDD�XXZZ\PP���8��|��(� �L��T �"��� �0 � ��$��+ �%��0���3���3���4� ��6��x:� ��>���D��@M'�'�4N5�A��NC�C��QF�I�RP�Y��V`�i��c\EFS-tjenesten startet ikke. Feilkode: %3.

�EFS-tjenesten kan ikke fylle ut SID-informasjonen. Feilkode: %3.

�EFS-tjenesten kan ikke fastsl� datamaskinnavnet. Feilkode: %3.

�EFS-tjenesten kan ikke initialisere hurtigbufferl�sen. Feilkode: %3.

�EFS-tjenesten kan ikke initialisere leverand�ren av BCrypt-algoritmen. Feilkode: %3.

�EFS-tjenesten kan ikke be om programvarelisensiering hurtigbufferst�rrelsen. Feilkode: %3.

�EFS-tjenesten kan ikke �pne referanse til MS_DEF_PROV-leverand�ren. Feilkode: %3.

�EFS-tjenesten kan ikke konfigurere varsler fra LSA. Feilkode: %3.

�EFS-tjenesten kan ikke initialisere gjenopprettingspolicyressursen. Feilkode: %3.

�EFS-tjenesten kan ikke behandle gjenopprettingspolicyen. Feilkode: %3.

�EFS-tjenesten kan ikke varsle NTFS om sin tilstand. Feilkode: %3.

�EFS-tjenesten kan ikke konfigurere varsler om endring av gruppepolicy. Feilkode: %3.

�EFS-tjenesten kan ikke behandle aktive bruker�kter. Feilkode: %3.

�%1.%2: EFS-tjenesten kan ikke abonnere p� oppdateringer for en MDM-policy. Indeks: %3.

�%1.%2: Kan ikke initialisere ett eller flere synkroniseringsobjekter. Feilkode: %3.

�%1.%2: EFS-tjenesten kan ikke behandle MDM-policyoppdateringer. Feilkode: %3.

�%1.%2: EFS-tjenesten kan ikke klargj�re en bruker for Windows Information Protection. Feilkode: %3.

�%1.%2: EFS-tjenesten kan ikke klargj�re en bruker for DPL. Feilkode: %3.

�%1.%2: EFS-tjenesten kan ikke initialisere filkrypteringsk�er. Feilkode: %3.

�%1.%2: Policydata for gjenoppretting er i et ugyldig format. Feilkode: %3.

�%1.%2: EFS-tjenesten kan ikke klargj�re RMS for Windows Information Protection. Feilkode: %3.

<En klient fors�kte � kalle opp en EFS-tjeneste-API uten godkjenning p� personvernniv�. Feilkode: %3. Se https://go.microsoft.com/fwlink/?linkid=2181030.

PMaskinrolle kan ikke bestemmes. %1

pStandard gruppepolicyobjekt kan ikke opprettes. %1

Feil

Advarsel

Informasjon

Detaljert

4Microsoft-Windows-EFS

App

dAn API call failed at %1.%2. Error code: %3

xAn API call failed at %1.%2. Error code: %3, Data: %4

�An API call failed at %1.%2. Error code: %3, Data: %4, %5

P%1.%2: Failed to allocate %3 bytes.

�EFS key promoted from current key. CertValidated: %1, cbHash: %2, pbHash: %3, ContainerName: %4, ProviderName: %5, DisplayInformation: %6, dwCapabilities: %7, bIsCurrentKey: %8, eKeyType: %9

�EFS key demoted from current key. CertValidated: %1, cbHash: %2, pbHash: %3, ContainerName: %4, ProviderName: %5, DisplayInformation: %6, dwCapabilities: %7, bIsCurrentKey: %8, eKeyType: %9

|EFS key flushed from cache. CertValidated: %1, cbHash: %2, pbHash: %3, ContainerName: %4, ProviderName: %5, DisplayInformation: %6, dwCapabilities: %7, bIsCurrentKey: %8, eKeyType: %9

d%1.%2: The specified key is not valid for EFS

X%1.%2: Attempt to create a new EFS key

d%1.%2: A new EFS key was successfully created

x%1.%2: Begin searching the MY store for a valid EFS key

\%1.%2: Deleting currentkey from registry

�%1.%2: The EFS cert is self-signed, but self-signed certs are disabled by policy

�%1.%2: RSA is required by policy, but the key does not support RSA encryption

�%1.%2: MASTERKEY is required by policy, but the key does not support MASTERKEY encryption

�%1.%2: SMARTCARDS are required by policy, but the key is not SMARTCARD-based

4%1.%2: key is expired

0%1.%2: key is valid

|%1.%2: try and locate the matching key based on cert hash

d%1.%2: key successfully loaded from registry

h%1.%2: try and locate the matching key in cache

`%1.%2: trying to load the masterkey history

H%1.%2: masterkey history loaded

\%1.%2: failed to encrypt: SIS or HSM file

�%1.%2: Suite B is disabled by policy, but the key is a Suite B key

�%1.%2: Suite B is required by policy, but the key is not a Suite B key

l%1.%2: releasing user cache object. Refcount: %3

`%1.%2: trying to stop cache polling thread

T%1.%2: no decryption status in cache

l%1.%2: found matching decryption status in cache

`%1.%2: attempting to add key to user cache

|EFS key added to user cache. CertValidated: %1, cbHash: %2, pbHash: %3, ContainerName: %4, ProviderName: %5, DisplayInformation: %6, dwCapabilities: %7, bIsCurrentKey: %8, eKeyType: %9

P%1.%2: ensuring user has cache node

T%1.%2: found cache node in user info

X%1.%2: found cache node in global cache

X%1.%2: creating new cache node for user

�%1.%2: Policy settings specified flush on card removal. Starting the polling thread...

�%1.%2: Policy settings specified NO flush on timeout. Stopping the polling thread...

�%1.%2: Policy settings specified flush on timeout. Starting the polling thread...

%1.%2: Policy settings specified new cache flush interval: %3. Stop polling (will restart if there are active user caches)

D%1.%2: Polling thread stopped

�%1.%2: Flush cache specified by policy, and we have active user caches. Start polling.

D%1.%2: Polling thread started

x%1.%2: User logon detected. Beginning SSO processing.

�%1.%2: User logon detected, but is not smartcard-based. No SSO processing required.

�%1.%2: Smartcard notification detected. Beginning SSO processing.

�%1.%2: Smartcard notification detected, but the logon cert is already cached. No processing required.

�%1.%2: Current key matches the logon cert. Setting up the PIN cache.

�%1.%2: User does not yet have a current key. If smartcard is required by policy, the logon cert and PIN will be cached.

�%1.%2: Logon notification detected on DC. Beginning DRA install.

�%1.%2: user does not already have a cache: generating one now

p%1.%2: generating pre-cache for PIN and logon cert

�%1.%2: tried to install logon cert, but it's not available (not a smartcard logon, or the smartcard was removed)

\%1.%2: logon cert successfully installed

P%1.%2: trying to install logon cert

t%1.%2: User lock detected. Beginning SSO processing.

x%1.%2: User logoff detected. Beginning SSO processing.

H%1.%2: Flushing the user cache

�%1.%2: User has locked workstation, but policy says not to flush cache

\%1.%2: Checking for expired cache entries

d%1.%2: Expired certificate in recovery policy

x%1.%2: Certificate in recovery policy is not yet valid

T%1.%2: SL policy successfully updated

P%1.%2: EFS is disabled by SL policy

L%1.%2: EFS is not yet initialized

8%1.%2: EFS is disabled

�%1.%2: the data received by the API was too large. Expected: %3, Actual: %4

�%1.%2: the data received by the API was too small. Expected: %3, Actual: %4

h%1.%2: POSSIBLE EFS ATTACK DETECTED: %3, %4, %5

\%1.%2: attempting to validate EFS stream

@%1.%2: EFS stream validated

DPIN prompt dialog has closed

tPrompt the user to select a smartcard-based EFS cert

�Smartcard-based EFS cert successfully selected by the user

8Prompt the user for PIN

XPIN successfully acquired from the user

DPerfect match found in cache.

LMasterkey history already loaded

DCurrent key loaded from cache

LCurrent key loaded from registry

�%1.%2: Masterkey history: failed size consistency check. %3, %4, %5

H%1.%2: Encrypted keys not equal

x%1.%2: doing a REKEY, but the DDF entry already exists

l%1.%2: replace operation added a DDF (unexpected)

�%1.%2: user is modifying a DDF entry not matching the PoP entry. Require WRITE_ATTRIBUTES

�%1.%2: user is modifying a DDF matching the PoP entry, or the DRF. Don't require WRITE_ATTRIBUTES

�%1.%2: UNEXPECTED condition: no ENCRYPTED_KEY for SC failure

�%1.%2: Plug-n-Play service not ready. EFS server will not try to detect interrupted encryption/decryption operation(s).

�%1.%2: Cannot open log file. Encryption/decryption operation(s) cannot be recovered.

�%1.%2: Cannot read log file. Encryption/decryption operation(s) cannot be recovered.

�%1.%2: A corrupted or different format log file has been found. No action was taken.

�%1.%2: The log file cannot be opened as non-cached IO. No action was taken.

�%1.%2: Interrupted encryption/decryption operation(s) found on a volume. Recovery procedure started.

�%1.%2: EFS recovery service cannot open the file %3. The interrupted encryption/decryption operation cannot be recovered.

d%1.%2: EFS service recovered %3 successfully.

�%1.%2: EFS service could not open all the streams on file %3 The file was not recovered.

�%1.%2: %3 could not be recovered Completely. EFS driver may be missing.

�%1.%2: IO Error occurred during stream recovery. %3 was not recovered.

%1.%2: EFS recovery service cannot open the backup file %3 by name. The interrupted encryption/decryption operation (on file %4) may be recovered. The backup file will not be deleted. User should delete the backup file if the recovery operation is done successfully.

@%1.%2: %3 was opened by File ID successfully the first time but not the second time. No recovery operation was tried on file %4. This is an internal error.

$%1.%2: EFS recovery service cannot get the backup file name. The interrupted encryption/decryption operation (on file %3) may be recovered. The temporary backup file %4 is not deleted. User should delete the backup file if the recovery operation is done successfully.

t%1.%2: %3 could not be opened. %4 was not recovered.

�%1.%2: Stream Information could not be got from %3. %4 was not recovered.

�%1.%2: EFS service could not open all the streams on file %3. %4 was not recovered.

h%1.%2: EFS Service received logon notification.

t%1.%2: User cache entry purged. Reference count: %3.

�%1.%2: All user cache entries purged. Reference count: %3.

tEncrypting File System server ready to accept calls.

,%1.%2: Start: %3.

H%1.%2: Complete: %3. Code: %4.

8%1.%2: Error Code: %3.

8%1.%2: Status Code: %3.

,%1.%2: Enter: %3.

,%1.%2: Leave: %3.

@%1.%2: Leave: %3. Code: %4.

@%1.%2: Error: %3. Code: %4.

D%1.%2: Warning: %3. Code: %4.

4%1.%2: %3. Code: %4.

4%1.%2: %3. Value: %4.

H%1.%2: Complete: %3. Code: %4.

@%1.%2: Leave: %3. Code: %4.

lThread %1: %2, Line %3, HRESULT %4, Message: '%5'

Kan ikke oppheve beskyttelse av legitimasjonsn�kkel for enhetsbruker ved hjelp av Windows Hello for brukeren: %3. Feilkode: %4

�Personlig datakryptering og Windows Hello-status oppdatert: 1) Windows Hello-tilgjengelighet: %3; 2) Windows Hello-p�loggingsfunksjonalitet: %4; 3) Windows Hello-maskinvarefunksjonalitet: %5; 4) eksterne tilkoblinger for Eksternt skrivebord deaktivert: %6; 5) Windows-p�logging for automatisk omstart deaktivert: %7.

�Kryptering av personopplysninger er aktivert for brukeren %3.

�Kryptering av personlige data er deaktivert for %3. 1) Policyverdi: %4; og 2) er valgt bort: %5.

�Brukeren %3 fors�kt � f� tilgang til brukerens %4 data som er beskyttet med personopplysningskryptering, og ble nektet.

(Konvertering av personopplysningskryptering startet.%n: "%3",%npaths i policy: "%4",%npaths beskyttet: "%5",%npaths fors�kt: "%6",%nstatus: %7.

�Konvertering av personopplysningskryptering fullf�rt.%n:"%3",%npaths i policy: "%4",%npaths beskyttet: "%5",%npaths fors�kt: "%6",%nstatus: %7,%nnumber av elementer konvertert: %8 (totalt antall byte konvertert: %9),%nnumber systemelementer: %10,%nnumber skrivebeskyttede filer: %11,%nnumber elementer som er sett p�: %12.

LKonvertering av personopplysningskryptering ble ikke fullf�rt.%n:"%3",%npaths i policy: "%4",%npaths beskyttet: "%5",%npaths fors�kt: "%6",%nstatus: %7,%nnumber elementer som er konvertert: %8 (totalt antall byte konvertert: %9),%nnumber av systemelementer: %10,%nnumber skrivebeskyttede filer: %11,%nnumber av elementer som er sett p�: %12,%nnumber ukjente feil: %13,%nnumber elementer som ikke kan beskyttes: %14.

HKonvertering av personopplysningskryptering kan ikke konvertere �n eller flere filer eller mapper. Det oppstod f�rst en feil i filen eller mappen "%3" ble %4.

�Policyen for personopplysningskryptering for skrivebordsmappen er satt til %4 for brukeren %3.

�Personopplysningskrypteringspolicy for dokumenter-mappen er angitt til %4 for brukeren %3.

�Personopplysningskrypteringspolicy for Bilder-mappen er angitt til %4 for brukeren %3.

�Policyen for kryptering av personlige data for skrivebordsmappen slettes for brukeren %3.

�Policy for personopplysningskryptering for dokumenter-mappen slettes for brukeren %3.

�Policyen for Kryptering av personlige data for Bilder-mappen slettes for brukeren %3.

�Policyen for personopplysningskryptering for skrivebordsmappen er tilordnet til bane "%3" for brukeren %4.

�Policy for personopplysningskryptering for dokumenter-mappen er tilordnet til bane "%3" for brukeren %4.

�Policyen for Kryptering av personlige data for Bilder-mappen er tilordnet til bane "%3" for brukeren %4.

�Personopplysningskryptering: Baner for � beskytte mapper er tomme for brukeren %3.

dWindows Information Protection er deaktivert.

�Windows Information Protection kan ikke deaktiveres. Feilkode: %3.

�Konvertering av personopplysningskryptering fullf�rte ikke forrige gang den ble kj�rt. Modus for siste kj�ring: %3.

�Kryptering av personopplysninger er ikke tilgjengelig for gjeldende enhet. Bare Azure AD-sammenf�yde enheter st�ttes.

LKryptering av personopplysninger er ikke tilgjengelig for gjeldende enhet. St�ttede enhetstyper er Azure AD-sammenf�yde og hybride Azure AD-sammenf�yde enheter.

|4VS_VERSION_INFO��
�e
�e?�StringFileInfo�041404B0LCompanyNameMicrosoft CorporationPFileDescriptionEFS-kjernebibliotekh$FileVersion10.0.26100.1 (WinBuild.160101.0800)8InternalNameEFSCORE.DLLp&LegalCopyright� Microsoft Corporation. Med enerett.HOriginalFilenameEFSCORE.DLL.MUIj%ProductNameOperativsystemet Microsoft� Windows�>
ProductVersion10.0.26100.1DVarFileInfo$Translation�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX

Anon7 - 2021