Files
2026-06-02 03:37:09 -07:00

61 lines
1.9 KiB
Groff

<?xml version='1.0' encoding='utf-8' standalone='yes'?>
<assembly
xmlns="urn:schemas-microsoft-com:asm.v3"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
manifestVersion="1.0"
>
<assemblyIdentity
language="*"
name="Microsoft-Windows-MemExt-Driver"
processorArchitecture="*"
version="0.0.0.0"
/>
<!--
To ensure that matching rules are used during the "gather" and "apply"
phases of an in-place upgrade, the following attributes should be updated
whenever a change is made to the migration rules in the...
minkernel\ntos\mm\memext\man\driver\memextdriver.man
...manifest:
/assembly/migration/@settingsVersion
This attribute should be incremented by one. Any new value must be
mirrored in manifest located here:
minkernel\ntos\mm\memext\man\driver\memextdriver.man
/assembly/migration/@replacementSettingsVersionRange
This attribute should be set to "0-(@settingsVersion-1)". For
example, if @settingsVersion is incremented to "4",
@replacementSettingsVersionRange should be "0-3".
Additionally, the contents of the...
/assembly/migration/migXml
...section should be mirrored between the two manifests (with the caveat
that merge rules always come up the up-level manifest).
-->
<migration
alwaysProcess="yes"
replacementSettingsVersionRange="0"
scope="Upgrade"
settingsVersion="1"
>
<migXml xmlns="">
<rules context="System">
<!-- Migrate everything under the MemExt key. -->
<include>
<objectSet>
<pattern type="Registry">HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\MemExt\* [*]</pattern>
</objectSet>
</include>
</rules>
</migXml>
</migration>
</assembly>