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

Developer builds MCP server connecting 18 e-commerce tools to Claude
A developer created an MCP server that integrates 18 e-commerce platforms and tools with Claude, enabling cross-referencing queries across multiple data sources. The project was primarily built using Claude Code (Opus) in days rather than months.

Real Cost of AI Coding Tools: 42 Hours of Overhead per 60 Days — A Solo Dev's Detailed Breakdown
A solo dev tracked every dollar and minute spent on AI coding tools for 60 days. Subscriptions ($200/mo) were the smallest cost; 42 hours of overhead from bad output and tool-switching were the real tax. Net productivity gain was 1.7-2x, not 10x. Surprise: CodeRabbit, a $15/mo review tool, had the highest ROI.

LLM Cost Profiler: Open-source tool tracks API spending to make case for local models
LLM Cost Profiler is a Python tool that tracks every API call to OpenAI/Anthropic, showing exactly what you're spending and where. It exposes tasks that are overpriced relative to their complexity, providing concrete dollar amounts to justify moving to local models.

agent-data: Structured Web Data for OpenClaw Agents, 70% Cheaper Than Browser Automation
agent-data provides pure Python API endpoints for X, Reddit, flights, and job listings, designed for AI agents like OpenClaw—no browser automation needed. Benchmark shows significant cost savings and reliability improvements.