File name: | sysmain.dll.mui |
Size: | 27136 byte |
MD5: | 06c23e2f40b399e9fb74070e090ca910 |
SHA1: | 994c3a9c127661666a519ce959d07bfb5c1fdaa5 |
SHA256: | 29f490e401123a253645b00edddc33f0d2c30059397cefa28417bebe4f287479 |
Operating systems: | Windows 10 |
Extension: | MUI |
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 |
---|---|---|
1 | Om forhåndshentning af programstart er aktiveret | Whether Application Launch Prefetching is enabled |
2 | Om funktionalitet til forhåndshentning af Operation-API er aktiveret | Whether Operation API Prefetching Functionality is enabled |
3 | Om sidekombination er aktiveret | Whether Page Combining is enabled |
4 | Om forudstart af program er aktiveret | Whether Application PreLaunch is enabled |
5 | Om komprimering af hukommelse er aktiveret | Whether Memory Compression is enabled |
6 | Det maksimale antal filer, der hentes på forhånd, til scenarier, som registreres af Operation Recorder-API'et | The maximum number of prefetch files for scenarios recorded by the Operation Recorder API |
7 | Konfiguration af agentkomponent til hukommelsesstyring | Memory Management Agent Component Configuration |
8 | Indeholder funktionalitet til aktivering af alle kombinationer af følgende: 1. Forhåndshentning af programstart 2. Funktionalitet til forhåndshentning af Operation-API 3. Sidekombination 4. Forudstart af program 5. Komprimering af hukommelse |
Provides the capability to enable any combination of the following: 1. Application Launch Prefetching 2. Operation API Prefetching Functionality 3. Page Combining 4. Application PreLaunch 5. Memory Compression |
9 | Om forhåndshentning af programstart skal aktiveres. Med forhåndshentning af programstart kan du gøre start af apps hurtigere ved at overvåge de data og den kode, som aktiveres i disse tilfælde, og bruge disse oplysninger til at forudindlæse data og kode i den fysiske hukommelse til efterfølgende start af apps | Whether to enable Application Launch Prefetching. Application launch prefetching would would speed up app startup by monitoring the data and code accessed in these cases and use that information to preload the data and code into physical memory for subsequent app startups |
10 | Om funktionalitet til Operation Recorder-API'et skal aktiveres. Operation Recorder giver programmer mulighed for at øge hastigheden for handlinger, der gentagne gange åbner de samme fildata, ved at vise Windows-mekanismen til forhåndshentning som en offentlig grænseflade.
|
Whether to enable Operation Recorder API Functionality. Operation Recorder enables applications to speed up operations that repeatedly access the same file data by exposing the Windows prefetching mechanism as a public interface.
|
11 | Om Sidekombination skal aktiveres. Med Sidekombination kan du reducere operativsystemets forbrug af fysisk hukommelse ved med mellemrum at kombinere sider i den fysiske hukommelse, der har identisk indhold.
|
Whether to enable Page Combining. Page Combining helps reduce the physical memory usage of the operating system by periodically combining pages in physical memory that have identical content.
|
12 | Om forudstart af program skal aktiveres. Forudstart af program kan spekulativt starte programmer, som brugeren sandsynligvis vil bruge i den nærmeste fremtid, så tiden til programskift reduceres. | Whether to enable Application PreLaunch. Application PreLaunch can speculatively launch applications that the user is likely to use in the near future, thus reducing application switch time. |
13 | Om Komprimering af hukommelse skal aktiveres. Komprimering af hukommelse er en Windows-funktion, som komprimerer ubrugt hukommelse for at gøre flere data residente i RAM. Det reducerer også den mængde data, der skrives til og læses fra sidefil og forbedrer på denne måde ydeevnen. | Whether to enable Memory Compression. Memory compression is a Windows feature which compresses unused memory to keep more data resident in RAM. It also reduces the amount of data written to and read from the pagefile, thus improving performance. |
14 | Giver mulighed for at angive det maksimale antal filer, der hentes på forhånd, til scenarier, som registreres af Operation Recorder-API'et. | Provides the ability to set the maximum number of prefetch files for scenarios recorded by the Operation Recorder API. |
15 | Returnerer, om en eller flere af følgende kombinationer er aktiveret: 1. Forhåndshentning af programstart 2. Funktionalitet til forhåndshentning af Operation-API 3. Sidekombination 4. Forudstart af program 5. Komprimering af hukommelse og returnerer også det maksimale antal filer, der hentes på forhånd, til scenarier, som registreres af Operation Recorder-API'et. |
Returns whether any combination of the following are enabled: 1. Application Launch Prefetching 2. Operation API Prefetching Functionality 3. Page Combining 4. Application PreLaunch 5. Memory Compression and also returns the maximum number of prefetch files for scenarios recorded by the Operation Recorder API. |
16 | Det sæt komponenter, der er aktiveret, og det maksimale antal filer, der hentes på forhånd, til scenarier, som registreres af Operation Recorder-API'et. | The set of components enabled and the maximum number of prefetch files for scenarios recorded by the Operation Recorder API. |
17 | Indeholder funktionalitet til deaktivering af alle kombinationer af følgende: 1. Forhåndshentning af programstart 2. Funktionalitet til forhåndshentning af Operation-API 3. Sidekombination 4. Forudstart af program 5. Komprimering af hukommelse |
Provides the capability to disable any combination of the following: 1. Application Launch Prefetching 2. Operation API Prefetching Functionality 3. Page Combining 4. Application PreLaunch 5. Memory Compression |
18 | Om forhåndshentning af programstart skal deaktiveres. Med forhåndshentning af programstart kan du gøre start af apps hurtigere ved at overvåge de data og den kode, som aktiveres i disse tilfælde, og bruge disse oplysninger til at forudindlæse data og kode i den fysiske hukommelse til efterfølgende start af apps | Whether to disable Application Launch Prefetching. Application launch prefetching would would speed up app startup by monitoring the data and code accessed in these cases and use that information to preload the data and code into physical memory for subsequent app startups |
19 | Om forudstart af program skal deaktiveres. Forudstart af program kan spekulativt starte programmer, som brugeren sandsynligvis vil bruge i den nærmeste fremtid, så tiden til programskift reduceres. | Whether to disable Application PreLaunch. Application PreLaunch can speculatively launch applications that the user is likely to use in the near future, thus reducing application switch time. |
20 | Om funktionalitet til Operation Recorder-API'et skal deaktiveres. Operation Recorder giver programmer mulighed for at øge hastigheden for handlinger, der gentagne gange åbner de samme fildata, ved at vise Windows-mekanismen til forhåndshentning som en offentlig grænseflade.
|
Whether to disable Operation Recorder API Functionality. Operation Recorder enables applications to speed up operations that repeatedly access the same file data by exposing the Windows prefetching mechanism as a public interface.
|
21 | Om Sidekombination skal deaktiveres. Med Sidekombination kan du reducere operativsystemets forbrug af fysisk hukommelse ved med mellemrum at kombinere sider i den fysiske hukommelse, der har identisk indhold.
|
Whether to disable Page Combining. Page Combining helps reduce the physical memory usage of the operating system by periodically combining pages in physical memory that have identical content.
|
22 | Om du vil deaktivere Komprimering af hukommelse (deaktivering træder i kraft, når systemet er genstartet). Komprimering af hukommelse er en Windows-funktion, der komprimerer ubrugt hukommelse for at holde bevare mere hukommelse i RAM. Den reducerer desuden den mængde data, der skrives til og læses fra sidefil og forbedrer på denne måde ydeevnen. | Whether to disable Memory Compression (disabling will take effect after the system is restarted). Memory compression is a Windows feature which compresses unused memory to keep more data resident in RAM. It also reduces the amount of data written to and read from the pagefile, thus improving performance. |
23 | Giver mulighed for at udføre fejlfinding i forudstart af program for et bestemt program ved at udløse forudstart og for at afslutte fejlfindingstilstand for programmet. | Provides the ability to debug the application prelaunch of a specific application by triggering the prelaunch to occur and to exit debug mode for the application. |
24 | Angiver det fulde navn på programpakken. | Specifies the package full name of the application. |
25 | Hvis denne parameter er angivet, vil det angivne program ikke længere være i fejlfindingstilstand. Hvis parameteren ikke er angivet, vil programmet blive forudstartet i fejlfindingstilstand. | If this parameter is specified, the specified application will no longer be in debug mode. If not specified, the application will be prelaunched in debug mode. |
26 | Angiver den streng, der identificerer appen i pakken. | Specifies the string identifying the app in the package. |
27 | Agent til hukommelsesstyring | Memory Management Agent |
207 | Ukendt | Unknown |
1000 | Superfetch | Superfetch |
1001 | Vedligeholder og forbedrer systemets ydeevne på længere sigt. | Maintains and improves system performance over time. |
3000 | Microsoft Corporation | Microsoft Corporation |
3001 | Vedligeholdelsesopgave med vurdering af arbejdssætskift | Working set swap assessment maintenance task |
3002 | Vedligeholdelsesopgave for cacheafbalancering af hybriddrev | Hybrid Drive cache rebalance maintenance task |
3003 | Genopfyldningsopgave for hybriddrevscache | Hybrid Drive cache prepopulation task |
3004 | Reserveret prioritet statisk db synk.vedligeholdelsesopgave | Reserved Priority static db sync maintenance task |
0x11000031 | Svartid | Response Time |
0x30000000 | Oplysninger | Info |
0x31000001 | Start | Start |
0x31000002 | Stop | Stop |
0x50000002 | Fejl | Error |
0x50000003 | Advarsel! | Warning |
0x700003F8 | ReadyBoot | ReadyBoot |
0x700003FB | ReadyBoost | ReadyBoost |
0x700003FC | HybridDrive | HybridDrive |
0x90000001 | Microsoft-Windows-ReadyBoost | Microsoft-Windows-ReadyBoost |
0x90000002 | Kan anvendes | Operational |
0x91000001 | Microsoft-Windows-Superfetch | Microsoft-Windows-Superfetch |
0x91000002 | Hoved | Main |
0x91000003 | Lagerlog | StoreLog |
0xB00003E8 | Enheden (%1) er velegnet til en ReadyBoost-cache. Den vilkårlige læsehastighed er %3 KB/sek. Den vilkårlige skrivehastighed er %4 KB/sek. | The device (%1) is suitable for a ReadyBoost cache. The random read speed is %3 KB/sec. The random write speed is %4 KB/sec. |
0xB00003EA | The device (%1) will not be used for a ReadyBoost cache because it is not attached to a supported interface.%n For USB devices, ReadyBoost requires that the device be connected to a USB 2.0 interface.%n | The device (%1) will not be used for a ReadyBoost cache because it is not attached to a supported interface.%n For USB devices, ReadyBoost requires that the device be connected to a USB 2.0 interface.%n |
0xB00003EB | Enheden (%1) kan ikke bruges til en ReadyBoost-cache, da den ikke har tilstrækkelig ledig plads. Ledig plads: %2 MB | The device (%1) will not be used for a ReadyBoost cache because it does not have enough free space. Free Space: %2 MB |
0xB00003EC | Enheden (%1) anvendes ikke på en ReadyBoost-cache, da den ikke har den nødvendige skrivehastighed: %2 KB/sek. | The device (%1) will not be used for a ReadyBoost cache because it has insufficient write performance: %2 KB/sec. |
0xB00003ED | Enheden (%1) anvendes ikke på en ReadyBoost-cache, da den ikke har den nødvendige læsehastighed: %2 KB/sek. | The device (%1) will not be used for a ReadyBoost cache because it has insufficient read performance: %2 KB/sec. |
0xB00003EE | Tjenesten ReadyBoost stødte på en fejl under forsøg på at analysere den nye enhed (%1). Fejlkode: %2 | The ReadyBoost service encountered an error during the analysis of the new device (%1). Error code: %2 |
0xB00003EF | Enheden (%1) kan ikke bruges til en ReadyBoost-cache, da den ikke er formateret med FAT, FAT32 eller NTFS. Nuværende format:%2 | The device (%1) will not be used for a ReadyBoost cache because it is not formatted with FAT, FAT32, or NTFS. Current Format:%2 |
0xB00003F0 | Enheden (%1) anvendes ikke på en ReadyBoost-cache, da den ikke udviser ensartet ydeevne i enheden. Størrelse på hurtigt område: %2 MB. | The device (%1) will not be used for a ReadyBoost cache because it does not exhibit uniform performance across the device. Size of fast region: %2 MB. |
0xB00003F1 | Enheden (%1) anvendes ikke på en ReadyBoost-cache, fordi enheden er for lille. Størrelse: %2 MB. Minimumstørrelse: %3 MB | The device (%1) will not be used for a ReadyBoost cache because the device is too small. Size: %2 MB. Minimum Size: %3 MB |
0xB00003F2 | Der blev oprettet en ReadyBoost-cache på enheden (%1) med en størrelse på %2 MB. | A ReadyBoost cache was successfully created on the device (%1) of size %2 MB. |
0xB00003F3 | Cachelagring blev aktiveret for enhed (%1). | Caching was enabled for device (%1). |
0xB00003F4 | Enheden (%1) anvendes ikke til en ReadyBoost-cache, da der allerede findes en ReadyBoost-cache (på enhed %2), og kun én cache understøttes på et givent tidspunkt. | The device (%1) will not be used for a ReadyBoost cache because a ReadyBoost cache already exists (on device %2) and only one cache is supported at a given time. |
0xB00003F5 | En ReadyBoost-cache blev slettet på enheden (%1). | A ReadyBoost cache was successfully deleted on the device (%1). |
0xB00003F6 | Cachelagring blev deaktiveret for enheden (%1). | Caching was disabled for device (%1). |
0xB00003F7 | Summary of ReadyBoot Performance:%n Io Read Count: %12%n Io Read KB: %3%n Cache Hit Count: %13%n Cache Hit KB: %4%n Cache Hit Percentage: %9%n Cache Fragmentation: %10%n Compressed Data Size KB: %5%n Raw Data Size KB: %6%n Compression Ratio: %11%n Cache Size KB: %14%n Boot Prefetch Time us: %7%n Boot Prefetch Bytes Read: %8%n Boot Timestamp (UTC): %1%n Last Boot Plan Timestamp (UTC): %2%n Last Boot Plan Timestamp (Local): %16 | Summary of ReadyBoot Performance:%n Io Read Count: %12%n Io Read KB: %3%n Cache Hit Count: %13%n Cache Hit KB: %4%n Cache Hit Percentage: %9%n Cache Fragmentation: %10%n Compressed Data Size KB: %5%n Raw Data Size KB: %6%n Compression Ratio: %11%n Cache Size KB: %14%n Boot Prefetch Time us: %7%n Boot Prefetch Bytes Read: %8%n Boot Timestamp (UTC): %1%n Last Boot Plan Timestamp (UTC): %2%n Last Boot Plan Timestamp (Local): %16 |
0xB00003F8 | Boot plan calculation completed.%n Boot Plan Timestamp (UTC): %1%n Valid Boot Plan Obtained: %2 | Boot plan calculation completed.%n Boot Plan Timestamp (UTC): %1%n Valid Boot Plan Obtained: %2 |
0xB00003F9 | En defragmenteringshandling er fuldført. Der beregnes snart en startplan. Tidsstempel for defragmentering (UTC): %1 | A defrag. operation has completed. A boot plan will be calculated soon. Defrag. Timestamp (UTC): %1 |
0xB00003FA | ReadyBoot disk assessment completed.%n Disk Assessment Timestamp (UTC): %1%n Success: %2 | ReadyBoot disk assessment completed.%n Disk Assessment Timestamp (UTC): %1%n Success: %2 |
0xB00103EB | Enheden (%1) bruges ikke til en ReadyBoost-cache, da den ikke har nok ledig plads. Ledig plads %2 MB. Der kræves %3 MB. | The device (%1) will not be used for a ReadyBoost cache because it does not have enough free space. Free Space %2 MB, required %3 MB. |
0xB00103EF | Enheden (%1) kan ikke bruges til en ReadyBoost-cache, da den ikke er formateret med FAT, FAT32, exFAT eller NTFS. | The device (%1) will not be used for a ReadyBoost cache because it is not formatted with FAT, FAT32, exFAT, or NTFS. |
0xB00103F7 | Summary of ReadyBoot Performance:%n Io Read Count: %5%n Io Read Bytes: %1%n Cache Hit Count: %6%n Cache Hit Bytes: %2%n Cache Hit Percentage: %4%n Boot Prefetch Time (us): %8%n Boot Prefetch Bytes: %3%n Boot Prefetch Read Count: %7%n | Summary of ReadyBoot Performance:%n Io Read Count: %5%n Io Read Bytes: %1%n Cache Hit Count: %6%n Cache Hit Bytes: %2%n Cache Hit Percentage: %4%n Boot Prefetch Time (us): %8%n Boot Prefetch Bytes: %3%n Boot Prefetch Read Count: %7%n |
0xB00103F8 | Beregning af startplan er fuldført efter %3 ms.%n Tidsstempel for startplan: %1%n Årsag: %4%n Resultat: %2 | Boot plan calculation completed in %3 ms.%n Boot Plan Timestamp: %1%n Reason: %4%n Result: %2 |
0xB00103F9 | Enheden (%1) anvendes ikke på en ReadyBoost-cache, da den medfører søgefejl. | The device (%1) will not be used for a ReadyBoost cache because it incurs seek penalties. |
0xB00103FA | Vurderingen af ReadyBoot-disken er fuldført efter %3 ms.%n Tidsstempel for diskvurdering: %1%n Resultat: %2 | ReadyBoot disk assessment completed in %3 ms.%n Disk Assessment Timestamp: %1%n Result: %2 |
0xB00103FB | Enheden (%1) anvendes ikke på en ReadyBoost-cache, da den er i fjerntilstand, skrivebeskyttet eller virtuel eller ikke understøttes af andre årsager. | The device (%1) will not be used for a ReadyBoost cache because it is remote, read-only, virtual, or otherwise unsupported. |
0xB00103FC | Enheden (%1) anvendes ikke på en ReadyBoost-cache, da den indeholder et systemdrev. | The device (%1) will not be used for a ReadyBoost cache because it contains a system volume. |
0xB00103FD | Enheden (%1) anvendes ikke på en ReadyBoost-cache, da den indeholder en konfigurationsfil, der udtrykkeligt forbyder det. | The device (%1) will not be used for a ReadyBoost cache because it contains a configuration file which explicitly prohibits this. |
0xB00103FE | Enheden (%1) anvendes ikke til en ReadyBoost-cache, fordi ReadyBoost-driveren er knyttet til diskenhedens stak. | The device (%1) will not be used for a ReadyBoost cache because the ReadyBoost driver is attached to its volume stack. |
0xB00103FF | The device (%1) will not be used for a ReadyBoost cache because it is mounted read-only.%n%nThis is usually caused by one of the following reasons:%n* Write-protected devices/media%n* BitLocker group policy settings prohibit write access to non-encrypted removable devices | The device (%1) will not be used for a ReadyBoost cache because it is mounted read-only.%n%nThis is usually caused by one of the following reasons:%n* Write-protected devices/media%n* BitLocker group policy settings prohibit write access to non-encrypted removable devices |
0xB0010401 | Enheden (%1) vil ikke blive brugt til en ReadyBoost-cache, fordi det er en VHD (virtuel harddisk). | The device (%1) will not be used for a ReadyBoost cache because it is a VHD (virtual hard disk). |
0xB0010402 | The attach state for volume %6 (Unique Id: %1) has changed.%n Old ReadyBoost State: %2%n New ReadyBoost State: %3%n%n Old Hybrid Drive State: %4%n New Hybrid Drive State: %5%n | The attach state for volume %6 (Unique Id: %1) has changed.%n Old ReadyBoost State: %2%n New ReadyBoost State: %3%n%n Old Hybrid Drive State: %4%n New Hybrid Drive State: %5%n |
0xB0010403 | ReadyBoot har opdateret systemets entydige enheds-id: %3%n Fejlkode: %1 | ReadyBoot has updated the system volume unique ID: %3%n ErrorCode: %1 |
0xB0010404 | Cachelagring på den hybride solid state-disk (disknummer: %1) er deaktiveret på grund af utilstrækkelig enhedsydeevne. | Caching on the solid state hybrid disk (Disk number: %1) has been disabled due to insufficient device performance. |
0xB0010405 | Der blev udført en hastighedstest på den hybride disk.%nTestresultat: %1%nFejlkode: %7 | A speed test was performed on the Hybrid Disk.%nTest result: %1%nErrorCode: %7 |
0xB00203F7 | Summary of ReadyBoot Performance:%n Io Read Count: %5%n Io Read Bytes: %1%n Cache Hit Count: %6%n Cache Hit Bytes: %2%n Cache Hit Percentage: %4%n Boot Prefetch Time (us): %8%n Boot Prefetch Bytes: %3%n Boot Prefetch Read Count: %7%n Flags: %13%n Sync Prefetch IO Bytes: %9%n Sync Prefetch IO Count: %10%n Sync Prefetch Duration (us): %11%n Post Sync Phase Pend Count: %12%n | Summary of ReadyBoot Performance:%n Io Read Count: %5%n Io Read Bytes: %1%n Cache Hit Count: %6%n Cache Hit Bytes: %2%n Cache Hit Percentage: %4%n Boot Prefetch Time (us): %8%n Boot Prefetch Bytes: %3%n Boot Prefetch Read Count: %7%n Flags: %13%n Sync Prefetch IO Bytes: %9%n Sync Prefetch IO Count: %10%n Sync Prefetch Duration (us): %11%n Post Sync Phase Pend Count: %12%n |
0xD0000001 | Systemstart er fuldført | System boot completion |
0xD0000002 | Diskdefragmentering | Disk defragmentation |
0xD0000003 | Eksplicit brugeranmodning | Explicit user request |
0xD0000004 | ReadyBoost-cachelagring er aktiveret for denne enhed. | ReadyBoost caching enabled for this device. |
0xD0000005 | ReadyBoost-cachelagring er deaktiveret på grund af højt ydende enhed. | ReadyBoost caching disabled due to high performance device. |
0xD0000006 | ReadyBoost-cachelagring er kun aktiveret for ReadyBoot. | ReadyBoost caching enabled for ReadyBoot only. |
0xD0000007 | ReadyBoost-cachelagring er deaktiveret for denne enhed. | ReadyBoost caching disabled for this device. |
0xD0000008 | ReadyBoost-tilstand kunne ikke bestemmes. | ReadyBoost state not determined. |
0xD0000009 | Hybriddrev er deaktiveret. | Hybrid Drive disabled. |
0xD000000A | Hybriddrev er aktiveret. | Hybrid Drive enabled. |
0xD000000B | Hybriddrev er aktiveret. Der er registreret langsom sekventiel I/O-ydeevne. | Hybrid Drive enabled, slow sequential I/O performance detected. |
0xD000000C | Tip til hybrid drevvært er stoppet midlertidigt på grund af langsom enhedsydeevne. | Hybrid Drive host hinting suspended due to slow device performance. |
0xD000000D | Hybrid enhed er deaktiveret på grund af langsom enhedsydeevne. | Hybrid Drive disabled due to slow device performance. |
0xD000000E | Tilstand for hybrid drev kunne ikke bestemmes. | Hybrid Drive state not determined. |
0xD000000F | Testen var ufuldstændig. | Test inconclusive. |
0xD0000010 | Hastighedstestene er godkendt. | Speed tests passed. |
0xD0000011 | Hastigheden er utilstrækkelig til sekventiel I/O-cachelagring. | Speed insufficient for sequential I/O caching. |
0xD0000012 | Ydeevnen er uacceptabel til cachelagring. | Performance unacceptable for caching. |
0xD0000014 | Ydeevnen kunne ikke bestemmes. | Performance not determined. |
0xD1000001 | Prelaunch | Prelaunch |
0xD1000002 | Prefetch | Prefetch |
0xD1000003 | Successful | Successful |
0xD1000004 | ActivationFailed | ActivationFailed |
0xD1000005 | Crashed | Crashed |
0xD1000006 | SwitchedTo | SwitchedTo |
0xD1000007 | Throttled | Throttled |
0xD1000008 | Suspended | Suspended |
0xD1000009 | NotThrottled | NotThrottled |
0xD100000A | NotAvailable | NotAvailable |
0xD100000B | SameCSSession | SameCSSession |
0xD100000C | PrelaunchedInPastHour | PrelaunchedInPastHour |
0xD100000D | TooBigToBeSwapped | TooBigToBeSwapped |
0xD100000E | BiggerThanWorkingSetLimit | BiggerThanWorkingSetLimit |
0xD100000F | Speculative | Speculative |
0xD1000010 | RPCRequest | RPCRequest |
0xD1000011 | Install | Install |
0xD1000012 | Filter | Filter |
0xD1000013 | Cleanup | Cleanup |
0xD1000014 | Duplicate | Duplicate |
0xD1000015 | Installed | Installed |
0xD1000016 | Uninstalled | Uninstalled |
0xD1000017 | PrelaunchApp | PrelaunchApp |
0xD1000018 | Other | Other |
0xD1000019 | Inbox | Inbox |
0xD100001A | AppStore | AppStore |
0xD100001B | AddApp | AddApp |
0xD100001C | RemoveApp | RemoveApp |
0xD100001D | StartCallback | StartCallback |
0xD100001E | BenefitScore | BenefitScore |
0xF1000001 | FreeNetwork | FreeNetwork |
0xF1000002 | BackgroundCostNotHigh | BackgroundCostNotHigh |
0xF1000003 | ACPowered | ACPowered |
0xF1000004 | TaskAlreadyScheduled | TaskAlreadyScheduled |
0xF1000005 | SwitchedToRecently | SwitchedToRecently |
0xF1000006 | PrefetchedRecently | PrefetchedRecently |
File Description: | Vært for tjenesten Superfetch |
File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
Company Name: | Microsoft Corporation |
Internal Name: | Superfetch |
Legal Copyright: | © Microsoft Corporation. Alle rettigheder forbeholdes. |
Original Filename: | sysmain.dll.mui |
Product Name: | Microsoft® Windows® Operativsystem |
Product Version: | 10.0.15063.0 |
Translation: | 0x406, 1200 |