/
/

How to Lower Screen Brightness When Using Battery Saver in Windows 11

by Mauro Mendoza, IT Technical Writer
How to Lower Screen Brightness When Using Battery Saver in Windows 11 blog banner image

Windows 11’s Battery Saver mode is your device’s lifeline when power is low, automatically curbing background tasks and lowering screen brightness to extend runtime. This guide walks you through precisely how to lower screen brightness while in battery saver by using command/scripting tools or the Registry Editor, giving you control over this key power-saving feature.

Methods for changing screen brightness in battery saver mode

Tailoring your screen dimming during battery saver mode ensures optimal visibility and power efficiency.

📌 Use cases: Users and organizations set the screen brightness in battery saver mode to have a good balance of visual optimization and aggressive power saving. Setting the brightness percentage for battery saver mode can help keep the device usable in low-battery scenarios, while in workspaces or outdoors, since the default 30% brightness can be too dim.

📌 Prerequisites: The methods in this guide are available for all editions of Windows 11 (update 22H2 or later). Ensure that you have administrative privileges, as well as basic familiarity with command-line tools and the Registry when following these procedures.

We recommend checking ⚠️ Things to look out for before proceeding.

📌 Recommended deployment strategies:

Click to Choose a Method💻

Best for Individual Users

💻💻💻

Best for Enterprises

Method 1: Windows Terminal (Command Prompt or PowerShell)
Method 2: Registry Editor

Method 1: Using Windows Terminal (Command Prompt or PowerShell)

Adjust brightness during Battery Saver with a single command for quick, scriptable changes.

📌 Use cases: Ideal when you need immediate adjustments or to deploy settings across multiple devices via scripts. Perfect for IT admins managing policies or users preferring terminal efficiency over GUI navigation.

Step-by-step procedure:

  1. Press Win + X, then select Terminal (Admin).

Select Terminal (Admin)

  1. Select your preferred command-line tool (Command Prompt or PowerShell):
    • By default, PowerShell is the set command tool in the Terminal.
    • To select Command Prompt, click the dropdown chevron (˅) in the tabs above the window, then select it.

Select tool

  1. In your chosen tool (CMD or PowerShell), run this configuration command:

powercfg /setdcvalueindex SCHEME_CURRENT SUB_ENERGYSAVER ESBRIGHTNESS <percentage>

    • Replace <percentage> with your desired brightness level (e.g., 0-100).
  1. After running it, execute this command to verify that the new setting takes effect:

Get-CimInstance -Namespace root/wmi -ClassName WmiMonitorBrightness

Execute command to verify the new setting

    • Look for the value of CurrentBRIGHTNESS in the output.

Your new brightness settings should take effect instantly the next time your device activates battery saver mode. If it is already active, toggle it off or on via the system tray battery icon to see your customized dimming. Windows 11 will keep using this configuration until it is modified again.

Method 2: Using Registry Editor

Directly modify Windows 11’s power settings through the registry for targeted control when other methods aren’t viable.

📌 Use cases: This is ideal for deploying enterprise-wide brightness policies via Group Policy Preferences (GPP) or when troubleshooting scenarios where powercfg commands fail. It is not recommended for casual users due to the higher risk.

⚠️ Warning: Editing the Registry incorrectly can lead to serious system instability. Always back up your Registry or create a system restore point before proceeding. Review the ⚠️ Things to look out for section to learn more.

Step-by-step procedure:

  1. Open the Run dialog (Win + R), then type regedit to open the Registry Editor.
    • Confirm the UAC prompt if it pops up.

Open Registry Editor

  1. Go to or paste this path in the address bar: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\de830923-a562-41af-a086-e3a2c6bad2da\13d09884-f74e-474a-a852-b6bde8ad03a8 

Input path in the address bar

  1. Under this key, open the DefaultPowerSchemeValues subkey.

