Claude AI Opus Disables Intel DPST Auto-Dimming by Editing Registry in 0002 Key

A Reddit user documented how Claude AI Opus (via Claude Cowork) disabled Intel DPST (Display Power Saving Technology) auto-dimming by directly editing the Windows registry — after every manual method failed. The fix involved setting FeatureTestControl to 1210 in the correct registry key, which turned out to be 0002 rather than the commonly cited 0000 or 0001.
The Problem
Intel DPST is a power-saving feature that adjusts screen brightness based on content. On this user's Lenovo laptop, it behaved paradoxically: bright backgrounds made the screen blindingly brighter, dark backgrounds made it nearly invisible. Standard fixes failed:
- Windows Settings had no dynamic display option
- Intel Graphics Command Center (Beta) and Intel Graphics Software could not disable it
- Disabling three Windows Sensor services did nothing
- Device Manager offered no relevant toggle
- Setting
FeatureTestControlto9250at the usual path (0000) had no effect - Manually adding the DWORD to
0001also failed
The Root Cause
The user had swapped an M.2 drive from an older laptop into a newer unit (same model, double RAM/CPU). Windows reinstalled the graphics driver, which created the DPST registry entries in 0002 instead of the expected 0000 or 0001. The standard forum advice pointed to the wrong keys.
How Claude Fixed It
The user told Claude Cowork (Opus model): “I don't care what you have to do, just fix my computer and disable this DPST.” Claude took the following autonomous actions:
- Checked the registry for relevant keys
- Searched the internet for the correct fix
- Opened a shell and granted itself admin permissions (a PowerShell window flashed briefly)
- Identified that the correct key was
0002at pathComputer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0002 - Set
FeatureTestControlto1210— where1200means DPST ON and1210means DPST OFF - Rebooted the system
After reboot, the dimming was gone. The user verified by toggling between all-white and all-black images — no brightness change.
Key Takeaway
When dealing with Intel DPST issues, especially after a motherboard or drive swap, check which registry subkey (0000, 0001, 0002, etc.) actually contains the graphics driver settings. The FeatureTestControl value may need to be 1210 to disable DPST, but verify the current value — common forum values like 9250 may be for different hardware or driver versions.
📖 Read the full source: r/ClaudeAI
👀 See Also

Optio: Orchestrating AI Coding Agents in Kubernetes from Ticket to PR
Optio is an open-source orchestration system that turns tickets into merged pull requests using AI coding agents like Claude Code or Codex. It handles the full lifecycle in isolated Kubernetes pods with a feedback loop that auto-resumes agents on CI failures or review feedback.

Claude Cowork vs OpenClaw: Where the replacement narrative holds and breaks
Claude Cowork offers persistent desktop sessions with low friction, while OpenClaw maintains advantages in system-level automation, skill ecosystems, and workflow control.

Conduid: Trust Infrastructure Layer for MCP Servers Built with Claude
Conduid indexes over 25,000 MCP servers across GitHub, npm, PyPI, and major directories, scoring each 0-100 based on GitHub activity, security posture, documentation quality, and maintenance signals. The entire codebase was written with Claude by a solo founder.

ClearSpec: A Spec Generator to Reduce Hallucination in Claude Code
ClearSpec is a tool that generates structured specifications from plain English descriptions, connecting to GitHub repos to reference real file paths and dependencies, then uses those specs as prompts for Claude Code to provide better context.