[BUG] Windows desktop 1.49585.0 — computer use app-permission card for File Explorer shows only "Deny", no "Allow"

Summary

Since the Windows desktop app updated to 1.49585.0 (2026-09-09), the computer-use app-permission card that appears when a session asks to control File Explorer (c:\windows\explorer.exe, localized name "Prieskumník" on a Slovak Windows) shows only a "Deny" button — there is no "Allow" button. The same request worked fine the day before on the previous version.

Environment

• Claude Desktop (Windows) 1.49585.0 (the public changelog's latest entry at the time was v1.46388.4)
• Windows 11, Slovak locale (File Explorer = "Prieskumník")
• Pro/Max plan, computer use (Beta) enabled in Settings; sessions run from the desktop app (Cowork mode), not from cloud Code sessions
• Chrome extension (Claude in Chrome) connected

Steps to reproduce

1. Start a new session from the Claude Desktop app with the computer linked; computer use is ON in Settings.
2. Ask Claude to control File Explorer (click tier). Claude issues a computer-use access request for File Explorer.
3. The permission card appears: "Claude wants to use File Explorer — Click only — Can access all your files — Your other windows will be hidden…" with a single Deny button. No Allow / Allow once / Allow always.

What I tried

• Requesting by the localized app name ("Prieskumník") and by the executable path — same Deny-only card. (Note: since the update, the English name "File Explorer" no longer resolves at all; only the localized name resolves.)
• Requesting from a different session type (Cowork) — same card.
• Checked Settings → General → "Denied apps": File Explorer is not listed.
• Closed all sessions, fully quit the app from the tray, restarted — same.
• Toggled computer use off/on — same.

Expected

The card offers Allow (once/always) as it did before the update, or at least explains why the app cannot be allowed.

Actual

Only "Deny" is available, so any workflow that needs File Explorer control is blocked with no way to grant permission.

Impact

All automated workflows that launch .bat files via File Explorer stopped working after the update. Happy to provide logs or a screenshot on request.