This is actually a result of Microsoft changing something in the PowerShell extension on Friday (version 2022.7.2). The only workaround at the moment is to downgrade to 2022.7.1 or earlier. We’re working on a fix and will have it out ASAP
2 Likes