Unable to move/rename folders which contain files

[zoltair]

Issue Type: Bug

I am unable to move or rename folders in the open folder from within Visual Studio Code, though I am able to move or rename files. It seems that Visual Studio Code itself holds these folders "open" in a way which prevents them from being changed, but only if the folder contains at least one file.

Reproduction

1. Open a project folder in Visual Studio Code from WSL (code-insiders .)
2. Create a folder within this folder. (Right-click in project tree, select "New Folder", give it a name.)
3. Try to rename this folder. (Right-click on newly-created folder, select "Rename", give it a new name.) This works.
4. Create a file within this newly-created/newly-renamed folder. (Right-click on folder, select "New File", give this new file a name, such as test-file.md.)
5. Try to rename the folder again. (Right-click on folder, select "Rename", give it a new name.)

Expected Behavior

The renamed folder should have the new name it was given.

Actual Behavior

The renamed folder reverts to its previous name. Any attempts to rename this folder using the bash command line, Windows Explorer, or any other tool results in a "Permission Denied" or similar access error. But, closing Visual Studio Code allows these other methods to work, strongly suggesting that it is Visual Studio Code itself or the "Remote - WSL" extension which is preventing Visual Studio Code (and others) from moving or renaming these folders.

Opening the same folder with Visual Studio Code locally (rather than using the remote WSL environment) does allow these same folders to be moved/renamed without issue, strongly suggesting that it is the "Remote - WSL" extension specifically which is holding these folders open.

Extension version: 0.36.0
VS Code version: Code - Insiders 1.35.0-insider (a69d0f8b218498e22b7c3a0f76926cc6322e6106, 2019-05-17T05:18:13.839Z)
OS version: Windows_NT x64 10.0.17134
Remote OS version: Linux x64 4.4.0-17134-Microsoft

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.91GB (21.91GB free)
Process Argv	--folder-uri=vscode-remote://wsl+default/net/projects/family/gen-index --remote=wsl+default
Screen Reader	no
VM	0%

Item	Value
Remote	WSL
OS	Linux x64 4.4.0-17134-Microsoft
CPUs	Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)
Memory (System)	31.91GB (21.91GB free)
VM	0%

[zoltair]

It seems I didn't look hard enough for duplicates. This issue is a duplicate of microsoft/vscode-remote-release #208 and microsoft/WSL #3395 (among others). Apparently, it will be addressed by WSL2.