[BUG] Windows: Claude Desktop with computer use enabled repeatedly locks the user session (7 lock screens in 4 minutes) until the Claude/Cowork service is killed

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Environment: Windows 11, ASUS laptop, Claude Desktop (MSIX), Microsoft account sign-in. Zoom meeting running with camera active. Computer use had recently been enabled in Claude Desktop settings.

What happened
With Claude Desktop open, Windows locked my session 7 times in about 4 minutes (15:05 to 15:09 local). Each time I had to sign back in; toward the end I was locked again 7 to 24 seconds after unlocking. Zoom kept running throughout, so the machine never slept. Closing Claude and ending the Claude process stopped it immediately.

Event log evidence (Security + System)

• Security 4624 Logon Type 7 (unlock) at 15:05:48, 15:07:30, 15:08:13, 15:08:59, 15:09:06, 15:09:17, 15:09:41.
• Security 4798 from LogonUI.exe (lock screen shown) at 15:05:43, 15:07:26, 15:08:08, 15:08:55, 15:09:02, 15:09:13, 15:09:35.
• Security 4624 Logon Type 5 (SYSTEM service logon via services.exe) at 15:04:55, 15:05:43, 15:07:25, 15:08:07, 15:08:55. Four of these land 0 to 1 s before a lock.
• System, Service Control Manager 7034: "The Claude service terminated unexpectedly" at 15:09:49, 8 s after the last unlock, when I ended the process. Locks stopped at that point.
• No 4800 events (audit policy not enabled). No process other than LogonUI/lsass/svchost appears in the logon events.

Notes

• No Presence Sensing option exists on this machine. Dynamic Lock not in use.
• Possibly related: #95580 (computer use re-pins the main window at "screen-saver" level on Windows) and #46483 (powerSaveBlocker usage on Windows).
• Workaround so far: disabled computer use in Claude Desktop settings and restarted. Testing whether that resolves it.

Happy to share the exported .evtx files.

What Should Happen?

Claude Desktop (and its background Cowork/Claude service) should never trigger a Windows session lock. I should be able to keep Claude Desktop open during a Zoom call without being signed out.

Error Messages/Logs

System log, Service Control Manager:
2026-09-23 15:09:49 Event 7034: The Claude service terminated unexpectedly. It has done this 1 time(s).

Security log (condensed):
15:04:55 4624 LogonType=5 SYSTEM services.exe
15:05:43 4624 LogonType=5 SYSTEM services.exe
15:05:43 4798 LogonUI.exe (lock screen)
15:05:48 4624 LogonType=7 (unlock)
15:07:25 4624 LogonType=5 SYSTEM services.exe
15:07:26 4798 LogonUI.exe (lock screen)
15:07:30 4624 LogonType=7 (unlock)
15:08:07 4624 LogonType=5 SYSTEM services.exe
15:08:08 4798 LogonUI.exe (lock screen)
15:08:13 4624 LogonType=7 (unlock)
15:08:55 4624 LogonType=5 SYSTEM services.exe
15:08:55 4798 LogonUI.exe (lock screen)
15:08:59 4624 LogonType=7 (unlock)
15:09:02 4798 LogonUI.exe (lock screen)
15:09:06 4624 LogonType=7 (unlock)
15:09:13 4798 LogonUI.exe (lock screen)
15:09:17 4624 LogonType=7 (unlock)
15:09:35 4798 LogonUI.exe (lock screen)
15:09:41 4624 LogonType=7 (unlock)
15:09:49 7034 Claude service terminated unexpectedly

Steps to Reproduce

1. Windows 11 laptop (ASUS), Claude Desktop installed from claude.com/download (MSIX). Sign in with a Microsoft account.
2. In Claude Desktop settings, enable computer use.
3. Join a Zoom meeting with the camera on.
4. Open Claude Desktop and use it normally.
5. Within 1 to 2 minutes the Windows lock screen appears and requires sign-in. It repeats every 10 to 100 seconds.
6. Close Claude Desktop and end the Claude process in Task Manager. The locking stops immediately; Service Control Manager logs 7034 for the Claude service at that moment.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Desktop for Windows, current MSIX build as of 2026-09-23

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Full Security and System .evtx exports for the 15:03 to 15:13 window are available on request. Computer use was enabled shortly before this started; disabling it and rebooting is the workaround under test.