Certificate and execution policy strangeness #17267
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
Set-ExecutionPolicy to Allsigned, restart PowerShell, run get-module -listavailable.
Start VSCode with may 2022 PowerShell extension,
Expected behavior
PowerShell starts, loading PS Readline. Get-Module lists available modulesActual behavior
On loading PowerShell reports untrusted signatures for Psreadline.format.xml and PSReadline.psm1 (but not .PSD1)
Get-Module reports untrusted signatures for every signed CDXML file (but not their associated PSD1), but reports no errors where files are unsigned.
Loading VSCode the PowerShell Integrated console reports untrusted signatures for the PS1, types.ps1.xml and .PSM1 files for PowerShell editor services (but not their PSD1 nor files in PSReadline).Error details
No errorEnvironment data
�[32;1mName Value�[0m
�[32;1m---- -----�[0m
PSVersion 7.2.3
PSEdition Core
GitCommitId 7.2.3
OS Microsoft Windows 10.0.19042
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0Visuals
No response