vscode
vscode copied to clipboard
microsoft
Windows “Open Folder” dialog freezes when right-clicking inside the dialog (100% reproducible)
Environment
- VS Code version: 1.105.1 (system setup)
- Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
- Date: 2025-10-14T22:33:36.618Z
- Electron: 37.6.0
- Chromium: 138.0.7204.251
- Node.js: 22.19.0
- V8: 13.8.258.32-electron.0
- OS: Windows_NT x64 10.0.19045 (Windows 10 22H2)
- Hardware acceleration: Disabled
- Input method: English / Microsoft Pinyin
- Reproduction rate: 100%
Steps to Reproduce
- Launch VS Code.
- Go to File → Open Folder....
- In the native Windows folder picker dialog, right-click on any blank area inside the dialog.
- The cursor turns into a spinning blue circle, and both the dialog and the entire VS Code UI become unresponsive.
Expected Behavior
A normal context menu should appear (as in Chrome or Notepad, which use the same Windows folder picker dialog).
Actual Behavior
- The cursor changes to a spinning busy indicator.
- The dialog window and the VS Code main window completely freeze.
- The freeze never resolves; VS Code must be forcibly terminated.
Additional Information
- This issue only occurs in VS Code — other applications using the same
IFileDialog(e.g. Chrome, Notepad) behave normally. - All non-Microsoft context menu shell extensions were disabled via ShellExView, but the issue persists.
- All VS Code extensions were disabled (Safe Mode), but the issue persists.
- Hardware acceleration is already disabled (
"window.enableHardwareAcceleration": false). - Switching to English input method does not help.
- The freeze is 100% reproducible every time.
- No crash dumps are generated even when launching with
code --crash-reporter-directory <path>（As provided in the attachment, it can be seen that an empty folder has been generated） vscode_crash.zip
Unable to repro with latest insiders https://code.visualstudio.com/insiders, please confirm if the issue persists.
Unable to repro with latest insiders https://code.visualstudio.com/insiders, please confirm if the issue persists.
The problem still exists.
Version: 1.108.0-insider (user setup) Commit: 9ba40f8204f1b4cb092f9585b19ab3f26d0a588c Date: 2025-12-12T14:19:49.836Z Electron: 39.2.3 ElectronBuildId: 12895514 Chromium: 142.0.7444.175 Node.js: 22.21.1 V8: 14.2.231.21-electron.0 OS: Windows_NT x64 10.0.19045