Document PowerShell prerequisites and separate runtime updates

This commit is contained in:
Dandaedre 2026-11-21 11:06:25 +01:00
parent 7d44cd9839
commit 6a7554ec5f
1 changed files with 22 additions and 0 deletions

View File

@ -24,6 +24,28 @@ when you add software to the install list, or when you need to repair setup.
Requires Windows 10 1809 or newer, Windows 11, or Windows Server 2025, with
internet access and support for WinGet.
Setup installs PowerShell using the official MSI (`--installer-type wix`), which
bundles its .NET runtime. It checks that PowerShell starts before configuring the
checkout and pins the `cc` launcher to that executable. A broken existing
installation is reported for repair rather than silently replaced. If startup
asks for .NET, keep the full error and check which executable is being launched
with `Get-Command pwsh.exe -All` in Windows PowerShell; a .NET-tool installation
or a stale PATH entry can differ from the MSI installation.
Config Central does not update PowerShell during apply or software updates,
because replacing its own runtime can interrupt the operation. Update PowerShell
separately with Config Central and PowerShell 7 sessions closed, using the original
installation method. For an MSI installation, run this from **Windows PowerShell**:
```powershell
winget upgrade --id Microsoft.PowerShell --exact --source winget --installer-type wix
```
WinGet can recognize manually installed software too. Previously the base profile
requested PowerShell upgrades, which could replace that manual installation.
The installer logs are needed to establish why a particular upgrade left it missing.
See Microsoft's [PowerShell installation and upgrade guidance](https://learn.microsoft.com/en-us/powershell/scripting/install/install-powershell-on-windows).
## 2. Update installed software
Close applications that may be updated, open PowerShell as your normal desktop