Change:
disturl "https://electronjs.org/headers" <del> target "25.9.4" ms_build_id "25127168" </del> <ins> target "25.9.6" ms_build_id "25427645" </ins> runtime "electron" build_from_source "true"

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: No, issue occurs in extension. I reported the issue to the extension and it is an issue with VS Code. Note that my repro steps are slightly different as I simplified them, but they have the same effect. <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.79.2 and Insider's OS Version: Windows 10 21H2 Build .2788 Steps to Reproduce: Python extension and Pylance extension attached ZIP file to a local and UNC location. the folder from the UNC path in VS Code. Confirm that you want to add the UNC host to the whitelist permanently. file in editor, once the analysis completed after a few seconds, note that is indicated as an error. Under note the message Import "somepackage" could not be resolved Now repeat 3-5 but for the in the local folder location. Note that the does not appear here.
what is your exact entry for the UNC setting? And does it reproduce even after a restart?
Tried both of these with the same result. and Regarding restart, I assume you mean of VS Code - that also has no effect. Have not tried restarting the entire machine.
I am not entirely convinced this is a bug in VS Code, I have asked on the Pylance extension side how they perform the file system operations. is this all running locally or some kind of remote involved?
Thank you, I think that particular extension is closed source so it is hard to know what's going on for end users. I do most of my day to day work using the extension connecting from macOS to Windows.

For this test, I am just running locally on the Windows machine to rule out anything related to the remote extension. I see the same issue in both.
Any difference when you define an environment variable with the value of ? How does a UNC path look like typically that fails for you?
I still see the "unresolved" message from Pylance with that environment variable set. This would be a typical production path we use daily:
Well but in that case you need to allow , no?
Correct. The above example was for my testing setup which I was keeping separate from my production settings to rule out any interactions. For testing, I had the folder at with the settings shown in
I am just curious if this is really a VS Code issue or an extension issue. Could you also try something out with a TypeScript file: in that setup in a workspace like that create a file in the first line add something like make sure that contains some more folders put your cursor right after the last backslash of that import statement trigger intellisense () if UNC access is working fine, you should see a intellisense window of the folders within if UNC access is not working, you see generic word suggestions
This does indeed work as you describe, showing the additional folders. !
Oh nice, this is a step forward! Now we need to learn what the PyLance extension is doing differently.
I am able to reproduce this issue.
curious if you can reproduce the issue using our exploration builds which contain a newer runtime:
Trying this out but it seems like Pylance is not operating at all in the build you linked. I am not getting any Intellisense or anything. Even with logging set to , this is the only output shown for the Python Language Server: The build suggested the pre-release version of the Python extension so I tried that first, then switched to release. Both have the same result.
the runtime update has landed in VS Code insiders, so please try with now.
Unfortunately I am still seeing the message log from Python Language Server:
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected.

If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
I'm testing on this version of Insider's: and I am still seeing this issue (logs: )
I attempted to repro the issue today, I can repro it in latest stable whereas it works fine in latest insiders attaching recording below, let me know if I missed some steps
I think I found the difference - in my case I initially had the property set to and in that case, I am still seeing the issue in the latest Insider's build. However, when I set to and instead accept the unc host in the prompt as allowed, the issue goes away.
Thanks for clarifying, I can confirm the bug with that setting disabled.
can you give the latest insiders another try, it should now respect the setting with the python extension.
it is working as expected with the setting now. Thank you!