http://www.mediafire.com/file/wt37sbsejk7iepm/PowerSettingsExplorer.zip MD5 hash for zip-file: AA4208D2E4BDBFB884E2A5970E26ACD2 I got sick of fidgeting either in registry or in command line to unhide this or that power plan setting to edit its value in Windows`dialog with advanced power settings. So I wrote this little utility to explore all power plan settings, to edit and to hide/unhide them. Utility is built with .Net 4.5 and uses only power management functions from Win API to do the job. No reboot required after you apply changes. Features: - Column "hidden" in main grid gets and sets the visibility of settings in the dialog with advanced power settings. - Values can be edited in second grid (no need to unhide them and go to Windows` power plan advanced settings dialog). - Double click on the main grid opens regedit and navigates it to the key for that setting in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\SubGroupGuid" - but you need to launch utility as Administrator for that. - Double click on second grid on the column with schemes brings the dialog with advances settings with this scheme selected. - Export and Import of settings through buttons at the bottom. - Column "active" in second grid gets and sets currently active power scheme. - Pressing <Ctrl>+<F> in the main grid shows search toolbar with edit field for search pattern, buttons for searching of next, previous occurrence of pattern, button for hiding of search toolbar; search is performed only in cells of "current" column; search is case insensitive; search is performed with use of regular expressions (Regular Expression Language - Quick Reference), so pattern can be either simple word/part of word/phrase or regular expression. Update - some notes on settings relevant to CPPC enabled systems (hardware P-states, aka Intel SpeedShift, may be AMD has these too): Processor performance autonomous mode Spoiler - controls whether autonomous mode is enabled on systems that implement version 2 of the CPPC interface, and determines whether desired performance requests should be provided to the platform. On systems with other performance state interfaces, this setting has no effect. Note Platforms that support CPPC version 2 may only support autonomous disabled or autonomous enabled mode. If only one mode is supported, the OS uses that mode and ignores the PerfAutonomousMode power setting. Values 0 - Disabled The performance state engine disables autonomous mode, determines desired performance levels, and conveys those performance levels to the platform. 1 - Enabled The performance state engine enables autonomous mode and stops providing desired performance levels to the platform. Processor energy performance preference policy Spoiler - specifies the value to program in the energy performance preference register on systems that implement version 2 of the CPPC interface. When set to 0, the energy performance preference register is programmed to 0 to favor performance. When set to 100, the energy performance preference register is set to 255 to favor energy savings. When set to an intermediate value, the energy performance preference register is programmed to the value: (setting * 255) / 100. Values (The value denotes percentage (%).) Minimum value - 0 Maximum value - 100 Processor autonomous activity window Spoiler - specifies the value to program in the autonomous activity window register on systems that implement version 2 of the CPPC interface and have autonomous mode enabled. Longer values indicate to the platform that it should be less sensitive to short duration spikes/dips in processor utilization. Values (The value denotes microseconds.) Minimum value - 0 Maximum value - 1,270,000,000 Processor performance boost mode Spoiler Intel Turbo Boost and AMD Turbo CORE technologies are features that allow processors to achieve additional performance when it is most useful (that is, at high system loads). However, this feature increases CPU core energy consumption, so Windows Server 2016 configures Turbo technologies based on the power policy that is in use and the specific processor implementation. Turbo is enabled for High Performance power plans on all Intel and AMD processors and it is disabled for Power Saver power plans. For Balanced power plans on systems that rely on traditional P-state-based frequency management, Turbo is enabled by default only if the platform supports the EPB register. Note The EPB register is only supported in Intel Westmere and later processors. For Intel Nehalem and AMD processors, Turbo is disabled by default on P-state-based platforms. However, if a system supports Collaborative Processor Performance Control (CPPC), which is a new alternative mode of performance communication between the operating system and the hardware (defined in ACPI 5.0), Turbo may be engaged if the Windows operating system dynamically requests the hardware to deliver the highest possible performance levels. To enable or disable the Turbo Boost feature, the Processor Performance Boost Mode parameter must be configured by the administrator or by the default parameter settings for the chosen power plan. Processor Performance Boost Mode has five allowable values, as shown in Table 5. For P-state-based control, the choices are Disabled, Enabled (Turbo is available to the hardware whenever nominal performance is requested), and Efficient (Turbo is available only if the EPB register is implemented). For CPPC-based control, the choices are Disabled, Efficient Enabled (Windows specifies the exact amount of Turbo to provide), and Aggressive (Windows asks for "maximum performance" to enable Turbo). In Windows Server 2016, the default value for Boost Mode is 3. Code: Name P-state-based behavior CPPC behavior ------------------------------------------------------------------------------------------------------- 0 (Disabled) Disabled Disabled 1 (Enabled) Enabled Efficient Enabled 2 (Aggressive) Enabled Aggressive 3 (Efficient Enabled) Efficient Efficient Enabled 4 (Efficient Aggressive) Efficient Aggressive It can be that when autonomous mode is enabled (and activated) other settings for legacy P-states - like minimum processor state and maximum processor state - are just ignored.