????

Your IP : 216.73.216.152

Current Path : C:/Windows/System32/en-US/
Upload File :
Current File : C:/Windows/System32/en-US/sysmain.dll.mui

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

$��<߱�R���R���R�U�����R�U�P���R�Rich��R�PEL�!b

�rc@ `_8.rdata�@@.rsrc` `@@�f��
T88�f��$��8.rdata8x.rdata$zzzdbg .rsrc$01"�].rsrc$02 ��RK6�f��Gr3/�
w�r'��4��f����0�H�����������
��?��(�@�X�	p	�	�	�	�	�	�	��!���"��3���C.��C��TD���E�5��{��MUI���`���"�@2�.�˔��ڍ%<������A���MUIen-US1Whether Application Launch Prefetching is enabled:Whether Operation API Prefetching Functionality is enabled!Whether Page Combining is enabled(Whether Application PreLaunch is enabled%Whether Memory Compression is enabledYThe maximum number of prefetch files for scenarios recorded by the Operation Recorder API/Memory Management Agent Component Configuration�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
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�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.

�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 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 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.vProvides the ability to set the maximum number of prefetch files for scenarios recorded by the Operation Recorder API.MReturns 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.|The set of components enabled and the maximum number of prefetch files for scenarios recorded by the Operation Recorder API.�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
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�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.�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.

�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.  

2Whether 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. �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.3Specifies the package full name of the application.�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.8Specifies the string identifying the app in the package.Memory Management AgentPAUnknownPASysMain4Maintains and improves system performance over time.PAMicrosoft Corporation,Working set swap assessment maintenance task-Hybrid Drive cache rebalance maintenance task%Hybrid Drive cache prepopulation task1Reserved Priority static db sync maintenance task11�0011PP<�p�p��p�p������H���������������������������"����'�Ј*��1���4$Response Time

Info

Start

Stop

Error

Warning

 Information

ReadyBoot

 ReadyBoost

 HybridDrive

DMicrosoft-Windows-ReadyBoost

 Operational

DMicrosoft-Windows-Superfetch

Main

StoreLog

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) 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 does not have enough free space. Free Space: %2 MB

�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 read performance: %2 KB/sec.

�The ReadyBoost service encountered an error during the analysis of the new device (%1). Error code: %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

8The 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 the device is too small. Size: %2 MB.  Minimum Size: %3 MB

�A ReadyBoost cache was successfully created on the device (%1) of size %2 MB.

TCaching was enabled for device (%1).

LThe 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.

�A ReadyBoost cache was successfully deleted on the device (%1).

TCaching was disabled for device (%1).

�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

�Boot plan calculation completed.%n

    Boot Plan Timestamp (UTC): %1%n

    Valid Boot Plan Obtained: %2

�A defrag. operation has completed.  A boot plan will be calculated soon.  Defrag. Timestamp (UTC): %1

�ReadyBoot disk assessment completed.%n

    Disk Assessment Timestamp (UTC): %1%n

    Success: %2

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 is not formatted with FAT, FAT32, exFAT, or NTFS.

,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

�Boot plan calculation completed in %3 ms.%n     Boot Plan Timestamp: %1%n     Reason: %4%n     Result: %2

�The device (%1) will not be used for a ReadyBoost cache because it incurs seek penalties.

�ReadyBoot disk assessment completed in %3 ms.%n     Disk Assessment Timestamp: %1%n     Result: %2

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 contains a system volume.

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 the ReadyBoost driver is attached to its volume stack.

8The device (%1) will not be used for a ReadyBoost cache because it is mounted read-only.%n%n

This 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 a VHD (virtual hard disk).

�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

�ReadyBoot has updated the system volume unique ID: %3%n ErrorCode: %1

�Caching on the solid state hybrid disk (Disk number: %1) has been disabled due to insufficient device performance.

�A speed test was performed on the Hybrid Disk.%nTest result: %1%nErrorCode: %7

xSummary 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

8System boot completion

4Disk defragmentation

4Explicit user request

`ReadyBoost caching enabled for this device.

�ReadyBoost caching disabled due to high performance device.

hReadyBoost caching enabled for ReadyBoot only.

dReadyBoost caching disabled for this device.

LReadyBoost state not determined.

8Hybrid Drive disabled.

4Hybrid Drive enabled.

�Hybrid Drive enabled, slow sequential I/O performance detected.

�Hybrid Drive host hinting suspended due to slow device performance.

tHybrid Drive disabled due to slow device performance.

PHybrid Drive state not determined.

0Test inconclusive.

0Speed tests passed.

hSpeed insufficient for sequential I/O caching.

TPerformance unacceptable for caching.

TPerformance unacceptable for caching.

@Performance not determined.

Prelaunch

Prefetch

 Successful

,ActivationFailed

Crashed

 SwitchedTo

Throttled

Suspended

$NotThrottled

$NotAvailable

$SameCSSession

4PrelaunchedInPastHour

,TooBigToBeSwapped

<BiggerThanWorkingSetLimit

 Speculative

 RPCRequest

Install

Filter

Cleanup

Duplicate

Installed

 Uninstalled

$PrelaunchApp

Other

Inbox

AppStore

AddApp

RemoveApp

$StartCallback

$BenefitScore

 FreeNetwork

4BackgroundCostNotHigh

ACPowered

4TaskAlreadyScheduled

0SwitchedToRecently

0PrefetchedRecently

�4VS_VERSION_INFO��
|O
|O?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationRFileDescriptionSysMain Service Hosth$FileVersion10.0.20348.1 (WinBuild.160101.0800)0InternalNameSysMain�.LegalCopyright� Microsoft Corporation. All rights reserved.HOriginalFilenamesysmain.dll.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.20348.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING