Specs: Add EnergySaverStatus2 API spec#6484
Open
RuthNjeri wants to merge 9 commits into
Open
Conversation
Introduces spec for the new Microsoft.Windows.System.Power.PowerManager EnergySaverStatus2 API, which expands the legacy two-state EnergySaverStatus (On/Off) to a three-state model (Off/Standard/HighSavings) reflecting the Windows Germanium Energy Saver update. New APIs documented: - PowerManager.EnergySaverStatus2 property - PowerManager.EnergySaverStatus2Changed event - PowerManager.IsEnergySaverStatus2Supported() method - EnergySaverStatus2 enum ADO: Task 60383995, 61020635, 61020638, 61020649 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Updated EnergySaverStatus2 documentation to reflect changes in API behavior and requirements for Windows 11, 24H2. Clarified enum descriptions and fixed formatting issues.
Added namespace declaration for PowerNotificationsContract.
Author
|
/azp run |
|
Commenter does not have sufficient privileges for PR 6484 in repo microsoft/WindowsAppSDK |
Scottj1s
reviewed
May 15, 2026
jonwis
reviewed
May 15, 2026
Updated documentation to reflect changes in the Energy Saver feature, including the introduction of three modes: Off, Standard, and High Savings. Removed outdated examples and remarks related to unsupported OS builds.
Scottj1s
reviewed
May 20, 2026
Scottj1s
requested changes
May 20, 2026
Member
Scottj1s
left a comment
Scottj1s
left a comment
There was a problem hiding this comment.
Just need to call out deprecation
Mark PowerManager.EnergySaverStatus, PowerManager.EnergySaverStatusChanged, and the EnergySaverStatus enum as deprecated in the EnergySaverStatus2 spec. Deprecation notices added in Background section, EnergySaverStatus2 enum Remarks, and Appendix/Legacy API compatibility section. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Clarify the limitation of the legacy EnergySaverStatus and its impact on app behavior.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR Addresses issue #6483
What: Adds an API spec for
EnergySaverStatus2a new addition toMicrosoft.Windows.System.Power.PowerManagerthat expands the legacytwo-state Energy Saver (On/Off) into three states: Off, Standard,
and HighSavings, reflecting the Windows Germanium release.
Why: The existing
EnergySaverStatusAPI has a bug where Standard modeincorrectly reports
Off. This new API surfaces all three states accurately.A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.