[BUG] Cowork VM bundles in %APPDATA%\Roaming cause Windows Explorer freeze when navigating user profile directory (Win11 25H2)

Resolved 💬 2 comments Opened Mar 2, 2026 by GoldenPantaloons Closed Mar 30, 2026

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?

After installing Claude Desktop with Cowork on Windows 11 25H2, Windows Explorer freezes/hangs when attempting to navigate to the user profile directory (C:\Users\<username>). The root cause is the ~12.6 GB of VM bundle files stored in %APPDATA%\Roaming\Claude\vm_bundles\claudevm.bundle, which Windows Search Indexer attempts to enumerate and index. The largest file is rootfs.vhdx at approximately 9.3 GB.

Workaround
Excluding C:\Users\<username>\AppData\Roaming\Claude\vm_bundles from Windows Search Indexing (Settings → Privacy & Security → Searching Windows → Exclusions) resolves the issue immediately.

What Should Happen?

Installing Claude Desktop with Cowork should not cause Windows Explorer to become unresponsive. Large VM bundle files should be stored in a location that does not interfere with normal OS operations, such as %LOCALAPPDATA% which is excluded from search indexing by default. If %APPDATA%\Roaming must be used, the installer should automatically register a search indexer exclusion for the vm_bundles directory to prevent Explorer from hanging when accessing the user profile.

Error Messages/Logs

Steps to Reproduce

  1. Install Claude Desktop App with Cowork
  2. Navigate to C:\Users\<username>\ in Explorer
  3. Explorer immediately freezes and does not recover.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.63 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