| File name: | sysmain.dll.mui |
| Size: | 25088 byte |
| MD5: | 7fc009441ae5768df2826bda661d823d |
| SHA1: | 6aff27b13126ce73fdec226042dc0fc02f925294 |
| SHA256: | f6abbf9e0b1992550ef15709c75b2cb05a6b75b63ab54d58da1516670975140c |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in English (British) 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 (British) | English |
|---|---|---|
| 1 | Whether Application Launch Prefetching is enabled | Whether Application Launch Prefetching is enabled |
| 2 | Whether Operation API Prefetching Functionality is enabled | Whether Operation API Prefetching Functionality is enabled |
| 3 | Whether Page Combining is enabled | Whether Page Combining is enabled |
| 4 | Whether Application PreLaunch is enabled | Whether Application PreLaunch is enabled |
| 5 | Whether Memory Compression is enabled | Whether Memory Compression is enabled |
| 6 | The maximum number of prefetch files for scenarios recorded by the Operation Recorder API | The maximum number of prefetch files for scenarios recorded by the Operation Recorder API |
| 7 | Memory Management Agent Component Configuration | Memory Management Agent Component Configuration |
| 8 | Provides the capability to enable any combination of the following: 1. App Launch Prefetching 2. Operation API Prefetching Functionality 3. Page Combining 4. App PreLaunch 5. Memory Compression |
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 | Whether to enable App Launch Prefetching. App launch prefetching would speed up app start-up 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 start-ups. | 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 | Whether to enable Operation Recorder API Functionality. Operation Recorder enables apps to speed up operations that repeatedly access the same file data by exposing the Windows prefetching mechanism as a public interface.
|
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 | 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.
|
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 | Whether to enable App PreLaunch. App PreLaunch can speculatively launch apps that the user is likely to use in the near future, thus reducing app switch time. | 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 | Whether to enable Memory Compression. Memory compression is a Windows feature that 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. | 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 | Provides the ability to set the maximum number of prefetch files for scenarios recorded by the Operation Recorder API. | Provides the ability to set the maximum number of prefetch files for scenarios recorded by the Operation Recorder API. |
| 15 | Returns whether any combination of the following are enabled: 1. App Launch Prefetching 2. Operation API Prefetching Functionality 3. Page Combining 4. App Prelaunch 5. Memory Compression and also returns the maximum number of prefetch files for scenarios recorded by the Operation Recorder API. |
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 | The set of components enabled and the maximum number of prefetch files for scenarios recorded by the Operation Recorder API. | The set of components enabled and the maximum number of prefetch files for scenarios recorded by the Operation Recorder API. |
| 17 | Provides the capability to disable any combination of the following: 1. App Launch Prefetching 2. Operation API Prefetching Functionality 3. Page Combining 4. App Prelaunch 5. Memory Compression |
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 | Whether to disable App Launch Prefetching. App launch prefetching would speed up app start-up 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 start-ups. | 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 | Whether to disable App Prelaunch. App Prelaunch can speculatively launch apps that the user is likely to use in the near future, thus reducing app switch time. | 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 | Whether to disable Operation Recorder API Functionality. Operation Recorder enables apps to speed up operations that repeatedly access the same file data by exposing the Windows prefetching mechanism as a public interface.
|
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 | 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.
|
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 | Whether to disable Memory Compression (disabling will take effect after the system is restarted). Memory compression is a Windows feature that 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. | 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 | Provides the ability to debug the app prelaunch of a specific app by triggering the prelaunch to occur and to exit debug mode for the app. | 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 | Specifies the package full name of the app. | Specifies the package full name of the application. |
| 25 | If this parameter is specified, the specified app will no longer be in debug mode. If not specified, the app will be prelaunched in debug mode. | 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 | Specifies the string identifying the app in the package. | Specifies the string identifying the app in the package. |
| 27 | Memory Management Agent | Memory Management Agent |
| 207 | Unknown | Unknown |
| 1000 | Superfetch | Superfetch |
| 1001 | Maintains and improves system performance over time. | Maintains and improves system performance over time. |
| 3000 | Microsoft Corporation | Microsoft Corporation |
| 3001 | Working set swap assessment maintenance task | Working set swap assessment maintenance task |
| 3002 | Hybrid Drive cache rebalance maintenance task | Hybrid Drive cache rebalance maintenance task |
| 3003 | Hybrid Drive cache prepopulation task | Hybrid Drive cache prepopulation task |
| 3004 | Reserved Priority static db sync maintenance task | Reserved Priority static db sync maintenance task |
| 0x11000031 | Response Time | Response Time |
| 0x30000000 | Info | Info |
| 0x31000001 | Start | Start |
| 0x31000002 | Stop | Stop |
| 0x50000002 | Error | Error |
| 0x50000003 | Warning | Warning |
| 0x50000004 | Information | Information |
| 0x700003F8 | ReadyBoot | ReadyBoot |
| 0x700003FB | ReadyBoost | ReadyBoost |
| 0x700003FC | HybridDrive | HybridDrive |
| 0x90000001 | Microsoft-Windows-ReadyBoost | Microsoft-Windows-ReadyBoost |
| 0x90000002 | Operational | Operational |
| 0x91000001 | Microsoft-Windows-Superfetch | Microsoft-Windows-Superfetch |
| 0x91000002 | Main | Main |
| 0x91000003 | StoreLog | StoreLog |
| 0xB00003E8 | 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. | 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 | The device (%1) will not be used for a ReadyBoost cache because it does not have enough free space. Free Space: %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 | The device (%1) will not be used for a ReadyBoost cache because it has insufficient write performance: %2 KB/sec. | The device (%1) will not be used for a ReadyBoost cache because it has insufficient write performance: %2 KB/sec. |
| 0xB00003ED | The device (%1) will not be used for a ReadyBoost cache because it has insufficient read performance: %2 KB/sec. | The device (%1) will not be used for a ReadyBoost cache because it has insufficient read performance: %2 KB/sec. |
| 0xB00003EE | The ReadyBoost service encountered an error during the analysis of the new device (%1). Error code: %2 | The ReadyBoost service encountered an error during the analysis of the new device (%1). Error code: %2 |
| 0xB00003EF | The device (%1) will not be used for a ReadyBoost cache because it is not formatted with FAT, FAT32 or NTFS. Current 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 | 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. | 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 | The device (%1) will not be used for a ReadyBoost cache because the device is too small. Size: %2 MB. Minimum Size: %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 | A ReadyBoost cache was successfully created on the device (%1) of size %2 MB. | A ReadyBoost cache was successfully created on the device (%1) of size %2 MB. |
| 0xB00003F3 | Caching was enabled for device (%1). | Caching was enabled for device (%1). |
| 0xB00003F4 | 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. | 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 | A ReadyBoost cache was successfully deleted on the device (%1). | A ReadyBoost cache was successfully deleted on the device (%1). |
| 0xB00003F6 | Caching was disabled for device (%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 | A defrag. operation has completed. A boot plan will be calculated soon. Defrag. Timestamp (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 | 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. | 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 | The device (%1) will not be used for a ReadyBoost cache because it is not formatted with FAT, FAT32, exFAT or 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 | Boot plan calculation completed in %3 ms%n Boot Plan Timestamp: %1%n Reason: %4%n Result: %2 | Boot plan calculation completed in %3 ms.%n Boot Plan Timestamp: %1%n Reason: %4%n Result: %2 |
| 0xB00103F9 | The device (%1) will not be used for a ReadyBoost cache because it incurs seek penalties. | The device (%1) will not be used for a ReadyBoost cache because it incurs seek penalties. |
| 0xB00103FA | ReadyBoot disk assessment completed in %3 ms%n Disk Assessment Timestamp: %1%n Result: %2 | ReadyBoot disk assessment completed in %3 ms.%n Disk Assessment Timestamp: %1%n Result: %2 |
| 0xB00103FB | The device (%1) will not be used for a ReadyBoost cache because it is remote, read-only, virtual or otherwise unsupported. | The device (%1) will not be used for a ReadyBoost cache because it is remote, read-only, virtual, or otherwise unsupported. |
| 0xB00103FC | The device (%1) will not be used for a ReadyBoost cache because it contains a system volume. | The device (%1) will not be used for a ReadyBoost cache because it contains a system volume. |
| 0xB00103FD | The device (%1) will not be used for a ReadyBoost cache because it contains a configuration file which explicitly prohibits this. | The device (%1) will not be used for a ReadyBoost cache because it contains a configuration file which explicitly prohibits this. |
| 0xB00103FE | The device (%1) will not be used for a ReadyBoost cache because the ReadyBoost driver is attached to its volume stack. | 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 | The device (%1) will not be used for a ReadyBoost cache because it is a VHD (virtual hard disk). | 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 has updated the system volume unique ID: %3%n ErrorCode: %1 | ReadyBoot has updated the system volume unique ID: %3%n ErrorCode: %1 |
| 0xB0010404 | Caching on the solid state hybrid disk (Disk number: %1) has been disabled due to insufficient device performance. | Caching on the solid state hybrid disk (Disk number: %1) has been disabled due to insufficient device performance. |
| 0xB0010405 | A speed test was performed on the Hybrid Disk.%nTest result: %1%nErrorCode: %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 | System boot completion | System boot completion |
| 0xD0000002 | Disk defragmentation | Disk defragmentation |
| 0xD0000003 | Explicit user request | Explicit user request |
| 0xD0000004 | ReadyBoost caching enabled for this device. | ReadyBoost caching enabled for this device. |
| 0xD0000005 | ReadyBoost caching disabled due to high performance device. | ReadyBoost caching disabled due to high performance device. |
| 0xD0000006 | ReadyBoost caching enabled for ReadyBoot only. | ReadyBoost caching enabled for ReadyBoot only. |
| 0xD0000007 | ReadyBoost caching disabled for this device. | ReadyBoost caching disabled for this device. |
| 0xD0000008 | ReadyBoost state not determined. | ReadyBoost state not determined. |
| 0xD0000009 | Hybrid Drive disabled. | Hybrid Drive disabled. |
| 0xD000000A | Hybrid Drive enabled. | Hybrid Drive enabled. |
| 0xD000000B | Hybrid Drive enabled, slow sequential I/O performance detected. | Hybrid Drive enabled, slow sequential I/O performance detected. |
| 0xD000000C | Hybrid Drive host hinting suspended due to slow device performance. | Hybrid Drive host hinting suspended due to slow device performance. |
| 0xD000000D | Hybrid Drive disabled due to slow device performance. | Hybrid Drive disabled due to slow device performance. |
| 0xD000000E | Hybrid Drive state not determined. | Hybrid Drive state not determined. |
| 0xD000000F | Test inconclusive. | Test inconclusive. |
| 0xD0000010 | Speed tests passed. | Speed tests passed. |
| 0xD0000011 | Speed insufficient for sequential I/O caching. | Speed insufficient for sequential I/O caching. |
| 0xD0000012 | Performance unacceptable for caching. | Performance unacceptable for caching. |
| 0xD0000014 | Performance not determined. | 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: | Superfetch Service Host |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | Superfetch |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | sysmain.dll.mui |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x809, 1200 |