|
|
| 第 21 行： |
第 21 行： |
| * '''[[Redlock]]''' 由 lucasm 和 gus33000 开发，他们是两位 BetaWiki 成员和软件开发者。初始版本于 2020 年 1 月 29 日发布。此工具旨在尽可能接近地复制 Microsoft 的原始 Redpill 实现。 | | * '''[[Redlock]]''' 由 lucasm 和 gus33000 开发，他们是两位 BetaWiki 成员和软件开发者。初始版本于 2020 年 1 月 29 日发布。此工具旨在尽可能接近地复制 Microsoft 的原始 Redpill 实现。 |
|
| |
|
| == Windows 10 and later == | | == Windows 10 及以上版本 == |
| <!-- todo: gather information (i need you guys help) --> | | <!-- TODO：收集信息 （我需要你们的帮助） --> |
| Windows versions since the [[Windows 10 Anniversary Update]] utilize a simplified feature locking mechanism which make use of numeric strings internally referred to as Velocity staging keys. These values are controlled by dynamic link library <code>fcon.dll</code> (''Feature Configuration'') found within the <code>Windows\System32</code> directory, responsible for managing feature enablements in the <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement</code> key (and related subkeys, such as <code>Overrides</code> and <code>EnterpriseTempControls</code>). Features can also be restored from their previous state through the use of a Last Known Good store (found in <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\LastKnownGood</code>) if the library detects problems with the existing overrides. Built-in feature overrides were introduced from as early as [[Windows 11 build 22606]].
| | 自 [[Windows 10 v1607|Windows 10 周年更新]]以来的 Windows 版本使用简化的功能锁定机制，此机制使用内部称为 Velocity 暂存密钥的数字字符串。这些值由 <code>Windows\System32</code> 目录中的动态链接库 <code>fcon.dll</code>（''功能配置，Feature Configuration''）控制，此库负责管理 <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement</code> 键（和相关子项，如 <code>Overrides</code> 和 <code>EnterpriseTempControls</code>）中的功能启用。如果库检测到现有覆盖的问题，还可以通过使用上次已知良好存储（位于 <code>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\LastKnownGood</code>）从其以前的状态恢复功能。内置功能覆盖早在 [[Windows 11 Build 22606.1.ni_release.220420-1415|Windows 11 Build 22606]] 中就引入了。 |
|
| |
|
| The availability of certain features may depend on the current state of an associated staging key. In most cases, feature states can be modified if the priority data returns 8 (<code>User</code>). In certain cases, a feature may be either forcibly enabled or disabled in code if its priority returns <code>ImageDefault</code>. This type of feature lockout also introduces a data type called "variants", which ship multiple treatments for the same staging key. Treatments may vary between devices and installations.
| | 某些功能的可用性可能取决于关联暂存密钥的当前状态。在大多数情况下，如果优先级数据返回 8（<code>User</code>），则可以修改功能状态。在某些情况下，如果某个功能的优先级返回 <code>ImageDefault</code>，则可以在代码中强制启用或禁用此功能。这种类型的功能锁定还引入了一种称为“variants”的数据类型，此数据类型为同一暂存密钥提供多个实现方法。处理方法可能因设备和安装而异。 |
|
| |
|
| Currently, most features introduced in newer Windows releases employ this method for concealing and/or testing features that are not ready for widespread release to a scoped set of users. The first known feature to use this new feature lockout mechanism is Sets, which was first introduced in [[Windows 10 build 17618]] with staging keys <code>13849566</code> and <code>10727725</code>. Traditional feature enablement checks via the Windows registry remain as a perennial choice for certain aspects of the operating system.
| | 目前，在较新 Windows 版本中引入的大多数功能都采用此方法来隐藏和/或测试尚未准备好向一组有范围的用户广泛发布的功能。使用这种新功能锁定机制的第一个已知功能是“集”（Sets），它首次在 [[Windows 10 Build 17618.1000.rs_prerelease.180302-1651|Windows 10 Build 17618]] 中引入，具有暂存密钥 <code>13849566</code> 和 <code>10727725</code>。通过 Windows 注册表进行的传统功能启用检查仍然是操作系统某些方面的常态选择。 |
|
| |
|
| === Tools === | | === Tools === |