Powershell extension intellisense not came up

Hello @All,

I’m working with vscode to script my Power Shell scripts but the last days my intellisense of Cmdlets or parameters are not working.

I type import-cs and wait until 30 seconds and nothing comes up. The same way with parameters…

If I completly remove the extension Powershell 1.4.1 than intellisense are working fine but than not Script Analyser is present and so on. 😦

I check the same issue on a different machine with the same result. I hope anyone can help me.

Many thanks Arne

System Details

1498640602-ed165210-2f74-43fb-ae48-5fddad6c84561498640598532.zip

• Operating system name and version: Windows 10 US Enterprise
• VS Code version: 1.13.1
• PowerShell extension version: 1.4.1
• Output from `$PSVersionTable

Name Value

---

PSVersion 5.1.14393.1358 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} BuildVersion 10.0.14393.1358 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1

PS C:> code -v 1.13.1 379d2efb5539b09112c793d3d9a413017d736f89 PS C:> $pseditor.EditorServicesVersion

Major Minor Build Revision

---

1 4 1 0

PS C:> code --list-extensions --show-versions DavidAnson.vscode-markdownlint@0.9.1 DotJoshJohnson.xml@1.9.2 ms-vscode.PowerShell@1.4.1 ms-vscode.Theme-MarkdownKit@0.1.4

[coendewit]

Just confirming that the powershell project causes the failure. Opening just a subfolder of the project solves the problem.

[rjmholt]

I had a brand new install of VS code and the powershell extension. tab-complete and intellisense didn’t work until I read here that having a 50-line script enabled intellisense.

Intellisense should just work; it doesn’t depend on the length of the script.

However, it may be that the extension hasn’t started. Do you see the Integrated Console in the bottom (not ordinary PowerShell)? You can test this by seeing if the $psEditor variable is populated (if it is, then you are in the Integrated Console).

If the Integrated Console is not present, the extension likely hasn’t started. To start it you need to open a PowerShell file (open a file with a ps1, psm1 or psd1 extension in VSCode or open a new file and change its language mode to PowerShell).

If you definitely have a PowerShell file open and still get no intellisense, it may be you are experiencing a bug. In that case, you should open a new issue and attach your logs.

I’m going to close this issue, since it’s an old unrelated issue that is either fixed or captured by a newer issue with better discussion.