version 1.101 no longer expands network drives in Explorer view

[ramfree17]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version:
• OS Version:

When version 1.101 was pushed in our corporate devices, my workspace mapped local Windows drives no longer shows the contained files and directories. Adding/mapping a direct child folder in those drives still works so this only seem to affect the mapping of the root drive. The previous version 1.98 does not have this issue.

Steps to Reproduce:

1. Create a temporary local folder that will be mapped (or map an existing one that is readable to the user). Create a sub-folder and create a dummy file content in the sub-folder.

   mkdir c:\mapme
   mkdir c:\mapme\child-dir
   dir "C:\Program Files" > C:\mapme\child-dir\dummy.txt

2. Create a temporary drive mapping in the local machine

   subst X: 'C:\mapme'

3. in VS Code's Explorer view, add the X: drive as a folder to the current workspace.

4. Expand the X: network drive .

   Expected behavior: the "child-dir" sub directory will be visible.
   Actual behavior : there is no entry when the X: drive entry is drilled down/expanded.

5. in VS Code's Explorer view, add the X:\child-dir\ as a folder to the current workspace.

6. Expand the child-dir entry. The dummy.txt file will be visible in the view.

[ramfree17]

This invalidates the work-around recommendation in https://code.visualstudio.com/docs/setup/windows#_working-with-unc-paths to map as netwokr drives the UNC resources.