Short answer: on a laptop with two graphics cards - an integrated Intel or AMD chip plus a dedicated NVIDIA or AMD card - Claude Desktop can run on the dedicated card while the screen is wired to the integrated one. Every frame is then copied from one card to the other. The result: the fan never stops, the laptop heats up, and the mouse and keyboard lag everywhere, while the processor looks almost idle.
The fix: tell Windows to run Claude on the power saving graphics card, then restart Claude. Free, reversible, one minute. Not on a desktop PC whose monitor is plugged into the dedicated card.
One laptop, before and after: an HP ENVY 16 (Intel Core i9-13900H with Iris Xe graphics, plus an NVIDIA GeForce RTX 4060 Laptop GPU).
| Before: Claude on the dedicated card (30 July 2026) | After: Claude set to power saving (7 October 2026) | |
|---|---|---|
| Dedicated card | "Copy" engine busy at 32 %, non-stop | No Claude process on it |
| Dedicated card temperature | 64 °C, fan running | 43 °C |
| Processor / disk | 4 % / 1 % | Not measured |
| Lag on the whole desktop | 0.5 to 2 seconds | Not measured |
| Claude windows open | 1 | 2 |
After the change, with Claude Desktop 2.26454 and two Claude windows open, both of Claude's graphics processes ran on the Intel chip only, and the NVIDIA card had nothing to do. Before it, the processor was nearly idle while the desktop lagged: the bottleneck was the copy between the two cards.
Most laptops with two graphics cards wire the built-in screen to the integrated chip. The dedicated card does the heavy work for games and 3D apps, then hands each finished frame to the integrated chip, which puts it on screen. For a game, that trip is worth it. For a chat window, it is pure cost.
Claude Desktop is built on Chromium, like Chrome and Edge, and Chromium may pick the dedicated card. Then every repaint - each streamed word, each animation - is copied across to the integrated chip. That copy is what keeps the dedicated card awake, warm and loud, and what makes the whole desktop stutter.
More windows, more cost. Each Claude window runs its own graphics process, so two windows mean two streams of copies. If you keep several Claude accounts open side by side, this matters more for you than for anyone.
The same setting, written directly. No administrator rights needed:
reg add "HKCU\SOFTWARE\Microsoft\DirectX\UserGpuPreferences" /v "Claude_pzs8sxrjxfjjc!Claude" /t REG_SZ /d "GpuPreference=1;" /fGpuPreference=1 means power saving. The name Claude_pzs8sxrjxfjjc!Claude is the app ID of Claude Desktop as installed from claude.ai; check yours with Get-StartApps | Where-Object Name -like 'Claude*' in PowerShell (column AppID). For an older, non-packaged install, use the full path to Claude.exe as the name instead. Then quit and reopen Claude.
To undo, and let Windows decide again:
reg delete "HKCU\SOFTWARE\Microsoft\DirectX\UserGpuPreferences" /v "Claude_pzs8sxrjxfjjc!Claude" /fNothing is lost. Claude keeps its hardware acceleration; it simply draws on the card that drives the screen. The integrated chip is more than enough for a chat window.
In Claude Desktop Manager: Settings → Optimise for dual-graphics laptops. The switch only appears on laptops with two graphics cards - on purpose, because of the desktop PC case above. It writes the same Windows setting for Claude, covers every profile at once, reminds you to relaunch Claude, and one more click undoes it.
🖥️ Windows app - download it from a PC. This page reads fine on a phone, but the installer only runs on Windows 10 / 11.
| Your computer | What Task Manager shows for Claude | What to do |
|---|---|---|
| Laptop, two graphics cards | Dedicated card, "Copy" or "3D" | Set Claude to Power saving, quit and reopen Claude |
| Laptop, two graphics cards | Integrated chip at 99 % while streaming | A different problem: shrink the window, update Claude |
| Desktop PC, monitor on the graphics card | Dedicated card | Nothing - that is the right card |
| Any | Graphics idle, typing still lags | Not graphics: update Claude |
On laptops with two graphics cards, Claude Desktop can run on the dedicated card while the screen is wired to the integrated chip. Every frame is then copied from one card to the other, which keeps the dedicated card busy even when Claude is idle. Setting Claude to Power saving in Windows graphics settings stops it.
Most often because Claude is drawing on the dedicated graphics card, which then has to copy each frame to the integrated chip that drives the screen. On our test laptop that kept the dedicated card at 64 °C with the fan running; after switching Claude to Power saving it sat at 43 °C.
Open Settings, System, Display, Graphics, find Claude and set it to Power saving, then quit Claude completely and reopen it. The same setting can be written with one reg add command under HKCU\SOFTWARE\Microsoft\DirectX\UserGpuPreferences, without administrator rights.
Not as a first step. It moves all drawing onto the processor, and reports go both ways. On a laptop with two graphics cards, running Claude on the power saving card keeps acceleration and removes the costly copy between cards.
Yes. Each Claude window has its own graphics process, so the cost of drawing on the wrong card is multiplied by the number of windows.
No. On a desktop PC whose monitor is plugged into the graphics card, the dedicated card is the right one. Forcing the integrated chip would create the same problem in reverse.
Free to download. Standard ($10, one-time purchase) runs two Claude windows at the same time with no time limit. Pro ($30, one-time) removes all limits and adds QuickPrompt and QuickAsk.
🖥️ Windows app - download it from a PC. The installer only runs on Windows 10 / 11.