Intellisense does not work properly with workspace

[pilgi3]

Issue Type: Bug

I am open from my workspace in VS Code a Powershell script and wait until the Integrated console was loaded.
Then I start writing (for example) 'start-process' but the IntelliSense does not appear.
If I move and hold the pointer on the command I can see a little box 'Loading ...'.

Restarting the current session did not help, restarting VS Code did not help either.
If I create a new file (in the workspace) and choose the file type powershell did not help too.
But when I close the workpace and open a new single file the IntelliSense working properly!
This happens on two devices (Windows 10 20H2, and Server 2016).
I am using the same (big) workspace on both devices.
That's very annoying, because of this behavior I cannot use VS Code anymore!
Would be greate if this bug get fixed!

Extension version: 2021.2.2
VS Code version: Code 1.55.1 (08a217c4d27a02a5bcde898fd7981bda5b49391b, 2021-04-07T15:06:02.360Z)
OS version: Windows_NT x64 10.0.19042

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: enabled rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	23.89GB (13.28GB free)
Process Argv	--file-uri file://sccm.engel.int/apps%24/sccm-workspace.code-workspace --crash-reporter-id ff4ed618-203b-4bcd-8784-2b376987aec6
Screen Reader	no
VM	0%

[SydneyhSmith]

Thanks @pilgi3 could yo please provide a screenshot of this it would be really helpful if you could also attach the logs--instructions for how to do that are here

[pilgi3]

I hope this helps.
Actually it works a few minutes after reopening vscode or restarting the powershell session.

vscode.zip

[SydneyhSmith]

Thanks @pilgi3 looks like this issue could be caused by the way we are loading files in the workspace-- we will need to investigate this area

This issue was closed automatically as repro info was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information!

[andyleejordan]

This was actually still pending (on me, in fact) for investigation. The bot got a little over-eager, sorry about that!