Powershell lsp server doesn't working

I've searched open issues for similar requests

• Yes

I've manually reviewed logs to find potential errors

• Yes

I've recently downloaded the latest plugin version of mason.nvim

• Yes

Problem description

After update mason and mason-lspconfig i've got a error while open powershell files. Lsp serv couldn't start with errors.

Expected behavior

Correct start lsp server

Steps to reproduce

1. Install mason.nvim, mason-lspconfig, nvim-lspconfig.
2. Configurate definitions of ps1, psm1 and psd1 files to correct lsp server.
3. open ps1 file.
4. you got a error about starting lsp server.

Affected packages

mason.nvim mason-lspconfig, nvim-lspconfig

Neovim version (>= 0.10.0)

NVIM v0.12.5
Build type: Release
LuaJIT 2.1.1774638290

Operating system/version

Windows 11 25h2

Healthcheck

==============================================================================
mason:                                                                   13 ⚠️

mason.nvim ~
- ✅ OK mason.nvim version v2.3.1
- ✅ OK PATH: prepend
- ✅ OK Providers: 
    mason.providers.registry-api
    mason.providers.client
- ✅ OK neovim version >= 0.10.0

mason.nvim [Registries] ~
- ✅ OK Registry `github.com/mason-org/mason-registry version: 2026-09-02-joyful-friday` is installed.
- ✅ OK Registry `SynthesizedRegistrySource` is installed.

mason.nvim [Core utils] ~
- ✅ OK unzip: `UnZip 6.00 of 20 April 2009, by Info-ZIP.  Maintained by C. Spieler.  Send
`
- ✅ OK wget: `GNU Wget 1.21.4, a non-interactive network retriever.
`
- ✅ OK curl: `curl 8.21.0 (Windows) libcurl/8.21.0 Schannel zlib/1.3.2 WinIDN WinLDAP
`
- ✅ OK gzip: `gzip.exe" 1.3.12`
- ✅ OK tar: `bsdtar 3.8.4 - libarchive 3.8.4 zlib/1.2.13.1-motley liblzma/5.8.1 bz2lib/1.0.8 libzstd/1.5.7 cng/2.0 libb2/bundled 
`
- ✅ OK pwsh: `7.6.5 Microsoft Windows 10.0.26100 Win32NT
`
- ✅ OK 7z: `7-Zip 26.02 (x64) : Copyright (c) 1999-2026 Igor Pavlov : 2026-06-25
`

mason.nvim [Languages] ~
- ⚠️ WARNING Go: not available
  - ADVICE:
    - spawn: go failed with exit code - and signal -. Could not find executable "go" in PATH.

- ⚠️ WARNING Composer: not available
  - ADVICE:
    - spawn: composer failed with exit code - and signal -. Could not find executable "composer" in PATH.

- ⚠️ WARNING PHP: not available
  - ADVICE:
    - spawn: php failed with exit code - and signal -. Could not find executable "php" in PATH.

- ⚠️ WARNING cargo: not available
  - ADVICE:
    - spawn: cargo failed with exit code - and signal -. Could not find executable "cargo" in PATH.

- ⚠️ WARNING luarocks: not available
  - ADVICE:
    - spawn: luarocks failed with exit code - and signal -. Could not find executable "luarocks" in PATH.

- ⚠️ WARNING javac: not available
  - ADVICE:
    - spawn: javac failed with exit code - and signal -. Could not find executable "javac" in PATH.

- ⚠️ WARNING java: not available
  - ADVICE:
    - spawn: java failed with exit code - and signal -. Could not find executable "java" in PATH.

- ⚠️ WARNING julia: not available
  - ADVICE:
    - spawn: julia failed with exit code - and signal -. Could not find executable "julia" in PATH.

- ⚠️ WARNING Ruby: not available
  - ADVICE:
    - spawn: ruby failed with exit code - and signal -. Could not find executable "ruby" in PATH.

- ⚠️ WARNING RubyGem: not available
  - ADVICE:
    - spawn: gem failed with exit code - and signal -. Could not find executable "gem" in PATH.

- ✅ OK node: `v26.8.1
`
- ⚠️ WARNING python: not available
  - ADVICE:
    - spawn: python failed with exit code 9009 and signal 0. Python 
- ⚠️ WARNING pip: not available
  - ADVICE:
    - spawn: python failed with exit code 9009 and signal 0. Python 
- ✅ OK npm: `11.19.0`
- ⚠️ WARNING python venv: not available
  - ADVICE:
    - On Debian/Ubuntu systems, you need to install the python3-venv package using the following command:

          apt-get install python3-venv

Screenshots or recordings

No response

No repository file or test is named. Start by reproducing the failure when opening a ps1, psm1, or psd1 file and capture the complete LSP startup error, then trace the configured server through mason.nvim, mason-lspconfig, and nvim-lspconfig. Done means the PowerShell LSP starts correctly on Windows 11 with the reported setup.