sysmain.dll.mui Superfetch Service Host 07d6c02b7b5eb226a4204879d3e8de88

  1. File Info
  2. MUI

File info

File name: sysmain.dll.mui
Size: 25600 byte
MD5: 07d6c02b7b5eb226a4204879d3e8de88
SHA1: 3d73db47b714e3e44e21d51e937bf80dab1994ab
SHA256: 061afd0b68c69c280eb1f60bedbe2e906a5105f88241575ff9aef27c37445a51
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in English (U.S.) 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 (U.S.) English
1Whether Application Launch Prefetching is enabled Whether Application Launch Prefetching is enabled
2Whether Operation API Prefetching Functionality is enabled Whether Operation API Prefetching Functionality is enabled
3Whether Page Combining is enabled Whether Page Combining is enabled
4Whether Application PreLaunch is enabled Whether Application PreLaunch is enabled
5Whether Memory Compression is enabled Whether Memory Compression is enabled
6The 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
7Memory Management Agent Component Configuration Memory Management Agent Component Configuration
8Provides 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
 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
9Whether 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 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
10Whether 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.
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.
11Whether 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.
12Whether 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. 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.
13Whether 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. 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.
14Provides 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.
15Returns 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.		 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.
16The 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.
17Provides 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
 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
18Whether 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 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
19Whether 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. 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.
20Whether 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.
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.
21Whether 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.
22Whether 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. 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.
23Provides 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. 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.
24Specifies the package full name of the application. Specifies the package full name of the application.
25If 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. 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.
26Specifies the string identifying the app in the package. Specifies the string identifying the app in the package.
27Memory Management Agent Memory Management Agent
207Unknown Unknown
1000Superfetch Superfetch
1001Maintains and improves system performance over time. Maintains and improves system performance over time.
3000Microsoft Corporation Microsoft Corporation
3001Working set swap assessment maintenance task Working set swap assessment maintenance task
3002Hybrid Drive cache rebalance maintenance task Hybrid Drive cache rebalance maintenance task
3003Hybrid Drive cache prepopulation task Hybrid Drive cache prepopulation task
3004Reserved Priority static db sync maintenance task Reserved Priority static db sync maintenance task
0x11000031Response Time Response Time
0x30000000Info Info
0x31000001Start Start
0x31000002Stop Stop
0x50000002Error Error
0x50000003Warning Warning
0x50000004Information Information
0x700003F8ReadyBoot ReadyBoot
0x700003FBReadyBoost ReadyBoost
0x700003FCHybridDrive HybridDrive
0x90000001Microsoft-Windows-ReadyBoost Microsoft-Windows-ReadyBoost
0x90000002Operational Operational
0x91000001Microsoft-Windows-Superfetch Microsoft-Windows-Superfetch
0x91000002Main Main
0x91000003StoreLog StoreLog
0xB00003E8The 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.
0xB00003EAThe 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
0xB00003EBThe 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
0xB00003ECThe 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.
0xB00003EDThe 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.
0xB00003EEThe 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
0xB00003EFThe 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
0xB00003F0The 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.
0xB00003F1The 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
0xB00003F2A 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.
0xB00003F3Caching was enabled for device (%1). Caching was enabled for device (%1).
0xB00003F4The 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.
0xB00003F5A ReadyBoost cache was successfully deleted on the device (%1). A ReadyBoost cache was successfully deleted on the device (%1).
0xB00003F6Caching was disabled for device (%1). Caching was disabled for device (%1).
0xB00003F7Summary 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
0xB00003F8Boot 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
0xB00003F9A 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
0xB00003FAReadyBoot 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
0xB00103EBThe 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.
0xB00103EFThe 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.
0xB00103F7Summary 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
0xB00103F8Boot 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
0xB00103F9The 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.
0xB00103FAReadyBoot 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
0xB00103FBThe 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.
0xB00103FCThe 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.
0xB00103FDThe 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.
0xB00103FEThe 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.
0xB00103FFThe 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
0xB0010401The 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).
0xB0010402The 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
0xB0010403ReadyBoot has updated the system volume unique ID: %3%n ErrorCode: %1 ReadyBoot has updated the system volume unique ID: %3%n ErrorCode: %1
0xB0010404Caching 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.
0xB0010405A 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
0xB00203F7Summary 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
0xD0000001System boot completion System boot completion
0xD0000002Disk defragmentation Disk defragmentation
0xD0000003Explicit user request Explicit user request
0xD0000004ReadyBoost caching enabled for this device. ReadyBoost caching enabled for this device.
0xD0000005ReadyBoost caching disabled due to high performance device. ReadyBoost caching disabled due to high performance device.
0xD0000006ReadyBoost caching enabled for ReadyBoot only. ReadyBoost caching enabled for ReadyBoot only.
0xD0000007ReadyBoost caching disabled for this device. ReadyBoost caching disabled for this device.
0xD0000008ReadyBoost state not determined. ReadyBoost state not determined.
0xD0000009Hybrid Drive disabled. Hybrid Drive disabled.
0xD000000AHybrid Drive enabled. Hybrid Drive enabled.
0xD000000BHybrid Drive enabled, slow sequential I/O performance detected. Hybrid Drive enabled, slow sequential I/O performance detected.
0xD000000CHybrid Drive host hinting suspended due to slow device performance. Hybrid Drive host hinting suspended due to slow device performance.
0xD000000DHybrid Drive disabled due to slow device performance. Hybrid Drive disabled due to slow device performance.
0xD000000EHybrid Drive state not determined. Hybrid Drive state not determined.
0xD000000FTest inconclusive. Test inconclusive.
0xD0000010Speed tests passed. Speed tests passed.
0xD0000011Speed insufficient for sequential I/O caching. Speed insufficient for sequential I/O caching.
0xD0000012Performance unacceptable for caching. Performance unacceptable for caching.
0xD0000014Performance not determined. Performance not determined.
0xD1000001Prelaunch Prelaunch
0xD1000002Prefetch Prefetch
0xD1000003Successful Successful
0xD1000004ActivationFailed ActivationFailed
0xD1000005Crashed Crashed
0xD1000006SwitchedTo SwitchedTo
0xD1000007Throttled Throttled
0xD1000008Suspended Suspended
0xD1000009NotThrottled NotThrottled
0xD100000ANotAvailable NotAvailable
0xD100000BSameCSSession SameCSSession
0xD100000CPrelaunchedInPastHour PrelaunchedInPastHour
0xD100000DTooBigToBeSwapped TooBigToBeSwapped
0xD100000EBiggerThanWorkingSetLimit BiggerThanWorkingSetLimit
0xD100000FSpeculative Speculative
0xD1000010RPCRequest RPCRequest
0xD1000011Install Install
0xD1000012Filter Filter
0xD1000013Cleanup Cleanup
0xD1000014Duplicate Duplicate
0xD1000015Installed Installed
0xD1000016Uninstalled Uninstalled
0xD1000017PrelaunchApp PrelaunchApp
0xD1000018Other Other
0xD1000019Inbox Inbox
0xD100001AAppStore AppStore
0xD100001BAddApp AddApp
0xD100001CRemoveApp RemoveApp
0xD100001DStartCallback StartCallback
0xD100001EBenefitScore BenefitScore
0xF1000001FreeNetwork FreeNetwork
0xF1000002BackgroundCostNotHigh BackgroundCostNotHigh
0xF1000003ACPowered ACPowered
0xF1000004TaskAlreadyScheduled TaskAlreadyScheduled
0xF1000005SwitchedToRecently SwitchedToRecently
0xF1000006PrefetchedRecently PrefetchedRecently

EXIF

File Name:sysmain.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-s..vice-core.resources_31bf3856ad364e35_10.0.15063.0_en-us_468967d03c2a2204\
File Size:25 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:25088
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:English (U.S.)
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:Superfetch Service Host
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:Superfetch
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:sysmain.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0

What is sysmain.dll.mui?

sysmain.dll.mui is Multilingual User Interface resource file that contain English (U.S.) language for file sysmain.dll (Superfetch Service Host).

File version info

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:0x409, 1200