Open the DefaultPowerSchemeValues subkey

  1. Identify your active power scheme GUID (e.g., 381b4222-f694-41f0-9685-ff5bb260df2e for Balanced).
  2. Double-click DCSettingIndex (battery power):
    • Set Base to Hexadecimal.
    • Enter brightness percentage in Value data (e.g., 32 for 50%).

DCSettingIndex (battery power)

  1. If needed, repeat step 5 for ACSettingIndex for plugged-in behavior.
  2. Close Registry Editor and restart your device to apply changes.
  3. Toggle battery saver mode to activate the new brightness setting.

💡 Note: You can use the verification step in Method 1 to verify the battery saver screen brightness setting.

⚠️ Things to look out for

This section highlights potential challenges to keep in mind while following this guide.

RisksPotential ConsequencesReversals
1. Incorrect Registry editsThe operating system can become unstable, and booting up fails.Back up the registry (regedit > File > Export) or create a System Restore Point.

Watch How to Back Up and Restore Windows Registry for more details.

2. Incorrect hex conversion in the Registry DWORD valueExtreme brightness (100%) or no display (0%)Recalculate decimal-to-hex: [Desired %] > Hex (e.g., 50% = 32); or verify it via powercfg /query
3. Typos in powercfg commandsSettings not applied or unexpected power behaviorCheck syntax via SCHEME_CURRENT(caps), SUB_ENERGYSAVER(exact spacing) in the command-line tools.

You can also run powercfg /? for command validation

4. Wrong power scheme GUIDChanges could affect the wrong profile (e.g., High Performance).Make sure to match the GUID in the Registry to your active power scheme.

Confirm active scheme: powercfg /getactivescheme

5. Forgotten powercfg /applySettings can appear in the query, but don’t activate.Always run the apply command after changes. Toggle Battery Saver manually post-configuration.
6. Over-aggressive dimmingUnusable screen in bright environmentsTest settings at 50% first. Remember: Does lowering brightness save battery? Yes, but balance usability.

Key considerations for lowering screen brightness in battery saver

Optimizing brightness settings requires understanding Windows 11’s technical constraints and behavior.

No native Group Policy control

Windows 11 lacks direct GUI or GPO settings for battery save brightness percentage. A workaround for this is deploying Registry edits (Method 2) via Group Policy Preferences (GPP) or Intune administrative templates, targeting the Registry key path.

Power scheme specificity

Adjustments to the battery saver’s screen brightness through Windows Terminal (command-line tools) will only affect your current active power scheme. To apply your adjustment to all schemes, run this command:

powercfg /setacvalueindex <SCHEME_GUID> SUB_ENERGYSAVER ESBRIGHTNESS <percentage>
powercfg /setdcvalueindex <SCHEME_GUID> SUB_ENERGYSAVER ESBRIGHTNESS <percentage>

You can find the GUID (<SCEME_GUID>) for each power scheme via powercfg /list.

Quick-Start Guide

NinjaOne provides some power management scripts and settings, NinjaOne offers several related scripts that might be helpful:

1. Power Management Scripts:

– “Change Power and Sleep Settings” script allows configuring power and sleep settings

– There’s a script to “Set Bandwidth Delivery Optimization for Windows” which relates to power management

2. Battery-Related Script:

– A “Check Battery Health” script is available that can retrieve overall battery health

While NinjaOne doesn’t have a direct script to change brightness percentage in battery saver mode, you might:– Use Windows native settings for this functionality– Create a custom script to adjust brightness– Consult with NinjaOne support for a potential custom solution

Optimize battery saver screen brightness to balance visibility and power saving

Lowering screen brightness while in battery saver is your most effective tool for balancing visibility and extended runtime in Windows 11. Whether you use Command Prompt/PowerShell for quick adjustments or Registry Editor for enterprise deployment, you now have precise control over this critical power-saving feature.

These methods ensure your devices maintain optimal usability during low-power scenarios, whether preserving battery during critical meetings or squeezing extra runtime for field work.

Related topics

You might also like

Ready to simplify the hardest parts of IT?